Read through the guide on here for Basilisk II and it should help you out. You've already got an OS image with that archive, but your ROM image is either improperly named for your prefs file, or it got damaged somehow. Also, the cdenable.sys note indicates that the original poster is using an old ve...

Well, here's the issue: VirtualBox 4.3.6 runs OS X 10.5.8 just fine. My 2015 MBP however, runs OS X 10.11, which is incompatible with 4.3.6 -- it needs 5.something. Furthermore, the MBP uses the CrystalWell architecture, which 10.5 doesn't recognize. So, I've done the following: 1. remove /System/Li...

Sort of; I think some work was recently done to fix it so it doesn't need the driver. See http://www.emaculation.com/forum/viewto ... f=6&t=5282 for the 2015 build.

You can upgrade from 8.6 to 9.0.4 with the 9.0.4 install CD (or CD image); it's a pretty painless process, as you don't even need to reboot prior to running the upgrade. I miss the days of Mac OS overinstalls where you didn't need to boot off separate media to overinstall :) That said, I started spl...

Yes. That's the only bit of CB you need, other than the ROM.

Nope; your question and answer might help the next person who searches this site because they've got a similar issue.

And having said that, how did you fix the issue? Even if it's "I turned up the volume on my host device" it would likely be useful to others.

Any hardware extensions should be disabled in SS as they either won't help at best, or will cause hard to trace crashes at worst.

I'll second that -- there are documented security bugs in 10.6 that even the exploit kit landing pages check for. If you're playing movies through VLC on 10.6, this is another attack vector currently in the wild. 10.4 PPC on the other hand... at this point it's basically safe from malware attack. Mo...

If you're talking 68k, there's also the MESS source, which compartmentalizes the hardware logic nicely. The PPC code is still unfinished in there though, as far as I know.

Thanks, Mossy! I hope the funding goes well for you I've found that a number of sources for old info like this appear to be vanishing, so really appreciate the work you've done in putting it all in one place

You may need to edit your prefs file following the documentation and threads on here. The defaults *should* work, but it's been a long time since I've started from scratch.

See that file named "Mac OS ROM.rom"? You need to rename it "Mac OS ROM" (no extension).

From memory, I think this addresses most of your questions: 1. SheepShaver compiles on 10.6.8 or earlier. It'll compile in a VM running 10.6.8. There are compile instructions on the wiki. 2. SheepShaver starts memory addressing at physical value 0. This is a no-no on modern OSes, so modern compilers...

Just to avoid confusion, everywhere that enryfox said Lion in the previous post, he meant Leopard. When he said "Mountain Lion" he meant "Snow Leopard". :) Also worth pointing out that both Tiger and Leopard had Intel and PPC builds, but both the PPC and Intel builds of Leopard h...

Have you tried running them under 9.0.4? I recall doing this with both CW3 and MSW5.1 on actual hardware back in the day. I didn't use 8.6 for long because I had all sorts of memory conflicts in it regarding third party extensions. Vanilla install was faster/cleaner than 9.0.4, but keeping the syste...

Any work that can be done to abstract the emulators from the underlying OS is beneficial in terms of longevity: nowadays CPU's are pretty fast and we can allow an intermediate layer if that helps making the code less OS-dependant ( basilisk II on my iMac runs hundred of times faster than a 68040 CP...

It's still in the development stages. There are customized images linked in this thread that will boot, but some OS functionality is removed, and there's a high likelihood of failure.

Any reason why you're using 10.5 instead of 10.4.11 with Classic?

Is that the original Mini with 2GB RAM? If so, then there's your problem You're running two operating systems in tandem, and have used up the memory. If you can upgrade it to 4GB, there will be a noticeable speed improvement.

Read a bit further back in the thread -- a factory OS 9 image won't boot currently due to some issues with Open Transport and the lack of an emulated serial port. A bit further back in the thread are some prepared images that allow you to boot OS 9 by removing the Open Transport resources. The post ...

You're not going to get the printer to communicate with the guest OS via USB though; so you'll need to print to a file, and then send that file out the USB interface from the host OS. If the printer just blindly prints, this shouldn't be an issue, but if there's any sort of negotiation that goes on ...

What does your prefs file look like? Have you tried removing the nvram file?

Actually, one of the original developers of the drivers popped up a while back, and created a patch that obviates the need for the drivers on modern systems; the code's still in the source though I believe. It's the entire structure of the emulation cores that is obsolete; specifically, in SheepShav...

It's worth a try, but SS and BII are also both obsoleted source, and depend on things that are quickly becoming deprecated. BII should hang on a bit longer than SS, as it doesn't depend on running at address 0. Basically, if someone has the spare cycles, it might be worth refreshing them to use SDL2...

Back in the day, I had an extension that created an extra virtual serial port, for redirecting data to virtual devices/files. That might work here, but you'd need extra work to translate the output to Postscript. Could probably be done with a perl script, considering the vendor had a Postscript add-...

A further note on emulation vs. virtualization: Emulation involves dynamically translating instructions meant for one piece of hardware to work in software. As such, an iPhone can emulate a car horn. Virtualization involves replicating hardware interfaces in software. As such, a computer can virtual...