From microsoft
http://msdn2.microso...y/ms791569.aspxfrom
http://msdn2.microso...y/ms791545.aspxThis boot parameter is supported only on Windows Server 2003, Windows XP, and Windows 2000.
The /noguiboot option is supported only on Windows Server 2003 with SP1 and Windows XP with SP2.
When /noguiboot is used, the system does not initialize bootvid.dll, the software component that provides basic video support before the computer's graphics drivers are loaded. Because bootvid.dll is not operating, the computer cannot display bit-mapped graphics during the boot process.
You can use this parameter to investigate problems with video devices.
Example
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noguiboot
Windows Driver Kit: Driver Development Tools
/sos
The /sos parameter displays the names of the drivers as they load during the boot process.
/sos
Comments
The /sos parameter is supported only on Windows Server 2003, Windows XP, and Windows 2000. On Windows Vista and Windows Server "Longhorn", use the SOS option with BCDEdit.
Example
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /sos
Windows Driver Kit: Driver Development Tools
/bootlog
The /bootlog parameter records the names of drivers as they load during the boot process and saves the ordered list in the %SystemRoot%\ntbtlog.txt file.
I was just trying to help you find the problem driver. It's obvious that the reason you have a very long boot time is that windows is stuck looking for a driver.
SRX660