McDanger Posted May 4, 2005 Posted May 4, 2005 That did the job. I guess I should read better... Now, I have a hotfix and realize that this doesn't help at all. During the Unattended Installation (AI) Windows will search for the available drivers. It will find the appropriate driver but the hotfix isn't installed yet.I use Windows XP SP2 integrated and I install the hotfixes during app install fase. Hhhmm,....Is there a way I can integrate the hotfix in the source?
McDanger Posted May 4, 2005 Posted May 4, 2005 And another example of reacting to quick... For anyone who had the same problem. Use:WindowsXP-KB873333-x86-ENU.exe /integrate:C:\XPCDWhere C:\XPCD should be the path to your source dir.I'll give it a go and post my outcome.(It'll probably take some time a I now want to integrate all my hotfixes )
Bâshrat the Sneaky Posted May 4, 2005 Posted May 4, 2005 @McDanger: that way it will probably NOT work, maybe in this case but... The way I just mentioned, it will ALWAYS work! EDIT: unless that hotfix of you isn't a driver of course...
Nas001 Posted May 5, 2005 Posted May 5, 2005 I was installing all my patches from svcpack.inf, but I used the /integrate switch to slipstream this one patch into my unattended install. It worked great and solved the monitor issue.My company is now moving ahead with an SP2 rollout, so I will likely /integrate all of the patches in our next image.Just an FYI,
McDanger Posted May 9, 2005 Posted May 9, 2005 I must say. I've now integrated nearly all my hotfixes, two wouldn't work, and it's working great. B) Even the pop-up with the hardware wizard is gone now.Many thanks guys.
ajbritton Posted May 10, 2005 Posted May 10, 2005 I do RIS installs, and occasionally I get the odd PC that will appear to pause during a setup and ask for a driver, but in fact the installation continues behind the scenes with no user intervention actually required.
Nas001 Posted May 10, 2005 Posted May 10, 2005 I do RIS installs, and occasionally I get the odd PC that will appear to pause during a setup and ask for a driver, but in fact the installation continues behind the scenes with no user intervention actually required.<{POST_SNAPBACK}>Actually, that's what was happening with the setup I use. It prompted for the driver, and after about 4 minutes (yes, I timed it) it would continue on. It did pause setup during that time, which was unacceptable to my employer.
RogueSpear Posted May 10, 2005 Posted May 10, 2005 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.
Nas001 Posted May 12, 2005 Posted May 12, 2005 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 Posted February 8, 2006 Posted February 8, 2006 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.microsoft.com/?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 Posted February 23, 2006 Posted February 23, 2006 Is there any workaround yet? It only pops up when I intergrate my display drivers.. I have a Toshiba Equium m40x
RyanVM Posted February 23, 2006 Posted February 23, 2006 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 Posted February 24, 2006 Posted February 24, 2006 (edited) 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=32Xresolution=1280YResolution=1024Vrefresh=85Still work?I'll try it. Edited February 24, 2006 by Aid
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