For those that need a personalized OEM for their ROMS!!!!!

[tiermann]

Ok.. give this badboy a try.

I can't reproduce that error anymore after I juggled some stuff around.

[nickm]

I am still testing it. One thing I found is when I select the Internet and PIE check box. It causes the BuilOS to error on line 119. If I uncheck the box it works.

[tiermann]

K. I'll take a look at the registry entries in the PIE section. Thanks

Edit:
Fixed The problem was that I didn't convert the string from the dropdown box for "History" to a dword value. It was saving as "030 days".

[nickm]

I got it again (IE error) when BuildOS runs.

MY settings in the Internet PIE section:

unchecked the "warn when changing to unsecured page"; history saves only 2 days.

Is there a way to save the settings so I don't have to retype them. Right now I just leave the program open. When I change something I just "create OEM" and it deletes the only one. But I am going to have to reboot my system soon ( virus updates)

[nickm]

one more thing,,,
the GMT setting doesn't take day light savings time into consideration, or does it? Mine is an hour off

[tiermann]

Not yet. That's one thing I'm working on. I need to figure out how it decides to come up with the GMT value from the timezone key. But the timezone info I'm using is accurate with the DST update. There's still a seperate key for the DST though.

If you could try setting [HKEY_LOCAL_MACHINE\Software\Microsoft\Clock\HomeDS T to 1 and let me know if that fixes then I can add it for next version.

If it doesn't, then please let me know what setting->system->clock & alarms has for your GMT and what it should have, thanks

New Feature:
I've added an "Import Cab" button to the "Files & Shortcuts" section. If you have a cab file that uses a _setup.xml, you can try importing it. The program will extract it to Kitchen\Tools\Cabname.tmp\*, check for a _setup.xml, parse it, and try to give you a list of files and proper destinations as well as registry entries from the cab.

Anything highlighted in yellow on the "Files to Import" list are files with subdirectories or locations other than \Windows or \Windows\Start Menu. You may want to look at those and change things like themes to use one folder, etc. Mousing over a filename will give you the orignial filename it had in the cab, like FLASH00~.001. Mousing over a shortcut's name will give you the path it's linked to.

It's not perfect, but it will give most people a great starting point for converting cabs to OEMs (if not do it all for them).



Download here

[gguruusa]

Originally Posted by tiermann

PS: WTF is a dsm file anyway, and how does buildDSM come up with the gibberish in the file, hehe. I would like to incorporate this into OEMizer instead of having to shell to another app.

A .dsm file basically defines hardware/OS base requirements, module name, unique IDs, certificates, components, and dependencies. It's kind of like a .cab's .inf file in binary.

Generating a real .dsm (like BuildOS does) takes some magic that only a few possess, to my knowledge. BuildDSM makes a half-assed .dsm that if you're really determined you can replicate for simple OEM folders. It's not worth the effort unless you are seriously bored.

[tiermann]

Thanks gguruusa

I was desperate there for a while when I couldn't get buildDSM to stop crashing.

[nickm]

my registry setting had a 1 already. My clock setting said Saskatchewan (-6); I changed it to Central US (-6).

You've done some great work here

[tiermann]

New Feature: There's an "Add from Kitchen..." button next to the today items list on the "Today & Appearance" section. That will give you a list of today plugins (that it's able to find in your kitchen) and you can check them to add to your today items list. You'll be able to choose their order and toggle their visibility just like the rest of the stock today plugins.

But remember that you still have to actually add the plugins during BuildOS.


Next feature I'm working on is an OEMizer.ini file that will store your settings. I was originally going to do that all in the registry, but some people tote their kitchens around with them to different PC's. A seperate ini file will also allow you to keep different settings for different kitchens. Another thing an ini file will allow is trading of your settings with other people .