> > > Hi, > I had the same problem with the intel PRO 100 nic driver being in > a path too deep for the win2k setup to copy to the local machine. > I got round this by moving the files up a directory and then editing > the inf file to point to the modified path.
Ah! I figured that it would need to be modified in this manner at the time but was lacking in the necessary understanding of the schematics (and was somewhat pushed for time). > > Also I added the new path to the OEMPnPDriverPath in site\unattend.txt > so win2k setup should find it there as well. > > I did seem to be getting a problem with Win2k finding a driver in Oem.inf > that it thought was a better match with the hardware but didn't work. > Win2k setup identified the hardware as a PRO 100Ve card but if i changed > the driver for the Pro 100 then everything worked ok. Very interesting indeed. I'll take a look at this and give it a shot again one of the boxes in question. Thanks :) I'm somewhat suprised that Windows, to this day, continues not to provide out-of-box support for this particular card (which appears to be in common usage). Perhaps there is some intellectual property issue on Intel's side. Regards, --Kerin Millar ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
