Bizarre Windows XP and SIS graphics driver

[jake108]

Got a bizarre issue here wonder if someone here with experience with Windows XP / SIS chips can help me.

Basically I am repairing a ASUS K40C laptop and seem to be having problems getting it to identify the Graphics driver. I install the motherboard driver (which includes the graphics driver according to the FAQ) but it still loads the windows publisher driver in device manager and does not enable OpenGL Support.

The laptop was previously running Windows 7 but it seemed a bit too harsh for it and it needed a fresh reinstall / downgrade to XP. Performance was terrible.

It was a fresh install of Windows XP SP3 too. I have tried the drivers from the ASUS website to no avail, I have tried the SIS official drivers but it says it cannot find the hardware on install (same as nvidia and ati mobile drivers?).

I tried pointing to the ini files after extracting them, device manager recognises it but says it cannot find the hardware. Tried a manual driver selection too. Anyone have any advice? Thank you in advance.

 

[this_is_gav]

You've tried the VGA driver listed on the ASUS website? I've never known SiS downloads to have the graphics drivers included with the chipset drivers - they've always been a separate download when I've done it in the past.

There are no SiS 672 drivers listed for XP on the SiS site. I guess you could try the Vista/Win 7 32-bit drivers and pointing to the .inf, but there was enough of a change of graphics standard between XP and Vista for me to not really have any confidence that they'd work. (Edit: there are 672 drivers listed for XP under 67x... somehow I missed them).

Also, and not strictly relevant... grrr... SiS.

 

[jake108]

Yes I tried to VGA driver on the ASUS website, it says on install it cannot find the hardware. I did a probe of the graphics chip using AIDA, It says it is a SIS graphics chip but it doesn't list the model number anywhere.

Maybe I'm wrong but could it be problem with hardware detection on the laptop? Going to take a look in the BIOS more thoroughly to see if there is a setting somewhere I've missed.