Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Broadcom NICS

- - - - -

  • Please log in to reply
2 replies to this topic




  • Member
  • 28 posts
  • Joined 03-November 04
I've been using RIS for a little over a year now on HP boxes with Broadcom B57XX drivers. My boss just ordered a new shipment Thinkpads that have Broadcom NICs in them. My problem is it is a B57XX driver, however it will not use the same edited file for RIS. The only way I can get it to work is to edit the new driver .inf and put the three files in the i386 folder. I have tried moving them to the OEM folder for the image as well. Right now I am stuck moving the 3 files back and forth when I want to image a laptop or PC. Has anyone else encountered this and got it to work?

How to remove advertisement from MSFN



    Gustatus similis pullus

  • Supervisor
  • 11,252 posts
  • Joined 09-September 01
  • OS:Windows 8.1 x64
  • Country: Country Flag
Are those three edited files in the i386 folder of your flat file source, as well as the proper OEM drivers subfolder? If they're there (and you've restarted the binlsvc), you shouldn't have to do anything else. If you do remove them, you will of course lose the ability to use the NIC properly in RIS until they're placed back in the i386 directory (and the binlsvc is restarted).
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!



    OS: SimplyMEPIS

  • MSFN Sponsor
  • 1,529 posts
  • Joined 18-September 04
When adding support for non-native NICs in RIS, you need to have the driver in two different places. First the .inf file and the .sys file(s) must be placed in i386. Then the full driver set needs to be available elsewhere (depends on what method your using).

What I have noticed is that very rarely do you ever have to modify anything at all for the latter stage - where Windows XP Setup performs a PnP enumeration. Some people refer to this as T-39. It's the first part, getting the computer to boot to RIS that seems to present the most confusion and problems.

If you need to modify the .inf different for one group of computer from another group of computers, but they both will use the same .sys files, that's fine. Just put both .inf files, named differently, along with the necessary .sys driver files in the i386 directory. You don't need to concern yourself with breaking driver signing or anything for the first part. The only thing you need to do is jump start the thing into booting. Once that's done, the full driver set should be detected and installed during T-39.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users