jguyomar

Hi! I know that this post is from 1 year ago but it turned out that I had exactly the same problem with my HP NC4200 and that they gave me really hard time!! It took me almost 1 whole week to figure out what was the problem that prevented me to deploy a RIPREP image onto a HP NC4200. But now I'm relieved... Like imbrod00 said, during the Mini-Wizard Setup PNP Enumeration, ths Laptop was installing some devices and all the sudden stopped responding... And it would not go ahead except if rebooting the PC. I found out that this issue was coming from the Graphics/Monitor Drivers that somehow requires the PC to be rebooted to work properly. Knowing that I decided to postpone the Graphics/Monitor Drivers Installation to the GUIRunOnce part. And then, my HP NC4200 stopped freezing during the Mini-Wizard Setup PNP Installation. And just a last note: the HP NC4200 Graphics/Monitor Drivers are signed so that there is no need for user intervention. So u get a silent installation of your Graphics/Monitor Drivers. I hope that this will helpp some of you save some time looking for an answer to that f... problem!! Now I can go back home... Julien.

Thanks Br4tt3 for you answer! But I took a look at all the switches for the "dpinst.exe" utility and could not find one that would enable me to install an UNsigned Driver on a WINXP without any user interaction. Could you tell me what would be the command you would use to do that? J.

I am using RIPREP to deploy Images of WINXP SP2 via a WIN2K RIS Server. I've been testing RIPREP for a while now so know pretty much of this system of Image Deployment. But I'm still stuck with one weird thing that I noticed when making the inventory of my Network PCs. I noticed that in the registry of the Destination RIPREP PC, the Registry key corresponding to the NIC of the Source RIPREP PC remained in my Destination RIPREP PC. Here is the Registry path I'm talking about: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards Under this Registry key, you have info concerning all the NICs that you have on your PC. Here are the NICs referenced under the above Registry Key for 2 RIPREP Destination PCs: I-KSPACEY Broadcom NetXtreme Gigabit Ethernet I-KSPACEY Intel® PRO/Wireless 2200BG Network Connection I-KSPACEY Intel® PRO/100 M Network Connection I-THANKS 1394 Net Adapter I-THANKS 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible) I-THANKS Intel® PRO/100 M Network Connection And here are the NICs referenced in the RIPREP Source PC: I-RIPREP 1394 Net Adapter I-RIPREP Intel® PRO/100 M Network Connection The NIC named "Intel® PRO/100 M Network Connection" related Registry Key seems to remain in the RIPREP Destination PCs. Just a note for some of you who would like to ask me to check if that NIC is not actually installed on the 2 RIPREP Destination PCs, I verified and am 100% sure: the "Intel® PRO/100 M Network Connection" is only physically present on the RIPREP Source PC, that is I-RIPREP! Would someone have ever encounter this problem in the past? I searched on the net but no success so if someone can help me, please... J.

Thanks for the answer. I forgot to mention that during the RIPREP installation, Unsigned Drivers Installation is allowed and is working. For that I used the 2 following parameters in the Answer File riprep.sif: Unattended] UpdateInstalledDrivers = yes DriverSigningPolicy=Ignore Once the RIPREP-ed PC boots for the 1st time after the RIPREP installation has completed, the policy "DriverSigningPolicy=Ignore" is still applied so that unsigned drivers should be installed silently but they are not. The only thing this policy does is telling the OS not to display the Warning window saying that the Driver is not signed! But I am actually looking for a way to automatically, that is without any user interaction, install an UNsigned driver under WINXP! I don't want to have to install it manually via the "Found New Hardware..." window!! IF someone knows how to do that, god I can tell I would be really thankfull! J.

Take a look at the following article: http://www.microsoft.com/technet/prodtechn...y/tpcdploy.mspx (search for "Unattended Setup and RIS CD-Based Images") It says that "DriverSigningPolicy = Ignore" should take care of an unsigned Driver but only if it is the best match, that is a Hardware ID match! Maybe the drivers that you got from NVIDIA are not the proper ones for your Sound Card. I guess you checked first but sometimes websites are so messy that it is hard to find the proper driver especially with NVIDIA Drivers! To make sure, take a look at the Inf file of your driver and look for the Hardware ID or name that looks like the one of your sound card. To make sure that u get a Hardware ID match, install manually you NVIDIA driver and go to the Device Manager. Double click your Device and click on the "Details" tab. Look at the "Device ID" and "Hardware IDs". Then search for those IDs in your inf file. If you find 1 or more in your inf file, make sure that they correspond to Hardware IDs too and not Compatible IDs. Here is an example: [intel.Mfg] %iMGM% = i852GM, PCI\VEN_8086&DEV_3582 %iGDGD0% = i915G0, PCI\VEN_8086&DEV_2582 %iGDGD1% = i915G1, PCI\VEN_8086&DEV_2782 %iALVD0% = i915GM0, PCI\VEN_8086&DEV_2592 %iALVD1% = i915GM1, PCI\VEN_8086&DEV_2792 %iLPGD0% = i945G0, PCI\VEN_8086&DEV_2772 %iLPGD1% = i945G1, PCI\VEN_8086&DEV_2776 %iCLGD0% = i945GM0, PCI\VEN_8086&DEV_27A2 %iCLGD1% = i945GM1, PCI\VEN_8086&DEV_27A6 This is what you have in the INTEL 82852/82855 GM/GME Graphics Controller Driver Inf file. This Driver can actually handle different Graphic Controllers. The 1st line tells gives you the Hardware ID but no Compatible ID. So in %iMGM% = i852GM, PCI\VEN_8086&DEV_3582 "PCI\VEN_8086&DEV_3582" is the Hardware ID of your .inf file. If it had a compatible ID, it would read like this: %iMGM% = i852GM, PCI\VEN_8086&DEV_3582, Compatible_ID So just take a look at your .inf file and let me know about it. J

I am using RIPREP to deploy WINXP SP2 images to my new workstations. My RIS Server is WIN2K Server. I am trying to automate the Drivers Installation. (like many of us! ) So I decided to store all the BTS DriversPacks in a Distribution Point on a remote server so that all new PnP Devices be installed when RIPREP reboots the newly installed PC. Signed Drivers get installed automatically, that is without any user interaction (=Server-Side Driver Installation). But some of the drivers in the BTS DriversPacks are unsigned drivers and those drivers do not get installed automatically. I can still install them (Client Side installation) when the "Found new hardware..." window comes up but that requires me to do it manually which I don't want to given that I will have to install more than 120 PCs using this method very soon. Would someone know a way to modify the registry or another way so that even unsigned drivers can be installed without user interaction, that is via Server-Side installation? I hope someone will be able to help me out. J.

Hi! It may be that your drivers are either not signed or that there is only a Compatible-ID match and not a Hardware ID Match between you Sound Card and your drivers, in what case WINXP by default will not install those drivers automatically. But you would still be able to install them when logged on with administrative rights! Let me know if your drivers are signed or not! If they are, you should find a .cat file among all your driver files. J.

Thanks Laura!!

Ok! So where can I find the list telling me all the diiferent phases from t-n to t-0? Julien.

Hi! I'm a newbie in this area and have been reading many topics here on this forum and noticed many times that people were talking about different times named "t-something" where something is a number during the OS Setup! Could someone tell me where I can find a list enumerating all those phases of an OS Setup? Thanks in advance! Julien.

Thanks for your answer! I've been looking for other lists of Built-In Windows Drivers on the link you provided but couldn't find any other! The most important list to me would be NICs (LAN/WLAN), Graphic Cards, Sound Cards, MassStorage, and Chipset Built-In Drivers Lists! Would anyone know about such lists? There must be somewhere such lists!! Otherwise how do people using DriverPacks to find out which drivers to put in their DriverPacks??

I am looking for a list that would enable me to find out if such or such a device could be installed on WINXP or WIN2K without having to provide a Driver Floppy or CD. In other words, a list that would tell me if WINXP or WIN2K System-supplied Drivers contain the proper drivers for my Device! I thought that the HCL (Hardware Compatibility List) had that purpose. But I am wondering now if the HCL includes info about devices that can be installed on WINXP or WIN2K and that do not harm the OS or if it is the inventory of only the devices that have their drivers as system-supplied drivers. Would someone know the answer about this question? Thanks in advance for any help! Julien.

Would someone know how to make sure that a driver of for example a device "A" is a built-in WINXP Pro driver or if to install that driver vendor-supplied drivers are necessary? I am looking for such a list that would enable me to make sure that my PCs' NICs' drivers (and other drivers too actually!) will be supported when running RIS on them without having to add them to the RIS Server. I thought that the Windows Hardware Compatibility List (HCL) had that purpose but I'm not sure of it. If someone knows the answer, please let me know! Julien.