steck's Posts

I already had the Registry keys mentioned in Part A. They were set to Red, so I modified them to Green. After doing that, I was able to reserve Windows 10.
Doesn't quite work for me. I was getting the SVGA compatibility issue before. I see the Windows icon, so I performed only Part B. When I click on the icon, I still get a message that there'... See more...
Doesn't quite work for me. I was getting the SVGA compatibility issue before. I see the Windows icon, so I performed only Part B. When I click on the icon, I still get a message that there's a compatibility issue. But when I view the compatibility report, it says that everything is OK. !
Well, sure, but I've been using VMWare + Fedora for many versions without incident, other than installation issues.
I've just started running VMPlayer 5.0.2 on a Fedora 19 x64 host with a Windows 7 x64 guest. About once an hour or so, I'm getting a fatal error that shows up in the host terminal window:  ... See more...
I've just started running VMPlayer 5.0.2 on a Fedora 19 x64 host with a Windows 7 x64 guest. About once an hour or so, I'm getting a fatal error that shows up in the host terminal window:   terminate called after throwing an instance of 'cui::NullPointerError'   what():  Null pointer dereference When this happens, fortunately, the VM suspends itself, and I'm able to restart it without incident. Still -- very annoying.
Upgrading to VMPlayer 5.0.2 fixed the problem.
I'm running VMPlayer 4.0.4 with a Windows 7 x64 guest. The host is Fedora 19, which I just upgraded from Fedora 18. The sound was working fine before the Fedora upgrade. Now when the virtual m... See more...
I'm running VMPlayer 4.0.4 with a Windows 7 x64 guest. The host is Fedora 19, which I just upgraded from Fedora 18. The sound was working fine before the Fedora upgrade. Now when the virtual machine starts, or when I try to connect the sound card, I get   Failed to open Alsa sound device "default". Connection refused. then   Failed to open sound device /dev/dsp Indeed, there's no such device on the host. In the virtual machine settings, I tried using the "Default" sound device instead choosing Alsa specifically -- no change in behavior. Googling reveals lots of mentions of similar issues with Linux and VMWare, but I couldn't find a clear resolution.
I downgraded to VMWare Player 3.1.5 and the problem disappeared. Curiously, that version has the same release date as version 4.0. -- Paul
The VMWare Tools version is 8.8.0, copyright 1998-2011. I installed VMWare Tools twice, in fact. I assume that's the latest one. No joy. -- Paul
I just installed VMPlayer 4.0 on a Fedora 12 x64 host. I have Windows 7 Pro x64 installed as a guest. The Win 7 virtual machine had display acceleration enabled (needed to view digital TV in W... See more...
I just installed VMPlayer 4.0 on a Fedora 12 x64 host. I have Windows 7 Pro x64 installed as a guest. The Win 7 virtual machine had display acceleration enabled (needed to view digital TV in Windows Media Player, for instance). The display looked fine with the previous version of VMPlayer. When running the virtual machine in the new VMPlayer 4.0 in full-screen mode, there is horrible flickering. Context menus on the desktop appear and disappear. There are several Win 7 "gadgets" on my desktop, but only one of them will appear at a time. If I disable acceleration, the flickering is not present (but then I can't run Media Player). What's going wrong?