Prepare for a story:
Sometimes if I move my SSD to a different SATA port, it won't boot: it will hang on "verifying DMI pool data". That I can accept: it seems like there might be a reason.
But if I immediately move it back to where it was, it won't boot either - hanging in the same place. I can move it to any SATA port and it just won't boot. I can do anything with AHCI and IDE and it still won't boot. This I can't understand. Surely what used to work should work again moments later?
Last time this happened I solved it by initiating a fresh install of Windows (7 x64) and then using the useful repair tool that only ever appears when you pretend you're intalling Windows. You know the one that you can't get to if you choose "Repair" at the first menu?
Anyway this time that didn't work, because Windows couldn't find 8.5GB free on the SSD, which only has 4.5GB free at the moment.
So, game over. That was last time's solution out the window unless I could remember age old command line stuff to move some things to another drive... nope.
So what was the solution today? Well I keep my old copy of XP on another drive, so I hooked that up. Expecting XP to boot (or fail to boot) Windows 7 started up. What the heck?
Can someone explain any part of this? And if there's a way to avoid it in the future: if I can keep a fail-safe something somewhere, please help me out with that too.
Thanks!
Sometimes if I move my SSD to a different SATA port, it won't boot: it will hang on "verifying DMI pool data". That I can accept: it seems like there might be a reason.
But if I immediately move it back to where it was, it won't boot either - hanging in the same place. I can move it to any SATA port and it just won't boot. I can do anything with AHCI and IDE and it still won't boot. This I can't understand. Surely what used to work should work again moments later?
Last time this happened I solved it by initiating a fresh install of Windows (7 x64) and then using the useful repair tool that only ever appears when you pretend you're intalling Windows. You know the one that you can't get to if you choose "Repair" at the first menu?
Anyway this time that didn't work, because Windows couldn't find 8.5GB free on the SSD, which only has 4.5GB free at the moment.
So, game over. That was last time's solution out the window unless I could remember age old command line stuff to move some things to another drive... nope.
So what was the solution today? Well I keep my old copy of XP on another drive, so I hooked that up. Expecting XP to boot (or fail to boot) Windows 7 started up. What the heck?
Can someone explain any part of this? And if there's a way to avoid it in the future: if I can keep a fail-safe something somewhere, please help me out with that too.
Thanks!

