conflict between LogMeIn service and VB 4.3.6
Posted: 4. Jan 2014, 01:10
I had previously posted this issue as "VirtualBox crashes when upgrading guest to WinXP SP3".
I had then upgraded to VB 4.3.6, and re-installed Windows XP SP3 from scratch, and everyone had been running fine for two weeks, until I returned to work.... now I've clarified what the issue is...
My home system:
Host: Windows 7 Home Premium, 64 bit, SP1
16GB RAM, 9GB free
Guest: Windows XP Pro, 32 bit, SP3, guest additions installed
2GB RAM, 1.4GB free
I run the guest in Seamless mode.
I use an online service called LogMeIn dot com to log into my home machine from work.
I've been doing this for more than a year now, with no problems until recently;
Now, when I log into the host machine, even if I do not interact with the guest at all, one of two things happens; either VirtualBox crashes completely, or the Win XP disappears (meaning it is still running, according to the VB Manager, but the window is not visible).
I believe this started when I upgraded VB to a recent version, about a month ago; unfortunately, I don't know what that version was.
Later: No, actually this started occurring when I was trying to upgrade the WinXP guest from SP2 to SP3...
My original issue was that VB would crash when I was trying to install the SP3 update...
Any ideas on what is going on, and what I might be able to do to fix it?
I had then upgraded to VB 4.3.6, and re-installed Windows XP SP3 from scratch, and everyone had been running fine for two weeks, until I returned to work.... now I've clarified what the issue is...
My home system:
Host: Windows 7 Home Premium, 64 bit, SP1
16GB RAM, 9GB free
Guest: Windows XP Pro, 32 bit, SP3, guest additions installed
2GB RAM, 1.4GB free
I run the guest in Seamless mode.
I use an online service called LogMeIn dot com to log into my home machine from work.
I've been doing this for more than a year now, with no problems until recently;
Now, when I log into the host machine, even if I do not interact with the guest at all, one of two things happens; either VirtualBox crashes completely, or the Win XP disappears (meaning it is still running, according to the VB Manager, but the window is not visible).
I believe this started when I upgraded VB to a recent version, about a month ago; unfortunately, I don't know what that version was.
Later: No, actually this started occurring when I was trying to upgrade the WinXP guest from SP2 to SP3...
My original issue was that VB would crash when I was trying to install the SP3 update...
Any ideas on what is going on, and what I might be able to do to fix it?