cmdlines.txt not executed?

[bomek]

I've setup a unattended Windows 2000 cd and everything seem fine. Except one thing, cmdlines.txt is not read at all.

Here is where i put the file:

G:\I386\$OEM$\cmdlines.txt

Even if i just do that, it don't work:

[COMMANDS]
"echo hello"
"pause"

Here is a part of my winnt.sif

[Unattended]
	UnattendMode = FullUnattended
	UnattendSwitch = Yes
	OemPreinstall = Yes
	OemSkipEula = Yes
	FileSystem = *
	WaitForReboot = No
	TargetPath = "\WINNT"
	DriverSigningPolicy = Ignore
	NonDriverSigningPolicy = Ignore
	Hibernation = No

Anyone run into the same thing?

Thanks!

[Tsunami]

You have to run another batch file from cmdlines.txt. cmdlines.txt is not a batch file on it's own, it can only run other programs.

[sleepnmojo]

Tsunami is correct in this case. The echo and pause are part of the shell, so they shouldn't run. To run them either throw them in a cmd or bat file, or put cmd /c in front of each command.

[Alanoll]

Let's not forget the obvious, that if you're instlaling from CD, and booting FROM CD, then $OEM$ needs to be in the root of the CD.

However, you can use CMDLINES.TXT like a command prompt, but they need to be external commands (regedit , applicaiton installs , cmd.exe)

[bomek]

Well, for the "pause", it was taken from this document (but it's for NT4):

My current cmdlines.txt contain:

[COMMANDS]
"./logon.cmd"
"./ie6sp1.cmd"
"./mdac.cmd"
"./directx9.cmd"
"./dotnet.cmd"
"./wmp.cmd"

So, the problem was cause my $OEM$ is in the i386 dir instead of the root??

Thanks a lot!

[sleepnmojo]

If you do network installs, then $OEM$ goes in the i386 folder, otherwise it goes along side it, ie cdroot. The best thing to set it up for both, so both folders are in both locations.