GSOC qemu Boot Mac OS >= 8.5 on PowerPC system

[kataetheweirdo]

Just so you know, os922_uni.iso is the OS 9.2.2 bootable image posted in the goodies section by gtxaspec, so yeah there's something odd going on with my end. I can assure you I tried this with os92_test.iso (the 9.2.1 bootable image) too and that didn't work either. Here's what I'm typing in now:

<quote>
qemu-system-ppc -bios openbios-ppc -boot d -drive file=os92_test.iso,index=0,media=cdrom -M mac99 -m 256 -prom-env 'auto-boot?=true' -g 800x600x32 -cpu G3 -net none
</quote>

It crashes in the same spot (illegal instruction error bomb screen).

I'm getting the build from here. (It's qemu-w32-setup-20151115.exe I'm using.) I tried out the 64-bit Windows version (also from weilnetz), but I get the same result there too.

[adespoton]

Code: Select all

./qemu-system-ppc -bios ~/MacOS/qemu_master/openbios-qemu.elf \
 -boot d -drive file=~/MacOS/OS\ Images/os922_uni.iso,index=0,media=cdrom  \
 -drive file=~/MacOS/QEMU\ HD\ Images/test.raw,format=raw,index=1,media=disk \
 -drive file=~/MacOS/OS\ Images/macos-922-uni.iso,index=2,media=cdrom  \
 -M mac99 -m 256 -prom-env 'auto-boot?=true' -g 1024x768x32 -cpu G3 -net none

This was the recommended command line. At a glance, I see you're using openbios-ppc instead of openbios-qemu.elf. Did you rename it? Also, it might be worth trying -g 1024x768x32; it's possible that qemu isn't handling other screen geometries right now (can anyone confirm/deny?).

[kataetheweirdo]

I'm just using this version of OpenBIOS and placing it in my QEMU folder. I have renamed it to openbios-qemu.elf just now, but I doubt that made much of a difference.

It looks something like this now...
qemu-system-ppc -bios openbios-qemu.elf -boot d -drive file=os92_test.iso,index=0,media=cdrom -M mac99 -m 256 -prom-env 'auto-boot?=true' -g 1024x768x32 -cpu G3 -net none

All of this is in the same folder as QEMU, which itself is in Program Files (I should note I'm using Windows 7 64-bit). Needless to say, it still did not boot up. I doubt the resolution made much of a difference (aside from slowing the emulation down).

[CharlesS]

I get the same crash you get with your command line. Changing two things fixes it:

• -cdrom os9_test.iso instead of -drive file=etc...

• -m 512 instead of -m 256.

Not sure why this makes a difference, but it seems that it does.

[kataetheweirdo]

Per CharlesS's suggestion, here's what I typed in...

Code: Select all

qemu-system-ppc -bios openbios-ppc -boot d -cdrom os92_test.iso -M mac99 -m 512 -prom-env 'auto-boot?=true' -g 640x480x32 -cpu G3 -net none

It's no longer crashing with the illegal instruction dialog box, but it is beach-balling for a while, then turning my cursor into a bomb at the same place it usually crashes with the error dialog. The result is the same regardless of the screen resolution set.

I don't have much insight, since the QEMU monitor doesn't appear to be making the log needed to see the instructions that it's executing. It's also annoying that the default QEMU monitor is stuck at rendering at 640x400, just centering in the middle of the screen. I'll be viewing this info through the command line prompt from now (adding "-monitor stdio" (w/o quotes)).

[adespoton]

Hmm... I thought the lowest resolution for OS 9 was 800x600?

[kataetheweirdo]

Nope. It depends entirely on the system setup, particularly with the graphics card. On my old iMac G3, I could choose a resolution as low as 640*480 (with 8-bit colo(u)r too). This was with an ATI Rage 128.

I've tried 640*480, 800*600 and 1024*768 in QEMU, but the resolution doesn't affect how Mac OS 9.2.x runs.

[Cat_7]

Hi,

This is the first time I get a crash report when Qemu hangs while booting from a hd image with a quicksilver system folder just when the progress bar starts advancing:

qemu: fatal: Trying to execute code outside RAM or ROM at 0xff000000

NIP ff000000 LR 009c5550 CTR ff000000 XER 20000100 CPU#0
MSR 0000d032 HID0 00810000 HF 00004000 idx 0
TB 00000000 1016821000 DECR 00079535
GPR00 00000000ff000000 000000000bb8c800 0000000040c10000 0000000000000000
GPR04 0000000000000000 0000000000000000 0000000000384000 000000000000004c
GPR08 000000000bb8c750 000000006806de08 00000000ffc10000 0000000079000000
GPR12 0000000000000000 000000000092e660 0000000000004d50 000000000bb9578e
GPR16 0000000000004d50 000000000092e660 000000000bb8d392 000000000bb9a600
GPR20 0000000000000000 000000000bb9a590 000000000bb9a800 0000000000000001
GPR24 0000000000000001 0000000000000000 0000000080013000 0000000000000000
GPR28 0000000000000001 0000000000000000 0000000000000001 0000000000935580
CR 4a000448 [ G L - - - G G L ] RES ffffffff
FPR00 0000000082004000 0000000000000000 0000000000000000 0031e4fa00010000
FPR04 41ce51ce13000000 bfd549b141dea8e2 bf880033ba736cfd 3fefffd039962f40
FPR08 3faaf497f23bd4ec 4230000000000000 0000000082004000 4330000017d6dc13
FPR12 3f847b718aeb3db1 ffffffffff64bf4a 0000000000000000 0000000000000000
FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR 82004000
SRR0 ff000000 SRR1 4000d032 PVR 00080301 VRSAVE 00000000
SPRG0 0fbfe000 SPRG1 0bb8c800 SPRG2 009c5550 SPRG3 0fbfe420
SPRG4 00000000 SPRG5 00000000 SPRG6 00000000 SPRG7 00000000
SDR1 0fc0001f DAR 0f2b7000 DSISR 42000000
Abort trap: 6

OSX reports:
Crashed Thread: 5

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
abort() called

Thread 5 Crashed:
0 libsystem_kernel.dylib 0x00007fff92bea286 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff8e86e9b3 abort + 129
2 qemu-system-ppc 0x00000001058d5fed cpu_abort + 381
3 qemu-system-ppc 0x000000010592e832 get_page_addr_code + 386
4 qemu-system-ppc 0x00000001058dec6e cpu_ppc_exec + 1358
5 qemu-system-ppc 0x0000000105917271 qemu_tcg_cpu_thread_fn + 593
6 libsystem_pthread.dylib 0x00007fff85c0505a _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff85c04fd7 _pthread_start + 176
8 libsystem_pthread.dylib 0x00007fff85c023ed thread_start + 13

Best,
Cat_7

[rscaboyke]

I've been a freak regarding emulating software for years !!! basilisk, sheep, .... been in contact those days with gwenole himself regarding opcode-erros regarding framemaker issues in sheep !!! but now all this new Quemu direction !!! could just someone please give a step-by-step setup to try it on OSX el capitan !!! Is there already a all-in-one binary to be downloaded ? Because in terminal that building stuff needs dependencies and dependencies and dependencies and pffffff just want a quemu binary application runner !!

[adespoton]

At this point, if you need an all-in-one build to get you going, you probably shouldn't be attempting it yet; the emulation isn't complete yet -- it boots, but isn't functional. And we still don't know exactly WHY it boots and the other variants don't -- so at this point it's at a pre-alpha stage with testers who can search for potential fixes or specific fail points running it.

Once it's stable, it'll end up in the homebrew cask. That said, the QEMU part has been checked into the stable branch now, so assuming the OpenBIOS mod gets checked into the stable branch soon, it should be approaching the point where it "just loads". That said, there's no sound, no network, can't boot with any extensions or hardware-dependent scripts, and it appears to only boot the one OS variant so far, and only as far as the Finder.

[that-ben]

3D games were still pretty nascent during the OS 9 era, anyway; I'd think that other than the Pangaea games, there wouldn't be much that wouldn't either have an OS X port or be runnable via a Windows emulator or something.

There are many more titles than just Nanosaur and Bugdom that require graphics acceleration to run. Just to name a few: Dirt Bike 3D, Monkey Shines, Hexen II, Mech Warrior 2 RAVE, Oxyd, Short Circuit, Star Wars Episode I Racer, Tanaka... etc...

Hmm... I thought the lowest resolution for OS 9 was 800x600?

No, the lowest native resolution on Mac OS 9 is 640x480

[adespoton]

3D games were still pretty nascent during the OS 9 era, anyway; I'd think that other than the Pangaea games, there wouldn't be much that wouldn't either have an OS X port or be runnable via a Windows emulator or something.

There are many more titles than just Nanosaur and Bugdom that require graphics acceleration to run. Just to name a few: Dirt Bike 3D, Monkey Shines, Hexen II, Mech Warrior 2 RAVE, Oxyd, Short Circuit, Star Wars Episode I Racer, Tanaka... etc...

Hmm... I thought the lowest resolution for OS 9 was 800x600?

No, the lowest native resolution on Mac OS 9 is 640x480

Are you thinking of Oxyd Extreme? I was playing Oxyd on System 7.5.3 back in the day.

And yeah; lowest resolution was 640x480.

[CharlesS]

There are many more titles than just Nanosaur and Bugdom that require graphics acceleration to run. Just to name a few: Dirt Bike 3D

Don't know this one, so I'll grant the point.

Monkey Shines, Hexen II, Mech Warrior 2 RAVE

These all exist in DOS and/or Windows versions.

Oxyd

No way did Oxyd require graphics acceleration. I think I managed to even get it to run on a Mac Plus back in the day. That game ran on anything.

Short Circuit

Don't know this one either. This is what turns up on Macintosh Garden; it doesn't look like it would require 3D acceleration. I also found this, but as it's a Commodore 64 game from the 80s, it's even less likely to need accelerated graphics.

Star Wars Episode I Racer

Available for Windows, as well as several consoles.

Tanaka

Information is hard to find on this one, but there appear to be references to a Windows version.

Hmm... I thought the lowest resolution for OS 9 was 800x600?

No, the lowest native resolution on Mac OS 9 is 640x480[/quote]
OS X 10.0 is the one that bumped the minimum to 800x600 in the official system requirements.I think that OS 9 could probably go all the way down to 512x384 if you connected a small enough screen to it. I don't have the hardware to test that anymore, though, so don't quote me on that.

[gtxaspec]

This is a zip containing qemu-ppc, and a 2gb disk image file with macos 9.2.2 installed. The system folder was modified to allow it to boot from an unlocked HFS volume. This image has lots of extensions and control panels included and enabled. Once you download qemu_easy.zip, extract it, and run qemu_os9.command (this is just a batch file with arguments)

qemu will now load and boot from the disk image to OS9 desktop. The disk image included here is read/write enabled. I have only tried this on OS10.11, your success may vary. MacsBug is included in the root directory, but is not enabled.


http://bebop.gtxent.com/qemu_easy.zip

[DANADAX]

How did you get all that stuff to work? I ask because I thought they were still trying to fix a lot of things.

Anyway, I have OS 10.11, so tomorrow I'll test out the download you've posted.

[adespoton]

Excellent... now if I get time, I'm going to try to convert this into a Classic environment...

[edit]
hmm... running the script gives me:


I wonder if that has something to do with the NVRAM?

[edit 2]
That might be it... second run with no modifications gave:

[gtxaspec]

still some random issues booting, but progress nonetheless.

One of the issues of using the System file from the installer CD, some of the control panels and INITs will refuse to load, the Control Strip is one that comes to mind.

read about progress from the Qemu people here: http://lists.nongnu.org/archive/html/qe ... 05364.html

[24bit]

Thanks for sharing the "easy" package!
Seems it aint easy enough for me, as I got this:

Last login: Wed Nov 25 19:40:49 on ttys000
iMac:~ macpro780$ /Users/macpro780/Desktop/_qemu_easy/qemu_os9.command ; exit;
dyld: Library not loaded: /usr/local/opt/pixman/lib/libpixman-1.0.dylib
Referenced from: /Users/macpro780/Desktop/_qemu_easy/./qemu-system-ppc
Reason: image not found
/Users/macpro780/Desktop/_qemu_easy/qemu_os9.command: line 3: 798 Trace/BPT trap: 5 ./qemu-system-ppc -bios ./openbios-qemu.elf -boot c -drive file=./test.raw,format=raw,index=0,media=disk -M mac99 -m 256 -prom-env 'auto-boot?=true' -g 1024x768x32 -cpu G4 -net none
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

Sure enough I´m missing some basic steps.
Could you give me a link to the missing library please, if that would be all?

[adespoton]

Thanks for the thread link. If I get some more spare time, I'll dig into my memory and see if I can dig up some old docs on those modules. I seem to recall a TidBITS discussion when the module format was introduced (was that 7.6?).

[djblastyfone]

Thanks for sharing the "easy" package!
Seems it aint easy enough for me, as I got this:

Last login: Wed Nov 25 19:40:49 on ttys000
iMac:~ macpro780$ /Users/macpro780/Desktop/_qemu_easy/qemu_os9.command ; exit;
dyld: Library not loaded: /usr/local/opt/pixman/lib/libpixman-1.0.dylib
Referenced from: /Users/macpro780/Desktop/_qemu_easy/./qemu-system-ppc
Reason: image not found
/Users/macpro780/Desktop/_qemu_easy/qemu_os9.command: line 3: 798 Trace/BPT trap: 5 ./qemu-system-ppc -bios ./openbios-qemu.elf -boot c -drive file=./test.raw,format=raw,index=0,media=disk -M mac99 -m 256 -prom-env 'auto-boot?=true' -g 1024x768x32 -cpu G4 -net none
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

Sure enough I´m missing some basic steps.
Could you give me a link to the missing library please, if that would be all?

You can install the required libraries using homebrew. Just type

Code: Select all

brew update && brew install pixman glib

and you should be set!

Experienced the same crash on first launch and OTUtilityLib errors when opening System Profiler or Graphing Calculator as adespotson, but great progress nonetheless! Nice to finally see steady progress being made on OS 9 emulation .

[24bit]

Thanks for caring!
At least I may watch the magic too now. Too bad I´m lacking the knowledge to help to get things rolling.

[that-ben]

There are many more titles than just Nanosaur and Bugdom that require graphics acceleration to run. Just to name a few: Dirt Bike 3D

These all exist in DOS and/or Windows versions.

Hi Charles, about anything you replied having a DOS or Windows port, that's not the point. 99% of games had a DOS/Windows port. This mentality renders the whole Mac emulation problem pointless/useless in the first place. It's like saying: Why make so much effort in developping this emulator when Goodwill sells iMacs in working order that can already run Mac OS 9.2.2 for 20$... it's not the point.

No way did Oxyd require graphics acceleration. I think I managed to even get it to run on a Mac Plus back in the day. That game ran on anything.

[...] it doesn't look like it would require 3D acceleration

About the acceleration: I never mentioned ANYTHING about *3D* acceleration, I only mentioned graphics acceleration and I swear all the titles listed above don't run on SheepShaver. They do work on the *same* (copy/paste) Mac OS 9 folder booted on a real G3 iMac tough. Even Oxyd does NOT run on SheepShaver

Are you thinking of Oxyd Extreme? I was playing Oxyd on System 7.5.3 back in the day.

I was refering to "Oxyd" from 1996. The Mac OS version has nothing to do with hardware acceleration so of course it can run on Mac OS 7 and up, just not on SheepShaver...

[CharlesS]

There are many more titles than just Nanosaur and Bugdom that require graphics acceleration to run. Just to name a few: Dirt Bike 3D

These all exist in DOS and/or Windows versions.

Hi Charles, about anything you replied having a DOS or Windows port, that's not the point. 99% of games had a DOS/Windows port. This mentality renders the whole Mac emulation problem pointless/useless in the first place. It's like saying: Why make so much effort in developping this emulator when Goodwill sells iMacs in working order that can already run Mac OS 9.2.2 for 20$... it's not the point.

There are quite a few old Mac games that have no DOS or Windows equivalents (Glider Pro, the Marathon series, and a whole bunch of shareware games come to mind). There are also quite a lot of games from the pre-Windows 95 era in which the Mac version had vastly improved graphics and/or sound due to the Mac's greater graphical abilities at the time (Prince of Persia series, most of what MacPlay ported). This is the stuff that you can only run in a Mac emulator.

I'm not saying that graphics acceleration should never be supported, just that it's certainly a lower priority than more basic needs like sound and networking.

No way did Oxyd require graphics acceleration. I think I managed to even get it to run on a Mac Plus back in the day. That game ran on anything.

[...] it doesn't look like it would require 3D acceleration

About the acceleration: I never mentioned ANYTHING about *3D* acceleration, I only mentioned graphics acceleration and I swear all the titles listed above don't run on SheepShaver. They do work on the *same* (copy/paste) Mac OS 9 folder booted on a real G3 iMac tough. Even Oxyd does NOT run on SheepShaver

Oxyd does run in SheepShaver:



It's just almost impossible to play due to SheepShaver's janky mouse support. At any rate, the issue is not graphics acceleration (it runs on a Mac Plus, which definitely does not have any accelerated graphics).

[Cat_7]

This is a zip containing qemu-ppc, and a 2gb disk image file with macos 9.2.2 installed. The system folder was modified to allow it to boot from an unlocked HFS volume. This image has lots of extensions and control panels included and enabled. Once you download qemu_easy.zip, extract it, and run qemu_os9.command (this is just a batch file with arguments)

Hi,

This works like a treat, both on OSX and the latest Windows Qemu build. Funny that there are less error messages when starting with the G4 CPU.
I noticed there is no longer a need to provide the -net none parameter. But as the Open Transport extensions are missing from the hard disk installation of 9.2, experiments with networking are not yet possible. I tried installing them from the CD image, but the installer still crashes as before.

How did you install the system on the HD?

Best,
Cat_7

[gtxaspec]

I used the System file from the os9.iso installation image.

On most if not all MacOS installation discs, you will find if you copy the System Suitcase to a hard disk, MacOS refuses to boot, throwing an error along the lines the system was not designed to work on anything other than the original install media. These special System Suitcases from installer disks include a special resource named "xboot" with a special subroutine that checks whether the boot media is either read/write or read only. It will not boot on read/write media. Deleting the resource removes the check and allows MacOS to continue to boot.

I removed the resource in the suitcase and copied the System Suitcase along with the System Folder to the disk image and it booted wonderfully. I also tweaked the index of the image file, setting the disk to index 0.

Also, try disabling serial and parallel in qemu, and try booting MacOS. I believe the issue with open transport lies in the Serial interface subsystem and not networking. If anyone knows how to edit the Open Transport libraries to disable the serial interface subsystem please chime in.

I will have time to do additional testing later this week. I hope I will have more progress soon.

regards,
alfonso