ROM Kitchen Utensils

[tjlabais]

I'm flashing again my unit, edited default.hv using Registry Workshop...

[TomasNM]

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.

Then why there are same files? Doesn't matter,if I export it or save it.

[TomasNM]

It doesn't allow the device to start,if edited by RW.

[tjlabais]

Tomas: I have now booted successfuly... I don't get it. There's nothing wrong with Registry Workshop. AND you are right, there is no difference if you save or you export.

Now, I get, I made a mistake of flashing your rw.reg into my device this morning. Definitely, it wouldn't work.... So going back to your problem, there has to be another reason for failure of your device to start.

[TomasNM]

Okay. Can you now tell us all the steps what you have done? Step-by-step guide.
My way:
- With disassemble.bat I get both .reg files with "REGEDIT4" string inserted at the beginning
- I edit the reg files and save it as Win9x/NT
- Should now I remove the "REGEDIT4" string or it doesn't matter?
- Reassemble the nk.nbf. This contains your vbscript before rgucomp.
- I flash the image,but the device hangs while booting.
Something wrong?

[tjlabais]

Okay. Can you now tell us all the steps what you have done? Step-by-step guide.
My way:
- With disassemble.bat I get both .reg files with "REGEDIT4" string inserted at the beginning
- I edit the reg files and save it as Win9x/NT
- Should now I remove the "REGEDIT4" string or it doesn't matter?
- Reassemble the nk.nbf. This contains your vbscript before rgucomp.
- I flash the image,but the device hangs while booting.
Something wrong?

1. I picked default.hv from ROM dump
2. decompile hive using RGUCOMP
3. renamed boot.rgu to boot.reg and edited with RW
4. made some changes to registry settings specifically disabling some Today Items to disappear.
5. saved the registry in win9x format
6. removed extra REGEDIT4 header
7. processed vbscript to convert to unicode
8. recompiled hive
9. added to ROM
10. flashed to device for 10~12min.
Works perfectly...

[TomasNM]

Okay. Can you now tell us all the steps what you have done? Step-by-step guide.
My way:
- With disassemble.bat I get both .reg files with "REGEDIT4" string inserted at the beginning
- I edit the reg files and save it as Win9x/NT
- Should now I remove the "REGEDIT4" string or it doesn't matter?
- Reassemble the nk.nbf. This contains your vbscript before rgucomp.
- I flash the image,but the device hangs while booting.
Something wrong?

1. I picked default.hv from ROM dump
2. decompile hive using RGUCOMP
3. renamed boot.rgu to boot.reg and edited with RW
4. made some changes to registry settings specifically disabling some Today Items to disappear.
5. saved the registry in win9x format
6. removed extra REGEDIT4 header
7. processed vbscript to convert to unicode
8. recompiled hive
9. added to ROM
10. flashed to device for 10~12min.
Works perfectly...

Hmmm. It seems to be the same as I done. Okay,I will try that later.

[tjlabais]

I'm sorry, Tomas. I thought I had a working device... but it only stops at the boot screen where it says tap your screen to setup. I never pressed it because I was busy trying some things with registry on my PC. I'm really sorry. Now, I think it's the empty registry keys that's causing the problems. Will verify this.

[TomasNM]

Okay, I have now a tool,that erases the empty registry keys. Try it if you want. It reads any reg file(made with RW) and creates *.reg.test.reg file. You can compare them. Do you think,that backslashes are correct in the hex sequence? It doesn't any problems? Let us try...

[tjlabais]

Tomas, NOW I finally found the culprit. I noticed that when I compile the file save by RW, it becomes less than the file extracted by RGUCOMP.

RGUCOMP outputs multi string values as:
"Value Name" = multi_sz: "first", "second", "third"

REGISTRY WORKSHOP outputs multi string values as:
"Value Name" = hex(7):6f,00,6e,00,65,00,00,00,74,00,77,00,6f,00,00,00,74,00,68,00,72,00,65,00,65,00,00,00,00,00

SO, when RW reads file from RGUCOMP, it can not parse the value and deletes it. Therefore, all multi-string values are deleted when you save back. I'm trying to see, if I could work out conversion of multi_sz to hex.

EDITED: Okay, I have managed a vbscript that will convert the string to hex. See attachment multisz.zip

HOWEVER, after compiling boot.rgu saved by RW, I only get 588KB out of the original 592KB. Before multi_sz was corrected, it compiled 568KB. This means, something is still missing...

One more thing, if the value name is a path name, RW strips all slashes!!!
(i.e. "\\Windows\PPCContactMgr.dll"=dword:1) becomes ("WindowsPPCContactMgr.dll"=dword:1)
I'm stuck with this, as we will never know where to put the slashes if path is other than Windows! :? EDITED: Okay, I solved this. It's RGUCOMP having a problem with this, and I have corrected the entries. If entries are correct, they will come out okay when saved from RW. If the entries are wrong, the slashes are stripped. WE'RE back to RW business! Still looking for the other missing files

[JKR]

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.

Actually internet connection sharing is not a Mio module, I'm sorry if I gave you that impression. and neither are the AKU files, which were supplied by Bepe. You can however discount my remarks about the OEM modules needing to stay as modules, that was kind of device specific, and I corrected myself in my last post. But the MS files statements stands, some can be made into files, and some need to stay as modules. I think the internet connection sharing module was ripped from a wizzard ROM, but if you have made that into files, and works on a wizzard, I'd like to get a copy. Anyways, I found this thread going through the "new posts" option, and forgot to check that it was Himaaya, specific.
Regards,
Jason

[tjlabais]

Okay, NOW I found the remaining missing entries. The PPC registry supports mui_sz type value which is a multi-lingual support type, NOT found in Registry Workshop. This would mean, we can never convert it to work with RW. So, the only solution is to strip it out of the RGUCOMP file and save it on a separate file, then merge it back for compilation purposes. Is this worth all the hassle?

EDITED: Okay, now I have revised multisz.vbs to do the following:
1. look for ms.reg as the file extracted from RGUCOMP
1. convert multi_sz format to hex
2. copy mui_sz registry entries and save to mui.reg

will now work on joining back the two reg's as merely placing the mui_sz anywhere would not yield a working file.

EDITED: If I join the two files and compile then decompile, multi_sz values remains as hex(7)... I think I will have to convert hex(7) back to multi_sz when joining the two files.

[tjlabais]

Hi Tomas,
Attached herewith is the Registry Workshop processing script. It does the following:

workshop.vbs
1. It will look for filename - ms.reg which is decompiled registry hive from RGUCOMP
2. add REGEDIT4 into the first line of ms.reg
3. Convert multi string values readable by RW
4. copy mui_sz registry entries into mui.reg
5. ms.reg is now ready for RW editing

bootrgu.vbs
1. Remove empty duplicate registry keys
2. Reformat dword values
3. Join back mui.reg with ms.reg and place mui_sz values in the proper place
4. Convert multi string values back to RGUCOMP format
5. Save as UNICODE - boot.rgu file

I have tried this, edited some stuff in RW, saved the file, RGUCOMP, then flashed to device. It works!

Now, you can enjoy using RW for editing...

EDITED: ATTACHMENT DELETED - PLEASE SEE 12.14.06 POST FOR UPDATES

[TomasNM]

Perfectly! Thanks.
Sorry for me,but I am too busy last week to test that. Anyway,I will keep with this thread. Now I own an HTC Sonata(TM-SDA) Smartphone and that's my 2nd toy. I will(and want) to test it ASAP. I'll let you know...

[tjlabais]

Perfectly! Thanks.
Sorry for me,but I am too busy last week to test that. Anyway,I will keep with this thread. Now I own an HTC Sonata(TM-SDA) Smartphone and that's my 2nd toy. I will(and want) to test it ASAP. I'll let you know...

It's okay Tomas... When I'm busy, i'll be off for a while, too. We also need to earn a living and sustain our devices. hehehe

My 2nd toy is the ATOM, but was too addicted with my Hima after the virgy build. Somehow, the stability and speed buzz built in this ROM made me eager again to play with it. This prompted me to post this ROM cooking guide. But before this, I never dared cooked a ROM. I just wait for TofClocks and Buzz to post some new ROMs. Perhaps, its time to contribute... back to buzzdev...