Jump to content

Broadcom RIS Arhhhh


Recommended Posts

Hi :hello:

I've been trying to get a group of systems we've purchased (Viglen VM4 Cube PCs - If you're out of the UK you probably never heard of this brand), it runs Broadcom's Netextreme as it's onboard LAN, however trying to get the system to work with our RIS image has been an absolute pain in the butt :realmad:

I tried the original drivers shipped with the system, got the error 21 in setup.c... find I thought, consulted the boards and obtained an answer, so I modified the inf file (b57xp32.inf) to read:

%BRCM% = Broadcom.NTx86.5.1

Restart BINL and try again.. brilliant the error 21 in setup.c has been fixed! But then I get BSOD with a stop code 0x000000BB, now this is where the trail goes cold... looked around nothing that has helped.. tried the drivers from Broadcom, modified the b57win32.inf file to reflect the changes I made to the b57xp32.inf (which I had removed from the RIS prior to try broadcom's driver), restarted BINL and I get the exact same issue.

Anyone got any points??

Thanks

Edited by f5ferrari
Link to comment
Share on other sites


http://www.broadcom.com/support/ethernet_nic/faq_drivers.php

79.) How do I install Windows 2000 and Windows XP using Remote Installation Services?

Microsoft Remote Installation Service(RIS) Instructions for Adding Broadcom Network Adapter Driver

Problem: An error is encountered when attempting to load the Broadcom device driver for a 32-bit version of Windows XP or later operating system using a Windows 2000 Remote Installation Server: File b57w2k.sys caused an unexpected error (21) at line 3752 in d:\xpsp1\base\boot\setup\setup.c.

Solution: A modification to the b57win32.inf file can be made to allow for the installation to complete successfully. This will be in conjunction with instructions from the Microsoft Knowledge Base Article 315279 that describe "How to Add Third-Party OEM Network Adapters to RIS Installations."

Requirement: The Windows 2000 Server must be running Service Pack 3 or later.

Obtain the latest driver for your Broadcom adapter.

The driver files included for the Broadcom 57xx adapter are b57win32.inf, b57win32.cat, and b57xp32.sys. Create a copy of the b57win32.inf and b57xp32.sys files and locate them in a separate folder called RIS. This will allow you to distinguish them from the originals.

For the b57win32.inf file located in the RIS folder, make the following change using a text editor like Notepad:

Locate [Manufacturer] within the file.

Review the line below which reads: %BRCM% = Broadcom, NTx86.5.1, NTamd64.

Modify that line to read: %BRCM% = Broadcom.NTx86.5.1, NTamd64. The change made replaces the comma and space after "Broadcom" with a period.

Save the file.

On the RIS server, copy the b57win32.inf and b57xp32.sys files from the RIS folder to the RemoteInstall\Setup\Language\Images\Dir_name\i386 folder. (This allows Setup to use the driver during the text-mode portion of the installation).

At the same level as the i386 folder on the RIS image, create a $oem$ folder. Use the recommended structure: \$oem$\$1\Drivers\Nic

Copy the original b57win32.inf, b57xp32.sys, and b57win32.cat driver files to this folder.

Make the following changes to the .sif file that is used for this image installation:

[unattended]

OemPreinstall = yes

OemPnpDriversPath = \Drivers\Nic

Stop and then restart the Remote Installation service on the RIS server. To do this, type the following from a command prompt:

net stop binlsvc

net start binlsvc

Link to comment
Share on other sites

Hey, Thanks for the post.

I've already seen that on Broadcom's website, I don't get a error line 21 in Setup.c anymore... however the driver is producing a STOP code of 0x000000BB which I can't seem to find a solution anywhere :-/, am sure someone must of had this NIC and got it to work successfully on RIS.

Link to comment
Share on other sites

  • 1 month later...

have you looked at this post ?

http://www.msfn.org/board/index.php?showtopic=39778

this post also suggests its down to dhcp conflicts

http://bink.nu/forums/8005/ShowPost.aspx

btw, i had a poke at getting my tablet with that nic to install using ris. i never even got the setup to start :/ gave up on it in the end as its just not worth the effort for this one computer, but i will look at it again now that ris has been replaced on 2k3.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...