Newer isn't always better when it comes to Windows XP drivers
Getting hardware devices to cooperate with Windows has been an ongoing problem for support techs since Microsoft shipped Windows 1.0. Microsoft has bent over backwards with hardware vendors to try to make it easier for them to write new drivers. It has also tried to make it easier to deploy driver updates by shipping hundreds of drivers with Windows XP and adding a feature to Windows Update that checks your workstation's hardware and driver versions against a database to advise you when new drivers are available.
For all this effort, driver problems still exist. You must be very careful when updating or using XP drivers. Sometimes installing a new driver or using a driver Microsoft suggested can cause more problems than it fixes. In other cases, you may find that using a relatively ancient Windows 2000 driver can fix problems on your Windows XP system.
A practical example
Just to give you an idea about how drivers can drive you nutty with Windows XP, I'll explain the problems I had with Windows XP and a Dell Inspiron 7000 laptop. This particular laptop includes a DVD-ROM and DVD Decoder made by LuxSonor, the LS242. The laptop originally came with Windows 98 and shipped with a Windows 98 driver for the LuxSonor decoder.
I figured I would have a problem with the decoder when migrating to Windows XP because I had one when upgrading the laptop to Windows 2000. There were no drivers included with the Windows 2000 CD for the decoder. LuxSonor had been purchased by Cirrus Logic, which wasn't creating drivers for old LuxSonor products. The only way I was able to get the decoder to work with the laptop and Windows 2000 was by using some drivers supplied by Dell.
Sure enough, when upgrading the laptop to Windows XP, Windows XP's Setup complained about the LS242 decoder and the lack of XP support for it. Because finding Windows XP-specific drivers for this device was impossible, out of desperation I decided to use the Windows 2000 drivers. Windows XP further complained that the drivers weren't digitally signed, but it took them anyway. Windows XP didn't have problems with any other devices in the laptop, including the sound card.
After the installation finished, I tried to play a DVD in the laptop. The video played fine, but there was no sound. I knew there were no problems with the sound card because other sounds were playing fine through it, and everything had worked fine under Windows 2000.
I attempted to run Windows Update to apply other patches to Windows XP and discovered an update for the ESS sound card on the laptop. Thinking maybe there was a problem with the driver, version 7 of the ESS driver, I downloaded the offered driver. As before, other sounds worked fine, but there was still no sound with the DVD player.
While doing some research with Dell's Windows 2000 driver, I noticed that it included an ESS driver as well as a LuxSonor driver. That's when I decided that perhaps the newer Windows XP ESS drivers, version 7 that shipped with Windows XP and version 9 that was offered by Windows Update, were to blame.
Going through Device Manager, I deleted the Windows Update ESS driver and reinstalled another driver. Rather than using the offered Windows XP driver, I selected Have Disk and specified the Dell Windows 2000 driver. As with the LuxSonor driver, Windows XP complained about the driver not being signed and warned about the dire consequences of using unsigned drivers. Because the LuxSonor driver worked even though it was unsigned and the audio drivers weren't working anyway, I decided to try it.
Sure enough, after that everything worked. The Windows XP system sounds all worked fine, and so did the audio when playing a DVD. The older Windows 2000 drivers succeeded where the newer Windows XP drivers failed.
The moral to the story
During the upgrade process, Windows XP successfully detected the ESS and installed its own driver for it. Clearly, this driver didn't include the appropriate support to communicate with the old Windows 2000 LuxSonor driver. This turned a twenty-first-century DVD into a 1900's silent film, even though otherwise the sound worked perfectly in the laptop. Downgrading the ESS driver fixed the problem because this driver had the necessary LuxSonor support.
As you're deploying Windows XP across your organization, you'll invariably encounter hardware that doesn't work properly with Windows XP. Even if Windows XP doesn't include a driver for the hardware, don't panic. Follow these steps to try to get Windows XP to play nice with the device:
Check the system vendor's Web site
Unless the system vendor has gone out of business, or the system you're upgrading is older, the vendor may have drivers specific for the system. In my example, Dell provided Windows 2000 support but not Windows XP support for the Inspiron 7000.
Check the component manufacturer's Web site
If the system vendor doesn't provide support, you might be able to find support from the manufacturer of the component. OEMs are sometimes better at providing drivers for components than system vendors. In my example, LuxSonor had been purchased by Cirrus Logic, which wasn't supporting LuxSonor chipsets.
Check driver Web sites
Specialized Web sites such as DriverGuide provide pointers to drivers that people have found on the Internet. These drivers often originated from vendors or OEMs and were collected by users. These can be handy if vendors or OEMs have changed drivers or have stopped supporting a particular device.
Try Microsoft's drivers
I've ranked this lower on the list because, as I've said, oftentimes Microsoft's drivers cause more problems than they fix. For example, on my test system, Microsoft suggested upgrading a driver for an SMC wireless card included in the system. This caused the card to stop working entirely.
Try compatible Windows XP drivers
Often even though one manufacturer makes a component, sometimes a second manufacturer originally created the component and just resold it. This occurs often with sound cards, video cards, and modems. If you can find out the chipset surrounding the component, you may be able to get a driver from another vendor to work.
Try Windows 2000 drivers
Windows 2000 and Windows XP share the same basic driver architecture. Microsoft added a layer of security to drivers, reducing the likelihood that they've been hacked and guaranteeing that the drivers will work with XP. But if you don't have a Windows XP driver, sometimes a Windows 2000 driver will work, as shown in my example. However, be aware that using Windows 2000 drivers in Windows XP may lead to system instability, so do so at your own risk.
Replace the component
If all else fails, you can always replace the unsupported component with a new component that Windows XP does support. Naturally, this is nearly impossible with laptops and motherboards with integrated devices, but if your system supports swapping out components, this is one way to overcome the problem.
No messages found
No messages found
No one will read this, but. . .
I hate to say this, but the more I use Linux, the better I am getting with MS products.
No matter what the O.S.; once you understand the event, you can discern the process.
it is all about time invested vs return.
You need to check the layout of the driver though, sometimes the manufacturers used a kludge to make a win95 driver work.
Now, for the sneaky part. For a printer (and some of the other higher level drivers) it is often possible to install the original drivers using the compatability suite available in XP.
Yes, I know that the printer is considered a "core" driver. But it can be kludged. Usually, drivers written for NT4 will work without a hitch. They should be native win32 based drivers. Many of the drivers written for Win98se were actually back-ported from NT in order for them to process large objects (READ THIS AS GRAPHICS). Another evil kludge is the "inf" file. This gives you all of the registry entries for the device. I have found, on occasion, that the driver included with XP provides partial support--that is to say it provides the gross mechanical connection for the printer without the additional controls.
Where are these additional controls? The registry. What do these entries provide? They pass additional formatting and code to the driver and often involve another object or file(s) to be included with the ".vxd" in the original driver. (This is where the "layout" of the driver is important.) If the ".vxd" was kept simple--ie just a set of routines using the native 32bit dlls to provide a connection--then, the rest of the driver may be useful. A matter of a few alterations to the ".inf" file entries. The entries which provide the dlls are edited to a version-type of install using the compatability kit. 16-bit stuff can be made to work also. Just more time.
A native 32-bit driver is a native 32-bit driver. The versions of the "C-and-C++ runtime libraries" used by the driver must be installed with the driver using the "version" type of install. This is the core of the compatability function in XP, the ability to run different versions of the dlls at the same time via a "Wrapper". The "Wrapper" is necessary in many cases because the NT kernal is not he same one which was used in NT4. A wrapper is a filter program which converts legacy calls into their modern counterparts--and vice versa. Most of these sub-routines are invoked auto-magically when you use a version-type of install.
The compatability kit creates a database for each program which does not use the modern version of the run-time libraries--when the program or driver is installed properly, this database invokes the versions of the runtime libraries needed for the application, and redirects the lower level system calls to a wrapper program which provides translation to/from kernal space. Many of these wrappers actually keep track of memory allowcations and clean them up. It actually works!
*******A word of warning, if you kludge a driver, the machine must be re-booted every day. Most of the pre-NT4 stuff was really poorly written. That is the primary reason MS changed many of their APIs for Win32--it was to force all of the stuff to be re-submitted and evaluated for stability. NEVER USE A KLUDGE ON A "PRODUCTION/HIGH AVAILABILITY/ENTERPRISE MACHINE". *********************
XP is sort of like a bumble-bee. It shouldn't run at all let alone run as well as it does.
There are no posts from your contacts.
Adding contacts is simple. Just mouse over any member's photo or click any member's name then click the "Follow" button. You can easily manage your contacts within your account contacts page.