Jump to content

Problems getting Cmdlines.txt to run from RIS


Recommended Posts

ok, I am willing to admit defeat.

I am trying to get a XP RIS install to process the CMDLINES.txt file and no matter what I try, it dosn't seam to run it.

I am running RIS from a 2003 server and the instalation of XP installs. it appears to copy the files from the $OEM$\$$ folder to the system 32 folder just like it should, but it dosn't seam to process the CMDLINES.TXT file that is located at the root of the $OEM$ folder.

Does anyone have any suggestions?

here are some of the configuration files:

Directory Structure:

\\xload1\REMINST\Setup\English\Images\WINDOWS_xp\i386 XP files

\\xload1\REMINST\Setup\English\Images\WINDOWS_xp\i386\templates RIS SIF

\\xload1\REMINST\Setup\English\Images\WINDOWS_xp\$OEM$ Oem files

(The docs still say to put the OEM at the same level as the i386 for ris, and I even tried it in the i386 folder like you do for non ris).

The cmdlines.txt file is located at the root of the $OEM$ folder and is as fallows

________________________________________________________

[COMMAND]

"md c:\fred"

".\regedt32.exe /s .\AutoLogon.reg"

_________________________________________________________

the Autologon.reg folder is also located at the root of the OEM. I put the MD C:\fred to tray and make a folder to prove it was actually seeing the cmdlines.txt file (no luck).

Here is the SIF file that I am processing:

________________________________________________________________

;SetupMgrTag

[Data]

floppyless="1"

msdosinitiated="1"

OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"

OriTyp="4"

LocalSourceOnCD=1

[setupData]

OsLoadOptions="/noguiboot /fastdetect"

setupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"

[unattended]

OemSkipEula=Yes

OEMPREINSTALL = Yes

TargetPath=\WINDOWS

FileSystem=LeaveAlone

ExtendOEMPartition=0

InstallFilesPath="\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"

LegacyNIC=1

[GuiUnattended]

OEMSkipRegional=1

OemSkipWelcome=1

TimeZone=%TIMEZONE%

AdminPassword=(Deleted)

EncryptedAdminPassword=no

[userData]

ProductID=(Deleted)

FullName="Current User"

OrgName="Orgname"

ComputerName=%MACHINENAME%

[Display]

BitsPerPel=24

Xresolution=1024

YResolution=768

[identification]

JoinDomain=%MACHINEDOMAIN%

DoOldStyleDomainJoin=Yes

[Networking]

InstallDefaultComponents=No

[NetAdapters]

Adapter1=params.Adapter1

[params.Adapter1]

INFID=*

[NetClients]

MS_MSClient=params.MS_MSClient

[NetServices]

MS_SERVER=params.MS_SERVER

[NetProtocols]

MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]

DNS=No

UseDomainNameDevolution=No

EnableLMHosts=Yes

AdapterSections=params.MS_TCPIP.Adapter1

[RemoteInstall]

Repartition=Yes

UseWholeDisk=Yes

[OSChooser]

Description="Windows XP Profesional ver 8.1 - Select Installation"

Help="This will install Windows XP Profesional Select with configuration."

LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"

ImageType=Flat

Version="5.1 (0)"

_______________________________________________________________

the files in the $OEM$\$$ folder copies correctly, so that should mean that the preinstall setting are correct. but it refuses to process the cmdlines.txt file.

I suspect that it is some stupid typo that I am just not able to see. but I am at the stage of willing to beg for insight.

Link to comment
Share on other sites


i'm not even sure that RIS processes cmdlines.txt but...

instead of calling those commands, have it call like pause.cmd

create a pause.cmd in the same directory as cmdlines.txt and inside have

ECHO YAY!! IT WORKS!!PAUSEPAUSE

(two pauses jsut in case you press a key without meaning to)

also, for use of reading, please enclose your code in [\CODE] tages (minues the \)

Link to comment
Share on other sites

Thanks,

I tried using the Pause things before going with the MD command. I switched because I thought that mabey the file was processing, but not interactively.

I will give it another try though (like the idea of the two pauses).

Sorry about not useing

,  I forgot 
Link to comment
Share on other sites

i should point, i missed it the first time....

"md c:\fred"".\regedt32.exe /s .\AutoLogon.reg"

cmdlines.txt runsin the directory it resides. So if you're on a CD, like a normal disk it would be like D:\$oem$

regedit won't work unless you have regedit32 in $oem$. Try removing the .\ on both regedit32 and autologon.reg. Though regedit32 is in the PATH variable (in the systemroot) you specificed a path with .\

and [Command] should be [Commands]

Link to comment
Share on other sites

Thanks that was it. I thought it must be some typo I couldn't see (it always worked before).

Supprising how having Command and not Commands can really mess things up.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...