I tried downloading it separately three times, but I still got the same result. I'm really baffled... I don't know if this info helps, but I forgot to mention. When it gets stuck on that screen, I'm still able to go to the top bar and quit the game or mess with the applications at the bottom, so th...

No matter what value I put there, in BII, if I open say Zterm, both the modem and serial port will be unavailable (OSErr -23). "Modem Port is not available. Please select another port:" ### Error: -23 opening port I get the same -23 in my own code in BII, when calling OpenDriver(). (works...

Well I'm not *I* could easily do that, I don't have the foggiest clue how I would do that. Any hints? You'd have to play with it a bit to figure it out... with the source code and config script, that is. Track down the serial code section, and you should be able to point it at /dev/ttysX instead of...

I can't seem to find any working images of tiger. both dvd images I've tried won't boot. with both images both images qemu just spews "no valid state has been set by load or init program" A few things to check: 1. Are you using QEMU-PPC 5.2? 2. Which hardware are you emulating? I use the ...

Yes... this is why I've held off for years in asking for this addition. What I'm looking for is to be able to put a "title 8.6" on a line in the prefs file in my .sheepvm file, and when I run my MacOS8.6.sheepvm, the window shows "SheepShaver 8.6" but when I run my MacOS9.sheepvm...

So this is what I've got my BII config file set to: seriala /dev/cu.Bluetooth-Modem serialb /dev/tty.iPhone-Wirelessi The first lets me connect to bluetooth as if it's a tethered device, BT acting as an external modem for BII on the modem port. The second connects to the Bluetooth serial on my phone...

Mini vMac already emulates the modem and printer ports, it just has nothing attached to them by default. Building with the LocalTalk flag binds the modem port to some localtalk bridge software. You could easily bind the ports to tty paths; MIDI is special because it also requires a clock.

Except for an older build (build 142) of Basilisk II on Windows, there is no SCSI support in SS or BII. All disks are presented either as floppies or CDs at the hardware layer. The loopback idea might work, as long as the device is presented correctly on the virtual SCSI stack in SheepShaver. This i...

Tested on my late 2015 running 11.2.1, works fine in windowed and fullscreen. Will test later on El Cap on a non-Metal 2008 and see what happens (info.plist does state min requirements of 10.7).

I was told extended is the preferred format in the post below. But if you say standard will work just as well I will give it a try, I'm worried I will run into problems and won't know it's because the program is on the wrong kind of format. https://www.emaculation.com/forum/viewtopic.php?f=20&t...

In SDL 2.0.12, it was automatically judged in the library. However, SDL 2.0.14 adds a new flag to use Metal when creating a window, which must be specified manually. It seems that it can only be determined whether Metal can be used after the window is created. It's a strange specification... Isn't ...

Quick request - could we have a window title flag for BII and SS? Just something to put in the prefs file or command line flag that would set the window title, at least on macOS. Reason for the request is that I used to hack the binary to replace SheepShaver with the OS version being run, so I could...

Ronald P. Regensburg wrote: ↑Fri Feb 12, 2021 6:20 pm

adespoton wrote: ↑Fri Feb 12, 2021 5:51 pmthere are a few 2009-2011 devices that run on 10.12 but don't support Metal.

I suppose you mean "that run on 10.13". In MacTracker I found some iMacs from before 2012 (so no Metal) that indeed do run 10.13.

Yup; typo on my part.

Maybe using Metal should be the default behaviour on Macs that support it. Edit: Can any Mac running macOS 10.13 (High Sierra) or later be considered to support Metal? Any Mac running macOS 10.14 (Mojave) or later supports Metal; there are a few 2009-2011 devices that run on 10.12 but don't support...

Most likely the drive B tree or extents tree is damaged. Create a new image, boot up from that one, and then use Disk First Aid to try and repair the damaged one.

Someone with hardware that only goes up to Sierra will have to weigh in -- I've got some, but it's running El Capitan, so isn't supported by the build anyway.

The only time I launch into fullscreen is when I'm running a dedicated app like @almeath was mentioning. Usually when using it that way, I want to be able to use my gestures to switch desktops. That said, I rarely go fullscreen, as usually I'm running my configs in 720p windows. I'm only running on ...

If you’d like I can PM you the same code in two source files rather than in-line or I can try to submit on GitHub. Up to you. If you have any improvements, please make a pull request on GitHub. Also, I’d like to find a better spot for the chime to sound, like after main window creation. If you can ...

So you weren't loading a ROM or disk images in the one that "crashed" -- this is expected and documented. I also notice that your unix drive is "/" -- that's a really bad idea in general, and could lead to issues in Sierra onward, especially in Big Sur. I usually set mine to /Use...

That's great! I haven't heard from DogCow in years. I do wonder how they're going to support TLS1.2 on a 128k, since the dedicated chip that usually handles its ciphers is more powerful than a 128k Mac, but I do hope they figure that out. Also getting useful data speeds at 1200bps with no hardware h...

I just realized something that may be messing people up on Windows. On Linux and macOS, line wraps are written using the "\" character. On Windows in cmd.exe, batch file line wraps are written using the "^" character. However, in PowerShell, line wraps are written using the "...

Have you tried changing the screen resolution from the control strip at the bottom of your screen? After that you'd have to change the screen multiplier setting in windowed mode to make it look bigger, or just use the host OS zoom feature.

If I remember correctly, the chime is stored in-line as a SND resource, and is referenced via pointer. Some useful stuff to help patch the right references might be available here: https://github.com/elliotnunn/mac-rom , https://github.com/jpluimers/macrompatcher/ and http://educ.jmu.edu/~jarvislb/u...

The "right" place from a functional perspective would be right after BII patches the ROM and sets it up for loading. In the original, the chime loads after the system self-test, but IIRC, BII skips the self-test because it would fail due to the patching. I suppose it should be possible if ...

Going back to the sound issues, I found another thread (https://www.emaculation.com/forum/viewtopic.php?f=6&t=9134) which says it relates to the ROM version. Indeed, this fixed it for me, changing from the Q900 to the Q650 ROM. So, all good there. The only thing to fix is the startup chime. I s...