before I install a cab file, I examine a cab file thorough. I notice a lot of difference between different versions of cabs or cabs from different creators.
The values "Order", "Index" and "Flags" in the drivers section of HKLM differ a lot between the cabs, but they all seem to work.
I tried to look into the function of these values to see if they matter and if there is an optimum configuration.
could it have something to do with boot loading order, priority
Arjan
Related
How can I make a registry modifying only cab, that doesn't require files to be added??
So far, it seems that adding SourceDisksFiles and other required sections like this on the .inf files won't allow to create a registry modifying only cab file... :?
Yes those sections of the inf are mandatory.
To create a cab that only modifies registry you need to put your modifications in the form of an xml file, name it _setup.xml and use makecab.exe like this:
makecab /D COMPRESS=OFF _setup.xml mycab.cab
Do not try to use cabwiz because it will change the file name inside the cab.
To learn how to formulate registry changes as xml look in MSDN under Configuration Manager and Provisioning a device.
Hi Guys,
There are quite a few Registry hacks listed on this site, could someone develop a simple program that could read xml files in a directory and present them in an orderly manner, like HTweakC does...
Package the registry tweaks into a simple xml file that the program could read.
For example:
Menu Structure, ie Security, Today, Bluetooth
Title,
Description,
Registry Tweak.
On Program startup the program could read the xml files in a specified folder and order the tweaks according to the Menu Structure in the xml file.
And while you're at it an undo option wouldnt go amiss either.
Each change could be saved to an undo folder... or something.
Howdy.
Does anyone know of an autorun.exe which is coded to look in "extendedROM"? (As opposed to "extended_ROM").
I'm aware of PocketPC Installer and that it probably can create a custom autoexec.exe for me, but I'm looking for a free solution if there's already one hacked up out there.
Thanks
--SUmmiter
I thought that it got that value from the registry:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Extended_ROM\\AUTORUN.EXE"
"AutorunCFG"="\\Extended_ROM\\CONFIG.TXT"
"AutoRunType"=dword:0
"TurnRadioFlag"=dword:0
Yes but you have to add this into rom before building if you want it to look for autorun there after flashing
Right. My possibly incorrect assumption was that autorun.exe is hardcoded to look inside "Extended_Rom" for it's config, ignoring what is in the registry. I'll mod my OS rom and try changing AutorunCFG and see what happens.
joemanb said:
I thought that it got that value from the registry:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Extended_ROM\\AUTORUN.EXE"
"AutorunCFG"="\\Extended_ROM\\CONFIG.TXT"
"AutoRunType"=dword:0
"TurnRadioFlag"=dword:0
Click to expand...
Click to collapse
Autorun.exe and config.txt can be anywhere as long as the registry points to them.
(if the registry points to Extended_Rom, then of course the files need to be included in the Extended_Rom.)
My autorun.exe is in windows, and config.txt is in the extended rom, but I've tried it other ways and it's worked.
alot of cooked roms use this feature to do a final modification like loading a theme from the windows directory.
BTW config.txt contains the paths to the files you wish to process, so it doesn't matter where autorun.exe, or config.txt are.
In other words, you could put autorun.exe, and config.txt in windows or anywhere else as long as the registry points to them, and it will process the files on the paths contained in config.txt
Little question, has autoexec any link in startup, or not?
(I make in intiflash registry entry es mentioned before, I have hope corect congig.txt but after HR ... nothing, co customization . Interesting is, that I can launch autoexec in ext rom manualy and it runs ok. I rebuld quite naked WM 6.1 rom)
Thx for help...
I am using Visual Kitchen to build my ROMs. There are five types of files that are used to eventually create the registry: *.hv *.rgu *.reg *.provxml *.xml. I'm trying to find a program that takes all these files one by one and create ONE *.rgu file. When adding keys to the One.rgu the program should check whether the key exists with different value and ask the user whick value to keep. Is there a program like that? Could someone make one? I am not a programmer myself so i can't do it but i believe that this would be very useful for all cooks.
Hello all. I am being driven crazy not being able to make this work. I am trying to set all my theme elements in my ROM via registry in the kitchen, so as not to have to wait a few seconds for the TSK (Livven SimpleGloss Blue) to be formally set via RunCC. I can get everything working except for one color. Where I have it set to be 0000ff (blue) in my TSK, when the ROM boots it is an awful teal color. This of course goes away as soon as I go tot start>settings>home and set the theme. What I have done so far is take the TSK, open in WinCE Cab Manager, export all its reg's and files and put the registry into an app.reg and files into the files section of my EXT package (I use platformrebuilder in my kitchen). My registry entries look exactly like my TSK registry (I compared with windiff). What am I missing here? I hae heard that there might be issues with exporting the long binary regstry values in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Color... But I think I exported them correctly? (they are identical when copied and pastes and when exported from ceregeditor from the running ROM..)
Any idea?
THANKS!
EDIT: I have removed all the values in mxipcold_wpc_2.provxml.
solved...
there is a registry key that I cannot explain how it gets set, since it is not visible in the TSK file when viewed in Wince Cab Manager:
HKEY_LOCAL_MACHINE\System\GWE\SysColor
I ended up flashing the ROM, letting it boot and verifying the ugly teal was present. I then dumped HKCR, HKCU, and HKLM using CeRegeditor. I applied my tsk and dumped the keys again. I compared with Windiff. HKCR was identical. HKCU and HKLM were different as I was expecting. I would have never found HKEY_LOCAL_MACHINE\System\GWE\SysColor if it weren't for Windiff.
:-D