MSFN Forum: forcing XP to use a driver - MSFN Forum

Jump to content



Unattended CD/DVD Guide Homepage · MSFN Forum Rules

If you have questions about customizing Windows XP that are nLite-specific, please post them in the nLite forum, not here. If you have questions regarding the unattended installation of Windows XP, please post them in the Unattended Windows 2000/XP/2003 section.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

forcing XP to use a driver Rate Topic: -----

#1 User is offline   Asp 

  • Junior
  • Pip
  • Group: Members
  • Posts: 72
  • Joined: 17-April 05

Posted 01 July 2011 - 06:10 AM

I've got a laptop and a wifi PC card -- D-Link DWL-G630. (Both quite old.)

I'm having some problems connecting to a new wifi router.
I have found advice that using a driver from ASUS gives better results, the ASUS device has the same chipset.
(This post -- from 2004, so I don't think profitable to resurrect that thread.)

This says :

Quote

I used XP's add/remove hardware to use mrv8ka51.inf as the driver for the DWL-G630. I then set up WPA-PSK on both the DI-524 and DWL-G630.

But when I try this and point to the folder with the inf and sys files, Windows just says "no suitable drivers found" and reverts to the D-Link software.

Is there a way to override this? .


#2 User is offline   Tripredacus 

  • K-Mart-ian Legend
  • Group: Super Moderator
  • Posts: 7,349
  • Joined: 28-April 06
  • OS:Windows 7 x86
  • Country: Country Flag

Posted 01 July 2011 - 07:42 AM

First you need to check to see if the HwID for your device is in the INF you are pointing to.

When Windows looks for drivers, it looks for the HwID in the INF. For the most part, Windows can be tricked into using a driver by just putting the HwID in the INF. However there are a few problems you can run into:

1. The driver components may not work properly with the device, some functions may not work like power save, or the signal might not be great.
2. The driver may not install properly because the hardware is different. You'll end up with a Code error on the device description. Worst case scenario is that you could experience a lock up or a crash.
3. Windows isn't that dumb tho, because it will end up saying the the best driver is already being used. This could be because of multiple reasons, such as the subsys being specified, a driver is signed, or the date/version is higher.

In order to force Windows to use a driver, the best option (without having to learn exactly how Windows handles drivers) is to uninstall the current device and delete the already installed drivers. Even if you were to just uninstall the device and try to update with the "forced" drivers, Windows will reject it because it will still look at the other drivers on the system to find a better one. So you need to make sure those aren't there.

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy