VOGONS


First post, by chublord

User metadata
Rank Member
Rank
Member

I know this has been asked before, and I know it won't actually install due to a missing instruction CMPXCHG8B that terminates the install process. However, Socket 3 Pentium Overdrives have this instruction, and therefore XP supposedly will install using a POD.

My question is, if already installed, will XP 'run' on a 486? i.e. if the POD was swapped out for a DX4 chip once XP is already installed?

IBM Valuepoint 486 DX4-100, Opti 802G, 50 MHz FSB, Voodoo1+S3 864, Quantum Fireball EX 4.0 GB, Seagate Medalist 1.6 GB, 128 MB FPM, 256k L2

Reply 1 of 6, by Disruptor

User metadata
Rank Oldbie
Rank
Oldbie

No. It is a feature which is used for kernel mutex. It will refuse to boot.
However, there were guys that have had a battle for the slowest XP system:
https://www.winhistory.de/more/386/xpmini_en.htm

It seems like 18 MB or an 8 MHz clocked Pentium Overdrive without fan is the minimum.

Reply 2 of 6, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Win 2000 will run on a 486, so maybe an early build of XP/Whistler will, as well ?

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 3 of 6, by KCompRoom2000

User metadata
Rank Oldbie
Rank
Oldbie

I've been researching this in the past, and from what I remember, the only times Windows XP checked for the CMPXCHG8B instruction are at the first part of the setup (i.e. after the "Setup is inspecting your computer's configuration" screen) and when attempting to do an upgrade install from an older Windows version.

The last (leaked) Whistler/Windows XP Beta build to not have the CMPXCHG8B instruction check was 2223. Build 2250 is the earliest build to implement the check.

As an experiment, I replaced the SETUPLDR.BIN file on a Windows XP Setup boot floppy image with the one from Whistler Build 2223. The CMPXCHG8B check was gone, but it showed a BSOD after the "Setup is starting Windows" screen (I can't remember the exact STOP error code, I want to say it was 0x7B (INACCESSIBLE_BOOT_DEVICE), but I could be wrong on that). I tested this on Virtual PC 2007 back then, so I don't know if it would do the same thing on a 486 (real or emulated).

If you have a 486 computer and a Pentium Overdrive CPU for it, you're welcome to try to install Windows XP with the Pentium Overdrive CPU installed then replace it with a 486 afterwards to see if it would still boot.

Reply 5 of 6, by dionb

User metadata
Rank l33t++
Rank
l33t++
KCompRoom2000 wrote on 2021-08-23, 06:05:

[...]

If you have a 486 computer and a Pentium Overdrive CPU for it, you're welcome to try to install Windows XP with the Pentium Overdrive CPU installed then replace it with a 486 afterwards to see if it would still boot.

I did that in the early 00's.

Installed WinXP on a late PCI-based 486 board with PODP83 and 256M RAM. Worked 'fine'. Replaced PODP with an Am5x86-133: no boot.

Then took heatsink off PODP (drops multiplier to 1x) and dropped FSB to 16MHz. "Worked", although it took a few hours to boot to deskop 😜

Reply 6 of 6, by roytam1

User metadata
Rank Newbie
Rank
Newbie
dionb wrote on 2024-04-15, 09:37:
I did that in the early 00's. […]
Show full quote
KCompRoom2000 wrote on 2021-08-23, 06:05:

[...]

If you have a 486 computer and a Pentium Overdrive CPU for it, you're welcome to try to install Windows XP with the Pentium Overdrive CPU installed then replace it with a 486 afterwards to see if it would still boot.

I did that in the early 00's.

Installed WinXP on a late PCI-based 486 board with PODP83 and 256M RAM. Worked 'fine'. Replaced PODP with an Am5x86-133: no boot.

Then took heatsink off PODP (drops multiplier to 1x) and dropped FSB to 16MHz. "Worked", although it took a few hours to boot to deskop 😜

Not booting after replacing PODP with an Am5x86-133, because NT kernel throws Stop error 0x0000005D early before switching to graphics mode.