mpack wrote:On what facts? You have just described doing exactly the same thing as FrederikB, so naturally you got the same result. That doesn't mean that your (or his) explanation for it makes any sense.
Of course I did the same thing as FrederikB because this happend to me BEFORE I read this thread and search for a SOLUTION.
Oh my god, I found out that someone here, FrederikB, had the same problems. Isn't that what forums are for ?
Now what about the only fact that Virtualbox modified the image file because the modified date and time attributes of the file have changed ?
Maybe not a solid fact but it speaks by itself.
mpack wrote:Best guess? You or XP tried some kind of boot repair function. That's what stops it booting when you go back.
Nope. Only boot in Virtualbox, then boot in VMWare. Nothing else running at boot. Only hangs with error messages at boot in both cases.
mpack wrote:And if you want to stop it happening? Easy. Don't experiment on your only copy of the data.
Hey, I wrote this :
MisterR wrote:Fortunately, I was using copies, so I lost nothing.
Don't think everyone is stupid...
And I had to try it twice when the problem occured to me to be sure it wasn't only a problem with the first image.
Please stop behaving defensively !
Thanks.