• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

System 7 on a Rasberry Pi

zackl

Well-known member
Last edited by a moderator:

dcr

Well-known member
Recently?  No.  Haven't tried lately either.

I did get it working through RetroPie a number of years ago on a Raspberry Pi B (I think).  Downside was that you had to use the Emulation Station to get to it.  That build used Basilisk II as opposed to Mini vMac.  I've seen another video where the guy managed to get Basilisk II installed and configured where the Raspberry Pi would boot right into the emulator after going through its own startup process.  That's my goal but haven't figured out how to do that.

I have gotten it (Basilisk II) to run on a Raspberry Pi Zero but it has to go into the Raspbian desktop first and then you boot the Mac emulator.  That leaves less memory for the Mac itself because the Raspbian desktop is running.  Other problem I had was that the RPiZ would also lose the keyboard and mouse connection (USB) after a few minutes.  Then, I'd have to unplug them and plug them back in to get them working again. Makes no sense to me.  And that's not an emulator issue because it does it in Raspbian's desktop too.

 

demik

Well-known member
I have with Basilisk II, even 8.1. vMac should works ok too. For Basilisk II booting directly, you can use an empty X11 session with no window manager and autostart Basilisk II full screen with .xsession or something.

Unfortunately the RPI died and I trashed the SDCard with it, and bough a real Mac. So goodbye custom scripts

Just prepare your disk image on your Mac and move it :)  

 
Last edited by a moderator:

markyb86

Well-known member
I used that guide to get System 7 up on a Pi Zero W. 

It worked great, but like @dcr said, it needs to be launched from raspbian. It was about as slow as macintosh classic II. 

I think without the GUI OS in the background it would have been more responsive. For what it's work it worked pretty good, just used 100% of the cpu the whole time, so there was not much multitasking going on. 

image.png

 
Last edited by a moderator:

cheesestraws

Well-known member
and autostart Basilisk II full screen with .xsession or something. 
The easiest option I've yet found is to disable the display manager and launch X and BII from a systemd unit file.  I had some weird issues with SDL but that may have just been me having a moment

 
Top