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.
Related
Hello professionals ;-)
i have to delete some registry keys during an softwareinstall with a cab file.
Can anybody tell me how to make an installationfile (like *.cab ore something else) deletes some keys in the registry!
whatfor?
i want to install some programs (like pocket plus) and make some configuration during cab file installation. so i looked into the registry what changes when i configurate pocket plus.
as i noticed there where som keys changed i can overwrite with the new values BUT there are some registry keys deleted also. How get them out???
is there any way ??
Have a look at creating a custom setup.dll file to include in the cab file.
You can certainly delete registry entries using it.
I don't know about deleting registry using cab files.
I think there is only options to allow or not to replace a registry key if exists during install.
Here a good link for .cab files Cab files
Apart that you can make your own install from PC to Pocket using RAPI. With that no problem to delete keys, copy files, add new keys ...
want to delete some keys bevore install
Thank's for your tips!
Have a look at creating a custom setup.dll file to include in the cab file. You can certainly delete registry entries using it.
Click to expand...
Click to collapse
is there more information about this ?
how it works?
how to do?
as i looked at the CABFiles Website this looks very complicated to me ;-(
i am an absolute beginner in developing software!
i need an easy way to delete some regkeys during installation.
I think you can use the excellent scripting utility called nScriptM to achieve your goal. Simply run a search on this in google and you will come across a number of resources including the download location.
k_kirk said:
I think you can use the excellent scripting utility called nScriptM to achieve your goal.
Click to expand...
Click to collapse
i will try this, Thanks!
Hi, i have an Herald with the original windows mobile 6 executable i downloaded on a website and i extracted the RUU_signed.nbh, then i used Hypercore to get the OS.nb and then i got the OEM and SYS folders to start building my ROM the way i like it. First i thought about including my own registry modifications and i know those modification have to be installed in the device at the end of everything to over write the default that get install first so in the OEM folder i created a sub folder i called zzz_My_registry_OEM. As you can see, my attempt there is to put the .rgu file in there and because the name of the folder start by zzz, it will obviously be installed at the end. Is that right? Because if i'm wrong please tell me, i never did that before, its my first time cooking a ROM. Then, i face a new problem. I have the complete list of all the registry tweak i want to put in the .rgu file, i know i have to begin the file by REGEDIT4, the lines starting by ";" are not recognise so i can put a note of what the registry is for (for personnal reminder), then at the end of all my registry tweaks, i have to leave a blank line but... I just dont know how to write the lines properly because i know its some sort of code and i have to write in code. I'll show you precisely what i mean. Here i have a tweak to change the temp file to the storage card and it goes like this:
HKEY_LOCAL_MACHINE\System\FileSys
edit temp path key \Storage card\Volatile
Here an other one to change the language of the slide out keyboard to US:
HKEY_CURRENT_USER\ControlPanel\Keybd
create a new string
Name: Locale
Value: 0409
The problem as you can see, that is good if i tweak the registry of my already installed ROM from a registry editor, thats not valid for a .rgu file while cooking a ROM. But i have no idea how to write those codes properly and i found absolutely no instruction no where. And i have a lot more tweaks like that that i want to do. Is there any one here willing to link me to a detailed and intelligent tutorial or to translate my reg tweaks for me so i can finally nail that once for all? I thank you all in advance for your help. Anything could help because even if you dont have a complete answer, i'll do the job of reading the post and take all the bits together and figure it out. Some of you know a little bit that will complete some that an other one know to finally form the big picture.
I was hoping someone could help me out. I've been trying for a while to make a working OEM out of a few sense 2.5 cabs. At the moment I have 2 to choose from, one posted on modaco(thread http://www.modaco.com/content/i8000...07676/noobody-and-rapid-sense-2-5-rom-nxxje2/ and file link http://www.4shared.com/file/uV-HPoiM/nOObody__Rapid_Sense_252011_Rh.html) and http://www.freeza-inc.com/freezaROM/OEMCAB/fi. Sense - 2.5.2011.3030 for WM6.1 beta.cab(makes it easier, these cabs include full package, I've tried grabbing oem's from ppcKitchen with limited success). I was hoping someone could post a tutorial about converting cabs like such ^^ to an oem package for use with buildOS. Thanks in advance for any help.
This should help
http://forum.xda-developers.com/showthread.php?t=467842
When I use that tool the oem will build but not work. I've tried a few other tools but they also don't create working oems. cab2oem, oemizer etc.
I don't use sense, so haven't installed the cab, but here's how I make more complicated packages: Run sk tracker, and take a system snapshot. Install the cab, and run sk tracker again and take a second snapshot and compare the first two snapshots. Copy all new files to your oem (or EXT). Export all new reg keys to an app.reg or .rgu. My guess is that all the files go into \windows, so you won't need to deal with initflashes.txt files or app.dat files. You may need to get sense running (if it isn't running after the cab install). If you have to start it up (may require a soft reset), then run it and take a 3d snapshot. Compare shots 2 to 3-there could be a few new registry keys. Most are going to be in obvious places, like HKCU(or LM)\software\HTC\Manila, but you may have some certificates installed in odd places as well as random crap you'd never find without sk tracker in HKCR. You probably need all of these keys. The problem with just using an oem creator is that there may be reg keys installed by a setup.dll, or reg keys installed when the program first launches, and you'll miss these.
Remove any setup.dll from the package-it won't be needed. And since you're using buildos, I guess you'll need to create a .dsm (have fun with that-nicest thing about EVK is you don't need them). I guess there may be a startup shortcut, so you'll need the initflashfiles to get it in \windows\startup, unless you use an HKLM\init key to start sense up.
look at the main stickie or kitchen tools repository thread search for cab converter it works... but if your cab has a setup.dll will be hard you need to see whats inside of the setupdll and try to add that things to the OEM mannually like resources or regs
hi buddies, does anyone one know how to hack an app? for example, change a predefined （hard coded) path like "\storage card" to any other locations. I tried to use hex editor but couldn't find any paths hard coded. I know there's a program called "Olly Debugger" for Win32 which can change binary code to machine code. However it doesn't support PPC applications. Can anyone help?
Many thanks!!
If the path does not appear in the executable then it is not hard coded in the program.
Hard coded strings, string tables, static data and the like, get bundled together by the linker into a separate data segment. They would all appear in the same area within the exe.
The program is probably using FindFirstFlashCard() and FindNextFlashCard() functions to emumerate storage devices. "Storage Card" would be returned by this/these function(s) at run time.
Another reason may be that the executable has been 'signed'. In this case the code is encrypted with the certificate so the hard coded stuff cannot be seen. Altering the code here will invalidate the checksum and the operating system will refuse to run it.
hi stephj, thanks for your info! finally i can figure out the location is hard coded in a dll file instead.
btw do you know how to convert a module (in the form of folders) into a binary dll?
thanks!!
Not quite certain what you mean. A DLL file is the same structure as a .EXE except that it does not have a WinMain() function that a .EXE file has that the loader calls once it is loaded.
Once a DLL is loaded the loader can resolve the real address(es) of its exported function(s).
sorry, i was talking about the modules in rom cooking. after dumping the rom, some DLLs appear in the form of modules (which are folders). what I want to know is the ways to convert these folders into binary files.
In that case it's over to the chefs. My expertise is in the area of application development.
Thanks stephj!!
To convert module to file, look for recmod
It will give you a plain .exe/.dll you want to modify.
After you do it, restore it using reversmod
hey there,
i created an oem package which contains an dll file, one that exists also in the sys-folder as folder (contains imageinfo.bin and s000), when cooking with my kitchen buildos gives an error, something about that the expected file already exists as folder...
what can i do?
It's not a good idea to over-write a module; in fact, it's a bad idea, because it crashes most kitchens (buildos will crash every time).
1. Why are you trying to over-write a module with a file?
2. If you really want to do it, you need to remove the module from the sys directory. I'm not sure it's a good idea myself; you should at least convert the file to a module. If you don't know the difference between a file and a module, then you should search and find the answer. It's easy enough to do.
It would help a great deal when you start a topic if you give more information. What build are you using? What device? Most importantly, what module are you trying to replace?
Thanks Ted,
sorry for the small amount if informations. I'm using EXEcutor von pako777, it's kitchen tool for the omnia 2... almost, it dissambles the dump-file, then i can delete/add files and then it assembles it again... some kitchens i saw over here a really great, but the executor get the work done...
i found the informations, thanks for the hint i will now try reversmode.exe
right now i want to convert a taskbar.cab to an oem package and so i need to replace shellres.192.dll and some other files
I think that kheb 1.1 (search, it's easy to find) is the best way to make a package for your cab. Just run a snapshot, install the cab, then run another snapshot (+difference). Select the 'make an oem' function. It doesn't make a working oem, but it will dump the reg keys that you need, and collect all the files (I assume they'll all go to windows). It sounds like you're building the rom straight from a dump, and not with full packages? Then you'll need to just swap the new files in for any old ones (as well as add new ones), and figure out how to add the registry keys, if there are any. I guess you can use ceregeditor or something similar to import the keys into the default.hv. Convert files to modules, if that's how the dll's appear in the dump.
You have to be a little careful with an app like kheb (or sk tracker): it may dump out some extraneous files or reg keys, as changes occur all the time to a device's registry and file system. Make sure you separate the wheat from the chaff. It's best not to soft reset after the cab install, if you're prompted to do so. That creates a butt-load of random new reg values that are irrelevant. If any certificates are installed by the cab, you can probably ignore them.
Thanks again, but i used the package creator from ervius to convert the cab, converted the rgu to an provxml and the dll-files with reversmode and everything worked fine
but i will take a look onto kheb, sound promising when converting a cab with setup.dll