I just thought this was interesting.
One day I tried to startup VMware and it said it thought my CPU was 14.00 MHz. So I just let it proceed anyway to see what would happen. The guest OS (XP) felt like it was on drugs. I'd go in the clock applet and it should be going 100 mph. I captured some screenshots.
cpuid: http://xtknight.atothosting.com/images/cpu.png
taskmgr (using 50% cpu as the graphs fly by): http://xtknight.atothosting.com/images/taskmgr.png
save dialog frozen 1 and clock: http://xtknight.atothosting.com/images/vmgonewrong1.jpg
save dialog frozen 2 and clock (t+10 sec): http://xtknight.atothosting.com/images/vmgonewrong2.jpg
save dialog frozen 3 and clock (t+20 sec or so): http://xtknight.atothosting.com/images/vmgonewrong3.jpg
The screensaver would attempt to come on about every five seconds and when it did, it gave me a seizure.
Time flies when you're having fun!!
`sudo vmware-config.pl` fixed the message and problem, and no damage was done.
One day I tried to startup VMware and it said it thought my CPU was 14.00 MHz. So I just let it proceed anyway to see what would happen. The guest OS (XP) felt like it was on drugs. I'd go in the clock applet and it should be going 100 mph. I captured some screenshots.
cpuid: http://xtknight.atothosting.com/images/cpu.png
taskmgr (using 50% cpu as the graphs fly by): http://xtknight.atothosting.com/images/taskmgr.png
save dialog frozen 1 and clock: http://xtknight.atothosting.com/images/vmgonewrong1.jpg
save dialog frozen 2 and clock (t+10 sec): http://xtknight.atothosting.com/images/vmgonewrong2.jpg
save dialog frozen 3 and clock (t+20 sec or so): http://xtknight.atothosting.com/images/vmgonewrong3.jpg
The screensaver would attempt to come on about every five seconds and when it did, it gave me a seizure.
Time flies when you're having fun!!
`sudo vmware-config.pl` fixed the message and problem, and no damage was done.
