Tag Info

Hot answers tagged

2

Seems like a bug introduced in Fusion 7: https://communities.vmware.com/thread/488935 This solved it for me, in VMWare Fusion Version 7.1.0 (2314774): Settings for the virtual machine -> Keyboard & Mouse -> Edit Profile -> Key Mappings -> check "Enable Language Specific Key Mappings"


1

if your CPU doesnt support virtualization, then thats just it, you cant VIRTUALIZE it. But as you said, you can install it beside your win7 installation. i would run the live cd and mess around before installing it, thats one way you can see if any errors occur.


1

Dualbooting seems the best option to use linux on your pc considering that your computer only has 2 gb of RAM and does not support virtualization. If you want to learn about RedHat linux you can use Centos and Fedora. RedHat Enterprise Linux 7 introduced systemd while Fedora started using systemd long before RHEL did. Centos 7 is equivalent to RHEL7.


1

It will go to the wired connection, or the top-most connection on the connection settings. They work one at a time, but with tools like Connectify, you can access more than one connection simultaneously. If you are connected via LAN you can access shared folders in different computers. If you are connected to a wireless connection, you can access those that ...


1

NAT is the issue. Packets from the Ubuntu machine fly out of the machine, and onto the network. Router sees these, and sends them to your computer, because it knows where it is. then, VMWare ensures your VM gets the packets back, because that's its job. You get connection. When pinging the guest, packets from the Windows host fly out onto the network and ...


1

I think the short answer is that you can't directly sync the host and guest environments regarding Num Lock. However, a couple of alternatives are available: As noted in Rudolph's comment link, change the VM BIOS setting to enable/disable Num Lock at boot in the VM to match the hosts default Manually set the state of guest Num Lock to match the host


1

I think that is an issue specific to your hardware as it not behaving as expected. It is an issue of timing out of scheduling of an event. Shared services seeks time to look up the network discovery and find the content that is shared, decide the protocol for the communication, and then gets content if everything is okay. So it may appear that the CPU times ...



Only top voted, non community-wiki answers of a minimum length are eligible