-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BasiliskII and SheepShaver for macOS freeze during restart #134
Comments
Not reproduced. |
Also macOS Monterey 12.4 and SDL 2.0.22 here. I tried starting and restarting SheepShaver and BasiliskII numerous times, without a Startup.wav file available. I tried with different settings in the prefs files. Nothing I tried made a difference. Starting and then using the emulators works fine each time, but restarting does not. Both SheepShaver and BasiliskII behave inconsistent. In SheepShaver (MacOS 9.0.4) restarting does work occasionally, but mostly the startup process stops when the Finder should load and a forced shutdown is the only way out. At one occasion the Finder loaded only partially, only some files and folders appeared. In BasiliskII (System 7.5.5) I never could make a restart work. Sometimes BasiliskII froze at the point where the Finder should load, sometimes BasiliskII crashed at the point where the Finder should load, and sometimes a system error occurred at that very point in the startup process. See image. |
I do not know if this is of any help: ID=08 Trace Mode Error |
What happens if you remove all HDDs and mount only MacOS installation ISO, and restart? |
With only a MacOS installation CD image, restarting SheepShaver works fine. I have a whole collection of rarely used .sheepvm VMs with different installed System/MacOS versions. Restarting fails with all of those VMs. |
Did a clean MacOS 9 installation. Restarting fails. |
I also tried a clean install of MacOS 9.0.4, and was able to restart without any problems. |
Some observations regarding a Windows build from the latest code: I can restart SheepShaver several times when booted from CD image (9.0.4) in combination with the old world rom. With the new world rom restart fails. Restarting from the same CD image fails when a new hard disk with freshly installed Mac OS 9.0.4 from that CD image is present. Repeatedly booting and restarting from the HD image only (with old world rom) seems to work. When booting and restarting directly after deleting the SheepShaver_nvram.dat the nvram file is not written. It is only written at shut down. |
I spent all day trying. I have dozens of installations, with different System/MacOS versions in both BasiliskII and SheepShaver, some used regularly some used rarely. BasiliskII SheepShaver All failing restarts in both BasiliskII and SheepShaver fail at the very moment the Finder should be loaded. The startup process stops and the emulator freezes, or the emulator crashes, or (in BasiliskII) a system error occurs, or (in SheepShaver) the Finder starts loading and crashes before all icons have appeared. I considered location or content of the shared folder (extfs) as a possible cause, but I could not find any relation with different locations or content. |
In tried the old world rom, but it does not make any difference. |
Reproduced that it freezes when I restart using the New World ROM. Do not restart the emulator, but quit and rerun it instead. |
I will stop trying different configurations to find any consistent behaviour that could point to a possible cause.
|
Improved stability during reboot (except for SheepShaver and New World ROM combinations). |
I made and tried new builds from both BasiliskII and SheepShaver for the new feature where an available Startup.wav file would also play at restart of the emulated machine. When I try the new builds, the startup sound plays alright, but both BasiliskII and SheepShaver freeze during restart at the point where the Finder should appear.
I then tried my previous builds. Again, both BasiliskII (1 August 2021) and SheepShaver (24 January 2022) froze at the same point during restart.
I do not often restart the emulators, I usually shut down and launch the emulator again. But I cannot imagine how I could not have noticed this behaviour before with the previous builds.
Could this be related to changes in macOS Monterey updates? Now on version 12.4.
Edit: This behaviour is both with and without a Startup.wav file present.
The text was updated successfully, but these errors were encountered: