New
#31
Given what I have tried and reported on, what else could be causing XP not to boot on the new SSD?
Boot problem on cloned dual-boot SSD
-
-
New #32
Yikes, those videos do not look like you're dealing with a partition signature problem. A part-sig problem frequently results in a hang at the light blue screen (after the flag/four balls splash screen but before the desktop and task bar loads), or sometimes a hang at a gray screen with just a mouse arrow and nothing else.
Those videos kind of look like a driver problem, such as you might see if you get your BIOS set wrong between ATA/AHCI/RAID. But of course that can't be what's wrong because then Win7 wouldn't boot either, and because it worked before and you didn't change anything in the BIOS. The behavior looks like a driver problem but I can't imagine how that could be.
I really have no idea why the boot process is kicking out that soon in the process, but I'm sure it has nothing to do with the issues we've been addressing. (FWIW, that's also why it's not regenerating the MountedDevices entries; it's bailing too soon, before it ever gets that far.)
-
New #33
Right. So the only things that changed are these:
1. The HDD is now replaced with a SSD.
2. The SSD is larger in size than the HDD (500GB rather than 320GB)
3. Due to the enlarged Win7 partition (C:), the start of the XP partition (D:) is now at a higher sector number.
Everything else has remained the same. None of the above should cause XP not to boot, in my estimation, but what am I missing?
Just for sanity check, I pulled out the SSD and reinstalled the old HDD to test. Win7 and XP both boot just fine!
Since the SSD's XP partition is a literal copy from the HDD, the drivers are the same as before. I doubt that the fact that the disk is now a SSD matters, as it behaves mostly like a regular HDD, and there are people out there running XP successfully with SSDs (lack of TRIM support notewithstanding, but that should be irrelevant for booting purposes)...
XP doesn't store the drive's manufacturer or model number anywhere that might cause it to bail if the actual drive doesn't match the stored values, right?Last edited by amblabs; 01 May 2019 at 03:49.
-
New #34
Just another datapoint. I am now running Win7 on the SSD, and have the original HDD plugged in via the SATA-USB adapter. Under cygwin, I ran "fdisk" on the shell command line for both drives and the following is the output. "ti@anuenue$ " is my command prompt. /dev/sda is the new SSD and /dev/sdb is the original HDD.
I don't know if this information is of any use but maybe.
-
New #35
From the videos you posted:I didn’t see any error messages before the screen goes black and resets to POST
System Hangs at Splash Screen or Boot freezes on ACPITABL.DAT | Ask the Core Team
If that doesn't work, it is not impossible the avast drivers are causing a problem.
-
New #36
@SIW2
Hmm, that site didn’t offer any solutions for me. But you might be on to something, because I do have Avast antivirus installed (on both Win7 and XP). How might Avast be causing this? Should I boot the old HDD up into XP, uninstall Avast, then try copying that whole partition over to the SSD again?
-
New #37
You could make a copy of your xp system hive first.
Then load the xp system hive using win7 regedit. Search for aswARDisk. If found, try editing it out of upperfilters. In services, change the start type to 4.
Not sure if that is the problem, worth a try. I have come across issues with that little critter before. I can't explain why it might object to being moved - but it's possible.
That would be another way of testing it, probably easier for you.Should I boot the old HDD up into XP, uninstall Avast, then try copying that whole partition over to the SSD again?
-
New #38
I just tried this, because it seems easy to do. In regedit I found HKLM\SYSTEM\ControlSet0001\services\aswARDisk, HKLM\SYSTEM\ControlSet0002\services\aswARDisk and HKLM\SYSTEM\CurrentControlSet\services\aswARDisk under Win7's system hive, but there is no such entry in the loaded XP system hive. There are other aswxxx entries, but no aswARDisk. Is this called something else under XP?
Anyway, maybe I'll try putting the original HDD back in the laptop, boot XP and uninstall Avast. Then copy the whole XP partition to the SSD again.
-
New #39
-
New #40
I know you said you are not a windows guy but clone tools go about their goal differently so in your case may produce a different result, so I would at least try macrium.
Quote
Related Discussions