I have installed El Capitan on Virtual Box 5.1.28. However, the laptop keyboard isn't working even though the auto capture icon is turned on. When I use an external keyboard, that works. But I want to use my native laptop keyboard. Does anyone know what's wrong?
For anyone still having this problem, I learned that installing macOS on VMWare does not have this keyboard problem. Instructions are here
Related
My Macbook Pro mic was working normally but there is a system hang so I have to restore and install new OS Catalina.
However I find out that the mic is not working, when I check in setting, it is not showing signal as I speak.
I search around Google but there is no one have the same issue with me: there is no ‘Internal Microphone’ option in Sound setting.
Please refer to the below images:
Could you please give me some advice, thank you!
Recently I installed VirtualBox 6.1 on my MacBook Air and installed Windows 10 on it (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/), but somehow the sound on my guest Win10 is not working. I managed to dig for some info and found out that I need to install (https://www.realtek.com/en/component/zoo/category/pc-audio-codecs-ac-97-audio-codecs-software) but it does not work. Could anybody help me with this one?
EDIT: I get the error when I hover over the sound icon: "no audio output device is installed"
Fixing the sound on guest windows 10 where the host is Linux / Mac
Open the settings for your Windows 10 machine inside of virtualbox
Go to Audio > Host Audio Driver, change to "ALSA Audio Driver"
Go to Audio > Audio Controller, change to "ICH AC97"
Enable Test Mode on Windows 10 and reboot machine.
Download and install the Realtek driver for Vista/Win7 (32/64 bits) Driver only (ZIP file) from here and reboot your Windows 10 machine.
Disable test mode from the link in 4th step then reboot your Windows 10 machine.
In case you still have a crackling / popping sound
In the task bar, right click on the sound icon and choose playback devices
Double click on Speakers
Select the Advanced Tab
Set the Default Format to 16 bit, 44100 Hz (CD Quality)
In the Exclusive Mode, Uncheck the Allow applications... etc
Select the Enhancement Tab
Check the Disable all sound effects
Make sure you click apply then OK
The crackling sound would immediately disappear but you could reboot just to verify.
I tried the route in the most upvoted answer but couldn't get Win10 to install the AC97 driver. For me the solution was much simpler: select Audio Controller "Intel HD Audio" in the virtual machine settings (and leave Host Audio Driver to whatever the default was, in my case "Pulse Audio"). Enable Audio Output checked of course, and it should just work like the machine has a sound card.
Crackling is still there even with the stuff about turning off enhancements and exclusivity, but I think that's not going away since I'm trying to play 1080p video and I don't think the virtual machine has quite the kind of video hardware access (and memory allocation) that it needs to play this level of content perfectly smoothly.
Install Guest Additions if you haven't already. More info here for your specific case: https://www.virtualbox.org/manual/ch04.html#additions-windows
Host Linux Mint. Guest Win10. Had 'Guest Additions' installed, 'Host Audio Driver: Pulse Audio', 'Audio Controller: Intel HD Audio'. Sound in Win10-guest, but not in Commandos 2 or Patrician 3.
Installed Realtek drivers (https://realtek-download.com/wp-content/uploads/2014/07/6305_vista_win7_pg537.zip (thank you Wil)). Still no dice.
Win10 said: "No output devices found".
Changed Host Audio Driver to ALSA Audio Driver. And it worked! Thanks everybody.
With Fedora 36 host and Windows Server 22 Standard Desktop Evaluation as guest inside VirtualBox 6.1.34 it automagically worked after enabling sound at guest via:
Mouse Right Klick at (disabled) speakers symbol in Windows taskbar
Mouse Left Klick at "Sounds" (German)
-> See Screenshot
Accepting the prompt enabled sound with all default settings in VirtualBox VM Audio Settings:
Host Driver: ALSA Audio Driver
Controller: Intel HD Audio
VirtualBox 6.1.34 Oracle VM VirtualBox Extension Pack was also already installed here.
Sound tested successfully with Firefox 100 and https://fip.fr -> Rock
I installed OS X 10.11 El Capitan on VMware and it worked successfully but after i shut it down and reopen , it got stuck after loading with apple logo and turns a black screen
can anyone help me with this,Please ?
i run this VMware on Windows 10 ,Thanks in advance.
According to this source who had the same problem you can follow these steps and see if it works:
Reboot to safe mode, here are the steps.
Delete this file "/Library/Preferences/com.apple.loginwindow.plist"
Switch off iCloud authentication and revert to local authentication.
I had the same issue with 10.13 High Sierra
Editing my VMX file (Documents/Virtual Machines/MacOS/MacOS.vmx) to include:
virtualHW.version = "10"
Fixed it for me.
I am running windows 7. I have just finished downloading and converting (using vmware converter) the Windows XP Mode vmware image to a .vmx file for vmware player.
I can then play the Windows XP image fine in VMWare player. There is however and issue where the windows xp screen inside vmware does not take up the whole screen. In face it only takes up a very small area. I've read on some forums that this might be a compatibility issue between windows 7 and windows xp.
Does anyone know how to fix this please?
Install VMWare Tools on the guest XP machine and bounce it. It contains several virtualization drivers among them one for the virtual graphic card. This allows you to dynamically change the screen resolution of the guest, just by resizing the VMWare Player window.
We have developed an Qt application for Mac OSX in which we have used the following code to lock the screen.
system("/System/Library/CoreServices/Menu\\ Extras/User.menu/Contents/Resources/CGSession -suspend");
The code works as expected except sometime after locking, the screen freezes (a white/gray blank screen). We have to force shutdown the mac to unfreeze.
I have tested in Mac OSX 10.7.2, 10.7.4, 10.7.5.
I am not sure if its a problem of our app or the issue is caused by Mac itself?
Can anyone shed some light into this?
Thanks,