SiS190 integrated NIC causes BSOD during initialisation

[Guest]

Hi All,

I am working in a 2003 SBS environment and deploy all machines using RIS.
The machines are usually generic and the latest one has an ASUS K8S-MX
motherboard with an integrated SiS190-based NIC.

I have acquired the most recent drivers, v1.04 (2005-06-09), from ASUS and
verified that there is nothing newer according to SiS. The appropriate files
(cat, inf, sys) have been installed in the i386 directory on the RIS server
and the service restared.

Before adding the SiS190 drivers the CIW reports that "the appropriate
drivers for the network card do not exist". After installation the CIW
presents a BSOD stating that during the initialisation of the network adapter
there was an error: STOP 0x000000BB.

I have since tried to use previous versions of the driver - 1.02b, 1.03 -
with the same results. I can only assume that there is a problem with the
driver that does not make it suitable for use with RIS.

I would appreciate help from anyone who may know of a fix, a workaround or
have enough influence to have SiS ammend their driver for this task.

Cheers,

Aaron,

 

[Guest]

Hi Aaron,

Try this workaround:

1) Remove all the SIS inf, sys and cat files you recently put into the I386
folder
2) Download the SIS Windows 2000 drivers, copy the SIS W2K inf, sys and cat
files to the I386 folder of the RIS image folder
3) Create a subfolder in the \$OEM$\$1 folder. Give it a reasonable name
4) Copy the SIS WXP driver files to the folder created in step 3
5) Enter the path to the folder created in step 3 into the OemPnpDriversPath
key in the sif file. (If this key does not exist, it should be created along
with OemPreInstall and DriverSigningPolicy keys).
6) Restart binlsvc and tftpd

It should then work.

 

[Guest]

Soren,

Unfortunately, the WinXP and Win2000 drivers come in the same download and
use the same inf file, therefore installing the appropriate sys file when the
hardware is detected. I did get a little creative and decided to rename the
Win2000 files so that they would be used when running under WinXP but the end
result was the same - STOP 0x000000BB.

I have since acquired two more machines with almost identical hardware,
replacing the motherboard with a model using a VIA chipset instead. After
installing the supplied drivers I had no problem applying the RIS image.

Lesson learnt: prefer VIA chipset, avoid SiS chipsets
Still unknown: will VIA continue to be RIS friendly with future drivers

Aaron.

 

[Wallacetech]

Had exactly the same problem with this motherboard using a RIS image o
a Windows 2000 SP4 server. Tried everything I could think of with th
drivers including using different versions and some manual editing o
the driver's INF file.

In the end I discovered that there were some updated BIOS versions o
ASUS's website (www.asus.com). The version the machine currently ha
was 1012 and the latest was 1015. One of the versions in between thi
stated "Improved system more stable", which got me thinking this coul
be the problem.

Got the latest version and flashed the BIOS on the machine and low an
behold the RIS imaged worked without any problems.

*Hi All,

I am working in a 2003 SBS environment and deploy all machines usin
RIS.
The machines are usually generic and the latest one has an ASU
K8S-MX
motherboard with an integrated SiS190-based NIC.

I have acquired the most recent drivers, v1.04 (2005-06-09), fro
ASUS and
verified that there is nothing newer according to SiS. Th
appropriate files
(cat, inf, sys) have been installed in the i386 directory on the RI
server
and the service restared.

Before adding the SiS190 drivers the CIW reports that "th
appropriate
drivers for the network card do not exist". After installation th
CIW
presents a BSOD stating that during the initialisation of the networ
adapter
there was an error: STOP 0x000000BB.

I have since tried to use previous versions of the driver - 1.02b
1.03 -
with the same results. I can only assume that there is a problem wit
the
driver that does not make it suitable for use with RIS.

I would appreciate help from anyone who may know of a fix,
workaround or
have enough influence to have SiS ammend their driver for this task.

Cheers,

Aaron,

-
Wallacetec