Related
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
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
There are a lot of great things on this web site, but not much for the real newbie. This submission is to help newbies get up to speed. The concepts and some details here can help almost any newbie with any PDA.
I’ve worked with computers for 30 years since they were driven by “audio cassette” tapes. BUT I’m a PDA newbie! When I got my PDA, a Cingular 8525 (HTC Hermes), I compared it to my last cell phone and was amazed that it had a color screen. I had no clue how I was supposed to get it to do what I wanted it to do. Since I‘m retired, I spent long hours on many days researching, finding free software, and learning and doing things to make it what I wanted. These are the results. I’m not going to go into all the research, just give you the findings and actions. Read your manual or download one from the Internet to learn the very basics of your phone. Try every possible button, menu and program to see what they do. Don‘t be afraid to crash your PDA at this point so long as you know how to do a Hard Reset (HR). I’m not going to give keystrokes on how to find the following data. Just don’t transfer important information to the PDA until later.
First, decide what you need to do versus what you would like it to do. Here’s what I wanted. I travel a lot and wanted a mini computer I could do MS Office work on, access the Internet to take care of business, call home on, find my way in strange locations, and enjoy a little. IOW, do what my desktop does except I wanted to carry it in my pocket.
One thing that will happen while you are doing all the following is that many of the PDA programs will show up as installations in your “Add/Remove Program” program in your Control Panel on your desktop. Since this includes entries going into your registry, it can lead to different problems. I use Norton Ghost back up to totally back up my system drive, let things happen as they will, then restore it back to normal when I’m all done. Then I install only ActiveSync, MyMobiler and Remote Keyboard plus a few others than I want to sync with when I connect occasionally. You should strongly consider doing this yourself.
First, I found out what I had - A full install of WM6 with several programs I really didn’t want and a real problem when I began loading program I wanted - not enough memory. The device says I have 64 Mb of RAM and 128 Mb of Flash memory (this is the “hard disk” storage available). When I looked at memory allocation it said:
Storage Program
Total 44.77 48.77
In Use 10.96 23.55
Free 33.81 25.20
This means out of the 128 Mb of storage 44.77 + 48.77 = 93.54 Mb were available and being used. Where’s the rest? Being taken up by the Extended ROM which holds the installation and system programs you are safer NOT playing with unless you know how to - like RegEdit, Task Manager (not Task), etc. These are system “hidden” files you can play with and really screw up your PDA. With “AdvancedConfiguration” you can set Extended ROM to be read and used. Also, almost ½ of the total available area set aside for Program installation on the hard disk was already used. I tried and found I could NOT delete or move any of the originally loaded files in “Windows” folder. We’re stuck with the bloat.
I haven’t found out for sure but (someone correct me here, please) the Storage seems to be used for a dedicated operating Page File or programs loaded into active operating memory type of work based on how many running programs you have running right now and the Program refers to the actual Flash (hard disk) space set aside for installations. Think of your desktop as having only a 50 Mb hard disk and having to have the operating system, Page File and programs plus storage on it. Doesn’t leave much.
A neat little trick I learned is that when you do a HR and are reinstalling the OS it pauses for 3 seconds with an explanation screen at one point before going on to install other proprietary programs (some of which were junk to me). If you want to know what was different, back up all your personal data and do a HR and let it run fully. Check all the Settings and Programs screens to write down what you have. Do it again but push the Soft Reset (SR) pin in the hole when it gets to that 3 second pause and let it reboot. It will stop the extended installation. When you do this you will find the numbers are now:
Storage Program
Total 44.77 48.77
In Use 5.77 22.85
Free 39.00 25.92
IOW, you cut your Page File use (running programs loaded into memory) by ½ but you didn’t really change what was taking up your Flash memory. That’s because during the install every program is loaded into the “Windows” directory and then installed or not. If not installed, they just sit there and can’t be deleted or moved.
In order to change this memory bloat I had to find a different way. The only way I could find was to “cook” my phone and hope it didn’t turn into a “brick” to throw away or send back to the factory for a fix. I began looking at what was available. Keep in mind that I had written down ALL the programs installed by WM6 full and WM6 Lite (fast SR at 3 second screen). I had decided what I would like to have and what I didn’t need or want. This is important to do before this next step.
I am very experienced at installing lots of OSs over the years from CP/M (really, really old), DOS, Windows XT up to Windows XP (very different from XT) and tweaking the hell out of them. Doing it on the PDA had me a little concerned because it’s so tiny and different (so what, right?). I learned that it really is about the same as my desktop in setup and running. The first time I did it, I was worried and then surprised at how easy and straight forward it was. If you are concerned about this step and have this particular PDA, go to http://www.america.htc.com/support/8525/software-downloads.html , download the most current OS and do an install from your desktop to PDA with it. If your phone bricks send it to the factory, it’s their system. Once you’ve done it, it’s much less worrying. If you have a different phone do a little Google research and/or read more on this forum for your particular phone.
I researched different ROM cooks to see what they had compared to what I wanted. I came up with Shamanix and K-Flex as most likely for me. Their installs went just as easily and safely as the WM6 did. Don’t look at just the pretty colors, look at what programs they have and how they function doing what you want. Do some “WM6 FREE SOFTWARE” Google searches to find out what is available out there and what you can get it to do. Here are the test results with both Full install and Lite install:
Shamanix K-Flex
Full Lite Full Lite
Total 66.18 50.77 66.18 50.77 66.80 44.77 66.80 44.77
In Use 2.66 21.00 2.63 18.77 9.11 28.52 2.78 23.19
Free 63.52 29.77 63.55 31.99 57.69 20.25 64.01 25.70
FIRST - Now 66.18 + 50.77 = 110.95 for Shamanix and 66.80 + 44.77 = 111.57 for K-Flex versus only 93.54 Mb for WM6. Suddenly the OS installation files squeezed out an extra 18 Mb of Flash storage for other things. That’s a LOT when many programs average as little as 200 Kb (fit 90 in that free space). Next, K-Flex used almost as much Flash (hard disk) storage as WM6 but Shamanix only used 18.77 in the Lite install which freed up almost 6 Mb for more programs.
Sounds good, right? Remember, check what each OS provides, how you like the looks and what you want on you PDA. Since camera, media and online gaming usage are not important to me, Shamanix Lite is best for me. It still requires a few additional installs to replace what it doesn’t provide but that’s better than the bloat.
(PLEASE CONTINUE ON NEXT REPLY)
2nd half of first post
(Continued from beginning of thread)
Next, I bought a 2 Gb microSD card. That’s great for storage, but I want to install programs to that location, especially the ones I don’t use very often and can run slow safely (cards are much slower than RAM). Save the Flash storage for anything that needs processing speed like music, video, gaming, etc. Once you have a card installed, every time you want to install a program, it asks where to install. If you have access to ER enabled you can select from Device, Extended ROM or Storage Card. Use Storage Card as 1st, and Device 2nd. I tweak installation folders on my desktop but on the PDA you can’t. If it’s going to the Storage Card it will create the proper folder automatically like most Windows installations do in Program Files. Also, if you already have it loaded, it will tell you it must uninstall the prior one before it can install the new one. Actually, they’ve made PDA pretty idiot proof which is a good thing.
Before I go any further, here are two almost mandatory FREE programs you MUST HAVE!!!! MyMobiler and Remote Keyboard can be found many places. Both will allow you to connect your PDA to your desktop with a USB cable and set your PDA aside while you do everything on your desktop. It gives you a copy of the PDA screen on your monitor you can zoom plus use the normal mouse and keyboard on so long as the mouse is hovering over the PDA screen. Sooooo muchchch eeesieeer!!!!!!! In fact, it should be your first two installs before anything else!
Here’s a helpful hit on installing programs. Many times an installation program will come as a .exe file you run from your desktop. What it usually does is extract and create a folder that will hold a couple of files ending in .CAB. Then it will copy the appropriate .CAB to your mobile device. Then it will run the .CAB for installation. The .CAB is the important part. All the rest essentially sets up your desktop to run the .CAB on your PDA. Many times the installation program will be a .ZIP, .RAR, or other compressed file or even a .CAB file. If it’s a compressed file, uncompress it and look for the .CAB. When looking at .CAB files you will often find several with identical names except for the few letters just before the “.CAB”. These are the same but designed for different types of operating systems. I’m sorry I can’t rediscover the link for the details (maybe someone reading this will give us the link later) but I did learn that those with .ARM, .ARM4, Xscale, or rarely PXA, OMAP, or Samsung S3C24xx are for the newer PDAs running WM5 or WM6. Every PPC2000-2003 and every smartphone on the market (at least that I know of) is an ARM device. The others are for older system. If in doubt, try to run each one. The ones that are incorrect will NOT install. Only the one that IS correct will. From then on you will know which type to copy to your PDA. Once copied to a named folder (I use “Install CABs”) on the Storage Card, they can be simply clicked on at any time and installed. To regain memory or stop using it, use “Remove Programs” in Settings/System to get rid of them. You can reinstall anytime later.
One thing I did was move almost all of the CAB files for the programs I wanted to a designated folder on the Storage Card. One suggestion from others is to rename each CAB with a “#-“ in front of the name with the number corresponding to importance of that CAB to you. That way, when you do a reinstall, or HR, out in the field, your CABs are with you and you can see which ones should be loaded first. This works well if there is some conflict with installs one after another. Personally, I haven’t run into that so I rename them to a shorter name that identifies what it is (e.g. in35prtv33.24.arm4.cab becomes PocketPool.cab). The next thing I do is use the settings or preferences in each program to make a folder on the Storage Card the default folder - like My Documents, Favorites, Downloads, etc. Now they won’t be lost if I have to HR the PDA.
Along with the information in the above paragraphs, I do something else because I’m gone when I’m most using my PDA. On the Storage Card (a copy on each card I have) is the installed programs in the normal “Program” folder which are my operating files and a copy of the “Install CABs” folder which also includes a backup of my Contacts. One additional item is a “Serials” folder in the “Install CABs” folder. This has a .txt file of all the registration codes I need plus copies of all the altered (cracked) files I need if I have to reinstall anything on the road. So long as I can Hard Reset my phone, I can reinstall everything back to normal and continue as I need. Since I have several Storage Cards this is on each card. The balance of the Storage cards will have different eBooks, music, DVDs, etc. that don’t all fit on one card. That way, I have several backups of critical files plus entertainment as needed. I use a small dot of different colored paint on the bottom edge of each card so I can tell which card is in the phone at any time.
With all the above, if my PDA freezes or stops working properly, the universal fix-it is to do a Hard Reset. If that doesn’t work, I’m SOL. If it does I’m in business. All I do is a HR (Lite) and soft reset at the 3 second warning. Then I go back into my Storage Card and reinstall those programs I need to get back to where I can work.
Once you have things loaded and working properly, you can consider tweaking the system. During this process you may have found multiple editions of software you want to use like three different registry editors, five different tweak programs, etc. Go ahead and compare and see which ones you want and delete the rest. On a PDA it’s fairly easy. When everything is said and done, you can do a clean HR and only load those specific versions you want and have a fresh, clean, trim system to backup as your first installation process.
Finally, so you can see the results I came up with in this process, here’s a list of the programs I installed. All are on and working. None of them have to be cleared before I can have room to open another one. These are the final versions of similar programs such that there is minimal overlap but expanded utility when more than one is installed.
Sound Pocket Dictate
Mortgage CALC
WkTASK
Touch Caller
Tao Java
GSFinder+
Pocket Mechanic
Adobe Reader
ActiveX Flash 7
Sompy Media Player
enAlarmPPC
True Term Translator
TT Swedish-English
TT Spanish-English
TT Portugese-English
TT Italian-English
TT German-English
TT French-English
Town Compass US Travel Directory
Town Compass DataViewer
Tagalog for Travelers
SKTools
Paris Guide
Metro
mCity Tours
Google Maps
Flashlight Colors
UniSync
Spb Pocket Plus
tGetFile.dll
MIcrosoft .NET CF 2.0
Maufait Instafind
DinaSoft Tap Text
DinaSoft MemMaid
DinaSoft HandyMenu
CallFirewall
Tab Web Viewer (IE)
Dictionary Manager
Schap's Advanced Config 2.0
Yahtz
Warefare Incorporated
Vision Quest
Trivial Pursuit
Super Wild Wild Words
Space Adventure in Infinite Space
Smart Mahjongg
Dames are Trouble Game
Word Mojo
Ultimate Bowling Fighter
Mazera
Mars Need Cows
Hellfire
Bzzz
Realms
1001 Crossword Puzzle
Xplodus
Xonix
Pocket Spades
Patience
JumpyBall
Hot Death Uno
Advanced Lines
Here are my original results on memory usage.
Storage Program
Total 44.77 48.77
In Use 5.77 22.85
Free 39.00 25.92
Here are the final results
Storage Program
Total 66.18 50.77
In Use 36.55 25.77
Free 29.63 25.00
In other words, by opening and freeing the Extended ROM, Putting as much on the Storage Card as possible and applying a few tweaks for caching and folder locations, I still have almost as much of both Storage and Program Memory as I started with to run almost anything without having to remove and reinstall programs on the fly.
It’s a lot easier than you think and idiot proof in most cases. Don’t fear playing with your PDA and making it what you want. Have fun and ENJOY!
Dr. Ken Rich
Hi,
I am using in my ROM the normal process to start the customization after burning the ROM.
File \OEM\OperatorPKG\mxipupdate_zzPIED_101.provxml:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Comm" >
<parm name="AutoRunCFG" value="\windows\config_operator.txt" datatype="string" />
<parm name="AutoRun" value="\windows\AutoRun.exe" datatype="string" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
In my config_operator.txt I am installing some CABs - which works fine.
My idea was to delete all CABs after installation automatically. For that reason I have changed a *.rgu under \SYS\Shell:
from
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /delete 1"
to
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /nodelete"
In normal cases @="wceload.exe \"%1\" /delete 1" makes sure the a CAB will be deleted after installation.
If I install a CAB after customization the CAB is gone - so far so good - means the entry in the registry is fine.
Unfortunately, during the customization (which works fine) the CABs are still under \windows. It seems that the above change does not work with customization.
Question:
Does the autorun process (during the customization) after burning a ROM also using the wceload.exe to install a CAB ?
Regards
kuzco1
I was going to ask a very similar question, but I think I'll just bump yours instead
'Burn' the ROM
Yes, really like it rather than 'flash'.
If u want the cab deleted after autorun, just remove the read-only attributes & vice-versa. (if cabs in SD)
/nodelete switch wont work as it still delete the cab if the cab is not with read-only attr.
i think autorun doesnt use wceload but let the experts confirm it first. Just my guess.
So you want to delete a file from the ROM during customization (wont work) or off the MicroSD (would work), however I don't think I would include something from the SD in the customization XML I would use an auto installer first.
Thanks
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
bengalih said:
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
Click to expand...
Click to collapse
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
mbarvian said:
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
Click to expand...
Click to collapse
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
bengalih said:
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
Click to expand...
Click to collapse
wow, another good post
that is basically what I am trying to accomplish. I have my registry tweaks, files that don't get updated (Office, etc.) cooked in, but for some reason I cannot change the look of the dialer (I wanted to use poorlyduck's diamond dialer) by converting it to an OEM package with Ervius' Package Creator. Same with the comm manager skin. Therfore, I have resorted to installing these two through their default cabinet files during initial customization.
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
duttythroy said:
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
Click to expand...
Click to collapse
duttythroy said:
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
mbarvian said:
wow, another good post
....
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
Click to expand...
Click to collapse
Well dutty is by far a better cook than I... I'll stick to the scripting. I understand the basics of cooking...I just don't have the temperment for it.
However, I don't fully agree with all those points. I think his conclusions are correct, but I don't think the reasoning behind them are.
First off with space. Windows machines (be they PCs or WM devices) are basically made up of two things. File system and Registry (the registry just being a special file on the system). If I remove 2MB worth of an app from a ROM before I cook it, and then create a .CAB that contains those 2MB of files, the same amount of space is going to be taken up.
I have ripped quite a few apps to compile CABS from ROMs, and I know this to be the case.
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other point regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
bengalih said:
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other poing regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
Click to expand...
Click to collapse
can't argue with this post
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
hi,
yes you are right .. I have done the other wy. My fault in my first post. I have changed /nodelete to /delete.
But anyway, I understood that it is not possible to delete cabs during customization.
Many thanks to all
kuzco1
Scripted Angel 6.1.20923 - Nekid, Neat and Nearly everything versions
I say scripted because I have removed Autorun.exe and SDAutorun.exe to make room since these run once and never again until you hard reset.
I use MortScript to run my set up. This is very similar to Noonski's XDA_UC system. I also want to thank S.V.I for getting me hooked on his work.
I also removed as many files from the \windows folder as possible. This includes moving provxml file information to the rgu file when possible. Shortcuts that just get copied from \windows to other locations have been deleted and are created by my script. This is based on the idea that the fewer files you have in \windows folder, the faster your phone runs.
Do not worry. You can still have UC. My setup MortScript parses the SDConfig.txt as if it were SDAutorun.exe with some exceptions.
It does not do LOCK, HIDE, SHOW, or RESET. I have covered CPY1/CPY2, CAB, XML, TSK, and EXEC.
Since it does not support LOCK and HIDE settings you need to move the cabs you want to allow user input to the folder \Storage Card\SDAUTO\Manual.
Remove them from your SDConfig.txt file. Also, if you have registry files you use to change settings after these "manual" cab install, just place them in the Manual folder too.
The parser first installs all cab files then reg files, then xml files, then tsk files, and lastly any exe and mscr files.
You will need to respond to some OK boxes to keep setup running. Others are timed to default to my preferred choice. These are things like do you want ASyncKiller to run on your phone? Do you want BlueTooth Notification Icon to run on your phone? etc.
If you want to try to control the sequence which each file in a group (CAB, REG, etc) installs try putting 00_, 01_, etc as the first characters in the file name.
If like me you have some cabs that you have installed to your sdcard you can do the following. I have a folder \Storage Card\SDAUTO\Zip where I place zip files of the programs files I need on the phone like the shortcuts, etc.
I also place a reg file in the folder \Storage Card\SDAUTO\Zip that sets the registry for the program.
The parser unzips all of the zip files to the root of your phone and then runs all of the reg files.
Your zip files should have the folder hierchy in them.
I also have the ability to not use SDConfig.txt for silent cab install. Place any cabs in the folder \Storage Card\SDAUTO\Silent you want installed without response required.
This parser also first installs all cab files then reg files, then xml files, then tsk files, and last any mscr files.
Some other notes.
While my script is similar to Noonski's XDA_UC, it is not the same. He is working very hard on a system that is not language or device dependent. I on the other hand have written my script for my Wizard and for WWE. My script does not support XDA_UC or XDAS files, etc.
For Mort's sake: Please do not report any errors to the MortScript Forum but to the Forum Thread of the Rom you have just Flashed. Adding other user created or your own scripts can do serious damage to your device, only use installations from a trusted or confirmed source, but the responsibility and choice to use these, is always your own. Remove your SD Card if you want to prevent other than the phone's setup.
Page Pool is what it has always been 6 MB
DO NOT ACCEPT ANY REQUESTS FOR REBOOT. Phone will automatically reboot after you pick OK on finished notice.
Nekid Angel
I took out everything I thought I could. It still has Mobile Office and it has MortScript to run my setup.
Right after flash without running my User Customization.
Storage 44.34 MB free
Program 32.16 MB free
----------------------------------------------------------------------
Nearly Everything Angel
This is very close to S.V.I's typical Angel. It has everything he has typically put in it plus MortScript to run my version of setup.
You will need to install an adobe reader program if you want to read the manual for MortScript.
Right after flash without running my User Customization.
Storage 40.83 MB free
Program 26.52 MB free
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Neat Angel
This is the Angel I use.
It has the following removed:
OperaMini
SAP Settings - lets your car's bluetooth access you SIM card
1-Calc Lite - have my own calculator
Touch Response - decided I don't like the vibration
PIM Backup - I do not use this
BT Icon - I do not use this
I added:
Adobe Reader
Transcriber
Right after flash without running my User Customization.
Storage 42.24 MB free
Program 27.41 MB free
Neat Angel in 21054 Port
I took my neat scripted Angel and ported 21054 stuff to it.
My understanding is that 21054 is the last WM6.1 version out here.
Let me know what you think.
I had to take out Transcriber, and Adobe Reader
Right after flash without my customization
Storage 42.69 MB free
Program 26.40 MB free
dotfred's task manager is called dftaskmgr.exe to make it work with the WM version.
Fixed missing MMS, I accidentally removed the package. I managed to get Adobe Reader put in. I got weather working again.
Here's the new link http://rapidshare.com/files/284946281/21054_port_Neat_Angel_nk.nbf
MediaFire http://www.mediafire.com/file/ianqzukmyym/21054_port_Neat_Angel_nk.nbf
I did not put any of the package called Browsingie in the ROM above because it is so big. I put it in this ROM http://rapidshare.com/files/284946285/Browsingie_nk.nbf, but had to remove M2D and a lot more to get it to fit.
Now the bad news. I do not know what this Browsingie ROM looks like or does different because I bricked my phone. I was trying a new CID unlock method and messed it up. I won't be able to cook any more since I cannot test to see if any of the tweaks I do work.
Here are the kitchen files http://rapidshare.com/files/284957064/Port_21054_Angel_Kitchen.rar
Updated Kitchen: Neat Angel in 21054 Port with Extended_ROM
First, I was able to buy a lab rat from eBay to continue cooking.
I fixed up my kitchen to the latest implantxip.exe version. With this I was able to tryremove the ULDR and other things that has given me more room to fit stuff into the ROM.
This is the Browsingie version. I put back Transcriber and Adobe Reader. I also fit in Voice Command and Remote Desktop.
dotfred's task manager is called dftaskmgr.exe to avoid conflict with the WM version.
I think I have avoided the Extended_ROM problem I have seen mentioned before of battery drain if you flash a new Extended ROM. The extended ROM is still locked and hidden. I am using Extended ROM to install M2D and M2DC. The nice thing about this is you can use remove programs to get rid of them if you prefer a different home screen.
I also use zip files in the Extended ROM to hold files that just got copied over to other folders. This way there are not copies in the windows directory and now there are not even the zip files.
So if you use Extended ROM to hold files they will get overwritten by this ROM.
Here's the new link http://rapidshare.com/files/346929040/091112_Port21054_Ext_ROM_Browsingie_nk.nbf
MEGA Angel with 21056 Port and using Extended_ROM
I have two versions of MEGA Angel.
Based on version 23 Manila2D RapidShare MediaFire MegaUpload
Based on version 1917 Manila2D RapidShare MediaFire MegaUpload
version 1917 Manila2D with Extendir to see if it speeds things up RapidShare MediaFire MegaUpload
This is the older version of Extendir ver1.06 with 2MB cache
They both have everything in common except the version of Manila2D.
Both have working Album and Music tabs. Sound profiles does not work in the ver 1917 settings tabs, but I added a link to the program under \programs\tools in the start menu.
Still using Extended_ROM to fit everything. Mega is big. ROM setup takes a while as a result of so many files too.
Some things I have done:
Radio is off at the start. Reduces chance of call coming in while ROM is setting up. Turns on near the end and runs Network Wizard to set up phone service.
Took out ModemLink since it is the same as InternetShare and I doubt anyone uses the infrared method in ModemLink.
Took out Network Plugin since it requires a reboot every time you change it.
Added Total Commander for its features including the ability to have LAN and FTP connections, which replaces Network Plugin.
CommManager has nice feature. Select the text and you get the settings panel for that item. Select the on/off button and you start or stop the device.
BlueTooth settings allows start up of BlueTooth FTP and has a timeout settings for the radio.
USBtoPC is set to not be the enhanced feature setting by default.
Do not reset your phone while it is setting up. When Network Wizard says it is done and to reset, select cancel. ROM setup will reboot when it is done.
If I think of anything else I'll update.
you make me wish I still had my wizard.
is it still the same OS or have you updated?
It is still the same OS. 20923
I have been avoiding the 21xxx series of ROMs since Cracing has said they have memory drain or leaking issues.
I am trying to keep the strengths of your original Angel. I have just been playing with the clean up of what is in it.
Oops
Updated links for all three versions.
I removed debugging text messages to speed up setup.
thanx!!!!!!!!!!
Thank you for your work.Can I flash the rom as useal?
They are OS only nk.nbf files. You can flash your Wizard however you typically flash a nbf file to it. Since they are OS only they are G3 and G4 safe.
Nekid
Thanks RoryB.
I've always wanted the Nekid Angel. You had posted the source for it in your FFA thread. But I couldn't get it to compile. Too many errors and stuff.
Well, I will be installing the Nekid Angeld soon. I do not use any of the programs that you guys normally do. I just need a few small utils, which I have cabs to install.
So a big thank you for cleaning this up. Much appreciated.
A QQ -
Do I need to downgrade to install this? I have Final Final Angel installed.
Or can I just put it in soft IPL and load Nekid Angel?
You will be replacing the old Angel when you flash this one.
As far as downgrading is concerned. I have not done that for some time. I used to flash back to my original ROM and then flash a new one, but for me it does not seem to matter. I would say to just try flashing straight to your new ROM.
Thanks!!!
Today morning I installed Nekid Angel. I'm really loving it. Simple and fast. And allows a lot of space for what I want. Thanks a ton!!!
So far so good, no issues. Working like a charm.
SMS sent folder synch?
Guys,
I observed this in WM6.1. I've disabled threaded SMS and it does not store the SMS I sent in the sent folder. I really hate threaded SMS.
Is there a hack or way to store the sent SMS in the sent folder? I've tried a couple of things, but can not get it to work.
Hopefully someone that uses SMS/MMS can help you. Our company blocks them on our plan
Shift and symbol keys
Guys,
I'm facing problems with Shift and Caps keys on the keyboard. Is anyone else facing this problem?
Sometimes the shift key just wont work... have to press it hard or 2-3 times to get it to work. Not such a problem with Caps key.
But yes, sometimes these two keys in combination do irritate a lot when texting someone or when trying to type numbers.
My ELF might be dead but i stills got my Wizard .
Check the Forum for "MortScript HTML Manual" i'ts a bit lighter to include, but it might also be a bit outdated for some of the updates. (some prety faced Drunk posted it).
RoryB said:
Nearly Everything Angel
This is very close to S.V.I's typical Angel. It has everything he has typically put in it plus MortScript to run my version of setup.
You will need to install an adobe reader program if you want to read the manual for MortScript.
Right after flash without running my User Customization.
Storage 40.83 MB free
Program 26.52 MB free
Click to expand...
Click to collapse
Works great so far. I work out of town alot and roam alot as well...will post when i return how that all has worked for me. Lotsa room for the system to work. very little hesitation. Will keep you posted....Thanks
screenshots anyone ?
http://forum.xda-developers.com/attachment.php?attachmentid=201368&d=1246567845
http://forum.xda-developers.com/attachment.php?attachmentid=189290&d=1243429966
http://forum.xda-developers.com/attachment.php?attachmentid=189291&d=1243429966
Same as original Angel, but I removed Autorun and SDAutorun and use a mortscript ot parse the config and sdconfig files. Gains a (very) little more room in memory.