Unattend Install Prompts For Monitor Driver? but it works fine with all others tried
Posted 17 February 2005 - 01:36 PM
So during install with the 15", setup suddenly asks if I want to connect to the Internet to search for drivers for the monitor. clicking no, install automatically, it comes to Finish, then setup continues without a hitch. Display seems fine when all is done, and no special monitor drivers have been loaded. But it made setup STOP in the middle so it could ask me to provide nothing meaningful. So 1) is there a log I'm missing somewhere as to where PnP didn't find the drivers it wanted (and what that specifically was)? or 2) is there a way to tell setup that if it doesn't find a particular driver then tough luck, no it MAY NOT stop and ask, it must finish the install like a good setup program?
Posted 17 February 2005 - 01:53 PM
OemPreinstall = Yes
TargetPath = \WINDOWS
Filesystem = ConvertNTFS
OEMSkipEula = Yes
UnattendSwitch = Yes
NtUpgrade = No
Hibernation = 0
CrashDumpSetting = 0
Repartition = Yes
Value: Yes | No
Instructs Setup not to connect to the Windows Update site to download any available Windows Setup updates or necessary drivers that were not included on the Windows CD-ROM.
DisableDynamicUpdates is equivalent to the command:
winnt32 /unattend /disabledynamicupdates
Dynamic updates are disabled by default so corporate administrators can more easily standardize on a known set of Windows system components.
Instructs Setup not to connect to the Windows Update site.
Instructs Setup to connect to the Windows Update site to download any available Windows XP Setup updates. Setup also downloads any necessary drivers that were not included on the Windows XP CD-ROM.
Posted 17 February 2005 - 02:14 PM
and try again. I don't have it and it has never searched for drivers...
EDIT: what is that image in your signature?
This post has been edited by B‚shrat the Sneaky: 17 February 2005 - 02:14 PM
Posted 17 February 2005 - 02:23 PM
Microsoft MVP Info Page
thanks, I'll get rid of that line.
like I said, though, the wierd thing is out of 5 different setups I'm testing on, it only seems to do it with this monitor. I'll repost with results...
Posted 17 February 2005 - 02:27 PM
Posted 17 February 2005 - 02:28 PM
RichM, on Feb 17 2005, 03:25 PM, said:
Not to mention a Truemobile 1300 in my laptop thought I bought seperate.
Posted 17 February 2005 - 02:43 PM
soulin, on Feb 17 2005, 02:27 PM, said:
well... I'm not exactly sure what system the monitor came from... I have 4 different types of Dell Optiplexes at my desk, and none of the monitors actually came with any of the 4 that I have here. (plus I use MS VPC because sometimes waiting to burn a CD is too long a wait )
so I just tried searching for monitor drivers, for 151fp, looking for a monitor device group, etc... gave up after 30 minutes -- may not sound long but I have gotten up to speed from ground zero with a working AIO DVD after 3 days, including cdshell customized, BartPE customized, multiple encrypted product keys, etc, etc
usually the Dell site is good, and I only buy Dells if I can help it.
Ah an update.... Found New Hardware Wizard:
used winnt.sif from floppy, minus the DisableDynamicUpdates = Yes switch...
Told it I would choose a driver for this device, it failed, said there "was a problem installing this hardware:
An error occured during the installation of this device
There is no driver selected for the device information set or element"
I haven't added the drivers that Ryan linked to, I will in a minute (+rebuild ISO + reburn DVD-RW + re-run setup from DVD)
Posted 17 February 2005 - 04:33 PM
I just finished with the added drivers and it worked fine, no stopping. so either it was the drivers, or it was adding the space on either side of the =, as in:
DisableDynamicUpdates = Yes
does the space matter??
Posted 18 February 2005 - 09:07 AM
I'd bet there's already info on TCP/IP though...
Posted 22 February 2005 - 11:10 AM
BitsPerPel = 32
XResolution = 1024
YResolution = 768
VRefresh = 60
AutoConfirm = 1
I did this, no change. (I had everything but VRefresh and AutoConfim already in there)
It's the stupid Plug and Play Monitor being detected. Note that setup doesn't actually stop, it continues and right before the screen blanks a few times (installing the OEM video drivers I assume) the hardware detection dialog goes away. I included the monitor drivers in the drivers\00_sys directory, but it doesn't install them. After setup is through, I can go in and update the monitor drivers manually, using the files in the drivers\00_sys directory, and then it installs them fine. Nothing seems to change, but how do I make the stupid detection box not come up?!?!?!
DisableDynamicUpdates does not do it, by the way
Posted 22 April 2005 - 03:15 PM
I have the same problem on the XPsp2 image I'm building. Only the Dell D610 laptop gets the 'found new hardware' popup during hardware installation.
I don't have a external monitor hooked up BTW.
All the drivers are available. When I cancel out from the wizard, installation continues and the computer comes up fine with no hardware bangs.
Posted 22 April 2005 - 03:19 PM
Posted 26 April 2005 - 06:14 AM
I'm having the exact same problem with the "Found new hardware" wizard. I'll provide you guy's some extra info on my specific problems that might help us out.
I'm preparing an Unattended Installation for a company. Before I used the silent install option for driver support. After adding support for a couple of different types of machines some of the drivers wouldn't install properly anymore.
I'm now using the OemPnPDriversPath variable in winnt.sif which works fine. The UA is supporting several types of Dell desktops and laptops (GX270, GX280, D600 and D610). After adding the drivers for the X1 (a new model, very light) my installation comes up with the unwanted wizard.
My guess is that when the video driver (Dell driver, Intel Graphics Video v18.104.22.16843, A02) is being installed, Windows will be triggered to start the FNH wizard. I don't think it has anything to do with the winnt.sif or anything else in the unattended process but more likely in the driver. The reason for that is I didn't provide any display drivers at all for none of the supported types and they work fine. Normally undetected hardware will just show up with a yellow exclamation mark.
BTW The driver mentioned above was an MSI setup. I used MaSaI to extract the .inf and .cat files and added those to my OemPnPDriversPath. Driver installs fine.
- ← Can't Image due to different hdd controller driver
- Device Drivers
- Integrating generic SATA drivers into XP install disc →