Yes, I noticed the posts here and the pull request at kanjitalk755/macemu. It works for a specific situation in Windows. Not sure if it will also work for other configurations. No reply yet from kanjitalk755. I do not know where a similar change could be made for the macOS version. Of interest is th...

One would expect BasiliskII and SheepShaver to use memory in a similar way, but I really do not know. I recall reports of the "cannot map RAM" issue only with SheepShaver, usually on Linux or Windows hosts and rarely on OSX/macOS. Restarting the host usually solves the issue. Restarting do...

SheepShaver not only needs a contiguous block of addressable RAM, it will only use specific addresses. If anything occupies part of that, even when it uses only little memory, SheepShaver will not run. The size of the RAM setting cannot be the issue, SheepShaver can run with up to 1024 MB RAM. I am ...

The reported memory error probably points to the cause. The RAM setting cannot be the problem, as it is set to the very low default value (16 MB). The problem could be that SheepShaver is trying to use memory that is already in use by other processes. This is a known problem caused by the way SheepS...

That is the prefs file that SheepShaver normally creates when it is first launched. and not yet configured. The only thing I can imagine is that something is wrong with the rom file. Try:Trash this file, download "newworld86.rom.zip" again from Redundant Robot, unzip it, rename it, and the...

Did you have the new disks initialized at startup and do they appear on the SheepShaver desktop? SheepShaver cannot see disk images as hard disks, it will always see them as (large) floppy disks. Disk Setup cannot see them. (On a real Mac, Disk Setup can only see true hard drives on a SCSI connectio...

Not sure why you created that partition and not sure what you mean with "user profile". Is this on an external drive? As SheepShaver has not run so far, its prefs file will either not be created yet or it will only contain some default entries. Still, maybe you can show us its contents. I ...

There are two possible causes I can think of. 1. Is your ROM file named exactly "Mac OS ROM"? If you renamed the file in the Finder, the file name extension may be hidden and not removed. You can check and correct this in Finder Info panel for the file: Select the file and hit command-I 2....

Strange. It does not happen here. But this is in Sonoma on M1 iMac.

We should probably change the instructions on our wiki page to not refer to Redundant Robot for the OS 9 image anymore. As far as I am aware, we do not refer to Redundant Robot's OS9 image in the instructions on our wiki page. I often advised against using it for a final setup, because it is an inc...

- Is the quadra650.rom file still present in /Users/jimwong/Documents/Emulation/Classic-68k/ ? If not, BasiliskII will not run. - Is the Shrike.dsk a system startup disk? If not, BasiliskII cannot start up. - "ignoresegv false" should be "ignoresegv true" to lower the chance of c...

Without proper setup, BasiliskII will not run.
Did you have a working BasiliskII setup on this iMac and upgraded to the new build? If not, did you follow our setup guide: https://www.emaculation.com/doku.php/ba ... _osx_setup

emendelson replied while I was composing my reply. I will post it anyway. I am not sure if your remarks are about this "Mac OS 9" offering or about Mac OS 9 itself. Extensions are loaded during startup, you can see some marching along at the bottom of the screen at startup. That is normal ...

that-ben wrote: ↑Sun Feb 04, 2024 4:04 pmDo you have any idea about the missing .sheepvm alias icon in the Applications folder in the dock?

I do not know why the icon would not show in the Dock. Try deleting the alias and create a new one.

It seems you have SheepShaver.app installed inside the .sheepvm package. If you created several .sheepvm packages and installed SheepShaver.app in each of them, the Finder will loose track of which SheepShaver.app to use. That's exactly what I have, yes. And happy new year a little late to you too!...

I am not sure if the folder and its contents suffices, but you cannot run an installer (or any application) when it is still on the "Unix" volume (shared folder) nor when it is dragged from "Unix' onto the Desktop. The folder must first be copied to another mounted volume, like your v...

Ah! I remember now. Forgot all about it. Maybe because I am not a gamer.

Here is the discussion on kanjitalk755/macemu. kanjitalk755 suggests to first try delay 1000 to slow down emulation.

https://github.com/kanjitalk755/macemu/issues/117

Navigating to a certain location is done with the cd command. Type cd then a space and then the path to the location (in this case the Qemu folder).

But what could be the practical use, if any? Apparently delay = 0 is the default. When deleted from an existing prefs file, BasiliskII will not write it again.

Very observant!

I do not know what it is. BasiliskII only writes that line when launched with no pre-existent prefs file.
I cannot find it in the documentation. It may be a remnant in the source of an older BasiliskII version and not functional anymore. I will ask the developer.

You mean the 'advanced' feature mentioned in the wiki setup guide? • Shorten the sound buffer (17 March 2021 and later builds) Shortening the the length of the sound buffer can prevent delayed and choppy sound in some applications but will increase CPU use. The default setting is sound_buffer 0 Sett...

Didn't we drift off-topic? This topic is about BasiliskII while the latest posts are about QEMU screamer.

Indeed I did not. In fact, I rarely answer questions about QEMU.

Do you use the latest GUI version 0.22? When it saves changed settings, it will move other items it finds between its own settings to the end of the prefs file. Manually added settings will thus be preserved. This feature was already present in version 0.20. BasiliskII itself will add 'advanced' set...

Which GUI version do you use? The latest version 0.22 should work fine for creating new disk images. It can be downloaded from the first post in this topic. (MacOS versions that can be used in BasiliskII cannot read APFS and, with the exception of MacOS 8.1, not even HFS+. But when you start up Basi...