How does CMDLINES.TXT works in HFSLIP?

[Geej]

I'm aware there is an explanation for CMDLINES.TXT here. But how does it works in HFSLIP as it seems the explanation is written for nlite. Specifically, which folder should be use in HFSLIP context or when refer to $OEM$ directory?

Edited September 16, 2009 by Geej

[Yzöwl]

Cmdlines.txt is independent of the method used to slipstream the installation source.

It doesn't matter whether you slipstreamed manually, used nLite, HFSLIP or any other method.

You simply create the appropriate $OEM$ folder structure and cmdlines.txt file manually!

This topic will therefore be moved to the general, unattended forum!

[Geej]

Cmdlines.txt is independent of the method used to slipstream the installation source.

It doesn't matter whether you slipstreamed manually, used nLite, HFSLIP or any other method.

You simply create the appropriate $OEM$ folder structure and cmdlines.txt file manually!

This topic will therefore be moved to the general, unattended forum!

Thanks for the info. I got confused when I recently test with nlite and I saw nlite create this $oem$ folder. Will create manually to test in hfslip.

[Geej]

Tested ok with HFSLIP & nlite

As the explaination for CMDLINES.TXT does not have any screenshot, I thought it might be useful to post one.

And since it is mainly use for importing various registry tweaks, a more suitable batch command (I called it T12Tweak.cmd) would be

for %%e in ("*.reg") do regedit.exe /S "%%e"

Thanks, great forum indeed.