ziaxboss

I am not sure what I am looking at. I don't have a problem with the NIC driver. This installs when the [GuiRunOnce] line executes the start.cmd in the winnt.sif. The IE6 installs at the end of the XP installation routine, probably because it is part of the overall XP install. The issue is whether there is a way to have the start.cmd execute when the IE6 has finished because as my configuration stands, the NIC driver is installed while IE6 is also installing or if you like while the last part of XP installs.

The Start.cmd is simply a routine instigated in the winnt.sif ([GuiRunOnce]) to go to the Install/network folder and execute the setup.exe for the NIC driver. This driver seems not to be available in OEM format and won't install if included in the OEMdrivers path in the winnt.sif. The IE6 installs at the end of the XP installation routine. This happens whether or not the start.cmd is in the winnt.sif. The IE6 install is not an issue; it is the timing of the IE6 or the start.cmd routine that is a problem. As I said before it actually does not make any difference to the end result because the start.cmd allows 1 minute before is reboots the machine, which is enough time for the XP install to finish installing the IE6. see below for start.cmd contents. ******************************************************************* CLS @echo off TITLE Windows XP SP3 - Unattended Installation ECHO. ECHO Over the next few minutes you will see automated installations ECHO of various sofware and driver applications, windows updates, and registry ECHO updates. Your computer will restart automatically ECHO once the whole process has finished! ECHO ECHO Please enjoy your pcbusiness.ca computer system. ECHO. ECHO Installing Network Drivers ECHO Please wait... start /wait %systemdrive%\install\network\setup.exe /qn ECHO. ECHO Restarting the PC in 1 minute... shutdown.exe -r -f -t 60 -c "Windows XP will now restart in 1 minute, this provides sufficient time for the updates to finish and for the shell to fully load before it\'s ready to restart!" ECHO. ECHO Deleting Temp Installation Files... RD /S /Q %systemdrive%\Drivers RD /S /Q %systemdrive%\install EXIT **************************************************************************** As you can see there is no reference to IE6. Below is some info form the INF file for the driver, I don't if that helps. ; e100b325.INF ; $Revision: 11 $ ; ; Intel 8255x-based PCI Ethernet Adapters ; PnP install script for Windows XP ; ; Version 7.0.26.0 Regards

Hi I have made an XP_SP3 bootable disk using various methods including some from the recommendations on this site. I created an OEM Dell XP_SP3 bootable which works fine. I am creating several of these install disks to suite various models and I was missing an OEM driver which was not available, so I created a start.cmd batch file to execute the setup.exe for the required driver (network for Dell Dimension 8300). The install goes fine, however in course of the final stages IE6 is loaded. This is clumsey because the start.cmd does not wait until it is loaded before it executes its instructions. This does not affect the instsall because there is a 1 minute delay for restart following installation od the driver, which provides enough time for IE6 to also finish installing. My question is simple: Can I control the start.cmd to commence after installation of IE6 (so that the install is controlled and looks professional) Or is there a way of installing the IE6 automatically after the restart following succesfully reboot upon execution of the start.cmd batch. Compliments to the chef of the "unattended Guide" recipe! Regards

Hi all who was involved with this post. I am reselling various main stream used computers. These computers are off lease units and come with the COA and the HD is a blank canvass waiting for me to re-install the OS. Today I wanted to make a new OEM DELL Optimplex xp home disk. I took an original MS OEM xp SP1 home edition CD and copied all files to a local folder. I then stripped out the unecessary folders and added the following: winnt.inf and svcpack.inf together with a folder SVCPACK in which I placed a number of further KB123456.exe updates. So far so good. I added $OEM$ and inside added folders for the drivers specific to the Dell. I then used "Autostreamer" to (1) slipstream sp3 and (2) create my ISO. I used Roxio 8 to create the new CD from the ISO. I then proceeded to install xphome on my victim machine; the Dell Optiplex GX260. A little way into the installation, I got the dreaded message that there was a problem with the SXS.DLL; Syntax error in manifest or policy file. After some digging on the net I read various opinions but no real answer. I looked at my install and couldn't see anything wrong with the files or the method. I had previously burned an XP pro disk in the same way, which worked great. I did however notice that the volume name on the CD was slightly different to that of the original MS OEM disk. The original was XRMHOEM_EN and I had XROEM_EN. I decided to make a new cd from scratch going through the exact steps above, however I made sure the volume name was the same. The new CD installed the OS without a glitch. My experience may have been a one off but I thought I would share it with someone.