Vogue 20270 GPS kitchen

[colonel]

Oops, its in the shareware OEM.rar I believe. Make sure that one is updated.

[gammarho55]

Originally Posted by gguruusa

It usually means you are running antivirus software that is breaking the .rar extraction of the OEM packages. The first thing to try is disabling your antivirus software and trying agian. The alternative is to learn how to unpack the .rar files so that step is not part of the build process.

i posted this a few days back, please let me know what i need to do next...well, i uninstalled the crap antivirus program i have and i still get the same error. so unpacking the rar's is the next step? how do i do this? just unzip all the files to the same folder? thanks for all your time, i really appreciate it.

[aspalaasn]

Originally Posted by ludester

i notice the same thing I have bell selected. I usually don't select a carrier but on this cook I did and now I can't remove programs I install.

weird

how did you not select a carrier. I thought you had to select one to build. do you happen to know if it makes a big difference if we picked bell or some other carrier, or even no carrier (if possible)? Like I said before, I noticed that the remove programs was working when I accidentally picked ISUACell Carrier and it seems to me that I was still able to connect to the bell networks, didn't try giving myself a call but I see the Bell Mobility Name on my phone so I assume it'd work.

I wonder if there's other things that doesnt work if Bell Mobility is selected. Anyone else found anything that doesnt work?

[cismo]

I'm still trying to find documentation or whatsoever that explains what I can do with this.

I want to build my own image, how can this tool help me?

How do you guys know?

Thank You

[sean222]

Has anyone tried those little apps to hide the bottom softkey bar? It stays hidden until an app opens up, then it's not hidden anymore...Is this a problem in the ROM? any hints on how I can fix/troubleshoot this? Thanks

[Kreigz]

Colonial,

I have a 000_Shareware.rar and it seems to be updated as well. I've tried it with various versions and on two machines for building ... my laptop which is XP Pro and have been using for quite some time, and my desktop machine, Vista 64 which has only been used to build ROMs since last week.

Can't get the animated 3 splash screen to appear.

Originally Posted by colonel

Oops, its in the shareware OEM.rar I believe. Make sure that one is updated.

[xcopmanx]

Originally Posted by Kreigz

Colonial,

I have a 000_Shareware.rar and it seems to be updated as well. I've tried it with various versions and on two machines for building ... my laptop which is XP Pro and have been using for quite some time, and my desktop machine, Vista 64 which has only been used to build ROMs since last week.

Can't get the animated 3 splash screen to appear.

kreigz, did you select the startup animation selection in BuildOS?

[Kreigz]

Sure did ... "240x320:1:WMStartup_ani.gif".

This is really puzzling ... it always worked till I updated to 20270.

Originally Posted by xcopmanx

kreigz, did you select the startup animation selection in BuildOS?

[asenduk]

colonel or guru,

i keep getting the following message when trying to make initial selections:

Scanning module: USER_OEM\Holux GPS Viewer 1.5 Build 1210
No .DSM file: USER_OEM\Holux GPS Viewer 1.5 Build 1210
Scanning module: USER_OEM\MortScript
No .DSM file: USER_OEM\MortScript
Scanning module: USER_OEM\OEM_ArcsoftMMS_5_0_31_16
No .DSM file: USER_OEM\OEM_ArcsoftMMS_5_0_31_16
Scanning module: USER_OEM\OEM_GpsViewer_PPC300_2577
No .DSM file: USER_OEM\OEM_GpsViewer_PPC300_2577
Scanning module: USER_OEM\Personalizer_3.0_OEM
No .DSM file: USER_OEM\Personalizer_3.0_OEM
Scanning module: USER_OEM\Rapheal_TaskManager_2_1_34309_1
No .DSM file: USER_OEM\Rapheal_TaskManager_2_1_34309_1
Scanning module: USER_OEM\vOEM_Rapheal_TaskManager_2_1_34309_1
No .DSM file: USER_OEM\vOEM_Rapheal_TaskManager_2_1_34309_1

i removed all OEM's in the USER_OEM folder. i also unistalled BuildOS and then re-installed it but still getting the same error message

any suggestions?

[leoiden]

is not this the latest build for hermes so are not we going backwards here with these build
newer build ported would be from a newer device not an old one?