adespoton wrote:How about:

Code: Select all

cpuclock 200

That did not seem to do anything. What does this specifically do, and what number ranges could I try?

When SheepShaver freezes and pinwheels, this is all I see in Activity Monitor:

I'm talking about this –> https://emaculation.com/doku.php/sheepshaver_mac_os_x_setup#self-contained_virtual_machines I get the problem with both my own virtual machines, and also emendelson's wrapper. I decided to test with the wrapper because I wanted to make sure I did not have a problem with my...

So what makes it happen on some Macs and not on other Macs? And what makes it happen on all three of your (almeath) Macs? Perplexing. :???: I have posted an issue in kanjitalk755's Github repository. At least I am not the only one out there experiencing this issue. If we can gather more feedback fr...

I no longer think it is related specifically to the type of graphics card. This is based on the testing I conducted on my 2013 and 2019 iMacs, one being Nvidia and the other AMD. Your tests now show it occurs on Intel graphics as well. It is also not tied to whether it is a desktop or laptop, as it ...

On my 2019 iMac I see the following, repeating frequently until I force quit SheepShaver: 1456/0x193a87: psynch_cvwait(0x7FE617C10AC8, 0x3640100036500, 0x36400) = 0 0 1456/0x193a55: workq_kernreturn(0x20, 0x0, 0x1) = 0 0 1456/0x193a54: workq_kernreturn(0x40, 0x70000D63AB80, 0x1) = 0 Err#-2 While thi...

Yes, it is very strange, because when it happened on my older iMac I just assumed it was bugs introduced by Apple in their Nvidia graphics card drivers. It is well known that Apple does not like Nvidia and has gone out of their way to ensure their cards are not properly supported anymore. However, I...

So I tried building from the kanjitalk755 branch with SDL 2.0.7 through 2.0.10, but none of these fixed the problem. 2.0.5 is too old and fails to build, as does the mercurial 2.0.11 dev build of SDL2. So I am back to square one at this stage. :???: I can launch in fullscreen mode perhaps 50% of the...

Note that since July 2018 builds by emendelson and by me are from github.com/kanjitalk755/macemu not from github.com/cebix/macemu . Yes, I was aware of that, thanks for confirming. As I mentioned in my edited post above, I do not know if using a cutting edge dev build of SDL2 could help, but I will...

Thanks for the newest build. I wish I could say it fixed the problem, but unfortunately the black screen freeze up is still happening, in both Mojave and Catalina (Catalina being freshly installed from scratch just yesterday). As previously mentioned, my files and configs are fine, but to remove all...

I should add, when the freeze up occurs, there is absolutely nothing showing up in the console logs. It is as if the process is not running at all. I only see the resulting console log entry when I force quit SheepShaver.

Unfortunately, I am getting the same results in Catalina. I am wondering if this is an issue with updated video card drivers in Mojave 10.14.5 and up. I am otherwise at a loss to understand why the issue would only manifest itself in later releases of Mojave, and seemingly only on certain iMac model...

Yes, I do not think it would affect all iMacs, but clearly it affects some.

At this stage I will park the issue until I upgrade to the final release of Catalina.

I tried turning of all Mission Control options and rebooting, but that unfortunately had no effect. Just to reinforce the point that my system is not to blame, I formatted an external SSD drive and plugged it into my 2019 iMac 5k. I then installed Mojave 10.14.5, and as soon as it booted up I immedi...

When launching in windowed mode, switching to (and from) full screen with control-return still works. This really has me completely and utterly stumped. I have been able to reproduce the behavior on my 5k iMac (2019 Core i9), another 5k iMac (2015 Core i5), and my old 2013 iMac with 2560x1440 resolu...

I am using the latest build of SheepShaver (September 2019) in the latest version of Mojave 10.14.6, on a 27 inch 2019 iMac Core i9. It is a fresh install of Mojave and SheepShaver is running in a fresh admin account to rule out any system issues. SheepShaver will run fine in any windowed mode, but ...

I have tested SheepShaver in the first public beta of macOS 10.15 Catalina.

I am happy to report that it runs fine with no apparent issues.

I also tested Warcraft II. When I launch the game, I go to the advanced tab under Startup Options and next to "CD Audio Source" the menu has "none" selected and there are no other options. When the game starts, there is no background music. However, when I go to the CD Audio Play...

I have tested Decent II. When I start the game I can get the CD music working in the main menu. I have swapped between MIDI and redbook audio and the difference is obvious. However, when the introduction movie for the first level finishes, the game crashes with "Error locking sound 76". I ...

I will definitely do some testing and report back.

That is awesome news, thanks for revisiting this issue and making such quick progress.

Are there any current work-arounds to support mixed mode CD games with Red Book audio tracks? (encoded in BIN/CUE format)

I am thinking specifically of the Descent and Alone in the Dark games. I have wanted to get these working for years.

Could this have something to do with security patches for predictive code execution in 10.14.5, and the patches affecting different CPUs in different ways? That had crossed my mind. It makes sense considering the issue only emerged after the update, and also the fact that it works for me with fresh...

I tried removing all three of integer, nearest and hard cursor. Unfortunately, it still freezes on a black screen after 4 to 7 launches. When it freezes my CPU usage spikes to 300%. Does SheepShaver rely on anything external like SDL? I am using the latest stable version, 2.09. I also tried compilin...

I can't reproduce this on my 10.14.5 machine, so it's very puzzling. SheepShaver starts up in full-screen mode reliably. I've tried it a dozen times or more. This would suggest it is something Apple has done to Mojave that only affects certain systems. My clean install testing in Mojave and High Si...

To be honest, the problem is bothering me more because I cannot work out what is causing it, rather than the actual effect of it on my regular use of SheepShaver. I do not tend to quit and relaunch SheepShaver at short intervals unless I am configuring new VMs or trouble-shooting software. It looks ...