Discussion Locked

install windows xp for every chipset?

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
How to install windows with drivers for every existing chipset, not only for a present configuration ? Not to put every possible drivers but only for MB chipset, namely Intel, nForce, Via, Sis. So when I change my motherboard with Intel chipset with another motherboard with Via chipset, or make a ghost and den put him on a configuration with different MB chipset. I wont windows to recognize MB and go on working. So I don?t haw to make agene installation.

8 replies

by thechas

Well, XP has a fairly decent driver set. There are functional drivers for all of the major chip-sets that existed when XP was released.

Your problem is that XP only installs the driver for the actual chip-set on the motherboard for the system it is installed on.

Unlike DOS, XP will not allow you to install drivers for hardware that is not there.

Some of the chip-set reference drivers will NOT install if they do not detect a supported chip-set.

These are GOOD things in that they prevent problems from people installing drivers onto their systems that will not work.

About the only thing you "might" be able to do, is to extract the proper files for each chip-set and store them in the C:\Windows\Driver Cache\i386 folder and hope for the best.

Keep in mind, that unless you have a corporate edition of XP, when you move a hard drive or image to a different PC, you will generate an activation event.

Another idea would be to pause an XP installation just before the system specific drivers are installed, and create an install image.

Being a bit anal retentive, and a generally cautious person when it comes to system setups, I prefer to install the OS fresh after ANY significant system hardware change.

Unless you are VERY good at editing the registry and cleaning out system files, you always have some junk left over that will get in the way and slow the system down.

Chas

by koki777km

Thank you, C:\Windows\Driver Cache\i386 folder and hope for the best, it is the thing I will probably try.

by zaferus

TheChas is TheMan. He's right on all his points.

Microsoft RIS and IBM Deployment manager allow you to have different hardware build images for your chipsets and deploy the right one to the right system. They use a "common" storage so that similar files aren't duplicated saving on storage space.

But I digress - this is for corporate and you are talking home user stuff.

Take my advice and re-install Windows fresh with a new chipset. It will let you keep the aspirin bottle in the cupboard!

by koki777km

Thank you, not heart to tray whit Microsoft RIS and IBM Deployment manager.
Or maybe take your advice.

by wcp

I believe it can be done using slipstream method.

Slipstreaming Windows means creating a Windows CD (XP for example) that can integrate Service Pack, MS Critical Updates, Hot fixes, applications, DRIVERS, and others.

You can make it a completely unattended Windows installation that put property settings (Product key, Time Zone, Resolution, your name, and so on).

If the Windows is OEM or Retail version, you can always run Sysprep command at the end of the installation so a user must provide the right Product Key when fist boot up.

I find the website below extremely helpful.
http://unattended.msfn.org/unattended.xp/

by wcp

One of the purposes of slipstreaming drivers is to provide as many drivers available and Windows XP will choose the best matched one. In other words, you can make a slipstreamed Windows XP CD totally system non-specific.

This discussion is closed to new replies.