Anyone have a good method for tracking Reg errors in a kitch

[colonel]

I just started playing with sfaure03's latest kitchen (1.2) and when I am running CreateOS I am getting the error when it builds the hives. I have been going through all of the .rgu files looking for errors. Most of them I have even been copying to make them default.txt and running the default-to-hv tool to look for the errors. Still haven't found it. Just checking to see if anyone had any other tricks aside from this long and painful process.

[Perasite]

I got an error whenever the .rgu didn't have a final carriage return. Make sure all the .rgu's end with a blank line. Unfortunately I don't know of a way to do that without opening each one.

[colonel]

Yeah, I found the error I was looking for. It would be nice if there was a process to find these errors though. That was one thing I loved about the old way of building roms, the txt-to-hv app would tell you right where the error was. I guess with a stable kitchen, the only errors will be in OEMs.

[ImCoKeMaN]

the createOS program shows where the error is at the very end of the log in that window. Also if you need to do searching through the unicode files i've used agent ransack

[colonel]

Here is what I was getting

-- adding dump\ff1dcb21-efff-4a57-8d60-dbb09e72cccd.dsm
  -- adding dump\ff1dcb21-efff-4a57-8d60-dbb09e72cccd.rgu

Completed successfully

DEV:\Temp> rgucomp.exe 
Microsoft (R) RGUComp Version 1.0.000
Registry file processor and hive builder.
Copyright (C) 2004 Microsoft Corporation All Rights Reserved.
built: Nov 19 2004 15:17:13
importing registry file ".\boot.rgu"...
wmain: (RGUComp) !ERROR failed building DEFAULT hives

I think I was making a mistake when trying to patch the crossbow stuff using the batch file. Just to clarify, in the release notes, sfaure03 says this:

To use, after extracting the rom open a dos prompt
cd into the subdirectory CBOW then run the apply.bat script there.
This overwrites some original files from the OS/LOC/OEM direcotries of
the default kitchen and have been used by many to give us a more "crossbow" look..

I guess I am getting confused on when you actually are supposed to run the batch file.

[sfaure03]

hmm.. i get no error.

Trying again.

any chance you've reused that UUID in another rgu?

That is the DIM module, and well, i aint touched that bugger.

[finster869]

I guess I am getting confused on when you actually are supposed to run the batch file.

I believe you need to run it 1 time before you run createos. As far as I could tell, all it did was replace the standard files in the OS/LOC folders of the kitchen with the crossbow like theme files.

[verizonguy]

That message can be caused by 1 of 3 things: either the file wasnt saved in unicode, the last line wasn't left blank or the file rgucomp was looking for wasn't found. the latter is most likely. another problem you will run into with that build is that it has entries for .net cf2 built in which rgucomp has trouble parsing but that is a separate issue. I will be releasing a tutorial soon for working with hive files including simplified tools.

[isamu49]

Just a couple things,

At that part of the build, I don't think a UUID conflict is possible since they're all dumped into the same directory right before the hives are built using rgucomp and packages.sof. Also that last UUID that is showing isn't really indicative of anything other then that's the last sorted dsm/rgu file being built into the cab file.

I suspect you might get that sort of error if you try to build the hives with rgu files without matching dsm files. Most rgu compile errors are usually a little more descriptive.

That being said, I use a batch script to automatically compile/verify all the rgu's in the oem directories (this assumes all the components of the kitchen are verified).

Oh yeah, and of course, I try to avoid using createos if at all possible. I find it to be an unnecessarily cumbersome process.