MaxWilder Posted December 21, 2004 Share Posted December 21, 2004 Forgive me if I'm duplicating something, but I'm going a bit crazy trying to sift through the mountain of information on this site. I'm upgrading my whole company from Win2k to XP. I've got most of it figured out, but I keep running into problems because of a NIC Device Driver. The driver currently on all the machines is incompatible with XP.I have the XP version of the driver, but I can't figure out how to get it into an UPGRADE version of an unattended install. Since I can't copy over any OEM folder, I tried to use nLite to integrate it into a .cab, but all that does is cause an error message ("Setup cannot copy the file: e100b325.inf", etc.). I don't know exactly what nLite is doing, and I can't find any information about what to do next that isn't completely inapplicable to my situation. Does anybody have a newbie's guide to cab'ing drivers? Or is it even possible for an upgrade install?BTW, the stickies in this forum are completely unintelligible for a newb like me. Link to comment Share on other sites More sharing options...
MaxWilder Posted December 22, 2004 Author Share Posted December 22, 2004 Another option I'm exploring is devcon.exe. I've been trying various techniques with it and the best I ever get is "devcon failed". The documentation is vague and unhelpful.I think I'm cursed. Link to comment Share on other sites More sharing options...
MaxWilder Posted December 22, 2004 Author Share Posted December 22, 2004 Well, I finally got it to work. My boss discovered that devcon can only handle somewhere around 40 characters in the hardware id.For example, my NIC has the hardware id "PCI\VEN_8086&DEV_1229&SUBSYS_000C8086&REV_08\4&2AF9ED5&0&08F0"If you put that whole ID in the line, devcon will choke. However, it works fine if you just use PCI\VEN_8086&DEV_1229&SUBSYS_000C8086.So it finally worked when I used the line:devcon update c:\drivers\Network\Intel\e100b325.inf "PCI\VEN_8086&DEV_1229&SUBSYS_000C8086"This should solve my driver problem. I hope this can be of use to others. Link to comment Share on other sites More sharing options...
Bilou_Gateux Posted January 1, 2005 Share Posted January 1, 2005 Installing Intel® LAN Drivers Link to comment Share on other sites More sharing options...
MaxWilder Posted February 7, 2005 Author Share Posted February 7, 2005 In case anybody is interested in the batch code I now use...I have two drivers that need to be upgraded nearly every time I upgrade from Win2k to WinXP: The NIC and the Video Card. On our systems, we have some ATI cards and some nvidia cards. Since upgrading the NIC driver will disconnect the network until restart, I started by copying over all the XP install files. If you are doing this from a CD, this obviously doesn't apply. Remember, my challenge was a mass upgrade from Win2000 to WinXP. I ran this batch file over the network from an account with Administrator privileges. After copying the setup files, the main code is:_NIC_DRIVER_ECHO NICset hwid=for /F USEBACKQ %%l in ( `nic.bat` ) do SET hwid=%%lECHO Intel PRO Card hwid: >> drivers.logECHO ^ "%hwid%" >> drivers.logECHO. >> drivers.logSET hwid="%hwid:~0,21%"echo %hwid%if %hwid% == "" goto _SKIP_NIC_devcon update %SetupFiles%\drivers\Network\Intel\e100b325.inf %hwid%:_SKIP_NIC_:_NVIDIA_DRIVER_echo NVIDset hwid=for /F USEBACKQ %%l in ( `nvidia.bat` ) do SET hwid=%%lECHO NVIDIA Card hwid: >> drivers.logECHO ^ "%hwid%" >> drivers.logECHO. >> drivers.logif "%hwid%" == "" goto _SKIP_NVIDIA_SET hwid="%hwid:~0,21%"devcon update %SetupFiles%\drivers\NVIDIA\Win2KXP\66.93\nv4_disp.inf %hwid%:_SKIP_NVIDIA_:_ATI_DRIVER_echo ATIset hwid=for /F USEBACKQ %%l in ( `ati.bat` ) do SET hwid=%%lECHO ATI Card hwid: >> drivers.logECHO ^ "%hwid%" >> drivers.logECHO. >> drivers.logif "%hwid%" == "" goto _SKIP_ATI_SET hwid="%hwid:~0,21%"devcon update %SetupFiles%\drivers\ATI\2KXP_INF\c2_19577.inf %hwid%:_SKIP_ATI_:_BEGIN_INSTALL_Each of the batch files called are very small:nic.bat: The NICs in our systems are almost always some form of INTEL PRO PCI variation, so we had to really drill down to eliminate all the other INTEL lines that devcon found:@echo offdevcon find * | find "PRO/" | find "PCI"nvidia.bat: The video drivers were much easier to single out.@echo offdevcon find * | find "NVID"ati.bat@echo offdevcon find * | find "ATI"After the drivers were updated, the install command is executed from the local directory where all the install files were copied.%SetupFiles%\i386\winnt32.exe /s:%SetupFiles%\i386 /unattend:%SetupFiles%\%AnswerFile% /udf:%ComputerName%,%SetupFiles%\%UdfFile% /syspart:C /makelocalsource /debug4:install.logAs you can see I included lots of code to make logs, so I could see where things borked. Most of my upgrades run pretty smoothly now. I'm now incorporating defrags and backups of the vital WinNT folders in case of a major malfunction during the upgrade. The code just keeps expanding. Link to comment Share on other sites More sharing options...
staples Posted March 18, 2005 Share Posted March 18, 2005 I am having issues with some HP printer drivers. Have you done any printers with it. or other usb devices? Link to comment Share on other sites More sharing options...
buletov Posted March 23, 2005 Share Posted March 23, 2005 it's probably the same thing... just find the ID of your device... Link to comment Share on other sites More sharing options...
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