Why won't Windows XP install on a 486?

[hurtstotalktoyou]

Here's my system-to-be specs:

AMD Am5x86-P75 (basically a 486 clone running at 4x33=133 MHz)
128MB FPM DRAM
PCI video w/8MB VRAM
8.4 GB IDE hard disk
40x CD-RW
3.5" & 5.25" FDDs
SoundBlaster PCI 128
10/100 PCI NIC
DIN keyboard & serial mouse
15" XGA display

Now, I'm told that while Windows XP will *run* on a 486-based system, it can never be installed on one because the installation wizard will recognize the 486 CPU and refuse to run.

Question #1: Will the installation wizard recognize the Am5x86-P75 as a 486, or will it allow an installation?

I was thinking, maybe I could install Windows XP on the hard disk using another system, then remove the disk and insert it into the Am5x86 system. However, I have tried this method before with two other PCs, and when the hard disk is swapped out from one system to another XP refuses to boot.

Question #2: Is there any way to make Windows XP boot when the hard disk is moved from one system to another?

Thanks in advance, guys!

 

[0roo0roo]

just try it
windows generally freaks out if you install os on one system and try to shove the disk into a completely different one.

 

[montag451]

Could probably install in another system, then use the sysprep tool to swap it over.
Or, you could install xp in another system, delete all the drivers, and swap it over.
Bear in mind that you won't be able to find any ISA drivers for XP most likely, and most of the hw won't have had drivers written for them past win95.

Still, can't think of many other ways to waste a rainy Sunday that would be as fiendishly masochistic as this idea.

Can you post back with the results please.

 

[hurtstotalktoyou]

Originally posted by: montag451Can you post back with the results please.

Of course! But I won't be getting the system for another few weeks at the earliest.

 

[montag451]

Yeah, those systems have a waiting list for 'em.

I put my name down 3 months ago and I'm still waiting.

But seriously, if you burn out the cpu, I have a spare if you need it (really).

 

[JackMDS]

AMD Am5x86-P75? Even Win98se would have trouble with this setting.

WinXP runs slow, but would run on a P-III 400 with 196MB, bellow this it really Not very functional.

When you move WinXP from one computer to the other the Boot looks for the Hard Drive using the drivers that are compatible with the computer?s chipset. If you move it to another PC that have the same chipset it might Boot and repair itself, but if you move to a computer with different chipset (does not matter even if it the same or compatible CPU), the drivers are Not compatible and it would abort.

You can move an hard drive to another computer and boot from Original WinXP CD ROM, it sometimes possible to get to the new Installation screen and choose Repair, it would take 40min. but it usually repairs the boot and other devices chipset related and would work with new computer.

I do not know about the Chipset of the AMD Am5x86-P75 but it might not be recognized by WinXP and have no drivers for it.

BTW, No matter what, any manipulation like this needs legal reactivation of WinXP.

 

[hurtstotalktoyou]

Well, if WinXP doesn't work, I'll be installing Win98 FE. Thanks for the info about chipsets.

 

[montag451]

But Win 98 wouldn't be news.

We need Vista premium ultimate superwoopie on that machine, and we need it now.

 

[hurtstotalktoyou]

Originally posted by: montag451
But Win 98 wouldn't be news.

We need Vista premium ultimate superwoopie on that machine, and we need it now.

You may enjoy this page: Windows XP on a Pentium Overdrive @ 8 MHz and 20 MB RAM.

 

[JackMDS]

Originally posted by: montag451
But Win 98 wouldn't be news.

We need Vista premium ultimate superwoopie on that machine, and we need it now.

Yeah, I am working in a building that a lot of Medical Docs doing internship reside, their two years contract usually expires on June 30 and they have to move On, they tend to leave behind their old computers.

Each year in the begining of July there is about 10 computers lined up at the entry of the building free for grab.

This year No body even took any of the P-III class computers any more.

 

[bigsnyder]

Originally posted by: hurtstotalktoyou

Originally posted by: montag451
But Win 98 wouldn't be news.

We need Vista premium ultimate superwoopie on that machine, and we need it now.

You may enjoy this page: Windows XP on a Pentium Overdrive @ 8 MHz and 20 MB RAM.

Great site!

 

[Markbnj]

99% of the time Windows XP will figure out what's going on with a new board. It does hardware detection and initialization on every boot, and figures out what isn't there and disables the drivers. It detects new hardware and installs the drivers for it if available. There's enough available to get almost any compatible system board running, if not optimally. You can help the process along by uninstalling any 3rd party chipset or peripheral drivers immediately prior to shutting down and transferring the system into the new machine. Then reboot and let XP do it's thing. Have an install CD handy.

 

[JackMDS]

Originally posted by: Markbnj
99% of the time Windows XP will figure out what's going on with a new board. It does hardware detection and initialization on every boot, and figures out what isn't there and disables the drivers. It detects new hardware and installs the drivers for it if available. There's enough available to get almost any compatible system board running, if not optimally. You can help the process along by uninstalling any 3rd party chipset or peripheral drivers immediately prior to shutting down and transferring the system into the new machine. Then reboot and let XP do it's thing. Have an install CD handy.

This is very true, excluding the Hard drive Bus/Drivers. I there is a big change it can not access the drive and thus start the proccess.

You usually get a Blue Screen, and after few seconds a reboot.

 

[Narse]

If you install on another system make sure to use these instructions

MergeIDE

I have used this and have only had issues getting it to work on some latops due to the HAL, And I have instructions on how to change that also at work.

 

[Narse]

Originally posted by: JackMDS

Originally posted by: Markbnj
99% of the time Windows XP will figure out what's going on with a new board. It does hardware detection and initialization on every boot, and figures out what isn't there and disables the drivers. It detects new hardware and installs the drivers for it if available. There's enough available to get almost any compatible system board running, if not optimally. You can help the process along by uninstalling any 3rd party chipset or peripheral drivers immediately prior to shutting down and transferring the system into the new machine. Then reboot and let XP do it's thing. Have an install CD handy.

This is very true, excluding the Hard drive Bus/Drivers. I there is a big change it can not access the drive and thus start the proccess.

You usually get a Blue Screen, and after few seconds a reboot.

The link I posted will stop the 0x0000007B error

 

[imported_Willie]

Originally posted by: JackMDS

Originally posted by: Markbnj
99% of the time Windows XP will figure out what's going on with a new board. It does hardware detection and initialization on every boot, and figures out what isn't there and disables the drivers. It detects new hardware and installs the drivers for it if available. There's enough available to get almost any compatible system board running, if not optimally. You can help the process along by uninstalling any 3rd party chipset or peripheral drivers immediately prior to shutting down and transferring the system into the new machine. Then reboot and let XP do it's thing. Have an install CD handy.

This is very true, excluding the Hard drive Bus/Drivers. I there is a big change it can not access the drive and thus start the proccess.

You usually get a Blue Screen, and after few seconds a reboot.

Honestly, I've never experienced what you describe and I've moved XP installs from computer to computer with the only piece the same being the hard drive. Moved a hard drive w/XP on it from an AMD Athlon--NF3/250-chipset based computer to an Intel C2D 965-chipset based computer and all that happened was it had to reboot a couple of times to load this or that mb/system/bus driver. No BSOD, no refusal to run, no errors whatsoever.

I've heard tell of people having problems, but in the dozens of systems I've moved hard drives out of and into, they've all gone so smoothly that I guess I'm just overly lucky.

 

[JackMDS]

Originally posted by: Willie
Honestly, I've never experienced what you describe and I've moved XP installs from computer to computer with the only piece the same being the hard drive.

Good for you you were lucky.

Unfortunately it happened to me a lot of time since I deal with computers spanning from Intel BX chipset, to the current Intel, and AMD chipset.

In any case this thread has very good info to help many people including myself.

 

[Noema]

Originally posted by: hurtstotalktoyou

Originally posted by: montag451
But Win 98 wouldn't be news.

We need Vista premium ultimate superwoopie on that machine, and we need it now.

You may enjoy this page: Windows XP on a Pentium Overdrive @ 8 MHz and 20 MB RAM.

Heh heh, XP looks funky on 16 colors

And the guy has also installed Win98 on a 386 with 8MB of RAM.

 

[Lord Evermore]

Originally posted by: Narse
If you install on another system make sure to use these instructions

MergeIDE

I like that.

This error may occur if the registry entries and the drivers for the mass storage controller hardware in the backup computer are not installed in Windows XP.

For integrated device electronics (IDE) controllers, there are several different chip sets available, such as Intel, VIA, and Promise. Each chip set has a different Plug-n-Play identifier (PnP-ID).

The PnP-ID information of mass storage controllers for the backup computer must be in the registry before startup so that Windows XP can initialize the correct drivers.

The supported solution:

To resolve this error, use the same hardware for the backup computer:
? Replace the problem hardware components in the backup computer with components of the same manufacturer, make, and model as the motherboard in the computer that you are backing up.

They use that solution a lot.

Patient: "It hurts when I do this."
Doctor: "Well don't do that."

 

[TallBill]

Wow, 8 mhz, awesome.

 

[AnitaPeterson]

that is awesome, indeed!

 

[VirtualLarry]

First of all, if you want to install onto a 486, you need to press F5 (when it prompts you to press F6 for mass-storage controllers), and then you need to choose the HAL for a 486 Standard PC.

Secondly, I have no idea what kind of disk controllers are on that motherboard, or if you have seperate PCI, ISA, or VLB disk controllers, but XP needs to have drivers for the boot disk. If the mobo has a standard PCI IDE controller, then it will likely work, otherwise, I think you are screwed unless you have a floppy with XP drivers for your controller.

For example: DTC 2278, I used to have one on my VLB mobo, it appears to have "NT" drivers, unsure if those would work with XP or not. http://www.storagedrivers.com/drivers/24/24287.htm

Is there some reason why you don't want to run Win98se on that machine? It would seem to be more appropriate for that vintage of hardware.