I
Ian
Just wated to point out that in addition to an earlier article about
modifying the B57W23K.INF file to work with Windows XP installs, the
invesr applies for Win 2000.
Besides all the other stuff (modifying the .INF file to remove '.' in
the [Manufaturer] section, and making sure you put the .INF and .SYS
file in the \i386 folder of the image that was created from the
CD-ROMs (the 'flat' or RISETUP image)), you should also note the
following.
In another thread, mostly to do with install of XP, people talk about
modifyinf the Broadcom .INF file to replace all instances of
b57w2k.sys with b57xp32.sys (i.e replace references to Windows 2000
driver with Windows XP driver).
If you're trying to install Windows 2000 then the converse applies.
The Broadcom driver .INF file (both the versio supplied by Dell and
the one supplied by Broadcomm) seem to be set up that if you use them
as part of a RIS install on some machiens (I speak of Dell GX280
especially), then they will try and install and use the XP driver
b57xp32.sys. This will either cause a problem during text-mode setup
(an error citing b57xp32.sysys) or, if you add this driver file to the
\i386 file, then the BSOD (blue screen of death) when the Windows 200
starts. I can ponly assume this is due to Windows 200 lading the XP
driver and the predicatbaly choking on it.
So, if you're Luddit enough to want to install Win 2K on machines
(GX280) using the Broadcomm NIC, I recommend that you replace all
references to b57xp32.sys in the b57win32.INF file with a reference to
B57w2k.sys which goes in the \i386 folder of the flat (RISETUP) image
used during text mode setup. I still don't know if you have to do the
same with the driver loaded during the GUI phase, but I suspect it's
not so picky.
modifying the B57W23K.INF file to work with Windows XP installs, the
invesr applies for Win 2000.
Besides all the other stuff (modifying the .INF file to remove '.' in
the [Manufaturer] section, and making sure you put the .INF and .SYS
file in the \i386 folder of the image that was created from the
CD-ROMs (the 'flat' or RISETUP image)), you should also note the
following.
In another thread, mostly to do with install of XP, people talk about
modifyinf the Broadcom .INF file to replace all instances of
b57w2k.sys with b57xp32.sys (i.e replace references to Windows 2000
driver with Windows XP driver).
If you're trying to install Windows 2000 then the converse applies.
The Broadcom driver .INF file (both the versio supplied by Dell and
the one supplied by Broadcomm) seem to be set up that if you use them
as part of a RIS install on some machiens (I speak of Dell GX280
especially), then they will try and install and use the XP driver
b57xp32.sys. This will either cause a problem during text-mode setup
(an error citing b57xp32.sysys) or, if you add this driver file to the
\i386 file, then the BSOD (blue screen of death) when the Windows 200
starts. I can ponly assume this is due to Windows 200 lading the XP
driver and the predicatbaly choking on it.
So, if you're Luddit enough to want to install Win 2K on machines
(GX280) using the Broadcomm NIC, I recommend that you replace all
references to b57xp32.sys in the b57win32.INF file with a reference to
B57w2k.sys which goes in the \i386 folder of the flat (RISETUP) image
used during text mode setup. I still don't know if you have to do the
same with the driver loaded during the GUI phase, but I suspect it's
not so picky.