File b57w2k.sys caused an unexpected erro (21) at line 3788

  • Thread starter Phillip.C.Jones
  • Start date
P

Phillip.C.Jones

Hi,

I am currently working to deploy XP SP2 using images created through
SMS2003. I have created the images (burnt to CD) and copied them to the
apropriate folder on my RIS server. The machines i will be building
require the b57WIN32 and b57XP32 driver files which i have copied to
the i386 folder. When i PXE boot the workstation and select the image
to build from the list, the build fails giving me the following error

"File b57w2k.sys caused an unexpected error (21) at line 3788 in
d:\xpsprtm\base\boot\setup.c"

I have made sure there are no .pnf files in the i386 folder. I have
checked that the dirvers i am using are up to date from the HP website.


Any ideas where i am going wrong? Missing something?
From reading some other posts i have noticed people talking about a
problem using RIS with XPSP2, is this correct..

I am stuck trying to get these RIS images working and would really
appreciate some help.

Many thanks.

Pj
 
C

Charles Spencer

I had a similar problem,

If I remember correctly I had to make a change to the b57w2k.ini file

Here is the article I used to resolve this problem

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.

1.. Obtain the latest driver for your Broadcom Adapter.
2.. 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.
3.. For the b57win32.inf file located in the RIS folder, make the
following change using a text editor like Notepad:
1.. Locate [Manufacturer] within the file.
2.. Review the line below which reads: %BRCM% = Broadcom, NTx86.5.1,
NTamd64.
3.. Modify that line to read: %BRCM% = Broadcom.NTx86.5.1, NTamd64. The
change made replaces the comma and space after "Broadcom" with a period.
4.. Save the file.
4.. 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).
1.. At the same level as the i386 folder on the RIS image, create a
$oem$ folder. Use the recommended structure: \$oem$\$1\Drivers\Nic
2.. Copy the original b57win32.inf, b57xp32.sys, and b57win32.cat driver
files to this folder.
3.. 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
binlsvchttp://www.broadcom.com/support/ethernet_nic/faq_drivers.php
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top