![Script Script](http://cdn.osxdaily.com/wp-content/uploads/2015/04/remove-cloudkit-metadata-files-resolve-slow-finder-mac-os-x.jpg)
I did the OS 7 install with Mini VMac – great fun! Now I am trying to get OS 9 running with SheepShaver per the instructions in the video, but I’m hitting a snag. Everything follows the video fine until I try to boot from the 9.iso image.
Jul 19, 2017 Same problem here in dev preview 7. My script essentially does the same thing - mounts a series of NAS shares but on my macbooks it runs a loop that checks for a specific wifi SSID and only tries to connect the shares when that wifi is present.
The response is a grey background with a 3.5 floppy icon with flashing question mark “?” – this suggests to me that the emulator is bootstrapping from the ROM ok, but that I am failing to boot from the CDROM ( i.e 9.iso) I’ve tried the “Troubleshooting” hint in the blog of replacing “disk” with “cdrom” in the line which reads “disk /home/pi/mac9x/9.iso” in the file /home/pi/.sheepshaverprefs – to no avail. I’ve also tried fiddling with the bootdrive value in sheepshaverprefs – also no change in behaviour. The following is the console output from SheepShaver: ——- pi@raspberrypi:/mac9x $./SheepShaver SheepShaver V2.4 by Christian Bauer and Mar”c” Hellwig Reading ROM file WARNING: Cannot open /dev/cdrom (No such file or directory) WARNING: Cannot open /dev/mixer (No such file or directory) WARNING: Cannot open /dev/dsp (No such file or directory) WARNING: No audio device found, audio output will be disabled. PowerPC CPU emulator by Gwenole Beauchesne ——- Anybody have the same experience or any hints on how I can boot SheepShaver from the 9.iso? Do I need to mount the ISO at /dev/cdrom?
Advice is appreciated. Is anyone having issues with getting audio to work in the emulator? I am getting the same console messages as Matt above when I start from command line when it comes to audio output. WARNING: Cannot open /dev/mixer (No such file or directory) WARNING: Cannot open /dev/dsp (No such file or directory) WARNING: No audio device found, audio output will be disabled. Is any one having similar issues. My suspicion is that the Pi3 address its audio devices differently so if any one knows the correct devices or the correct solution to this (or what I am doing wrong) I would be very grateful.
I solved it a different way last night. I found a package called ‘oss-compat’ which is part of the alsa repository which creates ‘dummy’ dev/dsp and dev/mixer devices on the pi. Those devices automatically redirect the audio stream to the active audio device used by the system. The advantage of this solution is that you do not have to start another process before starting sheepshaver.
You can use the default settings of sheepshaver and it will just work So simply ‘apt-get install oss-compat’ in the terminal and then reboot the pi After that sheepshaver should work with default settings. Having said that though I am getting the same issue with speed when trying to run old games with audio.
It gets better when I try the same programs under Mac OS 8.5 vs OS9 but only slightly. I am still messing with it to see what I can come up with.
Don’t panic if your camera suddenly stops working during a video call or if you see a “No camera connected” or “No camera available” error when you launch an app. Camera issues on the Mac are usually minor, and their solutions can be as simple as just shutting down and powering up your computer. If you’re having trouble using your Mac’s built-in camera, try one of these quick fixes to get it working again. Force Quit VDCAssistant and AppleCameraAssistant If you need to use your camera right away or can’t dedicate a lot of time to troubleshooting the issue, try restarting camera-related processes like “VDCAssistant” and “AppleCameraAssistant” in the Terminal app. VDCAssistant and AppleCameraAssistant are programs that run in the background whenever you use your Mac’s built-in camera. Complications with these processes can affect any number of applications that can access the camera like FaceTime, iMovie, Messages, and Skype.
![Mac Mac](https://images.idgesg.net/images/article/2017/12/3-spotlight-suggestions_scaled-100745092-medium.jpg)
Sudo killall AppleCameraAssistant and press Enter. Once you’ve stopped both processes, launch an application that uses the built-in camera and see if the problem is resolved. Adjust Your Camera Settings There isn’t a camera section in System Preferences, so you can’t change the camera settings directly. However, most apps that use the built-in camera have adjustable camera settings.
FaceTime and Skype let you specify which camera you want to use for video calls, so make sure the built-in camera is selected. Reboot Your Computer Another quick way to solve camera problems is to reboot your Mac. Be sure to completely shut down your Mac instead of choosing the Restart option. Restarting your computer will close your session and temporarily turn off your Mac but leave the RAM untouched. On the other hand, shutting down your Mac will clear the RAM and end all processes, including ones that might be interfering with your camera.
Update Your Software If your camera doesn’t work with a specific photo-editing or video-conferencing app, it may be incompatible with that application. For example, you can’t make video calls using the Skype app if you or the person you’re contacting has an outdated version of Skype (version 2.8 or older). If you want to make video calls, both parties need to update the app to the latest version. The same philosophy applies to your operating system. If you’re having camera problems, see if there’s a security update available for your Mac. Apple includes important bug fixes in each build release, so it’s important to update to your software to the latest available version.
Chances are they’ve identified your camera bug and resolved it in the most recent update. Conclusion It’s not always easy to pinpoint the cause of a camera issue on the Mac, but troubleshooting the problem is rarely difficult. Most camera-related issues and errors on the Mac are minor, and you can usually solve them in a few steps. However, if you’ve tried the above fixes and still can’t use your camera, contact Apple for further assistance. Very easy to follow the crystal clear comprehensive instructions, inspite of my low-level knowledge of computer technology. After learning here the reason why the mere restarting of my MacBook failed to restore the sudden, for the first time loss of the built-in camera function (“No Camera Connected”) on my otherwise reliably and smoothly running MacBook, I was able to fix the problem with the shutting down command before having to try the other above well explained options. Thank you for the useful, much appreciated advice.