Using Cmdlines.txt

[the_doc735]

Using Cmdlines.txt

The Cmdlines.txt file contains the commands that GUI mode executes when installing optional

components, such as applications that must be installed immediately after Windows is

installed. If you plan to use Cmdlines.txt, you need to place it in the \$OEM$ subfolder of the distribution

folder. If you are using Sysprep, place Cmdlines.txt in the \$OEM$\$1\Sysprep subfolder.

Use Cmdlines.txt when the following conditions exist:

The syntax for Cmdlines.txt is as follows:

[Commands]

" command_1 "

" command_2 "

.

.

" command_x "

Parameters are defined as follows:

When using Cmdlines.txt, be aware of the following:

• You are installing from the \$OEM$ subfolder of the distribution folder.

• The application that you are installing has the following properties:

– Or –

• It does not configure itself for multiple users—for example, Microsoft® Office 95.

• It is designed to be installed by one user and to replicate user-specific information.

• " command_1 ", " command_2 ", ... " command_x " refers to the commands you want to run (and in

what order) when GUI mode calls Cmdlines.txt. Note that all commands must be in quotation marks.

• When the commands in Cmdlines.txt are carried out during Setup, there is no logged-on user and there

is no guaranteed network connectivity. Therefore, user-specific information is written to the default user

registry, and all subsequently created users also receive that information.

• Cmdlines.txt requires that you place the files that are necessary to run an application or tool in

directories that are accessed during the Setup process, which means that the files must be on the hard

disk.

B)

[pmshah]

I have created self extracting driver files which get copied to the %Systemdrive%\Drivers"

What would be the correct location for running these self-extracting files so that the drivers are available for installation to the setup procedure?

I have following line in my winnt.sif file

OemPnPDriversPath="DRIVERS\via,Drivers\intel"

The problem is of space on the CD. If I place expanded drivers in "$OEM$\$1\Drivers\via " and "$OEM$\$1\Drivers\intel" folders it works perfectly but I cannot accomodate these files on the CD I am working on. It is a 200 mb 8 cm cd which includes partitioning tools, boot manager installation & winxp installation as cd boot options.

[IcemanND]

expand them from DetachedProgram. see settings in winnt.sif.

[pmshah]

expand them from DetachedProgram. see settings in winnt.sif.

Thanks.

I read up on the subject elsewhere on the forum, tried it & it worked like a charm.

Now I am searching for methods of presetting my folder options & startmenu options. Mind you these are more like personal preferences type. Once I get that fixed upo I am all set with my 200 mb full installation that can also partition the hdd/ format the partitions & install boot manager - sort of an AIO.

As a final it runs change owner & organisation + change serial numnber, when I have to input details provides by the client & his xp package.