ROM Kitchen Utensils

[TomasNM]

How should the registry file appeared before rgucomp -b? I have it like this...

REGEDIT4

[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:00000409

[HKEY_CURRENT_USER\Software]

[HKEY_CURRENT_USER\Software\Microsoft]

[HKEY_CURRENT_USER\Software\Microsoft\Windows]
"DbPath"="\\mxip_initdb.vol"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"EnableNegotiate"=dword:00000001

...

[tjlabais]

YESS!!!

Please see my revised attached registry editing batch file. I also wrote a short vbscript to counter some errors RGUCOMP generated when decompiling. You no longer need to add REGEDIT4 manually PLUS the file is automatically converted to UNICODE. Further, I have discovered that the best editing software to use is MS Word, NOT WORDPAD AND DEFINITELY NOT NOTEPAD to avoid rearranging the unicode file and generate two entries in a line.

[TomasNM]

YESS!!!

Please see my revised attached registry editing batch file. I also wrote a short vbscript to counter some errors RGUCOMP generated when decompiling. You no longer need to add REGEDIT4 manually PLUS the file is automatically converted to UNICODE. Further, I have discovered that the best editing software to use is MS Word, NOT WORDPAD AND DEFINITELY NOT NOTEPAD to avoid rearranging the unicode file and generate two entries in a line.

Hallo. Finally,I've found a while to try this. It seems to work. Anyway I left the Disassemble.bat untouched with the REGEDIT4 commands to insert the text at the beginning. This is necessary to open the reg files with Registry Workshop. I put the VBscript to Reassemble.bat. Perhaps,it doesn't matter,if there are 2 REGEDIT4 strings at the beginning of the file,because I don't have noticed any problems. Here is my new Reassemble.bat. The replace.vbs file MUST be in same folder as nk.nbf and others.

Now I am thinking about another issue:
How to insert a file,if I want to use them as module? And when do I know,that this file must be saved as module or file? What can be wrong,if I save any file as file instead of module with addfile command? Will it working?

[JKR]

most modules don't run when they are made into files. We've had limited success w/ some of the M$ ones, such as excel. You may also have to investigate whether or not the extracion method for your device can produce modules that can be effectively rebuild by recmod. Some dump methods will allow to extract modules, but if they are rebuilt by recmod, they will output an unsuable file.
Regards,
Jason

[tjlabais]

most modules don't run when they are made into files. We've had limited success w/ some of the M$ ones, such as excel. You may also have to investigate whether or not the extracion method for your device can produce modules that can be effectively rebuild by recmod. Some dump methods will allow to extract modules, but if they are rebuilt by recmod, they will output an unsuable file.
Regards,
Jason

@JKR: I beg to disagree. The virgy build ROM (EXCEL FIXED) was corrected by extracting the excel files from AKU3.0 using recmod. They are working perfectly. The modules won't run if they are made into files, IF you simply transport the files to other ROMs without copying the registry entries as well. OR the dependency files to which the files need to run are missing. Another example is the Transcriber which I also uploaded here. They are pretty much extracted using recmod.

@Tomas: If you notice one of my utensil guide, how I wished there was a reverse tool from files to modules. The addfile by mamaich is limited only to files and not modules. I was looking for the source code of the recmod; as I was planning to study it for a possible reverse tool. This would be a breakthrough because compression is better for modules as compared to files. Module manipulation do not use the addfile and delfile. Rather, one edits the contents of \dump\ and build it from there.

[JKR]

@JKR: I beg to disagree. The virgy build ROM (EXCEL FIXED) was corrected by extracting the excel files from AKU3.0 using recmod. They are working perfectly. The modules won't run if they are made into files, IF you simply transport the files to other ROMs without copying the registry entries as well. OR the dependency files to which the files need to run are missing. Another example is the Transcriber which I also uploaded here. They are pretty much extracted using recmod.

You misunderstood my post, I was saying the most modules don't work if they are made into files, BUT some of the M$ ones have been successfully made into files, such as excel. I can understand how the misunderstanding could have occered. I could have changed

We've had limited success w/ some of the M$ ones, such as excel.

to "We've however had limited success w/ some of the M$ ones, such as excel." Now on the other hand, if you are saying that most modules can be extracted to files and work, this would be news to me, especially OEM ones. BUT every device is differen't, and I'm not discounting it.
Regards,
Jason

[TomasNM]

F...ing registries! I can't use Registry Workshop,because it has different format in saving the files. Rgucomp doesn't understand him and it causes to defected ROM image,even no error is occured. Now I am on the way to develop a tool,that converts an final registry file to the format,that can rgucomp understand. That is too difficult to write the entries and modifications by hand...:X

[tjlabais]

F...ing registries! I can't use Registry Workshop,because it has different format in saving the files. Rgucomp doesn't understand him and it causes to defected ROM image,even no error is occured. Now I am on the way to develop a tool,that converts an final registry file to the format,that can rgucomp understand. That is too difficult to write the entries and modifications by hand...:X

Pls post your edited RGU file using Registry Workshop, I'll look into it. So, far, I haven't had any problems using MSWORD to edit the files, and I have flashed my device a couple of times already.

[tjlabais]

... Now on the other hand, if you are saying that most modules can be extracted to files and work, this would be news to me, especially OEM ones. BUT every device is differen't, and I'm not discounting it.
Regards,
Jason

Perhaps, Jason, you could be more specific which OEM ones you are referring to; so, we can look into it AND post it in the utensils for others to learn.

[TomasNM]

F...ing registries! I can't use Registry Workshop,because it has different format in saving the files. Rgucomp doesn't understand him and it causes to defected ROM image,even no error is occured. Now I am on the way to develop a tool,that converts an final registry file to the format,that can rgucomp understand. That is too difficult to write the entries and modifications by hand...:X

Pls post your edited RGU file using Registry Workshop, I'll look into it. So, far, I haven't had any problems using MSWORD to edit the files, and I have flashed my device a couple of times already.

Yes,I know,that using MS Word is a working way,but I guess,that using RW is much easiest way to editing registries. Unfortunately,there is a different format,that RW saves and rgucomp doesn't understand him. In this pack is a rgucomp.reg file(this is original one made by rgucomp.exe. Don't care about the REGEDIT4 string-inserted with copy command,needed for RW to open),rw.reg(saved the rgucomp.reg with RW) and test.reg(converted with my tool). There is a thing,that I don't understand why,that I think,causes the registry unusable:In some hex values,there is a sequence splitted to next line with backslash followed by CR/LF.
My tool under developement does these things:
-Remove these backslashes from hex sequence
-Remove empty keys
-Remove the string REGEDIT4
-All hex values are uppercase
-All dword values are not 8-character long,but have just needed length
All these changes must be done before using vbscript by reassembling.

[tjlabais]

F...ing registries! I can't use Registry Workshop,because it has different format in saving the files. Rgucomp doesn't understand him and it causes to defected ROM image,even no error is occured. Now I am on the way to develop a tool,that converts an final registry file to the format,that can rgucomp understand. That is too difficult to write the entries and modifications by hand...:X

Pls post your edited RGU file using Registry Workshop, I'll look into it. So, far, I haven't had any problems using MSWORD to edit the files, and I have flashed my device a couple of times already.

FOUND the culprit. When you want to use Registry Workshop (RW), You have to export the registry as Win9x and not merely save it. The default setting for saving is Win2K/XP; which is a new registry format. The registry format for PPC is still the old one REGEDIT4. So, with this, I get a working hive.

Cheers!

[JKR]

Perhaps, Jason, you could be more specific which OEM ones you are referring to; so, we can look into it AND post it in the utensils for others to learn.

Internet connetion sharing, is one of the ones Oki has added the the Scoter custom ROM's that doesn't like being made into files, I've tried extracting this from a couple of different ROM's just to make sure it wasn't the dump method used that created the problem, and since it starts, I don't think that was the problem. It however doesn't function properly. Additionally on the Scoter, we are yet to be able to extract modules in a form that can be rebuilt into files, perhaps someday. As it is, the OEM modules from a Scoter have to stay modules. There again, I don't know about other ROM's, but I know a lot of the MS modules need to remain modules. If anybody can explain why this is, I would always like the info.
Regards,
Jason

[tjlabais]

Perhaps, Jason, you could be more specific which OEM ones you are referring to; so, we can look into it AND post it in the utensils for others to learn.

Internet connetion sharing, is one of the ones Oki has added the the Scoter custom ROM's that doesn't like being made into files, I've tried extracting this from a couple of different ROM's just to make sure it wasn't the dump method used that created the problem, and since it starts, I don't think that was the problem. It however doesn't function properly. Additionally on the Scoter, we are yet to be able to extract modules in a form that can be rebuilt into files, perhaps someday. As it is, the OEM modules from a Scoter have to stay modules. There again, I don't know about other ROM's, but I know a lot of the MS modules need to remain modules. If anybody can explain why this is, I would always like the info.
Regards,
Jason

Ahh... Thank you for your reply. So, this is to set the record straight for those reading this thread, RECMOD.EXE - an IMGFS tool by mamaich works perfectly okay for HIMALAYA under which this UTENSILS forum is written for. So, please understand that when we make statements here, all references refer to HIMALAYA WM2005.

[TomasNM]

F...ing registries! I can't use Registry Workshop,because it has different format in saving the files. Rgucomp doesn't understand him and it causes to defected ROM image,even no error is occured. Now I am on the way to develop a tool,that converts an final registry file to the format,that can rgucomp understand. That is too difficult to write the entries and modifications by hand...:X

Pls post your edited RGU file using Registry Workshop, I'll look into it. So, far, I haven't had any problems using MSWORD to edit the files, and I have flashed my device a couple of times already.

FOUND the culprit. When you want to use Registry Workshop (RW), You have to export the registry as Win9x and not merely save it. The default setting for saving is Win2K/XP; which is a new registry format. The registry format for PPC is still the old one REGEDIT4. So, with this, I get a working hive.

Cheers!

You're wrong. When I export it as Win9x/NT,I get same file as when I save it usually. Same filesize,same syntaxes. I think,that the backslashes+CRLF in hex values(used for split the sequence to next line) causes the registri unusable. Have a look:

RW saved format:

[HKEY_CURRENT_USER\Software\Microsoft\Inbox\MsgTypes\IPM\SMStext\MDSRequest]
"DLL"="MdsMailSvc.dll"
"GlyphInfo"=hex:20,00,00,00,cb,00,00,00,cb,00,00,00,00,00,00,00,01,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00

rgucomp format:

[HKEY_CURRENT_USER\Software\Microsoft\Inbox\MsgTypes\IPM\SMStext\MDSRequest]
"DLL"="MdsMailSvc.dll"
"GlyphInfo"=hex:20,00,00,00,cb,00,00,00,cb,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

Take a look at the 2 spaces before any reg value definition in rgucomp as well.

I will try to remove these backslashes and build a new nk.nbf and flash.

[tjlabais]

F...ing registries! I can't use Registry Workshop,because it has different format in saving the files. Rgucomp doesn't understand him and it causes to defected ROM image,even no error is occured. Now I am on the way to develop a tool,that converts an final registry file to the format,that can rgucomp understand. That is too difficult to write the entries and modifications by hand...:X

Pls post your edited RGU file using Registry Workshop, I'll look into it. So, far, I haven't had any problems using MSWORD to edit the files, and I have flashed my device a couple of times already.

FOUND the culprit. When you want to use Registry Workshop (RW), You have to export the registry as Win9x and not merely save it. The default setting for saving is Win2K/XP; which is a new registry format. The registry format for PPC is still the old one REGEDIT4. So, with this, I get a working hive.

Cheers!

You're wrong. When I export it as Win9x/NT,I get same file as when I save it usually. Same filesize,same syntaxes. I think,that the backslashes+CRLF in hex values(used for split the sequence to next line) causes the registri unusable. Have a look:

RW saved format:

[HKEY_CURRENT_USER\Software\Microsoft\Inbox\MsgTypes\IPM\SMStext\MDSRequest]
"DLL"="MdsMailSvc.dll"
"GlyphInfo"=hex:20,00,00,00,cb,00,00,00,cb,00,00,00,00,00,00,00,01,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00

rgucomp format:

[HKEY_CURRENT_USER\Software\Microsoft\Inbox\MsgTypes\IPM\SMStext\MDSRequest]
"DLL"="MdsMailSvc.dll"
"GlyphInfo"=hex:20,00,00,00,cb,00,00,00,cb,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

Take a look at the 2 spaces before any reg value definition in rgucomp as well.

I will try to remove these backslashes and build a new nk.nbf and flash.

I tried it on my device this morning. If I just save the registry file using RW, it compiles okay, but device does not start. BUT, if export using win9x format, compiles okay, and device starts.

the backslash is just a cue (code) for multiple line entries. I have many registry entries like it on my registry hive. If you look at my UTENSILS, the Ringtones entry is like it. Have you looked at the attachment I made when I exported using win9x format? There are no spaces before the regestry entries, BUT it works on my device. Are you absolutely sure it's the hive having a problem?

It doesn't matter if you have spaces before registry entries, RGUCOMP process on a per line basis with delimeters as cues.