Finding this old thread. I experience same issue. I've tried MCL 2.0 and MCL 4.X-something. Same result. It freezes up SS or crashes. I think there is the same issue with BasiliskII. I have to mention, that I just dug out my old PowerMac 7200/90 and got it up and running with no issues. Amazing. Cha...

Hello

Has anyone ever tried running Apple Unix, A/UX, under Basilisk II? Is it possible?
I read that A/UX is very particular about hardware identifiers, and that this is an issue when attempting to run it in an emulator. But it would be sooo nice to run under Basilisk.

/Frank

Before my experiments began, I installed a fresh copy of RetroPie 4.7.1 - same as on the RPi400. This was back in the beginning of january.
So, in principle the only difference between the two is the ARM processor.

OK, this whole SheepShaver-on-RaspberryPi-business is just SO weird. As mentioned in the other thread I opened, I was able to compile and run SS on RPi2+ and RPi400, using a kanjitalk755 clone. However, it seems that my compiles for both Pis were based on SDL1, and most likely this did not play well...

Hi, If slirp is not available in the drop down, and you cannot set "--ether slirp" on the command line or "ether slirp" in the prefs, then perhaps something goes wrong while compiling. Perhaps you are missing some dependency, but I would not be able to tell you how to check that...

If the default "slirp" somehow happens to be replaced in the prefs file by "wlan0", that is what may appear in the GUI menu as only choice. Enter "slirp" (without quotes) in the menu manually (typing) and save the change. Or, alternatively, edit the prefs file in a tex...

But no... Even with sheep_net completely removed I still cannot get slirp to do anything. And I still find it strange that I can't even select it as a drop-down value in the GUI.

Hi
Perhaps someone with some cred on this forum would consider donating some time to update the Wikipedia page about SheepShaver. It almost looks like an abandoned project:
https://en.wikipedia.org/wiki/SheepShaver
Best
Frank

Only my "wlan0". But then, choosing wlan0 requires sheep_net, as far as I understand. Edit: Thinking about it, is it possible that the sheep_net module is still loaded in the kernel, even thought the /dev/sheep_net device is not initiated, and that SS still thinks it is running sheep_net? ...

I tried to start SS with the GUI anyway, but it seems like "slirp" is not available as a dropdown item in the networking tab?

Yes, this is what I did. I tried both DHCP and manual setup, but connections timed out nevertheless.

Hmmm. I don't seem to be able to make slirp work at all. Tried --ether slirp and DHCP - only timeouts Tried --ether slirp and manual setup of 10.0.2.5 - only timeouts Checked to see that slirp was actually compiled, and it seems to be. Not really sure what I am doing wrong here. It seems so simple f...

Great, thanks! I'll try that as soon as I get home. It is also a simpler solution than installing sheep_net boot scripts.

That sounds really really familiar. We had that connection while fixing up audio for one of the emulators a number of years ago. The problem ended up being a bug in the buffer handling routine; the buffer could get into a state where it wasn't completely full, and so didn't flush, blocking the next...

Some additional info. When I try ping to a specific IP it times out after 5-8 pings. But if I then try to ping another IP, it picks up the connection for another 5-8 pings before it times out again, and so on.... So it seems to initialize the connection to any IP, but cannot keep it alive for more t...

Hi I need the sheep_net connection to the internet, and I have compiled it, and made a script to install the kernal modul at startup. User rights are set correctly for /dev/sheep_net, and --eth is set to wlan0. Upon boot and start of Internet Explorer 4.5 it connects briefly to the net, but then aft...

Hi I found this thread, as I am going down a similar route. I would like to hook up old Mac-disks to SheepShaver, mainly because I am trying to install my old Cubase VST from original disks. Cubase - and other programs - refuse to install unless they can identify an actual SCSI disk device. But if I...

Dang! This was so much the problem. After compiling the kanjitalk branch with direct addressing, it also boots!
So I will go with this branch in the future, as it is actively developed.

I do believe that I solved the problem! I had to go with the cebix fork to make it work. Once again I followed the recipe above with the direct addressing. But this time I checked the items of sysctl -a and I noticed that the vm.mmap_min_addr = 0 line wasn't there, even though it is in /etc/sysctl.c...

Yes I did, and it still didn't get me past that error. Had to startx as root, and start SheepShaver from the initial Xterm, but alas, it still fails.

I tried the original recipe for compile, with the ./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --disable-jit-compiler --with-gtk --enable-addressing=direct,0x10000000 Starting the app behaves the same, only now it fails with : SheepShaver V2.5 by Christian Bauer and Mar"c&qu...

I tried the kanjitalk fork first on the RPi2+, with the standard compile instruction found in the README file. Compile is fine, but when I start, I get the Settings dialog, and upon "Start" the following: sudo xinit ./SheepShaver X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 Buil...

OK, thanks for the response. I'll see if I can figure out how to get the kanjitalk-fork working, once more. The way I go about this, it to use my RPi2+ as a testing ground, where I can make mistakes and experiment, before I attempt compilation and installation on my Pi400. I only have the one, so I ...

Hi Just registered on this forum, as I have a question regarding compilation of SheepShaver for the Raspberry Pi 4. I have successfully compiled SheepShaver on a Raspberry Pi2+, on the newest version of Raspbian, and it runs and opens in RetroPie 4.7.1 by using xinit. However I am unable to repeat t...