G
Guest
I have recently built unattended setups for our 2003 server and Window XP SP2
core image build processes. I have followed the same procedures and
configurations for both platforms. The 2003 Server install works like a
champ...however, the XP SP2 setup fails (I also for compare purposes tried to
roll this back to our SP1 install, fails there as well).
The error I get is:
"INF file txtsetup.sif is corrupt or missing status 4"
Is there anything different in the process for the Unattended setup for
XPSP2 vs. 2003 Server other than the obvious things in the winnt.sif file
that are specific to XPSP2 & 2003 Server?
My unattended folder structure is as follows:
I386
|--$OEM$
| |--$1
| | |--DRIVERS
| |--$$
| |--TEXTMODE
| | |-<driver files and txtsetup.oem for SCSI controllers>
| |--txtsetup.oem
|
|--<all the normal directories and files from the I386 folder on the OS
source CD's>
core image build processes. I have followed the same procedures and
configurations for both platforms. The 2003 Server install works like a
champ...however, the XP SP2 setup fails (I also for compare purposes tried to
roll this back to our SP1 install, fails there as well).
The error I get is:
"INF file txtsetup.sif is corrupt or missing status 4"
Is there anything different in the process for the Unattended setup for
XPSP2 vs. 2003 Server other than the obvious things in the winnt.sif file
that are specific to XPSP2 & 2003 Server?
My unattended folder structure is as follows:
I386
|--$OEM$
| |--$1
| | |--DRIVERS
| |--$$
| |--TEXTMODE
| | |-<driver files and txtsetup.oem for SCSI controllers>
| |--txtsetup.oem
|
|--<all the normal directories and files from the I386 folder on the OS
source CD's>