I recently gave my XDAII (on Ather's WM6.1) away as a gift to friend. A few days ago he told me that after changing batteries a "RAMDISK 2" suddenly appeared and that his storage/memory was now half of what it was. Needles to say he wants to go back to the standard single RAMDISK config and recover his lost storage/RAM memory. I've been searching xdadev for two days now and all I could come up with is this:
"paulpax
01-08-2008, 02:16 AM
myxxx
youve got a case of weak backup battery, and you do frequent removal or changing of your main battery. doing this can cause you ramdisk to appear and disappear for no reason at all, sometimes your OS compensates by naming a folder RAMDISK but its not really a real ramdisk, when the real ramdisk gets restored, you will have RAMDISK - not real and RAMDISK2 - real ramdisk, where RAMDISK2 has a removable storage icon, it has happened to me a lot of times, but since i dont use RAMDISK because of this, its no problem."
Can anyone pls. tell me how to remove/delete the "phantom" RAMDISK2 and restore the full storage/memory of my friends XDAII. Thanks in advance
thats a quote from me alright. hehe.
just erase the folder RAMDISK then restart or soft reset your xda. then ramdisk2 will be named ramdisk after the restart and the old ramdisk, well you just deleted it.
also, if you installed some programs our your ramdisk, then copy those programs first to a storage card before erasing ramdisk, then just copy them back after restarting your xda.
hope that helps.
Related
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
Guyz i have noticed something very intresting about WM 6.1
Even if you hard-reset or flash a new ROM and perform a No/yes/yes way hardreset..the Ramdisk does not looses its data..i have flashed my currently being cooked ROM about 12 or 13 times and the data which i had since C_shekhars is still there...check it out when u flash another ROM
Hm....
Belive me it not becose of 6.1
I`ve use it since wm5.
I`ve already been reported abut that - sometimes in case of similarity of ramdisk it survive reflash if ramdisk similar.
this is not windows based thing
the most probable cause is same ramsize roms
is this the case?
Note
Yes, i also agree. i have upgrade my O2 XDA2 to WM 6.0c from C_shekhars one day i try to do a hard reset by pressing Power and Reset button it doesn't do anything what i have installed still there. Any Idea?
But when you remove the battary for changeing the sim
It is deleted .
Strange ......
@obaz is right.
It is happening since the time RAMDisk has come into existance.
May I add to it for all those who want to know more about it that:
When you flash another ROM having Eq to or larger-than-before RAMDisk size then the contents shall survive the Hard reset. But, when you flash the ROM having RAMDisk size smaller-than-befor then the RAMDisk contents shall be lost.
heres my problem, the RAMDISK is not recognized by my XDA as a STORAGE LOCATION, so when i install applications, instead of having 3 choices (DEVICE - STORAGE - RAMDISK), i am only left with 2 choices (DEVICE and STORAGE).
this happened while I was on WM6.1 ver A_CS, when i reflashed to WM6.1 Ver B_CS, the ramdisk survived intact and still it is not recognized as a storage location or drive.
by the way, 6.1A and 6.1B of shekhar has the same 16MB ramdisk. although im not a fan of ramdisk, I NEVER HAD A USE FOR IT, it sometimes just lose all programs installed on it.
for the sake of functionality, HOW can i bring back the old RAMDISK as DISK or STORAGE LOCATION?
see the picture, STORAGE CARD is classied as a DRIVE or DISK, whereas RAMDISK is not, it was a drive before but not now.
paulpax said:
although im not a fan of ramdisk, I NEVER HAD A USE FOR IT, it sometimes just lose all programs installed on it.
Click to expand...
Click to collapse
This happens when your battery dies.
Sascha
Hi Jeenj
Although i took battery out for along time, it's still not delete.
Hi there!
Is there a way to delete the demo mp3s and movies and pictures and ringtones and installers and crap from the WINDOWS-Folder without reflashing the entire ROM?
I mean they seem to reside in the same physical memory structure as the "userdata", (since the device only has one flash memory chip and there seems to be no separate partition like an "extended rom" or something), the phone can read them just like any other file, just they cannot be deleted and explorer hides them in list views, so they just sit there, wasting 80+MB of precious flash memory.
My guess is they just marked as read-only system files so WinCE denies write access. If that's the case, shouldn't it be possible to modify the file attributes somewhere and then get rid of all this junk?
I've seen the "cleaned" german rom in the forum, but somehow I'm not quite comfortable yet with flashing an otherwise nice official rom with some cooked image (no offence), just because I want some mp3s deleted...
Anyone has an opinion?
downloadtest82 said:
Hi there!
Is there a way to delete the demo mp3s and movies and pictures and ringtones and installers and crap from the WINDOWS-Folder without reflashing the entire ROM?
I mean they seem to reside in the same physical memory structure as the "userdata", (since the device only has one flash memory chip and there seems to be no separate partition like an "extended rom" or something), the phone can read them just like any other file, just they cannot be deleted and explorer hides them in list views, so they just sit there, wasting 80+MB of precious flash memory.
My guess is they just marked as read-only system files so WinCE denies write access. If that's the case, shouldn't it be possible to modify the file attributes somewhere and then get rid of all this junk?
I've seen the "cleaned" german rom in the forum, but somehow I'm not quite comfortable yet with flashing an otherwise nice official rom with some cooked image (no offence), just because I want some mp3s deleted...
Anyone has an opinion?
Click to expand...
Click to collapse
They sit there inside the ROM, not user memory unless they are installed.
So they aren't taking up space.
it does take up space, i.e. it makes the OS image bigger and so decreasing the storage space.
just dump the rom, remove the files, rebuild rom, flash, done. i had to do this for prerelease xperia now (it has half the rom size so this was quite necessary)
Ok, so the only option really is to manipulate the OS-Image as a whole.
Thanks for the clarification.
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.
First of all sorry for my english, i'm not a native english speaker.
I'm a new user, but a frequently anonymous visitor.
I finally decided to apply a custom ROM (FroyoMod 2.6.0) to my Milestone.
The problem is the following:
I have noticed that since i installed this particular ROM my /data directory is getting consumed by something.
I have not installed new apps, im just testing it and by some reason since yesterday i have lost more than 5MB.
For example since i started writing this post i have lost 100K more...
Perhaps is a log file that is consuming my /data directory but i can't seem to find the guilty one.
Has anyone experienced this problem?
Thanks in advanced for your help.
Try using busybox and 'find /data -mmin -5' to discover the files that are changing...
Thanks for the info i found that the files that are getting bigger and bigger are those under /data/logger/AOL_*
I'm a linux user, but i'm not sure if this logs files are important, because one solution that comes to my mind is just to empty those logs, i mean they are just logs after all.
I've decided that i will just clean those logs and for that i created a tiny bash script that cleans those logs, so far seems that i'm not losing to much memory.