On Monday 05 January 2009 15:39:48 Frank Mehnert wrote: > Paul, > > On Monday 05 January 2009, paul williamson wrote: > > Many thanks for the reply. However, I don't think it addresses the > > problem in my situation as I have done a complete full re-install of XP > > as a guest (from the original XP CD) on both my desktop and my Acer > > Aspire. This means that I am not using anything that remains of the > > earlier version. Even with everything new, the problem remains. On the > > desktop I get the error posted above. On the Acer Aspire the "restoring > > machine" stops at 99% and then it goes back to the main window showing > > "Aborted". > > If the VM is _restored_, then some old VM state is used. How did you create > this old VM state, which VirtualBox version did you use? Drop the saved VM > state and start the VM normally. > > Kind regards, > > Frank
I am using VB 2.1.0 - the "full" version (with USB support). I create the old VM state by going to the "machine" menu/close - then select the top option "save the machine state". (Or by using the Host Key/Q to get to the same shutdown menu). Yes, I can "discard" the machine state and re-start it, but that negates the whole purpose of "saving" the state in the first instance. I take my laptop into several different places each day, and each time I have to open my VB/XP guest OS. I value the amount of time saved by being able to "save" and "restore" instead of having to shutdown and "reboot" the guest OS. As I said, I have noticed that this behaviour only happens with the more recent versions of VB, and only when the host OS is installed on a SATA hard drive. I had no problems when my host OS was on an IDE drive (on my desktop PC), but that option is not available on my laptops. Thanks for your continued interest in this problem. Kind regards Paul _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
