Related
Hi ALL,
Which files of the windows directory are in the ROM and which is in the RAM ?
Does the OS allocate storage (Disk) of the ROM and the part in the RAM as one consecutive storage or ?
thanks in advance
Current wisdom on the ROM filesystem
There is a ROM filesystem of sorts. It combines files stored in ROM regions called "XIP blocks" into one directory (\Windows). Files in these blocks can be stored plain, compressed and using a special method which pre-separates the different parts needed for execution. (XIP stands for eXecute In Place, which I guess really refers to only this third storage method.)
(Within this third storage format, we differentiate between files meant to be copied to RAM and executed and files which are left in ROM and executed, but that's beside the point.)
These XIP blocks are chained, and XIP blocks on one side of the chain take priority over blocks on the other: i.e. if a file appears twice, only one is shown.
Now if you write to a ROM file, a copy is made in RAM, which takes an even higher priority, so it looks like you overwrite it. But if you delete the RAM copy, the ROM-copy appears again.
At cold-startup, the system parses a file called initobj.txt which holds commands that tell it which directories to create and what files to copy where. So all files which appear at cold-boot in locations other than \Windows are RAM copies of ROM files in \Windows.
Dear XDA developer Peter Poelman
thanks alot for the quick answer ...
Let me put my "Previous" understanding :-
In the XDA/QTEK we have three areas :-
1. ROM as STORAGE . (similar to the harddisk on a PC)
2. First half of the RAM as STORAGE . (similar to the harddisk on a PC)
3. Second half of the RAM as RAM . (similar to the RAM (SDRAM/DDRAM etc) in the PC).
Accourding to your replay , the above is some how correct BUT :-
__________________________________________________________
1. (through XIP concept ) The programs/DLL's which are stored in the ROM or RAM(First half) are NOT loaded to the RAM(Second half) when they are EXECUTED/RUN (like in the PC).
Which means that
- a programmer will not care how many DLL's she/he uses as they are ALL "loaded by default" (except the ones in the SD card) ?
- the user will not care if he run many many pograms as it will not overload the RAM(second half) ? so we don't need to "CLOSE" programs running to speed up the device ?
__________________________________________________________
2. All ROM files are in \windows directory ONLY.
__________________________________________________________
3. ALL files in the \windows directory are actually in ROM after the hard rest directly ?? , Is it ??
(This explains why the system when we try to access \windows directory take time as it reads from both ROM and RAM)
__________________________________________________________
3. If a duplicate file is copied into the same directory in \windows or any of its subdirectories , it will only "COVER" the old version and when ever this new file is deleted , the old version will APPEAR again like its spirt or a ghost :shock:
__________________________________________________________
4. At the cold-startup (when we do hard reset) , the system uses the file initobj.txt (like the installation scripts in PC) to creates the needed copies of the files (in \windows) in the RAM(first half) area like the registry file or configuration files needed by the already installed programs (pocket excel .. etc) and it will "COVER" the read only version of these files.
5. The concept of Cylinders/traks/sectors/FAT .. etc is not in the PDA ?
__________________________________________________________
More Questions
a. Is there a source where one can find more in depth information ?
b. Is this file system an xda/qtek thing or is it an MS windows thing ?
3. Can a program running on Pocket PC itself (i.e. a Virus) overite the ROM (the orginal copies (ghosts) not the new ones) ? (and therefore i can't get rid of it even if I hard reset !!!).
4. Can a program running on a PC (i.e. Virus) replaces ONLY one or two files (The ROM copy) ?
.... if NOT , then how did the Jeff's version of the XDA-Developers ROM (which runs on the PC) replaces the ROM ?
5. thanks alot ..
waleed said:
1. (through XIP concept ) The programs/DLL's which are stored in the ROM or RAM(First half) are NOT loaded to the RAM(Second half) when they are EXECUTED/RUN (like in the PC)./quote]
Most are loaded to RAM, only very few are actually executed in ROM. Itsme and W4XY know more about this than I do.
Which means that
- a programmer will not care how many DLL's she/he uses as they are ALL "loaded by default" (except the ones in the SD card) ?
- the user will not care if he run many many pograms as it will not overload the RAM(second half) ? so we don't need to "CLOSE" programs running to speed up the device ?
Click to expand...
Click to collapse
If they were running more from ROM this would be true, as it is they aren't.
2. All ROM files are in \windows directory ONLY.
Click to expand...
Click to collapse
Correct.
3. ALL files in the \windows directory are actually in ROM after the hard rest directly ?? , Is it ??
Click to expand...
Click to collapse
You can read this sentence multiple ways, but if you mean what I think you mean, you are right.
(This explains why the system when we try to access \windows directory take time as it reads from both ROM and RAM)
Click to expand...
Click to collapse
Very possible.
3. If a duplicate file is copied into the same directory in \windows or any of its subdirectories , it will only "COVER" the old version and when ever this new file is deleted , the old version will APPEAR again like its spirt or a ghost :shock:
Click to expand...
Click to collapse
Correct.
4. At the cold-startup (when we do hard reset) , the system uses the file initobj.txt (like the installation scripts in PC) to creates the needed copies of the files (in \windows) in the RAM(first half) area like the registry file or configuration files needed by the already installed programs (pocket excel .. etc) and it will "COVER" the read only version of these files.
Click to expand...
Click to collapse
The ROM copies remain in the \Windows directory.
5. The concept of Cylinders/traks/sectors/FAT .. etc is not in the PDA ?
Click to expand...
Click to collapse
It is on the SD-card, not in the ROM.
a. Is there a source where one can find more in depth information ?
Click to expand...
Click to collapse
No idea...
b. Is this file system an xda/qtek thing or is it an MS windows thing ?
Click to expand...
Click to collapse
WinCE, PocketPC, WM, i.e. it's a Microsoft thing. Works the same way on iPaq's for instance.
3. Can a program running on Pocket PC itself (i.e. a Virus) overite the ROM (the orginal copies (ghosts) not the new ones) ? (and therefore i can't get rid of it even if I hard reset !!!).
Click to expand...
Click to collapse
Yes.
4. Can a program running on a PC (i.e. Virus) replaces ONLY one or two files (The ROM copy) ?
Click to expand...
Click to collapse
Yes.
if NOT , then how did the Jeff's version of the XDA-Developers ROM (which runs on the PC) replaces the ROM ?
Click to expand...
Click to collapse
It uses a program called 'Programme A', which is the official HTC upgrade toold for the ROM. It in turn uses a program it loads into device RAM. This ARM program stops WinCE/PocketPC/WM and accepts data from the desktop (where 'Programme A' has sedated ActiveSync) over serial or USB to flash into ROM.
Click to expand...
Click to collapse
I've got lots of .dsm and .rgu files in my Windows folder, for example
12e09329-dd44-jhg589856-jh2525656598.DSM or .RGU
they're about 1 to 20k big. About 40-50 of them sit on top of my Windows folder.
have you got them too? What are they there for? And can I get rid of them?
They seem to be "hidden in rom" though, as they appear when the option "hidden on rom" is ticked in total Commander.
they also appear on my desktop's Explorer , throuh Windows Mobile/MyWindowsMobiledevice/Windows (or similar path)
Thanks for you help!
I think it is some digital cert for granting application access. If you delete it, you will be asked some applications is not signed and do you want to execute it. If you say yes, it will create this file again.
right. Have you got them too, or is it only me?
Yes, there is some in my k-jam too, from the timestamp you will know it is created when you installed some applications each time.
and what about this directory
\Windows\OEM on my qtek 9100
It contains MFC80U.dll
and msvcr80.dll
it looks like visual studio files and I don't understand what it does in my user memory.
Either it should be in WM5 files or It should be removed.
What do you think?
Regarding Bynaris Smartexplorer it is the best for smartphones clearly but:
1 - it is not a task manager, it is a file explorer
2 - it has been design to be used with numeric keypad shortcuts on pocket pc it is a pain to use.
However I really like its quickness.
I will just wait for a more pocket pc friendly version before I replace resco explorer.
ABOUT
The purpose of this CAB is to reach a sort of UC way but with a very easy & friendly approach
HISTORY
I come from Diamond world, so because this CAB can be adapted for other platform/devices why not preparing a separate sUC.cab to use for enabling ALL the stuff (ramdisk, pimbackup,ram recovery,etc...) included in Dia Duit rom series?
what have I to do with this cab?? simply it will apply these features:
Latest stable MortScript is inscluded & ready to go, so no more needs to install as separate cab
Choose between 3 speed profiles: 1. fast (takes more ram & battery), 2. balanced (not heavy tweaked but not funny) & 3. untouched (default WM6 settings)
GPS profile: TomTom, iGO, Navigator or default WM6
Everyday auto recover RAM feature (at 4.30AM) + automatic sms/contacts/calls backup/fav manila people (trough pre-configured pimbackup app, PimBackup included)
Ramdisk (2Mb) feature (optional)
A new way for a fully automated CAB/REG/EXE/CPY installation/copy after every hard-reset/rom upgrade
UPX executable, compress (fully automated) exe files from fresh installed cabs, this saves space & gives faster app load times
Easy & fast tweaking method without 3rd part software: tweak registry scripts (with comments)
Tips enabled by default to preserve a bit more battery life (for ex 3 secs of led blinking instead 5, increased battery life counter,etc) + increased speaker sound volume + many example for setting automatic alarms, rings, etc...
Moved MAIL + Attachments folders from main memory (My Device) to external one (Storage Card)
3 / 4 rows configuration
This should work on every WM based rom, also because I added the auto recognition of "Storage" name... so should work without troubles also on NON WWE roms (except for CABi installation)
DOWNLOAD sUC.cab HERE
DOWNLOAD sUC_source.zip HERE
BEFORE INSTALL (mandatory)
create in your "Storage" (the BIG one) a folder called "Backup and Restore", then inside it a folder CAB (inside this another folder called CABi), then at the same level of CAB folder create a folder called CPY, then REG, then EXE
so practically your basic structure should be like:
Code:
Storage Card (or whatever name)
=> Backup and Restore (folder)
=> CAB (folder, put here all the cabs you want install on main memory)
=> CABi (folder inside CAB folder, specific for "must go into Storage", see notes)
=> REG (if present all reg files here will be joined to default WM registry)
=> CPY (if present all files here will be copied under their correspondent folders)
=> EXE (if present all .exe & .mscr files will be launched)
all files in the CAB folder will be installed (automatically) into "device", the ones in the CABi folder will be installed into "Internal Storage" (or whatever you have, always automatically), from REG folder all *.reg/*.rgu files will be loaded on the fly, from CPY all files will be copied (with overwrite) into correspondent folders (for ex useful for copying personal dlls, wav/wma/mp3 files or background, etc...), for finish from EXE folder will be launched your executables (personally never needed, but who knows?) & if present all *.mscr scripts... pay attention to exe files that needs user interaction
INSIDE THE CAB (a deeper explanation)
when your sUC cab is installed it simply creates a registry entry under [HKLM\init\]"Launch69"="2ndboot.exe", this permits the script 2ndboot.mscr (launched by 2ndboot.exe) to be loaded upon system reboot (just one time)
this script, if the structure mentioned above isn't found, it will create automatically all the folder & default reg files needed under your storage card, the name isn't important because it should guess itself its correct name, so don't care if your storage is called something like "MyBigStorageCard"
then it will ask you some questions... such as if you use ActiveSync, which GPS performance adopt, etc... all this info, which at 1st you'll pay high attention, will be stored under your storage card in a file called config.txt ...why?? simple... because next time you will flash or hard-reset your phone you wont have to push a button the script will found that previous stored config file & it will take all the info needed for final rom configuration to skip all annoying questions after every upgrade/HR
note: there is also an hidden option that should be used only by experts, to enable this option simply add by hand to your config.txt file the line: FastInstall=1
this will skip all countdown menu & messages... personally I use this option because flashing a lot this saves much time more
next it will look in the CAB folder for installing your CABs into "device" or main memory
next in the CABi folder for installing CABs into your storage card (you need to do this just 1st time, I'll explain later...)
next it will look at a file called upxlist.txt (must filled before), where simply you will specify all the *.exe file you want to compress after every cab installation... for example your upxlist.txt could look like:
Code:
\Program Files\Navigator\TomTom Navigator.exe
\Program Files\9.5 Beta\Opera9.exe
\Internal Storage\Program Files\Binaryfish\All Mobile Mines\All Mobile Mines.exe
note: every line for every EXE file, pay attention that you can compress just EXE files coming from extra CABs, because EXE files present in the rom are read-only
next it will copy a set of basic reg files with many tips/tricks/examples inside, useful for making many customizations
note: of course if you have previously prepared the folder structure & you have copied your REGs files under the REG folder they will be processed together the files above
next it will look in the CPY folder and will replicate the found folder structure (with files too), for example create inside it a folder \windows with some file inside & it will copy all found files under \windows on your device, or create \program files\myapp & it will create that folder structure in your device, of course it works also for Internal Storage even if it has no sense, anyway just a note it doesn't create empty folder, to create an empty folder just use a single .mscr script (something like: MkDir("\mydir") ) & copy it in your EXE folder
next it will look in the EXE folder & will launch all the exe files inside it, if found it will launch also all *.mscr scripts
next if found (you'll understand better upon an HR), it will ask you to restore your backed-up start menu, so you don't have to re-arrange your icons again
next if found, it will ask you to restore your last PIM backup & will reboot
notes:
right now CABi procedure works only on WWE roms (due to translations work to be finished), anyway there is a trick to skip CABi installation, or better make by hand just once (read few lines below)
installing cabs into Storage Card sometimes will fail, this simply because some cabs need confirmation/accept license & so on, so don't expect will work 100%, also many cabs require to be installed into main memory so NOT into Storage Card, for ex I use to install into Storage Card simple cabs such as games
sometimes pim backup restore can fail, try to restore by hand after installation; backup are divided into week days (monday, sunday, etc... "Last" is the last saved backup)
if you put sUC.cab in your CAB folder wont re-processed of course, useful if using sUC together with UC/UC2 installation method (see at bottom)
if you still use the 1st sUC release way your personal scripts still work like before, simply move them under EXE folder, or transport as reg entries directly into your personal reg file & copy it under REG folder, you can find on the same folder some examples (to clean all your old stuff simply empty the REG folder, modded REG files wont be touched on future upgrades)
you don't need to re-install every time your CABi, just install them once, then on next upgrade answer No or simply edit your config.txt & change the correspondent value; after CABi installation on a clean boot go with your explorer under "\windows\start menu" folder & re-organize your start menu structure (cut/past links, create/delete folders, etc...), remember to don't delete "Settings" folder even if empty, then go under sUC menu & backup your StartMenu, on next upgrade sUC will detect start menu backup & it will reinstall automatically... because the content of your storage card isn't erased after a rom upgrade/hard-reset your installed CABs will stay there untouched, so backed-up start menu has inside correct links
is possible to move TomTom, iGO, Navigon, etc... definitively into your storage card, so you don't need to install them every time: copy entire nav software folders from \program files to \internal storage\program folders, re-create icon shortcuts (copy/past as shortcut in your start menu), for iGO you have to edit sys.txt (under iGO folder) & change the path of base installation
in the same way is possible to skip for example FingerKeyboard installation from related cab, simply take a look at this short guide
INSTALLATION
note: to migrate in every new sUC version simply move your reg mods in your Personal.reg file, erase all the rest of reg files because they will be re-generated with the new ones, remember that on upgrades reg files wont be touched so pay attention on what you mod
if the rom is UC compliant simply create a called SDConfig.txt file in the root folder of your Storage Card, for example your SDConfig.txt could look like (pay attention to upper-lower case & no empty lines):
Code:
LOCK:Enabled
CAB :\Internal Storage\Backup and Restore\CAB\sUC.cab
LOCK:Disabled
RST: Reset
in this way at reboot will start standard sUC procedure (remember MortScript is included & also that sUC cab wont be re-processed even if present in CAB folder), instead if the rom isn't UC compliant simply install sUC as any normal cab, then it will ask to restart (or restart manually) & automated procedure will begin on reboot[/b]
bye,
davide
OK, that's all very nice, but WTF is it?
Wouldn't hurt to have an "about" section in the post for ppl who see this thing the first time in their life.
GENIAL !!!!!!
aiiro said:
OK, that's all very nice, but WTF is it?
Wouldn't hurt to have an "about" section in the post for ppl who see this thing the first time in their life.
Click to expand...
Click to collapse
yep... you right sorry, I'll correct soon...
suiller
OMG~ You finally made it available!!! I'm going to test it with my HD and will report back once everything is organised
I didn't mean to sound rude, sorry... Anyway, thanks for the addition, but still - what is UC? User Configuration? Could You post some screenshots too to make it more comprehensible for dumbusers like me?
jackkkkk said:
suiller
OMG~ You finally made it available!!! I'm going to test it with my HD and will report back once everything is organised
Click to expand...
Click to collapse
oh FRIEND! I found you
yep, I'm looking here around to see if my mad projects can be useful
the cab isn't still perfect but should work, of course I haven't a different device from diamond so all you will be a sort of beta tester
I've removed all specific diamond stuff, so it should work
Of course this is just a starting point, I'm dedicating much time to develop this small piece of "software", thx also to many other friends
You know as it works, so you should feel a bit like at home
aiiro said:
I didn't mean to sound rude, sorry... Anyway, thanks for the addition, but still - what is UC? User Configuration? Could You post some screenshots too to make it more comprehensible for dumbusers like me?
Click to expand...
Click to collapse
yep you are right... UserConfiguration, the only difference is that you don't need to write any config file, at least not as "normal" user, it's enough to copy under correct folders the CAB plus other stuff you want installed/loaded after every flash/hard-reset
I'll porvide soon a video-guide, so it will be for sure more clear
OK, OK, nuff with making fun of me Or were You seriuous with video guide?
Cos I just had a brilliant idea - I'll install the damn thing and look for myself
I think I should have done that in the first place. But still, I believe screenshots would save some time understanding what's it really about.
Yeah Screwed Up Click for life
no no I'm serious friend... but I'll suggest to wait a couple of days because I'm working on a new version where is possible to cut-off all the specific HTC/manila stuff & above all I'm re-commenting all the registry entries that interact with OS
no no I'm serious friend... but I'll suggest to wait a couple of days because I'm working on a new version where is possible to cut-off all the specific HTC/manila stuff & above all I'm re-commenting all the registry entries that interact with OS
Hi,
really don't want to be rude or offence, but ... isn't this something like SASHIMI????
If so ... where are sUC's pros?
kind regards
fwt
almost... but it's very very simple... I'm testing an heavy modified version able to run on almost every WM6.x base device
OK the CAB is ready for testing purposes... please re-read 1st post because I'm making a better, I hope easier, description of features... thx
bye,
davide
Mate, this piece of software is plain GENIUS!
So much easier than the UC thing, with all the boring scripting. This way you just place in folders, and you are (mostly) done! Amazing stuff!
I have some questions/requests for you though...
Is there a way to repeat the procedure (restore at 1/2 start up), at a later time? This could be useful, for example, if some files get corrupted, or you just want to revert back to default cabs/settings, etc. So I guess what is needed is a way to manually activate the procedure.
Second thing is regarding mail settings. Is there a way to back this up? My hotmail settings get destroyed after every HR.
Cheers.
Forgot to mention, a manual activation of this procedure would also help if (for example) you want to make multiple program installations. This way you could just use the folder CAB, without wasting time on every single program you are installing/testing...
Cheers
krale said:
Forgot to mention, a manual activation of this procedure would also help if (for example) you want to make multiple program installations. This way you could just use the folder CAB, without wasting time on every single program you are installing/testing...
Cheers
Click to expand...
Click to collapse
hmm... it could be a good idea... even if some phases can't be reverted, or better it's very complicated to "go back"... such as for ramdisk
anyway many phases are yet accessible as indipendant scripts just take a look under "\Backup and Restore\scripts" folder, of course other script could be extrapolated but I'll do probably on next version... let's say this is a testing purpose version because I have to "think" that this app must work on many (almost all I hope) wm6.x based devices
As one of the end (l)users who first saw this in Suiller's Dia Duit rom series, I can attest to this resolving one of the major grievances of Windows Mobile rom-upgrades. With some "smart" planning ahead, getting everything back can now be mostly scripted by simply placing the install file in the correct directory. Same with restoring data from your pimbackup, or adding registry settings. Once again we have a case where the xda-developers have surpassed the "offficial" roms in user friendliness.
I have since moved on to WM6.5 (still on my Diamond), but I sorely miss sUC from my later roms.
//Svein
updated sUC, corrected some small issues
I corrected some default/samples reg files, so I suggest to erase all default *.reg files under REG folder to update correctly
move your personalization to something like "MyRegPers.reg"
please reports here bugs/issues/suggestions or whatever... thx
Hi guys,
Recently i have noticed tha my t9 words are not working
I found this on xda
Directory("\Windows"):-Directory("ET9IMEDB")
Directory("\Windows\ET9IMEDB"):-File("eT9AsDb.Adb","\Windows\eT9AsDb.Adb")
Directory("\Windows\ET9IMEDB"):-File("eT9Rudb.Rdb","\Windows\eT9Rudb.Rdb")
but when i added it to initflashfiles.txt, all the files look like on the screenshoot
when i simply change a name of \Windows\ET9IMEDB to \Windows\ET9IMEDB_t, and change it back again to ET9IMEDB, files are normal, but after soft reset its the same story
so i did a mort script
Rename ("\Windows\ET9IMEDB\", "\Windows\ET9_temp\")
Rename ("\Windows\ET9_temp\", "\Windows\ET9IMEDB\")
and added it to StartUP folder, it works, but i want to know what is causing it
thanks for help in advance
Billy
ps. I am using leo3.02 IME packages on Topaz Rom
Wow, I'm glad I clicked this. I've run into the same crap many times. My temp fix is the same as yours. I don't use et9, but this has happened to me w/ several apps that I've relocated to windows, like ucweb. My only fix is to get corruptable files/folders oit of windows.
yeah, but you can't get this folder out of windows, cause it must be located there
Have you looked in the .reg file in the package? There may be a key in there that sets the path.
The files would get corrupted every time I would soft reset.
I'll add that for me, I've run into several apps that would give me corrupted files. Usually, it was apps that I'd relocated from \program files into \windows (to save storage space). For instance, Bing would do this to me. The rom files were fine, but the sub-folders would become corrupted after every soft reset if they were in the \windows folder. In particular, the XAML folder would go wonky. The fix was to rename it, then name it back. I'm sure you figured this out the same way I did: you couldn't delete the corrupted files/folders, or copy them, or anything, unless you first renamed them (lucky that worked). When I'd rename the folders, I'd notice that the files inside were no longer wonky. I made an EXT for FpseCE that was relocated to \windows, and all six sub-folders would become corrupted after a soft reset. It was a royal pain to rename them, so that was basically when I decided it wasn't worth the saved storage space to have the apps located in rom, so I moved FpseCE, Bing, and UCWEB (the CDDATA folder would go bad) to program files. The other app that would mess up on me was Weather2go (a today plugin). The Weather.dat file (located in \windows) would go bad for maybe the first 4 or 5 soft resets after a flash, but then it would mysteriously become stable. It was annoying as crap, because the plugin would go blank and not show the weather forecast after a reset. I don't know why, but now it works fine. Perhaps it's because I took the other 3 apps or so out of \windows. The really weird file that would screw up on me was an ID txt file for SK Today Commander. SK software puts an ID text file in windows for all it's paid-for apps. I have maybe 5 of their apps, and the files were fine for all of them except today commander. It would become corrupted at each reset. Now, it doesn't happen any more to me.
I wish I knew why it happens, but I don't. Now, if I'm making a package for a new app, I will test it before flashing, and do several soft resets to make sure that none of the files that might be created by the app are not corrupted after a soft reset. It's been a couple of months since I had the problem.
I looked at the xt9 package I have, and it looks like you can relocate the entire thing to another directory. It will be a pain in the butt, but if you really need it it might be worth a try. There's an installdir key that needs to be changed (from \windows), plus many keys for the path to all the dll's. I don't see a path for the databases, but they will probably move to the new location (assuming you change all the paths).
now i had finished all correctiong all errors for my rom (new packages from Oobe and Huashan) and new manila, i was using topaz ext before, but is it time to change it for a fresh apps
so i will have time to find solution for this, it may be to many files in rom, first i will try to remove some apps, my nhb file has 230mb, so it could cause problems in filesystem, we will see
I doubt it's that, but you never know. My rom is pretty light (only ~2500 files). I tried Task 29, and that didn't do jack squat. Moving things out of \windows was the only thing that worked. I guess maybe moving to osbuilder could help; maybe the module allocation in EVK is causing issues. I've never had S.O.D. before, but I have had this plenty. It's pretty clear that something hinky is going on during boot-up, though.
well i am using osKitchen v1.31beta10, so it's not EVK problem
OsKitchen and EVK are pretty much the same, though, aren't they? They both run platformrebuilder; I'm not sure if they handle modules the same way, but I suspect that they do. Osbuilder is supposed to do a better job of it, but the thought of converting all my packages over makes me want to hurl.
I figured out what is going on with this (sort of). I don't know why you get the corrupted files/directories in \windows, but I know how to avoid it. Files/folders become corrupted after a soft reset when their names are all capital letters. For instance, if I have a folder named \CDDATA in \Windows (or \XAML or \BIOS-those are from Bing or fpsece), then any file inside that folder will become corrupted after a soft reset (except for .lnk files, go figure). So, the key is to just rename the folder with lower case letters. In the case of UCWEB, which used the CDDATA folder, it works just as well with a folder named cddata, except that I can soft reset the device w/o issues. I'm assuming that Bing would work with an \xaml folder, and fpsece would work with all 6 of its sub-folders being named in lower case.
The same thing happens with files: if their name is all capital letters (inc. the extension), then they become corrupted after a soft reset. Renaming them fixes it (same with the folders). Anyway, this is why the OP's files go wonky in the \ET9IMEDB folder.
Like I said, I don't know why it happens. I get it with EVK roms and OSBuilder roms.
Farmer Ted good find, thanks
Hi guys
While looking through my registry using Total Commander, my phone had a little fit and decided to rename a folder. I didn't see what the folder was called before my phone called it ,, and then crashed.
Now nothing is working properly, such as Comm Manager or my signal, I assume because they are pointing to the folder that has been renamed, and which needs to be changed back to what it should be called.
I would attach 2 pics of the problem - the first of the parent folder and where it sits in the registry, the second of the folders that appear in the problem folder - but as a new user I can't, so hopefully I can PM these?
Does anyone have any idea what the folders in \\\registry\HKLM should be called so I can change it back to what it should be? All I know is that it starts with a letter around m-p.
I really don't want to have to hard reset.
Thanks in advance for your help!
You have;
MUI, contains 2 keys for SysLang
nls, contains subfolder Overrides
Platform, contains 2 keys for Provxml
I've got the MUI folder already, but thanks for replying
What about nls and Platform?
You said m-p, right?
I have those as well. I assume it's m-p due to what folders I saw before it crashed. I guess it could be a folder around that area though
Cheers for your help
I gave in - hard reset it was!