[Nas001]

RogueSpear, on May 10 2005, 10:31 AM, said:

Nas001, on May 10 2005, 08:36 AM, said:

It did pause setup during that time, which was unacceptable to my employer.
<{POST_SNAPBACK}>

An impatient fellow considering you've probably automated 90% of the setup process to begin with.
<{POST_SNAPBACK}>

Maybe, but I like receiving my paycheck. The process is 99% automated, however it is quite lengthy (2-3 hours per machine) and used globally. They told me to resolve the issue, and I did. IMO, that's how employee/employer relationships are supposed to work. Besides, it wasn't difficult to contact Microsoft for the patch, once I realized there was a patch out there.

[Nucleus]

I have the same problem. During hardware detection, the «Found New Hardware» wizard pops up and asks me to click "Next" so that it can find the proper drivers for "Plug and Play Monitor" When I click "Next" it just installs it, without me having to do anything.

I was going to install KB883667 but then I read that this patch is for fixing windows from hanging while installing the video driver, which is not my case (http://support.micro...om/?kbid=883667). My setup does not hang, it just asks for the driver.

It seems that this problem mostly occurs on laptops. I am using an HP Compaq nx6110

[Aid]

Is there any workaround yet? It only pops up when I intergrate my display drivers.. I have a Toshiba Equium m40x

[RyanVM]

If any of you feel like being a guinea pig, send me a PM and we can try to see if we can fix the problem.

[Aid]

I'm not exactly familiar with using the CMDLINES.TXT, but it mentions it gets parsed at T-12.
I dont know wether this prompt comes up for people who intergrate their Display drivers at the start of Gui Install but it is for me.
Couldn't you use CMDLINES.TXT to launch a batch file to install the Display drivers at T-12?
Would the;
[Display]
BitsPerPel=32
Xresolution=1280
YResolution=1024
Vrefresh=85
Still work?

I'll try it.

This post has been edited by Aid: 24 February 2006 - 10:06 AM

[Nucleus]

Well, today I tried intergrading KB883667 too. It wouldn't let me, since I already have SP2 and all the updates. So I guess there is no solution for this problem.

[Nucleus]

I am currently using the Drivers from CD: Simple Method, as suggested in this topic to solve the problem of the Unattend Install Prompting For Monitor Driver.

This is my winnt.sif

;SetupMgrTag
[Data]
	AutoPartition=0
	MsDosInitiated="0"
	UnattendedInstall="Yes"
	AutomaticUpdates="Yes"

[Unattended]
	FileSystem=*
	UnattendMode=FullUnattended
	OemSkipEula=Yes
	OemPreinstall=Yes
	UnattendSwitch=Yes
	TargetPath=\WINDOWS
	DriverSigningPolicy=Ignore


[GuiUnattended]
	DetachedProgram=".\system32\cmd.exe"
	Arguments="/Q /C FOR /F %I IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %J IN (%I$OEM$) DO (IF EXIST %J (start /min /D%J NirCmd.exe exec hide Drivers.cmd)))"
	AdminPassword=*
	EncryptedAdminPassword=NO
	OEMSkipRegional=1
	TimeZone=130
	OemSkipWelcome=1
	
[Display]
	Xresolution=800
	YResolution=600
	AutoConfirm=1

[UserData]
	ProductKey=xxxx-xxxx-xxxx-xxxx-xxxx
	FullName="Windows XP"
	OrgName="Professional"
	ComputerName=Windows

[TapiLocation]
	CountryCode=357
	Dialing=Tone

[RegionalSettings]
	LanguageGroup=4
	SystemLocale=00000408
	UserLocale=00000408
	UserLocale_DefaultUser=00000408
	InputLocale=0408:00000408
	InputLocale_DefaultUser=0409:00000409

[Identification]
	JoinWorkgroup=WORKGROUP

[Networking]
	InstallDefaultComponents=Yes
	
[Components]
	msmsgs=off
	msnexplr=off

I have also tried installing KB883667 as suggested in this topic, no luck either, propably because I already have all the latest windows updates.

The problem of Unattend Install Prompting For Monitor Driver still exists though. What else can I try?

[RyanVM]

My next update pack will include KB883667, and I've heard reports from a few testers that it does indeed fix the problem. Stay tuned

[Nucleus]

You were right. KB883667 does work! I have no idea what was wrong with my I386, but as soon as I re-copied it from the CD to my HDD, and tried to slipstream KB883667, it all went very smooth. Then I did a fresh install on the laptop, and there were no popups asking for drivers. Perfect!

[x9731091]

I was having the same problem (pausing during install while NHW looked for a monitor driver) so I followed http://support.micro....com/?id=814847 (supplied by Bashrat) to fix my unattended install running off a W2K3 RIS server with the kb883667 hotfix.

Bashrat, I'm not sure why integrating the hotfix would not work as you mentioned; I tested it and it worked fine. My understanding is that any hotfix can be integrated (I use the SVCPack method). The only reason I wouldn't integrate it is because it is easy for me to see what hotfixes have been applied using SVCPack and also allows me to remove a hotfix should I need to.

[mbaker33]

sorry to bring back a basicly dead thread, but I am really looking for an answer to this.

I have a Windows 2003 server running RIS which works great, unless there is an intel video card on the client computer. When the intel card is present, the prompt for monitor driver happens.

I downloaded the WindowsXP-KB883667-x86-enu.exe file posted above, but I cannot integrate it because I already have SP2 integrated in the build. Does anyone have any ideas? Or does anyone have a how-to on integrating the WindowsXP-KB883667-x86-enu.exe, maybe I missed something.

[Victor]

I just wanted to add that I had the same problem here. During the monitor driver install part, the popup for 'plug and play monitor' was showing up 2 or 3 times and you have to go through the prompts even though nothing was really accomplished by that because the drivers were self-installed anyway. Yes very frustrating. I was using an XP SP2 install CD for a DELL D620. The D620 does not have a specific driver for the monitor so the MS generic one is installed.

I tried all those suggestions for WINNT.SIF, those 2 driver signing settings to ignore, everything was set to full unattended and this problem was still popping up. Then I tried integrating SP3 into the install CD. This alone fixed this problem for me. I wanted to pass that along, it might work for someone else.