[rewyn]

I have a problem with my unattended XP CD.
I Have made a RunOnceEx.cmd and a cmdlines.txt file in my $OEM$ directory.
the cmdlines.txt points to my RunOnceEx.cmd like this:

[Commands]
RunOnceEx.cmd

In the WINNT.SIF file i have deleted the GuiRunOnce or whatever the name is
When i start the RunOnceEx.cmd on my Local computer, it works and after reboot he tries to install the applications, but fails because they are not at the right place(is ok, because the are not there)

My WINNT.SIF file looks like this at the points of OEM including:

[Data]
Autopartition = 0
FloppyLess = 1
MsDosInitiated = 0
UnattendedInstall = Yes

[Unattended]
UnattendMode = FullUnattended
UnattendSwitch = Yes
OemPreinstall = Yes
OemSkipEula = Yes
FileSystem = *
WaitForReboot = No
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
TargetPath = Windows
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore
Hibernation = No

I know there are other lines in WINNT.SIF, but they are not nessecary for that porblem.

So i created an iso and started installation with VPC, everything worked, but after the second reboot the applications should be installed, but nothing happens.

I looked on the harddrive in VPC and there is no install folder.
Is this folder removed after the windows installation?
Another point is my cmdow.exe, which is Placed in $OEM$\$$\system32\
but after installation it is not placed in Windows\system32\

I'm sure it is not(only) the problem of the source, which seems not to be copied to the harddisk, because if the RunOnceEx.cmd runs at T-13 installation, the installation window must appear at the reboot, but it does not.

I have searched the forum and found an article, in which one said to set a PAUSE to the RunOnceEx.cmd and to remove the cmdow /HID command. So i have done this and on my Computer it worked, after setting the registry keys he waited for any key, but at installation on VPC he never stopped.

I think the problem is, that the RunOnceEx.cmd is never executet and it seems that the folders in $OEM$ are never copied to harddisk.

I have tested many things and now i haven't any ideas.

mfg rewyn

[sleepnmojo]

Since it looks like you have everything right, I'm gonna ask you to post the entire winnt.sif file. Sometimes the problem can lay somewhere in there, and you may not notice it.

Also I want to clarify if you are doing a cd install or network. Also where are you placing the $OEM$ folder and winnt.sif file?

It sounds like you did everything right, but it isn't running the OEM parts. This is generally caused by the OemPreinstall missing from your winnt.sif file, or a misplaced folder. Looks like you have both of those, but I just want to double check.

[rewyn]

I think i have found the error. My $OEM$ folder is placed in the i386 directory and not parallel to it.

I'll give that i try.

[Alanoll]

rewyn, on Jun 10 2005, 05:40 AM, said:

I think i have found the error. My $OEM$ folder is placed in the i386 directory and not parallel to it.

I'll give that i try.
<{POST_SNAPBACK}>

that will do it if you're trying to perform a CD based install

[rewyn]

The problem was, that the $OEM$ folder wasn't at the right place.

Now i want to do the same thing with Win2003. I have copied the $OEM$ folder from the XP Setup to the Win2003 setup at the right place. I have created the Winnt.sif with nLite an placed it in the right folder.
But after windows setup copies the windows files to disk, it should copy the alternative software to c:\install, but it dosen't and after installation he wants to install this software but it couldn't find its source...

I also tried with the winnt.sif from XP but, their also is no alternative software copied to disk.

Has anybody of you an idea?

[DonDamm]

If the structure of your folders is correct, the files will be copied during the first phase of the set up just after all the Windows files have been copied over.

If you post your winnt.sif as has been suggested, we can better see what you have done.

Your RunOnceEx.cmd file must be in the $oem$ folder along with your cmdlines.txt file, and the stuff you want to be installed must be placed in $oem$\$1\Install.

Please note the $1 folder. If you've left this out, it won't work as you expect. If you haven't done this properly, things won't be copied to the right place.

During the first part of setup you can watch and see the files being copied over. Note: If you have more than a few programs and more than about 50 or 100 MB, I would leave them on the disk and change my path to reflect that. My own UAI is now over 3 GB and growing, but fitrs comfortably on a DVD. :o)