.DSM & .RGU files - wasted space

[ADB100]

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 :confused:

Andy

[faria]

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

[ADB100]

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

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 :rolleyes:

Thanks

Andy

[funman]

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 :confused:

Andy

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

[ADB100]

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

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 :confused:

Andy

[edhaas]

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 :confused:

Andy

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,

[peter petrelli]

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

[ADB100]

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

What about the RGU files as these are just Unicode text files with registry entries in them?

Andy

[funman]

What about the RGU files as these are just Unicode text files with registry entries in them?

Andy


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!

[ADB100]

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!

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

[funman]

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

So what did you delete? As i have about 4-5 Mb to play with!!!

[anichillus]

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.

[ADB100]

So what did you delete? As i have about 4-5 Mb to play with!!!

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

[funman]

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

Ya you have to much in the rom!!! It will crash each and everytime you try to put to much in!

[ADB100]

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.

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

[ADB100]

Ya you have to much in the rom!!! It will crash each and everytime you try to put to much in!

Yes Iv'e guessed that, hence this thread....... I want to recover some space and I am asking for ideas :rolleyes:

What is the absolute limit for the created .nb file? It isn't like I want masses of space, I think about 2Mb.......

Andy

[anichillus]

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

[edhaas]

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

[mfrazzz]

Remove the autoupdate. I doubt that functionality will be useful for any custom roms anyway, and certainly does nothing now.
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).

[ADB100]

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).

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..... :confused:

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

[mfrazzz]

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..... :confused:

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....

Yep, you have just too much. I'm not sure what the magic number is, but its around 58MB. I had similar last night where one built, but it was just too big so at 99% the RUU just disappears and leaves the phone thinking its still flashing. I pulled out the PDF reader and then it flashed fine. So its definetly a size issue. On the Wizard you have a finite amount of space, so you can't put everything into the rom. You will have to remove some stuff (but be careful removing system stuff).

Personally Voice Command is another one that can be left out (and gives you back around 1meg of space). Not everyone likes VC (I personally love it), and there are different versions for different languages. So I took it out and did like anichillus and just provide links to the CABs for those that want it. Same can be done with other things.

Good luck

[edhaas]

If you haven't actually tried flashing it, you might give it a go. I seem to remember successfully flashing at around the size you're reporting. The worst that will happen is as mfrazzz reports above, and you'll have to reflash with a smaller package from bootloader.

BTW, I am putting out an update to the rompacker kitchen which incorporates your idea of deleting the .rgu's. I'll let people try both ways and we'll see what the feedback is!

Regards,

[edhaas]

Oops, I didn't get that you'd already tried it. Sorry about that.