Database Develop

Comment in config.txt in ext rom

Thanks for all the help. Just a few days ago I couldn't boild water and now I'm upgrading Radio Stacks and Cooking Ext ROM. Couldn't have done it without your help.
Looking forward to Radio 1.10, better bluetooth, and maybe one day WM2005.
In the mean time I'm working my way through config.txt deleting stuff I don't use. So far I'm just deleting the references in config.txt.
Is there a way to make a line a comment in config.txt? I would love to preserve the line I'm testing deleting so if I need it I can uncomment it. I have a good backup of the whole ext rom including config.txt
Thanks again
W

Happy for you, looks like wiki -ays off if you read and follow it.
I had come across that but never wrote it down as never saw the need for it. I use the regedit to pipe to a differnt storage space and run the autorun out of that.
Fot your understanding it gives me the option of a empty rom after rom flashing. Then I install stand apps, folder a, patches, folder b, apps that need input, folder c. Then i run a dos script to creat all sub folders, mover the shortcuts, add the shortcuts to sd card.
This all jeans that i can flash my device and have it back to the way i want it in less than 2 hours.
Whole thing is in a thread that i posted something about auomate after upgrad (0n wifi and pda cant find link).
Anyway, back to topic.
Think its ; before statement.
Have fun

Question about mod the rom ,language etc

After reading almost all the posts here and I decide to create my own WM5 rom based on the latest Helmi release. several thing that I want to do
1. Increase the pagefile to 8mb with the instruction in the post here
http://forum.xda-developers.com/viewtopic.php?t=61926
2. Install language pack "french" , however, I do not know how to do this, I unzipped the "Helmi_WM2k5_AKU3.2_32mb_v1.3.1", however I cannot find where I can put the language related stuff. Anyone knows how to do this?
3. This maybe a silly question. Most of my games and programs in 2003se are green(meaning do not need installation), do you think it makes any sense to put into the rom? or if I change the question a little bit, can the rom copy the files automatically to the SD card and create shortcut to it?

In the case of 3), do what I do...on my SD card I have a directory called "programs". Within here I keep a "cabs" directory for installers and a "manual" directory for apps that don't need installed. All you need to do is make the shortcuts to your storage card inside the Start Menu.
Also, a useful tweak I've heard of but don't do myself is to keep a folder with these shortcuts on the sdcard in /Storage Card/Shortcuts. Then create a shortcut to this folder in the Start Menu. You now have a customisable shortcut list representing what is currently in the SD card slot. Handy if you have several cards and switch between them.

I think you misunderstood me.
I know how to do that when I installed the WM5, I was talking about bundle all that to the Rom before upgrade to WM5

I think understand what you mean. I'm just saying that it's not really worth it for the really simple apps. You'd spend more time cooking roms than you would making shortcuts in Total Commander. Plus, I think you'd need to take some of the existing stuff out as Helmi undoubtably stuffs the rom full with all that he can fit in.
But if you have the time it's probably worth it just to have a play around & learn some new tricks in the process.

Programs in ROM - vs. installing CAB's

I hope this is not too noob'ish a question:
What is the advantage of
1. installing (most of) your programs in a ROM,
vs.
2 having a rather clean/small ROM, and installing (a lot of) CABS afterwards?
I know 1. is a bit easier.
But is there any difference in performance?

I would say that you can't install anything into the ROM
That's why they use the ROM to fill it with the "cookers" special needs

The Advantage of Rom Installed Software:
You don't have to manually install it after a Hard Reset of Flash. Enough said on that, it saves you some time.
The Disadvantages of Rom Installed Software:
Uses Rom Memory for the original copy of files and Storage memory for anything that must be moved as part of initial setup. So anything that can't simply stay in Windows folder is duplicated elsewhere. For example if you prefer to have your programs in folders under the Program Files Folder then a program that uses 1mb will use 1mb of Rom memory and then when it is copied (remember you can't really delete Rom Files) it will use 1mb of Storage Memory also for a total of 2mb of used memory.
Can't uninstall original version when an upgraded version is avaliable. Sure the Rom file can be marked as deleted so they aren't listed in File Explorer anymore but they are rom files so you don't free-up any space.
More files in your Windows Folder. While the affect this has on our devices isn't 100% clear we do know that it slows opening the windows folder and I believe that it does cause a general slowdown in the device's overall functioning. This is why I prefer to have programs installed to their own folders.
The Advantages of Manually Installed Software:
Saves Rom Memory which increases Storage Memory. Basically since you have everything in Storage Memory you aren't paying extra for anything as nothing took any Rom Memory.
Can uninstall original version when an upgraded version is avaliable. Yes, since everything was installed into Storage Memory you can actually deleted the files to upgrade thus saving Memory.
Fewer files in your Windows Folder. While the affect this has on our devices isn't 100% clear we do know that it speeds-up opening the windows folder and I believe that it does affect the device's overall functioning. This is why I prefer to have programs installed to their own folders.
The Disadvantage of Manually Installed Software:
You have to manually install it after a Hard Reset of Flash. Enough said on that, it costs you some time. UC Compliant Roms can overcome this.

Well, as some cooks report: there seems to be an extra advantage of installing into ROM: everything seems to work a little smoother and faster. Don't know how or why exactly but has to do something with the after-installing process which makes the device less stabile.
Experiments have shown that of you take a full ROM vs. a lite ROM with the extra's from the full ROM installed afterwards, the full ROM is faster and more stabile.
Kyphur: I believe the second red and green titles are wrong? (I believe yoe mean Cab Installed Software?)

One of the reason that loading windows up with files slows everything down is because the are all paged & cached, depending on the settings. Once the device catches up, it's not as noticable.
Storage card Files cannot be paged like the cooked in files. That's why some programs will add .exe & .dll resources to \windows even though themajority of the files are indeed installed to the SD card.

GSLEON3 said:
Storage card Files cannot be paged like the cooked in files. That's why some programs will add .exe & .dll resources to \windows even though themajority of the files are indeed installed to the SD card.
Click to expand...
Click to collapse
I don't install to my storage card anymore. Why would I do that when I start out with over 160mb of free Storage memory?

kyphur said:
I don't install to my storage card anymore. Why would I do that when I start out with over 160mb of free Storage memory?
Click to expand...
Click to collapse
No, I don't either. But also with installing on the device there seems to be some (speed)difference in ROM installing and CAB-installing.

I'm with Kyphur on this one. The less I have in the ROM, the better because software is constantly changing, being upgraded, etc. Also, I find a lot of times my needs vary and I don't require so much "stuff" on my ROMs, so w/ the XDA-Live approach, I have the freedom to only install what I need. I guess it's a matter of preference really. Sure there are technical differences, both they are overcome either way, so it just comes down to what you like better.

pietrucci said:
Experiments have shown that of you take a full ROM vs. a lite ROM with the extra's from the full ROM installed afterwards, the full ROM is faster and more stabile.
Click to expand...
Click to collapse
Ok ... thanks!
- Do you by any chance have a link to such a benchmark?
- Does that also go for ROMs you cook yourself (with Alex' Kitchen)?

How to actually mark as deleted files in ROM?
Hello, this is an interesting thread, and I also hope you guys know more on this, since you're explaining the concept (and I also searched for a solution, but sorry, didn't find, I might have not used the proper keywords for searching):
kyphur said:
Sure the Rom file can be marked as deleted so they aren't listed in File Explorer anymore but they are rom files so you don't free-up any space.
Click to expand...
Click to collapse
So I flashed Dutty's Official WM6.1 5.2.19716 UC RTM (but which ROM it is, doesn't really matter) as my question is related to "deleting" (or at least marking as deleted) ROM files. My problem is, I want to delete \Windows\Long Send.lnk because I don't like the Comm Manager show up when holding the green Send key during a call, while I'm expecting the phone to go into speakerphone mode like used from many other phones (even my Sagem cordless at home behaves this way). The folks in this ROM's thread suggested to delete that shortcut file (which is what I think they know right if they hadn't omitted the fact that the file is in ROM), but none of the in ROM or read-only attributes can be changed with Total Commander, so I can't "delete" it. Now I understand it's supposed to be just marked as deleted as it is "in ROM", so it is supposed to survive a hard reset, but how can I mark it deleted for the time being (next ROM upgrade for example, or hard-reset)?.

pedefede said:
Ok ... thanks!
- Do you by any chance have a link to such a benchmark?
- Does that also go for ROMs you cook yourself (with Alex' Kitchen)?
Click to expand...
Click to collapse
No I don't have a benchmark of this. But then again: the current benchmarks (SPB and VS Benchmark) aren't that reliable.
I remember one cook from the Hermes device (maybe it was Pandora) made a ultra-lite version with an option to autorun everything afterwards with cabs.
This ROM wasn't as fast and snappy as the original full ROM. I think he quitted developing the ROM further.
Don't know if it's always true that everything's worse installing with cabs, it was just something a remembered from the past.
(by the way: I also install a lot from cabs...)

ChaOConnor said:
I'm with Kyphur on this one. The less I have in the ROM, the better because software is constantly changing, being upgraded, etc. Also, I find a lot of times my needs vary and I don't require so much "stuff" on my ROMs, so w/ the XDA-Live approach, I have the freedom to only install what I need. I guess it's a matter of preference really. Sure there are technical differences, both they are overcome either way, so it just comes down to what you like better.
Click to expand...
Click to collapse
the ROMs change too, and not slower than the softwares

calvinzhang said:
the ROMs change too, and not slower than the softwares
Click to expand...
Click to collapse
But flashing every week a new ROM is not for everyone. The possibility to flash once in a while is cool and good enough for lots of people, but doesn't have to become the main occupation

Zoolooc said:
But flashing every week a new ROM is not for everyone. The possibility to flash once in a while is cool and good enough for lots of people, but doesn't have to become the main occupation
Click to expand...
Click to collapse
That's what "UC" is for! Auto Install all of your apps. Just remember to keep the cab files updated.

For me, one of the biggest advantage of full rom is I save a lot of time in doing backup since the files in the rom already.
Another advantage of full rom is they don't need to store any files under \Windows\AppMgr since they can't be uninstall anyway.
To overcome the bad effects of full rom. I tend to consider the following when putting programs in my full rom.
1. File can be run under \Windows
2. Programs that don't change that often, or doesn't need the latest version.

Can we not squeeze a little more out of the wizard's memory?

Adding an explanation for starting this thread
I started this thread because when I search for ways to get more memory, all I find is how others have things like "Big Storage" etc., but somewhere it will say cannot be done on wizard. I do not find very much about what can be done or why it cannot be done. I have found things about unlocking and unhidng the Extended_ROM. I used that as a basis for my trials and trying to understand how memory works in the wizard.
I started this thread hoping someone with much more knowledge than me would be able to shed light on the issue and it would be on the forum for future users to understand the memory issues on the wizard.
-----------------------------------------------------------------------------------------------------------
In default.hv which I converted to rgu so I could read I saw the following:
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable][/FONT]
[FONT=Arial]"26"="BINARY"[/FONT]
[FONT=Arial]"25"="IMGFS"[/FONT]
[FONT=Arial]"23"="RAWFS"[/FONT]
[FONT=Arial]"22"="RAWFS"[/FONT]
[FONT=Arial]"21"="BINFS"[/FONT]
[FONT=Arial]"20"="BOOT"[/FONT]
[FONT=Arial]"0F"="FATFS"[/FONT]
[FONT=Arial]"0E"="FATFS"[/FONT]
[FONT=Arial]"0C"="FATFS"[/FONT]
[FONT=Arial]"0B"="FATFS"[/FONT]
[FONT=Arial]"07"="NTFS"[/FONT]
[FONT=Arial]"06"="FATFS"[/FONT]
[FONT=Arial]"04"="FATFS"[/FONT]
[FONT=Arial]"01"="FATFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles][/FONT]
[FONT=Arial]"Folder"="Mounted Volume"[/FONT]
[FONT=Arial]"PartitionDriverName"="MSPART"[/FONT]
[FONT=Arial]"DefaultFileSystem"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:0[/FONT]
[FONT=Arial]"AutoFormat"=dword:0[/FONT]
[FONT=Arial]"AutoPart"=dword:0[/FONT]
[FONT=Arial]"AutoMount"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV][/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"Name"="Microsoft Flash Disk"[/FONT]
[FONT=Arial]"PartitionDriver"="mspart.dll"[/FONT]
[FONT=Arial]"DefaultFileSystem"="IMGFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\IMGFS][/FONT]
[FONT=Arial]"XIP"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS][/FONT]
[FONT=Arial]"FatCacheSize"=dword:100[/FONT]
[FONT=Arial]"DataCacheSize"=dword:800[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"Flags"=dword:600014[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\Part00][/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS][/FONT]
[FONT=Arial]"MountHidden"=dword:0[/FONT]
[FONT=Arial]"MountAsROM"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\MSPART][/FONT]
[FONT=Arial]"Dll"="mspart.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\IMGFS][/FONT]
[FONT=Arial]"ShadowROM"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="imgfs.dll"[/FONT]
[FONT=Arial]"FriendlyName"="Image-Update Filesystem"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"CacheSize"=dword:2000[/FONT]
[FONT=Arial]"Flags"=dword:44[/FONT]
[FONT=Arial]"CacheDll"="diskcache.dll"[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
In boot.rgu I found
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager] [/FONT]
[FONT=Arial]"PNPUnloadDelay"=-[/FONT]
[FONT=Arial]"PNPUnloadDelay"=dword:5dc[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\IMGFS][/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC][/FONT]
[FONT=Arial]"Name"="DiskOnChip M-Systems"[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS][/FONT]
[FONT=Arial]"Flags"=dword:1000[/FONT]
[FONT=Arial]"Index"=dword:1[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"="Extended_ROM"[/FONT]
[FONT=Arial]"MountHidden"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:14[/FONT]
[FONT=Arial]"FormatTfat"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Bootphase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1][/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC1"[/FONT]
[FONT=Arial]"Index" = dword:2[/FONT]
[FONT=Arial]"Dll" = "TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix" = "DSK"[/FONT]
[FONT=Arial]"Order" = dword:1[/FONT]
[FONT=Arial]"Ioctl" = dword:4[/FONT]
[FONT=Arial]"Use8Bit" = dword:1[/FONT]
[FONT=Arial]"WindowBase" = dword:00000000[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode" = dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Comm][/FONT]
[FONT=Arial]"AutoRun"="\\Windows\\AutoRun.exe"[/FONT]
[FONT=Arial]"AutoRunCFG"=[URL="file://\\Extended_ROM\\Config.txt"]\\Extended_ROM\\Config.txt[/URL][/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:6[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:00600014[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS2][/FONT]
[FONT=Arial]"Index"=dword:3[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC2"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"Ioctl"=dword:4[/FONT]
[FONT=Arial]"Use8Bit"=dword:1[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS2][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS2"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"BootPhase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial]"order"=dword:1 ; must be loaded before other filters[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"Flags"=dword:00000024[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"CacheSize"=dword:0[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\filters\HTCFSDSPY][/FONT]
[FONT=Arial]"Dll"="htcfsdspy.dll"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
Of course there is more than just the above in those files. What I wonder since I do not know enough to know what cannot be done is...
Can you change these settings to not define a region to be extended ROM?
Can you redefine the rest to use this left over space?
Can any of this space be used for program memory instead of storage memory?
I do not know if the dll files limit the size of the regions or is some of the settings determine the sizes.
As I said, I do not know enough to know the limitations, but the little boy saw all that was needed was to let the air out of the tires to get the truck unstuck from under the bridge.
Note: This work was done on my G4

Are you using LZX compression?
If not start reading form “HERE” post #877

I have been reading that and the Visual Kitchen Thread, but they leave me behind a little yet.
I am just now trying to go past using the HyperCore Kitchen and switch to CRBuilder 2. I am not sure what it does different. It seems to be less forgiving of my mistakes.
I also read the threads on porting XIP, etc. I am still trying to learn this stuff.
Since I am naturally lazy, I thought what if we could get more room by not defining ExtendedROM. Also, I did not know how program memory versus storage memory is set up and if it was possible to get more program memory available. This is going to become our limiting factor (M2D, WM6.5, etc.).

Everything i’ve read would suggest that we can’t use the extended ROM area for anything other then what it was designed for.
I don’t think you can gain any more memory without removing programs.

I have been doing a lot of reading. I have a G4 Wizard. I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I am beginning to think extended rom is coded in the chip and not set by our flashes. Has anyone tried something like DiskOnChip TrueFFS Uilities package or similar to redefine the spaces on the chip to not have extended rom? I know so little, I imagine there is something more that prevents this, but I thought I would ask. I did not know if this path would lead to more program memory in addition to storage memory.

Delete references to TRUEFFS_DOC1
I decided to do a separate post for each trial.
I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I did not notice a change in battery consumption.

Change TRUEFFS_DOC1 settings to be more like TRUEFFS_DOC2
I basically changed TRUEFFS_DOC1 (changed to call it StoROM) settings to match TRUEFFS_DOC2 (regular memory) except I did not set it as "root".
It shows up as removable storage with 4.9 MB of space.
I suspect something in TRUEFFS driver or I am missing a setting to tell it that is is not external memory.
I tried again, but named it "My Documents"
Word and excel would see the template files in My Documents\Templates twice. I could not set word's default file type. No choices showed in the option. I tried moving the templates, but then they could not be seen by word or excel.
Tried sync with my PC. What was already on the phone would not copy to the PC. I added things to the folder on the PC and they would add to the phone. If I deleted it off the phone, instead of deleting it off the PC it would put it back on the phone. If I copy a file from my phone to the my documents folder on the phone it would not show up on the PC. So it seems I have one-way sync capability.
I tried again, but named it "Program Files"
It works, but whatever gets written there stays so I had problems when I did a hard reset. I solved by deleting contents of folder before hard resetting.
Currently testing named to "FileSafe"
I can put files there and they do not get lost in a hard reset.
I am currently testing battery consumption on this latest format. First day, but after 5 hours only down to 91%. Will need to wait because I have noticed battery goes down faster as the level gets lower.
I did a soft reset and ended up with Storage card as a folder in root and storage card2 as the storage card. Cannot delete it since I have reg settings made to locate internet explorer files to storage card.
I'll have to keep tweaking settings.

More about Trueffs driver
I came across a package called "DiskOnChip(R) TrueFFS(R) Uilities package"
This Package includes the TrueFFS Version 6.3.2 Utilities Package
Reading the documentation gives me the impression that the chip is formatted at the factory and we cannot change the partitions. I suspect (stating again) that we only tell the software what to do with the partition. I tried to run the utility, but it could not find the chip to even do a read function.
It also looks like you have to have a password to gain access to parts. I do not fully understand this stuff, but I was reading about locking partitions with a password.
This may be why even though I have the format flag set in TRUEFFS_DOC1 it does not get formatted and as a result the things stored there are still there after a hard reset. Also, why it shows up as removable media even though I do not see where I tell it that it is such. I think anything other than the root is considered "external" and shows up as a storage card.

Explanation added
I added an explanation for this thread to the first post

Updated post #7 about FileSafe.

I have tried every which way I can think and can only create a folder that the phone considers a removable storage device. I keep getting the storage card2 problem so I have gone back to regular settings and installed a blank Ext_ROM.
I am fairly sure of my theory that the partitions are formated at the factory and we are only telling the software what to call them and how to access them. We cannot change what they have been set to at the factory.
I welcome any clarification from someone who knows more.
Hopefully this will help others like me who come in late in the game and wonder why we cannot get things like BigStorage, etc. other than just seeing people saying it cannot be done.

I read about hiding and unhiding the Ext-ROM, too. Unhiding and reading was no problem but writing didn't work.
Converting Ext-ROM to program-memory may not be possible, because AFAIK program-memory is SD-RAM and the Ext-ROM is Flash-MEMORY. But there are more ways the memory of the Ext-ROM could be usefull.
More space for the ROM (max. 57MB for OS.nb is not much when cooking a WM6.5 ROM) would be nice.
OR
A storage-partion like Ext-ROM but with write access!
Only unhiding the Ext-ROM didn't do the job! I could read from the Ext-ROM but couldn't write. After a write attempt the file list got corrupted and I had to hide and unhide again to get read access back.
If I understand the posting right, RoryB was already able to write to the Ext-ROM. How did you do that?
There is one more Problem! Not the MiniSD-Card but the Ext-ROM should get the name "StorageCard 2" (or any other name which comes alphabeticaly after StorageCard). Why? The Camera can save to different locations but you can only choose from 2: Main memory and the alphabeticaly first storage card.
My questions:
1. How do I get read, write and delete access to the Ext-ROM?
2. How can I rename this "Ext-ROM-Storagecard"? Something like "StorageCard 2" or "StorageMemory" or ...
Update:
Answer for question 2 might be:
AbuYahya said:
To Rename EXT-ROM
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"Folder"=string:Storage
--- can call it anything you like instead of "Storage"
Click to expand...
Click to collapse
I didn't check it yet.

I have stopped trying to get Extended_ROM as storage space. I did use it as a filesafe location. I could not get access to all of the space even though I installed an empty Extended_ROM. Here is the part of boot.rgu I changed (best as I can remember)
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:0
"SoftwareWriteProtect"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="FileSafe"
"MountHidden"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I think the "Storage Card 2" problem comes about from the order in which the Extended_ROM and SD Card get recognized and for some reason it sees the Extended_ROM as a storage card.
I now use Extended_ROM that way Cingular did. I have files in it in the form of cabs and zips. These files are things like Adobe Reader as a cab, Template files as a zip, etc. I use my customization mortscript to install those files. This way I get more room in the ROM for things that have to be in the ROM. Here is the format I have for my boot.rgu
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:1
"SoftwareWriteProtect"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="Extended_ROM"
"MountHidden"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I use winimage to change the contents of my Extended_ROM.nb file. Now when I run nb2nbf I pick the OS and the Extended_ROM as files to write to the nbf.

G4 processors do not allow you to flash a custom extended ROM (IIRC).

jwzg said:
G4 processors do not allow you to flash a custom extended ROM (IIRC).
Click to expand...
Click to collapse
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.

RoryB's latest ROM that uses ExtRom for cabs and such works fine on my G4.
Ham3r's experimental ROM that provides ExtRom as a read/write filesystem works on G3.
I even installed apps onto ExtRom, with no problems.
I don't know about its relative speed.
It is marked "G3 only" so I have not tried it on my G4.
If someone is brave enough to show that the Ham3r rom's method works on G4, that would be a great feature.
I think that making the most of extrom as a filesystem is the best we can do.

Cyberdyne said:
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.
Click to expand...
Click to collapse
For some reason I was thinking it wouldn't flash. I haven't touched my Wizard in a while, and my XP computer with my kitchen on it is dead. I'll have to upgrade my WM6 ROM again.
Mods ain't gods. I stand corrected.

What can I delete for files?

Hi I upgraded my 9090 to WB 6.5 from Xplode latest release. I’m really happy with this and everything works fine.
In this phone the memory is only 43.2 Mb, (I have another one, broken but it has 60Mb.) and the upgrade take almost all of this.
My question is what files can I delete to have more space?
Is it possible to install the OS on a memory card?
I’m really happy with this release so I hope there is a solution.
Regard
Ola A

you should downgrade to wm2003 first and repart your storage space, so that the device also has 60mb, also, the rom takes up 32mb in the rom storage, even if there was a rom with nearly nothing inside, just the operating system itself, it would still take up 32mb, because that is the rom size. and it must be in the rom space, there is no way to install it somewhere else.
so, what you can do to gain those extra 16mb, to need to flash wm2003 and then do exactly, what i wrote here: http://forum.xda-developers.com/showpost.php?p=4706441&postcount=2
in the end, flash wm6.5 back and following that guide, it will run smoothly and fast and you will have slightly more space. still, you will never have more than 60mb of internal storage, unless you pick a rom with a ramdisk, which can offer you yet another 16mb in another partition.

I’m really pleased for the solution...
Please tell me where can I find how I go back to wm2003?
You had in your mind to do the repart for the storage space as in the link you suggest?
Wye can’t I do the repart in WM 6.5?
The download for repart_doc.exe and the second file have download problems, you couldn’t have some down load alternatives...?
How can I install the OS on the Memorycard?
Regard
Ola A

1. for the downgrade to wm2003:
1.a go to firmware.atspace.com/blueangel.html
1.b look for a firmware to match your device, it doesn't matter much, but it should be either an english rom or one in your native language, i guess english would be best though.
1.c Important! Extract the rom, so you have a folder, containing files like nk.nbf, ms_.nbf, baupgradeut.exe and so on. don't just start the exe you downloaded!
1.d download maupgradeut_noid, if the rapidshare download from the link above doesn't work, search the forum for "Chef_Tony Ruu", you will find several mirrors.
1.e download "repart_doc" and "xda-unlocker.cab" also from the link or search the forum, i uploaded it many times
1.f put the maupgrade in the same folder as the nk.nbf and all the other stuff from the wm2003 rom
1.g hard reset your device by pressing reset+power and camera+record, in the menu appearing set
Enable Kitl No
Format Storage Yes
Clear Registry Hive Yes
and confirm with the mail button
1.h after the device started, switch it off and remove the sim card and sd card
1.i put your device into bootloader mode by pressing power+record+reset, the display shows Serial V2.0x, where x is a number from 5 to 7
1.j start MaUpgradeut_noID and flash the device
1.k perform a wm2003 hard reset by pressing power+reset
1.l wait for the extrom to install and the following soft reset
1.m proceed with the manual from the link i gave you.
2.yes, the reparting of the useless extrom partition is, what i had in mind, it slows your device down and is just a collection of useless cab files with carrier customizations like dialer skins and wallpapers, that are installed after a hard reset in wm2003
3. it cannot be done in any os but wm2003, that is what makes this partition so useless, it is just not accessible
4. for downloading those files, if rapidshare doesn't work for you, as suggested in 1. use forum search and look for the file name, together with my name, and you will find several direct download links from the forum.
5. there is absolutely no way, the os can be installed from or to the memory card, in fact, while installing the os, the sd card may not even be inside the device, it can lead to serious damage of the device. like i explained in my earlier post, the rom does not take away any usable space anyway. you have 60mb of storage space for programs and files and 32mb rom space for the rom. if your rom is 20mb, then it is still filling up your 32mb of rom space and your storage will still be 60mb. if you have a rom with a lot of stuff inside, that is really taking up 32mb, you still have 32mb rom and 60mb storage.
that is why it is even better to take a big rom with lots of programs inside, because that way you really save space... since you don't need to install those programs in your storage space.
with best regards
Chef_Tony

A big thank you for your support. I’m now going to try this out.
--------------------------
Three hour later.
Yes, now is everything done. Some hard to find WM2003 file but at last... (They who were in your link weren’t there anymore.)
Now the memory is big and clean. All my apps installed...
A happy new year
Ola A.