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

[nickm]

it pops up a dos box as soon as I hit the "create OEM"

[tiermann]

As it should.. that's BuildDSM running..
Thanks.

I'll have to maybe add quotes or something to the command line to make it work when your kitchen is in a path that contains a space.

Where is your kitchen folder located, btw?


Edit: Updated on the ftp and _should_ fix that error.

[nickm]

I put the Mizer here:

C:\Documents and Settings\Nick\Desktop\Helmi_APAC_Official_AKU3_5_K itchen_1_0_4\Helmi_APAC_Official_AKU3.5_Kitchen_1. 0.4\TOOLS\OEMizer

I tried to run the debug but it didnt do any thing

[tiermann]

K, let me know how the new upload works for you. It shouldn't care that the full path name has spaces now.

Always uploaded to the same spot.

[nickm]

same thing

[tiermann]

Ok.. give me a few mins. I just moved my whole kitchen to a path with a space in it like yours for testing and I do get that error now.

[DopeWeasel]

Looks great. Will test this weekend and report back.

For now one thing I will be trying out is the "Additional Registry Settings" item. It would be nice if we could incorporate a tab for common program registrations to make it easier for those of us who have to enter a dozen serials after building. Also, with the "Today Items" portion... would it be possible to add an "Optional" section for those of us who install third party apps like Spb Diary?

[tiermann]

I couldn't find a fix for the problem, but I have a workaround for now for those people getting BuildDSM errors. OEMizer.exe now generates an "OEMizer-BuildDSM.bat" file in your tools folder which can be run after the "Create OEM" process completes. For some reason, calling builddsm from a full path with a space in it is still erroring.. but running the generated bat file works fine. (I uploaded it to the ftp)


DopeWeasel:
I will be adding a drop down list with other programs to add to the today items eventually, but you'll have to wait a bit. What I want to do is have it parse existing OEM's for today item entries

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.

[AstainHellbring]

One thing you can also try is calling builddsm based off of the local directory and instead of the full path just do directory based off referencing local directory that OEMizer runs from

[tiermann]

That's what I had originally.. Just ..\OEM, but it still crashes when the full path has a space *shrug*. And still crashes when I just run the bat which cd's to the OEM folder and runs ..\Tools\builddsm <foldername>. I would say that it's because I still had some file open that I can't find, but it doesn't do it at all in a directory without a space in it's full path.

Wish I could figure out what buildDSM does anyway to get it's output, then I could bypass it completely.