Philster Posted May 11, 2005 Posted May 11, 2005 I have a Fujitsu S7010 laptop and i am creating an Unattended Installation for it.During the installation it stops and asks if I want to connect to Windows Update as it wants to look for a driver for Plug n Play Monitor.If I leave this message after a few mins it continues by itself and the installation eventually completes and works perfectly.If i click No the message disappears, the installation continues and the driver is I assume installed from the CD. Again the installation then completes and works perfectly.But of course I do not want it to keep doing this as it is most annoying and frustrating!Does anyone have any clues as to where I am going wrong.The CD I have is a Unattended Disk for multiple PCs and laptops and i have never had this problem at all before.ThanksPhil
bacd Posted May 12, 2005 Posted May 12, 2005 actually this has happened to me as well on a Toshiba laptop...seems kind of random as it doesn't happen everytime, yet I use the same set of install files (nlite, wmp integrated, and ryanvm's pack) each time (meaning I don't run through the update process everytime, i have an archive so I don't have to redo it everytime I make my UA)no idea as to what causes this though...
mythosaz Posted May 13, 2005 Posted May 13, 2005 I hate to just throw in "Me Too!" posts, but I see this on my Dell D410 laptops.
monisriz Posted June 1, 2005 Posted June 1, 2005 i hava the same problem but that is with my hp810c printer...the drivers for the bugger are included by default on the original windows xp cd..the "windows update/found new hardware" dialog still pops up for some friggin' reason...any way to bypass this would be highly appreciated!
Incroyable HULK Posted June 1, 2005 Posted June 1, 2005 The same goes for the Fujitsu S6210...I beleive it is because the Graphic drivers get installed and then Windows is re-detecting the monitor and asking for some drivers. Of course, you don't have to do anything and everything will go fine...
Bâshrat the Sneaky Posted June 1, 2005 Posted June 1, 2005 hehe You should include those drivers as any other driver using the OemPnPDriversPath in your winnt.sif.This only happens since SP2 and in fact it's a bug if I remember well. This heavily relies on my not-so-top-notch memory, but I think there was a hotfix available for it, though only available for 'gold members'.I think adding the monitor drivers would be less work.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now