SlipStreaming EXE File Into Win2K Install

[Anonymous]

Ok,

I know how to make a Win2K CD bootable.
I know how to slipstream a service pack.

Now, how can I slipstream, or trigger an exe file to run either duing setup, or on first boot.

In Win9X, I just added extra lines in the msbatch.inf to enable this.

I need to figure out how to have setup copy the file(s) to the hard drive then run them on first boot.
I know it must be in the winnt.sif somewhere...but I don\'t know the tag lines that need to be added to do this.

Anyone here know?

[Twinkie]

Go here http://www.tech-hints.com/oem.html

You will use the OEM folder sturcture to copy the files during the install and either cmdlines or GUIRunOnce to install.

Hope this helps,

[Space Between]

All this is mentioned in the multi 2k os thread here that is never ending...all you seek is in there

[Lash]

In the GuiRunOnce section of the .sif file, add a line for each program you want to run.  It will run once, upon first logon. You can point it to a network or local location.  Example:

[GuiRunOnce]
IE6 = \"servernameshareIEi386setup.exe\"

Hope this helps...
Lash

[TheReasonIFailed]

I think www.tech-hints.com would help you with that question.

[Anonymous]

Yeah, I tried that one. Nada.

Now I\'m using WinXP\'s Setupmgr program, I want to be able to install from a custom bootable install CD that has my file in the i386 directory, but I cannot figure out how to get my exe file to copy from the CD to the target install directory during setup so I can invoke it via command line on first boot.
Or maybe a *.sif entry that will search the i386 dir of the install CD?
Must be some sort of variable in case the CD drive is a different letter on differnet computers.

Anyone know?
Please help.

Thanks.

[Twinkie]

You can add extra files for an installation that might be specific to your software or hardware in/on the machine. These are placed in the $OEM$ folder under the I386 folder. You can have the following:

$OEM$textmode Hardware dependant files for use during the initial Windows 2000 install and text mode setup such as OEM HAL\'s, SCSI drivers etc.
$OEM$$$ Used to replace any core system files and must match the structure of the Winnt structure. For example to replace files in the winntsystem32 folder you would create $OEM$$$system32
$OEM$$1 Files that you want to be copied to the drive where Windows 2000 is installed (%systemroot%)
$OEM$$Drive Letter% Same as $1 but allows you to set a specific drive letter, e.g. $OEM$C would copy everything under it (including subfolders) to C
$OEM$$$Help This subfolder contains the OEM Help files to be copied to C:WinntHelp during setup.
$OEM$$$System32 This subfolder contains files to be copied to the C:WinntSystem32 folder during setup.
$OEM$$1PnPdrvrs This folder contains additional Plug and Play drivers not included. You can replace PnPdrvrs with a name of your own choosing with eight or fewer characters. Note: This folder replaces the Display and Net folders used in Windows NT Workstation 4.0
$OEM$$1Sysprep This subfolder contains the files required to run the Sysprep tool.

Files that must be renamed need to be listed in $$Rename.txt. Note that the files in these subfolders must have short file names.

Important

The OemPreinstall = Yes statement is required if you are using the $OEM$ folder to add any more files to the system.


For XP put the $OEM$ folder under the I386 folder.  With 2000 you will need to put the $OEM$ folder next to the I386 folder if installing from a CD.

Again more info can be found at my site,