I assume that the keyboardtype is as defined in Inside Macintosh. For my US-format extended keyboard I am using type 2.

I confirm that it runs on Lion and Mountain Lion. (And as expected, it does not run on Tiger, Leopard or Snow Leopard.)

Yes! This version solves the issue and runs on both my High Sierra and Yosemite machines. Also runs on Mavericks and El Capitan.

Many thanks to you and kanjitalk755!

Thanks, the 2019-02-24 build appears to work fine.

If anybody wants me to run any tests just let me know.

I use windowed mode and hardware cursor on a retina iMac running High Sierra. Just switched from Ronald's 2019-02-20 build to 2019-03-29, and now my cursor is large (looks like scaled up 2x) when inside the SheepShaver window. If I switch to the software cursor the size is correct (but the cursor is ...

Thanks, I just updated to 10.13 and the version you posted seems to be working fine for me so far. I very much appreciate the work you and others have been doing to keep SheepShaver alive!

SheepShaver's PPC emulation entirely omits the twi opcode.

Tiger (10.4).

I have been running it for years and it never crashes, except when I try to print things. MacMoney 4.02.11 and Mac OS 8.6.

Control-Escape is an "emergency quit".

Yea, thats true. I think Kikkoman was looking for a possibility to kill a hanging process, like it is done on real Macs running Classic OS. Agreed, but my comment was intended for yksoft1. I don't think the two of them are talking about the same thing.

Control-Escape is an "emergency quit".

Thanks. As I understand it, that will set quartzok to true with 1.2.10 and earlier and with 1.2.14 [... ] Do you or do I send this to basilisk-devel list for committing to cvs?
That's correct about quartzok.

As for the code, I haven't built or tested it (am away from my home machine). Somebody ...

quartzok = SDL_VERSIONNUM(vp->major, vp->minor, vp->patch) == SDL_VERSIONNUM(1, 2, 10) || SDL_VERSIONNUM(1, 2, 14);
Is this correct code? (It works with 1.2.14)
That would always set quartzok to true. Here is my suggestion: // Quartz driver bug prevents cursor changing in SDL 1.2.11, 1.2.12, and ...

2. Make cursor changing (between hardware en software cursor) available with SDL 1.2.14
Not sure if this is the proper way of doing this, but this is what I did (added one line, marked with +, and edited comment) and it appears to work with SDL 1.2.14:

I have some thoughts on this.

First, this ...

In your .sheepshaver_prefs, if you prefix the pathname of a disk image with an asterisk, it will be mounted as a locked, write-protected disk. For example:

disk */Users/kd/Classic/SheepShaver-2.3/Main.dmg

Did you test this thoroughly?
I must confess I didn't. But no crash so far.
The problems I observed were not crashes; just that the cursor was not always changing when it should. (I seem to vaguely recall that this had something to do with movement around the bottom of the SheepShaver window, but ...

So I tried something else: activate the 'hardware cursor' with SDL 1.2.14, and guess what: it seems to behave correctly.
A new build is available at the same location.

Did you test this thoroughly? With SDL 1.2.11, 1.2.12 and 1.2.13 the hardware cursor approach does not work properly, but the ...

You could try to isolate it to the SDL programs vs. SheepShaver, by building SS Leopard from SDL Tiger, or vice versa. I had been planning to try swapping a particular .o that caught my attention in the profiling output. Finding time to play with this stuff is going to be the hard part.

I'm ...

I tried my own experiment, building from unaltered CVS source code, with sdl 1.2.10 and configuration --enable-sdl-static --enable-sdl-video --enable-sdl-audio --disable-vosf.

Two Intel-only builds were performed, one on Tiger and one on Leopard, both on the same Intel MacBook Pro. Each build used ...

I haven't pulled a source tree in some time, so I'm missing any code changes that have gone in lately. Yet my CPU consumption experience is consistent with what you guys are seeing: my (non-vosf) builds are in the 50% CPU range, and yours are in the 20% range (same machine and SheepShaver ...

I am more interested in the --disable-vosf version. Do we have comparative results for cpu consumption with your build vs. Ronald's build, both with --disable-vosf, running on the same machine with the same SheepShaver configuration?

In some profiling runs that I did many moons ago, 85% of ...

The most likely thing on your list may be the difference in SDL versions, as there could have been performance work done in SDL between 1.2.10 and 1.2.13. Also, the SDL version determines which cursor management approach will be used ("hardware" vs. software) by SheepShaver.

The reason the SDL ...

What differences are there between the two builds that we know of? For example, configuration options and SDL version?

if the configure script can figure out whether VOSF works by running a test program, then why can't it do the same test at runtime? I seem to recall that it does; i.e., if you build with VOSF enabled but at runtime the code determines that it would not perform better that way anyway, it doesn't use ...

The biggest factor affecting SheepShaver CPU usage is the choice of video refresh strategy; for example, vosf vs. non-vosf.