Database Info

WM6 Windows Update - files & settings required?

Now I know Windows Update on WM6 doesn't work for the Wizard - It connects to the m$ update site but doesn't find any updates. I tested this previously with the MB ROM and used a sniffer to see what was going on and it does indeed connect to the windows update site using HTTP.
In Faria's WM6 ROM he has removed Windows Update by physically removing some files from the ROM and deleting some registry settings as well as commenting out a line in the 'initflashfiles.dat' file. I have attempted to re-add Windows Update to his ROM with some sucess, however I am not quite there yet....
I have restored 'autoupdate.exe' and 'AutoUpdateRes_wpc.exe.0409.mui' as well as a registry setting [HKLM\System\Autoupdate] and it's settings and uncommented the line in the 'initflashfiles.dat' file to add the shortcut back. Now Windows Update is available and when I open it it opens OK but fails to connect when I select update now. It then sort of hangs and can only be closed using Task Manager or similar.
Are there any other files or settings that need restoring to get this back. I understand it doesn't work but my curiosity is getting the better of me
Thanks
Andy

I thought I read (maybe here) that when someone did the update, they actually had a theme file that was available and it downloaded that.

No packets sent?
I have been playing around with the Windows Update application and it starts fine. If I select 'Check Now' it immediately comes back with the Error screen telling me 'connection to update server was not available....'. If I click OK and then attempt to end the application it just stays on the screen and the only way to stop it is to use Task Manager and terminate the process
I have also put a sniffer on the port my Wireless AP connects to and cannot see the Wizard transmit anything when I click select 'Update Now' (I have verified I can access the internet with IE and I can see this OK with the sniffer).
Does anyone know what I am missing to at least get the Autoupdate.exe application to attempt to connect as it did with the MB ROM?
Thanks
Andy

Anyone
Can I bump this up as I want to get this working and re-added to my ROM (I know it doesn't actually work but I would like the functionality restored anyway).
I have restored the files:
autoupdate.lnk
autoupdate.exe
AutoUpdateRes_wpc.exe.0409.mui
Added the registry settings:
[HKEY_LOCAL_MACHINE\System\Autoupdate]
"DetectionCookie"="0"
"IntervalEndTime"=dword:f0
"IntervalStartTime"=dword:3c
"OmaDmSessionTimeout"=dword:258
"NextRunNormalInterval"=dword:93a80
"Automatic"=dword:0
"OTA"=dword:0
And restored the line to the initflashfiles.dat:
Directory("\Windows\Start Menu\Programs"):-File("Windows Update.lnk","\Windows\autoupdate.lnk")
There must be something else I am missing as it never attempts to connect and hangs when trying to exit the application. I restored the files from the MB ROM to Faria's ROM as he didn't include the originals.
Thanks
Andy

I would very cautious about re-adding windows update to a beta evaluation ROM (all our WM6 roms are!!!!).
It will do no good, only harm, I think, since Windows Update as well as a few other components in these beta WM6 are actually there only to call home and manage the beta evaluation.
My position of this is that you want to remove as much as possible all these pieces of software, essentially to avoid the call-home feature and the ROM expiration process, without breaking the ROM, of course.
So, I recomment to leave Windows Update out, SQM and other modules, ceipui, the remote provisioning mechanisms, etc. I've already talked about this in diffent threads, but I'll try to post a summary of my findings in the short future.
Regards,
--eluth.

I understand and accept the implications but I would prefer it if this was restored to my ROM.
I am just after some help as to what I am missing to restore this functionality
I have listed what files and settings I have restored but AutoUpdate is obviously missing something based on it's behaviour.
Anyone?

Anyone?
Anyone know what I am missing? Surely some of the cookers on here who have removed the Windows Update from their ROMs know what they removed?
That's all I am after; not too big a task I assume?
Andy

ADB100,
I could not tell you what is missing, but I do know that it is enabled in mUn's ROM. Because I did the same as you. Hooked it up to a sniffer and looked at the packet exchange between my Wizard and the MS update site..
Regards

Projectile said:
ADB100,
I could not tell you what is missing, but I do know that it is enabled in mUn's ROM. Because I did the same as you. Hooked it up to a sniffer and looked at the packet exchange between my Wizard and the MS update site..
Regards
Click to expand...
Click to collapse
It's enabled in the original Orwells, the MB Edition, mUn's and Faria's Vanilla WM6.
However I still can't find what I am missing to get it back in my re-heat of Faria's latest 'Real Thing'.....
Andy

you are missing SQM .
ps;
there is WM6 ROM for a windows ppc that has time bomb....plus microsoft can expire your rom by update if they want.... the update feature uses .pkg and this settings will stay after hard reset.... so they can use it for any means,and so can anyone that can compile 1 of those packages. just to let you know.

faria said:
you are missing SQM .
ps;
there is WM6 ROM for a windows ppc that has time bomb....plus microsoft can expire your rom by update if they want.... the update feature uses .pkg and this settings will stay after hard reset.... so they can use it for any means,and so can anyone that can compile 1 of those packages. just to let you know.
Click to expand...
Click to collapse
All the SQM files are present and the SQM settings in the registry are identical
What else could be missing?

Also, Which rom as the timebomb and how do we find it?

hi, anibody have this files:
autoupdate.exe' and 'AutoUpdateRes_wpc.exe.0409.mui'?
Thanks

I don't have it handy, but go find the original Ingenetics dump that was posted here (do a search) and I know it has those files in it.

Andy,
The original dump by Ingenetics was pulled a few days after he posted it. But I think this link has it. Good luck on your quest.
http://rapidshare.com/users/T4RZX2

Little Help for First Time Cooker!

Hi There,
Ive been admiring the work of many here for a very long time.
I have owned a Blue Angel for about 18 months and a wizard since January.
The wizard has been flashed around 7 times in 4 weeks lol which is quite a bit for an HTC noob like me.
I have tried Orwells Rom (very stable for me) but then decided to upgrade to .mUn.'s rom as it was a newer version.
Unfortunately it wasnt quite as vanilla as I like.
Vanilla == No reg tweaks, No apps at all and no damned Cyberon!
Everytime I try to build myself a rom (tried Molski's kit and NotTooSmart's) I get a problem.
Dump decrypted NBA with Typhoon Tools
prepare_imgfs (with nosplit)
viewimgfs
hv > rgu
Added REGEDIT4 to the top line, saved as unicode, did everything correct as far as I know.
then back to hv's (yep right size, 750kb ish)
Then put it all back together. (incl the removal of bytes form initflashfiles.dat back to the first
1st Time with Molski's Kit = Booted fine, but would never load OS after a softreset
(few more attempts with the same kinda thing - failed )
Last time with NTS's kit = Stuck on the splash the IPL/SPL and would go no further.
Sorry for my ignorance, but what have I missed!
I hear about XIP sections and what have you, means very little to me!
I just want to build myself a rom on which I can mess around with :'(
Thanks Folks,
-Whiterat

When you remove the bytes from the front of the initfileflashes.dat file, what are you removing? It should just the FF, FE. Also, make sure you have English set in your regional and language options under the advanced tab.
If that fails, you may have a corrupt nk.nbf, since you've had BOTH kitchens fail. I would download a new ROM copy, dump and immediately rebuild and flash just to make sure you are properly going through that process. Then make one change at a time. It's time consuming I know, but you'll be wiser for the experience.
Peace,
JB

jwzg:
Thanks for taking the time to reply.
initflashfiles.dat should start with a ; (Since ; is used to remark lines) so I just remove back to that.
With regards to setting English, where abouts is the advanced tab? In what program even?
I did as you said with the nk.nbf and it goes on just fine without editting a thing
Its a pain testing these things, since I usually end up having to restore from SD which rewrites the extended rom, gsm, os, spash screen, htc screen,etc and then it takes ages for me to reflash my bits!
I can upload my rom if someone is willing to take a peek, see if I have missed something really obvious?

Too many files?
I had a similar issue (I think?) where everything seemed to work and the nk.nbf file was created OK. However there would be an error logged in the Windows Event Log about faulting an application. The resulting ROM image would install but I got a white screen following the reset (it made noises like it was working though). I followed the instructions for Molskis cooking tools to the letter and couldn't understand what the issue was I posted on here for some assistance but after I got no helpful replies I played around a bit more and realised the dump folder was slightly over 128MB (Size said less but I think it was over?). Anyway I removed some more files I didn't need and low and behold it all worked
I don't know what the absolute maximum size the dump folder can be, but I keep mine below 128,000,000 bytes....
HTH
Andy

ADB100 said:
...but I keep mine below 128,000,000 bytes....
HTH
Andy
Click to expand...
Click to collapse
Size on disk?

Whiterat said:
jwzg:
Thanks for taking the time to reply.
initflashfiles.dat should start with a ; (Since ; is used to remark lines) so I just remove back to that.
With regards to setting English, where abouts is the advanced tab? In what program even?
I did as you said with the nk.nbf and it goes on just fine without editting a thing
Its a pain testing these things, since I usually end up having to restore from SD which rewrites the extended rom, gsm, os, spash screen, htc screen,etc and then it takes ages for me to reflash my bits!
I can upload my rom if someone is willing to take a peek, see if I have missed something really obvious?
Click to expand...
Click to collapse
Not talking about that...
You have to open up initfileflashes.dat with a hex editor and remove the first two bytes (FF, FE). Then you can put the file back into the dump folder and build it.

jwzg said:
Size on disk?
Click to expand...
Click to collapse
The dump folder of the last one I cooked said:
Size: 121 MB (127,089,811 bytes)
Size on disk 131 MB (137,654,272 bytes)
And this worked fine, it was a re-heat of Faria's Real Thing ROM where I re-added VoIP & Windows Update (VoIP works but Windows Update won't and I can't figure out why - the application fails to connect to the MS site and won't close, but that's another story.......).
Andy

Yep I get that, I am a reverse engineer by trade so naturally I get what the manual had to say.
The limitation of imgfs is IF there are more than 1500 files being added to nk.nbf, the file size limitation also applies.
I am not adding any files to the dump, simply removing the cyberon stuff (and removing the microsoft callbacks, and sqm stuff)
Tried buling without removing sqm stuff and same thing.
I guess its just not going to be my thing

Here's what to do.
Delete the current 84000000-os.nb file in the ROMDUMP folder, then remake it. That should solve your problem. I forgot that I had the same problem.

Ahh I will give that a go
I was hoping to pick up a half broken wizard from ebay (broken digitiser/blocked/missing case/etc) and just use it as a tester, since I get alot of people whining when I am uncontactable for 90 mins
(About the right time to fiddle, flash and reinstall stuff)

.DSM & .RGU files - wasted space

I might have missed something here but I want to recover some space in my ROM as there isn't enough room to get all the OEM applications I would like into my build (and it's not a lot of applications believe me, however the latest mUn 5.2.1413 build has very little to spare). I thought I understood the .RGU & .DSM files in that they are used to create the registry .hv files (system.hv and user.hv), however they are still present in the ROM when it is built and it seems to me like they are wasting space? The .DSM files total about 800Kb and the .RGU files over 2Mb.
Are all these files needed or can the ROM be created without them? I realise the registry needs to be created but it seems like these files are redundant once the ROM is built
Andy

better leave them alone if you want your rom to even boot . some can be deleted but this is specific to every rom.

faria said:
better leave them alone if you want your rom to even boot . some can be deleted but this is specific to every rom.
Click to expand...
Click to collapse
Care to elaborate as to what can be done to 'compress' them then?
I want to recover about 2Mb of space? I thought the default system.hv & user.hv files were created from these .DSM & .RGU files and therefore they aren't actually needed in the ROM?
Is there any way to build the ROM with the kitchen tools but once the system.hv and user.hv files are created these redundant files aren't included in the ROM build?
I might be missing something obvious here, if I am please enlighten me
Thanks
Andy

ADB100 said:
I might have missed something here but I want to recover some space in my ROM as there isn't enough room to get all the OEM applications I would like into my build (and it's not a lot of applications believe me, however the latest mUn 5.2.1413 build has very little to spare). I thought I understood the .RGU & .DSM files in that they are used to create the registry .hv files (system.hv and user.hv), however they are still present in the ROM when it is built and it seems to me like they are wasting space? The .DSM files total about 800Kb and the .RGU files over 2Mb.
Are all these files needed or can the ROM be created without them? I realise the registry needs to be created but it seems like these files are redundant once the ROM is built
Andy
Click to expand...
Click to collapse
Well you can take 20 RGU adding up to 2MB or 1 file with 2MB its the same!!! The same information has to go in the the ROM

funman said:
Well you can take 20 RGU adding up to 2MB or 1 file with 2MB its the same!!! The same information has to go in the the ROM
Click to expand...
Click to collapse
Yes, I had sort of realised that, however there would still be a (small) saving if it was one file as opposed to 20.
What I was trying to get at was are these files needed since the system.hv and user.hv files are already there in the ROM? I used the Molski tools previously to build some ROMs and the 'rgucom.exe' tool built the system.hv and user.hv from the system.rgu & user.rgu files, however these were a lot smaller.
If I am missing something here, please enlighten me
Andy

ADB100 said:
Yes, I had sort of realised that, however there would still be a (small) saving if it was one file as opposed to 20.
What I was trying to get at was are these files needed since the system.hv and user.hv files are already there in the ROM? I used the Molski tools previously to build some ROMs and the 'rgucom.exe' tool built the system.hv and user.hv from the system.rgu & user.rgu files, however these were a lot smaller.
If I am missing something here, please enlighten me
Andy
Click to expand...
Click to collapse
It seems like a neat idea. Let me know if it works. If it does I'll incorporate it into the next version of my rom-packer kitchen. In the meantime you might try the rom-packer. It's been pretty consistent in giving 2+ meg or more back.
Regards,

I think you'd be well advised to leave the dsm's alone.....just speaking from my personal experience.

peter petrelli said:
I think you'd be well advised to leave the dsm's alone.....just speaking from my personal experience.
Click to expand...
Click to collapse
What about the RGU files as these are just Unicode text files with registry entries in them?
Andy

ADB100 said:
What about the RGU files as these are just Unicode text files with registry entries in them?
Andy
Click to expand...
Click to collapse
Yes but as above you should leave them alone, you mess tomuch and you phone may not boot as faria said above!!1 He knows what he is saying!

funman said:
Yes but as above you should leave them alone, you mess tomuch and you phone may not boot as faria said above!!1 He knows what he is saying!
Click to expand...
Click to collapse
So where do I find the space then............ I have a spare G3 Wizard and I know I can't brick it with just flashing the ROM (as opposed to flashing the bootloader), so I can try pretty much whatever I want to see what works.
Out of curiosity I have just tried removing the .RGU files that are in the DUMP directory after the BOS.exe (or other name, but the OS builder GUI application) has successfully ran and the ROM does get built, however it only frees up 1.5Mb, which isn't enough for what I want. I will continue analysing what I can and can't remove to get the apps in I want.
Andy

ADB100 said:
So where do I find the space then............ I have a spare G3 Wizard and I know I can't brick it with just flashing the ROM (as opposed to flashing the bootloader), so I can try pretty much whatever I want to see what works.
Out of curiosity I have just tried removing the .RGU files that are in the DUMP directory after the BOS.exe (or other name, but the OS builder GUI application) has successfully ran and it does indeed work, however it only frees up 1.5Mb, which isn't enough for what I want. I will continue analysing what I can and can't remove to get the apps in I want.
Andy
Click to expand...
Click to collapse
So what did you delete? As i have about 4-5 Mb to play with!!!

You could have 2-3 times more.
What's the size of the empty .nb
The one without extra applications preinstalled ? Of course using the mUn's latest.

funman said:
So what did you delete? As i have about 4-5 Mb to play with!!!
Click to expand...
Click to collapse
I am attempting to add the following applications into the ROM:
System:
Enterprise
Entertainment
WindowsLive
Office
AutoUpdate
Voice Command
VoIP
MediaOS
FWUPDATE
OEM/Other Stuff:
Adobe Reader LE 2.0
Bluetooth Explorer
Bluetooth SAP Profiles
HTC Wizard Camera
Arcsoft MMS
DotFred Task Manager
Total Commander
HTC X-Button 1.5
Battery Status
MS Live Search
MS Pocket Streets 2006
VoIP SIP Config tool
Plus a compilation of registry settings, however when I run the batch file to create the ROM it always fails towards the end. It gets to somewhere like 'wmv9decoder.dll' and then stops and a Windows dialogue box appears about an 'exception has occurred'. The batch file carries on but the ROM that is created is corrupt.
Andy

ADB100 said:
I am attempting to add the following applications into the ROM:
System:
Enterprise
Entertainment
WindowsLive
Office
AutoUpdate
Voice Command
VoIP
MediaOS
FWUPDATE
OEM/Other Stuff:
Adobe Reader LE 2.0
Bluetooth Explorer
Bluetooth SAP Profiles
HTC Wizard Camera
Arcsoft MMS
DotFred Task Manager
Total Commander
HTC X-Button 1.5
Battery Status
MS Live Search
MS Pocket Streets 2006
VoIP SIP Config tool
Plus a compilation of registry settings, however when I run the batch file to create the ROM it always fails towards the end. It gets to somewhere like 'wmv9decoder.dll' and then stops and a Windows dialogue box appears about an 'exception has occurred'. The batch file carries on but the ROM that is created is corrupt.
Andy
Click to expand...
Click to collapse
Ya you have to much in the rom!!! It will crash each and everytime you try to put to much in!

anichillus said:
You could have 2-3 times more.
What's the size of the empty .nb
The one without extra applications preinstalled ? Of course using the mUn's latest.
Click to expand...
Click to collapse
The 8004000.nb file in the 'ROM' directory is 42,688KB. The os-new.nb file that gets creates is 59,072KB. If I build the ROM without Adobe Reader LE 2.0 it is 57,792KB and it works so I guest it's over the size limit.
Andy

funman said:
Ya you have to much in the rom!!! It will crash each and everytime you try to put to much in!
Click to expand...
Click to collapse
Yes Iv'e guessed that, hence this thread....... I want to recover some space and I am asking for ideas
What is the absolute limit for the created .nb file? It isn't like I want masses of space, I think about 2Mb.......
Andy

Wait a few days so i will test and release my kitchen and i promiss you'll have your problem fixed

Remove the autoupdate. I doubt that functionality will be useful for any custom roms anyway, and certainly does nothing now.

edhaas said:
Remove the autoupdate. I doubt that functionality will be useful for any custom roms anyway, and certainly does nothing now.
Click to expand...
Click to collapse
Definetly get rid of this one. Also if you use the rompacker kitchen the edhaas ported from Bepe's, then you may get more space (I'm reworking Crossbow Reloaded right now, and I'm able to add a lot more to my rom with this excellent set of tools). If you use the rompacker kitchen, AutoUpdate is completely useless (if it was to ever work).

mfrazzz said:
Definetly get rid of this one. Also if you use the rompacker kitchen the edhaas ported from Bepe's, then you may get more space (I'm reworking Crossbow Reloaded right now, and I'm able to add a lot more to my rom with this excellent set of tools). If you use the rompacker kitchen, AutoUpdate is completely useless (if it was to ever work).
Click to expand...
Click to collapse
If I remove AutoUpdate the os-new.nb still ends up 59,072KB..... I will try and physically remove the two folders in the \SYS folder and edit the option.xml file.....
Nope, even if I physically remove the two AutoUpdate folders and remove them from the option.xml the os-new.nb that is created is 59,072KB. The tools I am using 'Wizard ROM-Packer Kitchen' doesn't crash like the other tools, however the ROM Update application just closes at 98% and leaves the Wizard in limbo....
Andy

Post install script

Is there instructions on creating a post-flash (or hard reset) install script? I'd like to have it run the cingular WAP cab, and maybe a couple others. I think I've been all over, but haven't seen anything...
Thanks!

Also - does anyone have a package or cab for camera 3.3???

Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.

JoelC said:
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
Click to expand...
Click to collapse
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!

mattk_r said:
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
Click to expand...
Click to collapse
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"

notyourdaddy said:
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
Click to expand...
Click to collapse
I just found this link that has an extended rom in it. It makes a lot of sense, especially the txt file that directs the installation and then initiates a reset. Getting warmer!
http://forum.xda-developers.com/showthread.php?t=309922

So here's what I'm thinking - just initial thoughts:
Have a folder with the base applications that are used every time like AutoRun.exe.
The user places the cab(s) in the "add files to ext rom" folder.
They run an exe that reads the directory file contents, verifies file type, copies the files to the extended rom folder, and displays the list. I'd write it in VB, since I'm most comfortable with file system operations in that language...
They change the list based on the order they want them installed using up and down arrows to sort priority.
The click OK, and it creates the config.txt file, including all necessary commands such as reset and whatnot.
That way when they build, it's all good to go.
Any thoughts?

Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy

Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best

JoelC said:
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
Click to expand...
Click to collapse
That's really good info, because I'm climbing the learning curve as fast as I can here to get a good grasp on what the extended rom is, as well as how to use it. I appreciate the conditional warnings... better to know ahead of time than find out following a problem.
I'd rather use the true extended rom (as I understand it anyway), so I don't loose any additional space for the BuildOS programs. That is, assuming the extended rom is a seperate memory location than the base...
In another thread, someone is going to post that tool. I'm really interested in how it works.
If I can get all the concepts together, I hope to get a solid tool that will improve functionality in the ROM, without adding complexity or trouble... and I greatly appreciate the help!

Interesting thread...guys, you just gave me some new ideas.
Before that...there's one thing that's bothering me...
Can we use ExtendedRom on a G4 or not...lol I thought not, until me an Boto made a clean one from a G4 ExtRom and when Boto flashed it it worked , and he has a G4. Why we always say that we don't use an Extended Rom for G4 users ?
Normaly, a G4 should/would brick when flashing IPL/SPL not Extended Rom, am I right ?
We are shrinking the OS space to integrate features of the ExtendedRom in order to all people use it but is it that true ?
Ok, now back to my idea .. I want that in my next rom to include an extended rom, of course and make it that way so when you first start your PDA, it will act like when installing windows on the PC , asking you which apps or what options you want to use. I think i can manage to do that...still the question remains ...will G4 users be able to use it ?

Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!

JoelC said:
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
Click to expand...
Click to collapse
I took the Ext Rom from the Wizard Love Rom and i edited the config.txt and deleted cabs ...that's it

Well, if it flashed OK... sounds like it might be usable after all But tell me, is Boto's G4 CID locked or unlocked? It's all very uncertain, but some of the G4 posts lead me to believe this may make a difference

ADB100 said:
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Click to expand...
Click to collapse
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.

wizzzard said:
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
Click to expand...
Click to collapse
Thanks for that but it isn't what I was really after.... I am just trying to automate everything. I have flashed my ROM that many times recently and going through the install of TomTom each time is a bit of a pain. I have got a couple of .CABs in the Extended ROM OK and these work fine, I just thought it would be nice if I could get TomTom in there as well.
Andy

I didn't want this to turn into a "how-to" thread, but I'm still scratching for hard info on the extended rom, and as many questions out there, it might be a good one to clarify some details...
As I understand it now, there's two forms of "extended ROM":
1. The true extended rom "similar to the radio ROM"
There is some "trigger" that runs the contents of the extended rom, such as AutoRun.exe?
2. The 'psuedo' extended rom that is basically a post install script to run cabs.
The contents of the folder under windows are run from a trigger that resides in the startup folder - similar to a runonce in Windows on first boot?
Does this sound close?
Also, where does the 'true' extended rom reside? Does it use the portion of memory reserved for the OS, or is there another portion just for it? (so if by adding applications to the extended rom, your available storage memory will remain unchanged - less the installed application?)
I'm presuming then by the 'psuedo' extended rom, that it does consume ROM space, but simplifies post-flash cab installations - assuming you follow the rules...
From what I see, by using the 'psuedo' ER, you waste space by keeping the installation files in addition to the installed application files.
If I'm wasting space and time by asking these questions and you know of a good extended rom tutorial, please direct me to it. I have spend some time tonight searching, but a definitive guide still eludes me... Thanks!

Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).

mfrazzz said:
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
Click to expand...
Click to collapse
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.

mattk_r said:
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
Click to expand...
Click to collapse
Yeah, never figured out why that one was never made a sticky. I just know to go look at Faria's sig and it (and a few other good links) are in there

v2.0 Integrating Touch Files into 318 Kitchen [kitchen updated 7/9/07 @ 21:37 PST]

I need some help debugging the kitchen with the touchflo files.
For those who are sent the new kitchen; as you test and find solutions, please post what you did.
I wanted a sperate thread for just these specific objecives.
Here is the objectives:
To retain the ability to build a ROM with or without TouchFlo
To have only ONE seperate camera package that will work in any configuration
To allow portions of the touch software to work seperately should TouchFlo not be installed
I know there are other threads dedicated to debugging the touch software, however this is targeted at just the kitchen integration.
Current issues (v2):
Streaming Media isn't showing up in Programs, won't open.
Speed Dial hasn't been confirmed working or not.
No images for Beam - still need pictures!!!
Windows Live won't connect. Cab fixes issue. Need to find missing entries
Black Keyboard doesn't show numbers across top row. Need to find setting.
The power button will put phone into "standby" mode (basically screen and Wifi off), but won't power down.

318
I'll be glad to test. I was working on a 318 Kitchen but didn't get very far.

Too many Duplicate files.
Going back to work on my own kitchen I was much further along than what you have here.
My suggestions:
1) You should at start by deleting duplicate files. I can build a rom and flash it with my kitchen, I can't build with yours w/o getting one dup file error after another.
Please update, I will try to devote some time to your kitchen.
Thanks

NP. I'll update shortly.

My Files
I deleted dup files in my kitchen but I think I deleted one to many, now I can build, and I can flash using shelltool but it gets stuck at splash screen. Damm where did I go wrong??? I feel like a dumbass!

Hopefully this one will work a bit better. another 30 mintues till it's up.
The boot issue is probably related to the files in the OEMAPPS folder. There are some dll's in there that I found are super sensitive to this build - too bad I wasn't more careful in documenting what they were.

Documenting.
Started documenting now! Too much going on now not to, especially after my last mistake.

Test
So have you actualy built and started testing a rom with your kitchen?

I've been doing that for days... but I've tried a number of different combinations and this one seems most promising - though by no means is it ready. 1413 has by far been the easiest, but I still believe the 318 is the best choice.
I'm gonna be out until Monday night, so this is my last attempt for a few days

I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.

Whiterat said:
I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.
Click to expand...
Click to collapse
If you could, it would be much appreciated. Anything to help get closer to a fully functioning setup

Ok, so i tested the oem folder from the reTouched Beta thing. I included everything in there but my problem is that TouchFLO does not function the way it is supposed to. With what you guys are doing, have you verified that TouchFLO even operates correctly?

I thnk the touch flo isn't all its cracked up to be..I ran the reTouch wasn't a fan..its not as fast as any rom..only thing I like is the dialer and the cube

I actually have a good feeling about it. I ran the french rom for a couple days - and other than not knowing most of what it said (glad I know the OS and took 2 years of french in high school) I was very pleased with the performance. Specifically the speed at which the screen "rotated", responsiveness, and how quickly the contacts scrolled on the screen was impressive. Enough to keep me interested well into the night

so matt, think you can make a cab from it? the cube that is lol.

Here you go:
http://rapidshare.com/files/40068930/OEM.rar
Click to expand...
Click to collapse
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)

Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
So if what you are saying is true I should be able to create cabs from the correct?

AFAIK It wont be possible due to the touch driver not being replacable, you might be able to rename touch.dll and then update the registry entry.

cleaning up
Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!

hanzieman said:
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
Click to expand...
Click to collapse
For what I see whiterat folder are some reg tweaks that you'll probably use anyways, and as far as folders to remove it might be less of a hassle to simply add the packages that you use that are not there.