v000

Hmm... As for "call nLite twice in the NT command script" - just tried that to be sure - after restart (it crashes on "Integrating hotfixes, service packs and themes"), nLite detects an unfinished operation. "Don't reuse broken installations." and all that. Thank you for the tip on ImgBurn.

Have you thought about using external command line tools for burning? These are free. I propose a simple .CMD script: call nLite 1st and cdrecord 2nd. I'ts what I'm going to do anyway.

Thank you, John. You are correct, I'm using Windows NT Command Script files to streamline ISO creation. %1 is just a profile name - M50SA in my case (notebook model name). I sent nuhi PM as soon as I created the topic; too bad he lost interest... Well, in any case I can share with you my setup so more people can use nLite this way (hence more will complain). I've written several scripts: - for 7-Zip to extract the original ISO into the working directory and extract ZIP files (such as M50SA.zip that contains PnP/TextMode drivers and favorite themes for integration): .\bin\7z\7z.exe x -y -o"%2" "%1" - for nLite to process the directory based on the predefined profile: .\bin\nLite\nlite.exe /preset:%%presets%%\%1 /path:.\release\oemdisc - for mkisofs to create ISO image for CD: .\bin\nLite\mkisofs.exe -iso-level 4 -l -d -D -r -J -joliet-long -allow-multidot -no-emul-boot -boot-load-size 4 -hide bootsec.img -hide boot.catalog -V %1 -b $OEM$/$BOOT$/bootsec.img -o .\release\%1.iso .\release\oemdisc - for calling other scripts to prepare the working directory, unzip required and optional packages, and cleanup I'm using PowerISO for burning (not automated yet). Another thing that can be improved is creating either CD or DVD ISO based on the folder size. The reason I'm doing all this is that I'm experimenting with different nLite settings - I had to, actually, since I figured out nLite 1.4.9.1 can damage Windows installation. For instance, any tweaks in the Start Menu sooner or later result in the context menu not showing up for My Computer (sooner if you ticked off disable Drag & Drop). Same for Control Panel inside My Computer if you tweaked Explorer (won't go away no matter what). And lots of other little things.

Details: System.IO.IOException was unhandled Message="The file '.\\xxxxxxxx\\yyyyyyy\\Shellstyle.dll' already exists." Source="mscorlib" StackTrace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at System.IO.FileInfo.CopyTo(String destFileName, Boolean overwrite) at System.IO.FileInfo.CopyTo(String destFileName) at ..(String , String ) at ..(String , String ) at ..(FileInfo , String ) at ..(String , String , Boolean ) at ..(DirectoryInfo , String , String , String , Boolean ) at ..(DirectoryInfo , String , String , String , Boolean ) at ..() at ..$() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() InnerException: More details: .\bin\nLite\nlite.exe /preset:%%presets%%\%1 /path:.\xxxxxxxx\yyyyyyy nLite crashes after extracting drivertmp and sp3tmp, this time it was on theme integration. Doing attrib -R .\xxxxxxxx\yyyyyyy\*.* /S /D does not help - when started manually, everything is OK.