My Intel & Broadcom Drivers

[John McGuire]

Just to help people out, as it took me a while to get all the drivers working

I've uploaded the Pro100, Pro1000 and Broadcom drivers I've used for our Dell PC's

Broadcom XP & 2000

http://www.chippers.me.uk/ris/Broadcom/

These where copied to i386 and $oem$/$1/Drivers

Intel Pro100 XP & 2000

http://www.chippers.me.uk/ris/Ris100/

The i386_2k deirectory contains the i386 drivers, same driver for XP

The Inst_2k is for the $oem$/$1/Drivers directory, same driver for XP

Intel Pro1000 XP & 2000

http://www.chippers.me.uk/ris/Ris1000/

The i386_2k directory contains the Windows 2000 i386 drivers

The i386_XP directory contains the Windows XP i386 drivers

The Install directory is for the $oem$/$1/Drivers directory for 2000 and XP

Server 2003 uses the XP drivers for all the above

Dont forget to net stop binlsvc & net start binlsvc afterwards

Hope these help

Tested amd working on

GX620 GX620USF GX280 GX270 GX260 GX240 GX400 D610

Edited November 22, 2005 by John McGuire

[Fencer128]

Hi,

If you need to get problematic NIC drivers working in RIS (text mode setup) then I've found that 99% of the time the fix is to edit the appropriate INF file as described below. The article is from Broadcom but applies to other INF files too.

The instructions for editing them can be found here on Broadcom's site under "No. 79":

http://www.broadcom.com/drivers/faq_drivers.php

It appears to be a parsing problem. Once you know this you should be able to get those drivers working on all your boxes. I have Broadcom, Marvell and Intel drivers all working this way on many PCs (actually the newer Intel drivers ship with RIS specific INFs in the driver folders - or they just work "out of the box" - it was the older pre 10.0 drivers that needed the editing mostly).

Cheers,

Andy

Edited November 23, 2005 by Fencer128