Page 1 of 1
1.5.6 > 2.0.2 GAME OVER
Posted: 13. Sep 2008, 12:51
by verbal_666
AMD X64 + Windows XP 32bit + 2GB/ram
1.5.6 works perfectly (VirtualBox_1.5.6-1_Win_x86.msi)
2.0.2 (VirtualBox-2.0.2-36488-Win_x86.msi)
The game is over?

Posted: 13. Sep 2008, 13:45
by Oblong7
VBox 2.02 is giving me the same error message.
I installed 2.02 on top of 2.0. After receiving the critical error, I uninstalled VBox, and cleaned out my registry. After re-installing 2.02 on a clean system, I still get the error.

Posted: 13. Sep 2008, 14:24
by Oblong7
Temporary Solution:
I went back to ver 2.0.0 and no longer experience this critical error.
It can still be downloaded from here:
http://www.virtualbox.org/wiki/Download_Old_Builds
Posted: 13. Sep 2008, 18:44
by TerryE
Hi, If you are seeing a problem in 2.0.2 that is not in 2.0, then could you please raise a ticket?
You need to register for a
wiki user account (this is different to a forum account sorry) and then you can use the public
Bugtracker to raise tickets for reporting problems in VirtualBox and make suggestions for improvements.
Posted: 17. Sep 2008, 15:03
by Oblong7
There is a patch posted on this page:
http://www.virtualbox.org/ticket/2212
Problem now solved for me. I am now at VirtualBox ver. 2.0.51
Posted: 17. Sep 2008, 19:28
by TerryE
?? There is no such thing as 2.0.51
Posted: 18. Sep 2008, 15:00
by Oblong7
TerryE wrote:?? There is no such thing as 2.0.51
Terry, there
is such a thing as 2.0.51. Here is a screenshot from my system after I applied the patches:
http://drop.io/vbox_screenshot
UPDATE
I just checked at the Bugtracker page, and there are now newer updated patches for version 2.0.2. After applying these patches, VirtualBox now @ version 2.0.3
Posted: 18. Sep 2008, 15:44
by TerryE
I've found the patch but I can't quite read the text on a screen shot that is 100x79 pixels

Posted: 18. Sep 2008, 16:00
by vkov_tinsky
I removed the irrelevant info.
Temporary fix helped, but only after a 20 second wait!
Posted: 18. Sep 2008, 16:48
by JohnSnyder
I updated from v 1.6 to 2.0.0. Immediately after updating, when I tried to get into the settings menu for existing machines on my Vista 32 system, VirtualBox simply stopped working ("Not Responding" showed on the top of the window) and I had to close it. I updated to 2.0.2, hoping to fix this problem, and the same thing happened. I have now updated using the temporary fix, replacing the two files in question. Now, when I click on "Settings", my VirtualBox window gives me the "Not Responding" message, but after about 20 seconds, this message disappears and the settings screen pops up and I can change the settings. This is an improvement, but there's a lengthy delay prior to the Settings' window coming up.
Posted: 20. Sep 2008, 10:42
by verbal_666
WORKS

Posted: 20. Sep 2008, 23:42
by JohnSnyder
Yes, the temporary fix that I mentioned was that patch which updated the version number to 2.0.3. Still a very lengthy delay before the Settings window will display.
1.6.6 fast; 2.0.2 sluggish on Vista x64
Posted: 21. Sep 2008, 01:39
by noespam
I decided to upgrade to 2.0.2 because I switch between OS X and Vista x64. VirtualBox 2.0.2 64-bit on Vista x64 is noticeably slower running virtual machines. even the network connection is slow. when i log into a debian image through SSH it's almost instant on 1.6.6, in 2.0.2 I have to wait about 10 seconds before i get the password prompt. everything is good again with a reisntall of 1.6.6.
thanks anyway! virtualbox is still the best. i'm sure version 2 will get better.