So you gave up your W2k RIS distribution to the new GX280? I think I just saw another message you had about GX280 NIC trouble using W2k. I work in a college and have used W2k as a standard for some time now. But world has to change....

 

I am in the same situation as you are. I just started deploying XP on a GX280 with my W2k RIS server and the errormessage looks just the same. I have been reading the http://support.microsoft.com/Default.aspx?kbid=315074

article and have just been on the phone with Microsoft to request the fix, cause I could not find it on net. If it will work I will know in a little while.

 

SORRY I DIDN'T FINISH THE MESSAGE.... :smileyvery-happy:

READ THIS ONE.

Hi Sindre,

Yes, you are right, most of the times problems are solved just upgrading systems, but I think it's not our problem.

The solution in my opinnion is comming via the drivers and how to put them properly in the images, I mean which are the proper drivers files to put and where put them; how modify the b57win32.inf and off course modify also the RIPREP.SIF; And in which image to put the drivers, I mean, this should work with the RISETUP image and the RIPREP images.

Anyway, this is the way I have been working in and didn't get any result, so maybe I'm wrong.

The files I'm using are:

b57w2k.sys  03/09/2004  12:23

b57win32.cat  03/09/2004  12:23

b57win32.inf 03/12/2004  12:01

b57xp32.sys  03/09/2004  12:23

I suppose you've got the last drivers, but just by the way you can get the V7.86 http://www.broadcom.com/drivers/downloaddrivers.php

I also saw the other discussion in the forum and it seems like JAUGUST is going to get the solution soon.

GOOD LIKE JAUGUST!!!  :smileyhappy:

Dungulo.

Thank you b_peter for sugesting downloading drivers from http://www.broadcom.com/drivers/downloaddrivers.php

I actually saw a difference in the installation after using the new drivers, but after copying some files the installation stopped again and the new message is:

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

 

Something must be wrong here when the installation is messing with a W2k .sys file when handeling XP.

 

I have experienced this and the answer to your problem is in the i386 folder replace the latest Broadcom *.sys driver file for XP with the Broadcom *.sys driver file for w2k  and perhaps things should work. It worked for me and I used the baseline driver files off the Broadcom website

 

 

Adding Broadcom Gigabit drivers to RIS for Windows XP Images - Step by step procedure
(found on Dell Optiplex GX280)

1. Download the updated drivers v7.80 from Broadcom site, http://www.broadcom.com/drivers/downloaddrivers.php
    
2. At the same level as the i386 folder of the RIS image, create a $oem$\$1\Drivers\Nic folder structure
   
   Example: RemoteInstall\Setup\Eng\Images\Windows_XP_SP1\$oem$\$1\Drivers\Nic
    
3. Extract the win_xp_2k3_32-7.80.zip package to a temporary location, create a subfolder named updated_inf and copy the win_xp_2k3_32\b57win32.inf to that folder. Then open the win_xp_2k3_32\updated_inf\b57win32.inf file in Notepad
    
4. Change the following information in the updated_inf\b57win32.inf file.
   
   [Manufacturer]
   %BRCM% = Broadcom, NTx86.5.1
   to
   [Manufacturer]
   %BRCM% = Broadcom
   
   Remove the [Broadcom.NTx86.5.1] line
   
   Do a search replace for b57w2k.sys and replace with b57xp32.sys
    
5. Copy the following file from win_xp_2k3_32 to i386 (Replace existing files)
   
   b57xp32.sys
    
6. Copy the following file from win_xp_2k3_32\updated_inf to i386 (Replace existing files)
   
   b57win32.inf
    
7. Copy the following files from win_xp_2k3_32 to $oem$\$1\ Drivers\Nic
   
   b57xp32.sys
   b57win32.inf
   b57win32.cat
    
8. Add the following to the ristndrd.sif file
   
    [Unattended]
   OemPreinstall = yes
   OemPnpDriversPath = \Drivers\Nic
    
9. Delete all .pnf-files from the i386 folder
    
10. Restart the Remote Installation (BINLSVC) Service
     
11. Test the client
    
    Note: The first time this will take a while because Windows rebuilds all the PNF files