Qemu-system-m68k macOS to run Mac OS 7-8 /AUX3.x /NetBSD

[mabinogian]

In the Mac guide, the "About disks, the scsi-id and boot order" section says:

"When no Startup Disk has been set with the Startup Disk control panel, the Quadra will search for bootable devices from scsi-id 0 upwards and boot from the 1st bootable device it finds."

But I think it should say "...from scsi-id 6 downwards and boot..." since the highest bootable scsi-id seems to be used, not the lowest.

[Cat_7]

Yes, you are right.
I'll fix it.

Best,
Cat_7

[Cat_7]

I updated the download in the first post in this thread.
The new version of the command file included now defaults to using a shared folder and the tablet driver.

Best,
Cat_7

[emendelson]

Am I right or (more likely) wrong to think that there is NO reason to update my AUXrunner app with the new version?

[Cat_7]

More right than wrong, A/UX cannot use the shared folder and tablet driver. Our guide differs for Mac OS and A/UX installations.
So no need to update.

Best,
Cat_7

[emendelson]

Thank you for saving me some effort!

[Cat_7]

I just created a universal build of Qemu-system-m68k. You can find it here:
https://surfdrive.surf.nl/files/index.p ... H/download
Also see the second post in this thread.

Please note that slirp networking might not work when you have ip v6 enabled on your host. Setting it to link-local-only will allow the network to function.

Let me know how you fare with this build.

Best,
Cat_7

[emendelson]

The download link is broken, alas!

EDIT: But the link in the second post in the thread is NOT broken, so I was able to try it as a drop-in replacement in my AUXRunner app, where it seems to work perfectly. I tested the network by pinging my university site, and the command worked. Is there anything else that I might test??

[Cat_7]

Link is fixed.
You tested on arm64? I just need to know whether it selects the correct architecture on run. Do you notice the increase in speed when not running under Rosetta 2?

How do you set the network for Qemu-system-m68k in the command file, and how is your host configured with respect to IP v6?

Best,
Cat_7

[emendelson]

Sorry for lack of information! I tested on my M2 MacBook Air running Sequoia.

The new version boots to the desktop at almost twice the speed (running the laptop on battery power): 42 seconds for the Rosetta version, 24 seconds for the universal.

It seems to choose the correct architecture. In Activity Monitor, when I sample the process, this is part of the result:

Code: Select all

Analysis of sampling qemu-system-m68k (pid 5980) every 1 millisecond
Process:         qemu-system-m68k [5980]
Path:            /Users/USER/Desktop/AUXrunner.app/Contents/Resources/Files/single/qemu-system-m68k
Load Address:    0x100034000
Identifier:      qemu-system-m68k
Version:         0
Code Type:       ARM64
Platform:        macOS
Parent Process:  bash [5978]

My command file is this:

Code: Select all

cd "$(dirname "$0")"

./single/qemu-system-m68k \
-M q800 \
-m 128 \
-bios Quadra800.rom \
-g 800x600x8 \
-display sdl \
-nic user,model=dp83932,mac=08:00:07:12:34:56,hostfwd=tcp::2121-:21 \
-drive file=./single/pram-aux.img,format=raw,if=mtd \
-device scsi-hd,scsi-id=0,drive=hd0 \
-drive file=root.img,media=disk,format=raw,if=none,id=hd0  \
-device scsi-hd,scsi-id=2,drive=hd1 \
-drive file=opt.img,media=disk,format=raw,if=none,id=hd1 

My app also has your two-monitor version (with "qfb" in the filename). Will there be a universal build of that also? I'm not putting any pressure on you, because I would guess that you intend to do exactly that.

[emendelson]

How do you set the network for Qemu-system-m68k in the command file, and how is your host configured with respect to IP v6?

Forgot to answer this: "Configure IPv6" is set to "automatically" - I never changed it or even knew how to find it.

[Cat_7]

Great! Thanks for the info. It shows that this dual-architecture build does what it is meant to do.

If you have a chance to also check the universal qemu-system-ppc build that would be great, as it is with that build that I experience the network issue.

(and yes, I will make a "qfb" as well.)

Best,
Cat_7

[emendelson]

If you have a chance to also check the universal qemu-system-ppc build that would be great, as it is with that build that I experience the network issue.

I don't have any convenient way to test it, unfortunately. Has anyone made a QEMU equivalent of my all-in-one SheepShaver apps? I experimented with making a BII-equivalent app with the 68K-emulating QEMU at one point, but gave it up when the shared folder didn't handle resource forks.

[Cat_7]

I posted a new universal build of qemu-system-m68k-qfb with qemu framebuffer enhancement in the second post in this thread.

Best,
Cat_7

[emendelson]

I posted a new universal build of qemu-system-m68k-qfb with qemu framebuffer enhancement in the second post in this thread.

Best,
Cat_7

When I replace the files in the "screens" folder in my app with the contents of your new build, and run the app with the multiple-screen option, the two screens briefly appear (both blank), and then I get the error message "qemu-system-m68k-qfb" quit unexpectedly. Possibly I've done something wrong, but I can't guess what.

Also, probably you've explained this already, but what is the function of the new "declrom" file?

[Cat_7]

The declrom is for file sharing function. Qemu can be run without file sharing and without the tablet-style mouse (the last three lines in the command file) (they will not work with A/UX anyway).
I you run the multiple screen option you also need the pram file that came with the "qfb" download (or the one you had earlier)

Also, I saw a message saying that setting 640x480 for both qfb devices would not work?

Best,
Cat_7

[emendelson]

The declrom is for file sharing function. Qemu can be run without file sharing and without the tablet-style mouse (the last three lines in the command file) (they will not work with A/UX anyway).
I you run the multiple screen option you also need the pram file that came with the "qfb" download (or the one you had earlier)

Also, I saw a message saying that setting 640x480 for both qfb devices would not work?

I tried changing the screen dimensions, with no luck. Here is the command file that I use in my app; it worked perfectly with the older version of the qfb variant:

Code: Select all

#!/bin/bash
cd "$(dirname "$0")"

./screens/qemu-system-m68k-qfb \
-M q800,fb=none \
-bios Quadra800.rom \
-device nubus-qfb,width=600,height=480,depth=16 \
-device nubus-qfb,width=600,height=480,depth=16 \
-display sdl \
-nic user,model=dp83932,mac=08:00:07:12:34:56,hostfwd=tcp::2121-:21 \
-drive file=./screens/pram-macos-qfb.img,format=raw,if=mtd \
-device scsi-hd,scsi-id=0,drive=hd0 \
-drive file=root.img,media=disk,format=raw,if=none,id=hd0  \
-device scsi-hd,scsi-id=2,drive=hd1 \
-drive file=opt.img,media=disk,format=raw,if=none,id=hd1 

As you see, I have folders for one-window mode (works perfectly with your new build) and two-window mode, which produces the "quit unexpectedly" message every time. I'll leave this for a while - not worth further effort unless someone else also reports problems.