Unattended Installation and cmdlines.txt
Scott D. Hill
between W2K and XP. I've noticed that while we were able to connect to a
network drive during the GUI phase of W2K we are not capable of performing
the same action in XP.
After the network is installed and gets it's configuration and joins the
domain, the "System error 1222 has occurred. The network is not present or
not started." error message is displayed while attempting to execute a net
use statement.
I've been watching and testing during the whole GUI phase using the cmd
prompt and I've noticed different services starting and stopping.
TaskManager shows the NIC operational and connected.
The unattended is set for OEMPreinstall=Yes, however, none of the
cmdlines.txt commands are being executed. We've verified that the file has
been copied to the C:\$win_nt$.~ls\$oem$\. It gets deleted during the last
step below (removing temporary files).
I'm curious, when is the cmdlines.txt supposed to be initiated? During W2K
it was during the Registering Components sub-process. The following is the
detailed process during the GUI phase:
Installing Windows - 37 minutes
37 Minutes - Installing Devices*
32 Minutes - Installing Network*
29 Minutes - Building File List
28 Minutes - Copying Files
27 Minutes - Completing Installation
24 Minutes - Installing Start Menu Items
18 Minutes - Registering Components
Finalizing Installation -9 minutes
9 Minutes - Saving Settings
1 Minutes - Removing Temporary Files
*During this time frame services start and stop due to the plug and play
verification process, however, the network services are started.
George S. Ellis
to the one that starts EXPERTS. I have responded there with a small
attachment. I use a VBS to control install and make sure I have a desktop
and services running before I start my heavy-duty installation routines.
"Scott D. Hill" <sdhi...@earthlink.net> wrote in message
news:uoa968HQBHA.1348@tkmsftngp05...