VOGONS


First post, by justin1985

User metadata
Rank Member
Rank
Member

I have a Thinkpad X220i with Sandy Bridge i3-2310 that I've used for some time now as a convenient XP machine. Today I went to use it for an actual work task (opening a very old Access MDB to resave to newer MDB that modern Access will open) and found the installation was totally corrupted. I'm pretty sure that was caused by the drive being loose in its bay (don't have the original caddy and modern SSD is thinner - I've added some sticky foam now to wedge it in place).

However, despite multiple attempts at wiping the SSD, and even swapping the SSD for a different one, I can't seem to get Windows XP setup to get past the first reboot. The progress bar splash screen comes up and animates, then sometimes briefly flashes to the white text on blue graphics screen that sometimes gives CHKDSK messages, then the screen goes blank. The HDD light continues for a while with the screen blank, then after a few minutes the HDD activity stops, and nothing more happens. Exactly the same behaviour, sometimes with the CHKDSK message, other times it flashes too quick to read.

If I remove the WinSetupFromUSB stick, then the GUI for the second stage of install does load - but obviously then it doesn't have the files it needs!

That is with the SATA controller set to compatibility mode. When I've tried it in AHCI mode (and the F6 drivers provided by the WinSetupfFromUSB project) I get the "critical error" BSOD. When I've tried with a CD installer in a USB CD drive, I also get the BSOD regardless of whether it is in AHCI or Compatibility mode.

The weird thing is that it clearly worked in the past when I originally set up XP, and nothing changed in the hardware setup or BIOS since then. I've just tried installing Windows 10 and that installed fine, so a hardware failure seems very unlikely (and I'd already tried with different SSDs). Any ideas what might be happening?

Reply 1 of 2, by theelf

User metadata
Rank Oldbie
Rank
Oldbie

Check RAM, if is ok, create fat32 partition in SSD, install DOS, copy winnt folder and install from same disk, without usb

But looks like hardware problem

Reply 2 of 2, by justin1985

User metadata
Rank Member
Rank
Member
theelf wrote on 2025-02-12, 22:15:

Check RAM, if is ok, create fat32 partition in SSD, install DOS, copy winnt folder and install from same disk, without usb

But looks like hardware problem

Thanks for the suggestion! I had assumed a hardware problem too, but then got the same result with a different SSD, but also got Windows 10 to install absolutely fine - weird. The Memtest within GParted boot disk also seemed to run fine.

By chance I happened to boot with the SSD with the part finished XP install but without the USB attached, and realised and added the USB just as it booted. Really weirdly, this time it worked, and didn't complain about missing files! Tried again with the other SSD, formatted and tried a fresh install, and repeated the same behaviour. Second boot with the USB attached got the CHKDSK prompt then blank screen, then disk activity for a few minutes. Then I tried removing the USB stick and rebooting again, and it worked!

Seems like maybe the file copy stage was happening anyway when the screen was blank, then disk activity was stopping when it got to the first languages prompt? But not having the USB connected somehow stops the whatever incompatibility is causing a blank screen? Really weird!