So First of all Apologies - I am having a low IQ week I guess You run it at your own risk!Ĭoncerning Mortscript: It's far out of this thread's scope to go into more details here. Warning: Running a script as printed above may unrecoverably brick your device. Not to forget, you also have to put files "RegFlushKey.exe" and "RestoreDefaultHiveFromROM.exe" into root of SD-card. Finally you edit launcher-file shell.ini which also must be in root of SD-card as following: "\\RegistryFixer.exe" - without the quotes, where you replace term with CE's name of storage card, ex.
#Pmp.exe windows ce code#
You create an ANSI text-file containing the lines of code printed, rename it to RegistryFixer.mscr and put it into root of SD-card, too. You rename Autorun.exe to RegistryFixer.exe. Some devices with hive-based registries don't save registryĮndSubYou put into root of SD-card Mortscript.exe, Autorun.exe. Keep in mind that even re-flashing a device doesn't correct any errors given in User.hv portion of registry.Ĭode: // Clean the entire Make sure device's initial default values get imported All errors there last unless they become fixed by user. What you citied only relates to Default.hv and System.hv, but in no case to User.hv.Īll changes made to a hive-based registry by user (User.hv portion of registry) will never be touched/corrected by OS. The hive-based registy always consists of 3 parts: Default (Default.hv) - hardcoded in ROM, System (System.hv) - hardcoded in ROM and User (User.hv). If it has changed, the links between the ROM and file system parts are broken, and Filesys.dll performs a clean boot of the registry by deleting the files and recreating them, based on the initial ROM version. When the registry part from the file system is loaded, Filesys.dll verifies that the ROM portion has not changed. Thanks so much for your support here - I have hope I don't have a brickĪn MD5 hash of the ROM file portion is stored in the registry part that resides in a file system.
#Pmp.exe windows ce how to#
Have read about a regformat.fmt file and 117_nav_en files which have recovered some of these devices - Now if only I could figure out how to get them to load up
Have tried renaming a couple of other reg editors to CE explorer - No luck I only get a blank screenĮmerson (The seller) has promised to work with his technical team and get back to me with a solution (updated firmware / Factory reset method)Īt present I am also trying to explore some method of doing thisĪn MD5 hash of the ROM file portion is stored in the registry part that resides in a file system. CE Explorer does not work (Did not at any point)
0 kommentar(er)
