RE: SiS190 integrated NIC causes BSOD during initialisation

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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.

--
Yours Sincerely,
Søren Rasmussen


"Aaron Wolski" wrote:

> 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,
.

Relevant Pages