I found a very competent ROM dumper. This particular dumper actually runs within a UNIX environment, which itself runs on classic Mac OS. We tested it out on a TAM and was able to dump the ROM properly.

The good news is that I found someone with a TAM. The bad news is that the ROM would not dump properly - it would dump the 68k portion of the ROM (the first 3 MB of 4 MB), but not the PPC portion (the last MB). The results were as follows: GetROM - didn't work CopyRom - outputted 3MB (68k portion) R...

Very nice. Once the mouse control is fixed in the Windows version of QEMU, I'd like to see if I can access some of the interesting stuff I've dug into. I don't think anyone has seen it before.

If anyone wants to help with the JIT in DingusPPC, we're currently investigating how to do it. So far, it seems like asmjit would be the best solution. However, we'll also need to carefully manage both PowerPC and 68k code, being aware of the context the OS is currently running in. Send a direct mes...

A couple of answers I have. There's a project I'm working on called DingusPPC. We've managed to get OpenFirmware from the Power Mac G3 Beige v3 ROM booting, but the emulator is very much a pre-alpha. SCSI is being worked on, but it's yet to be completed and merged. However, the MMU is emulated. Ther...

We've managed to debug the 68k ROM up to the point it reaches the BootRetry method. If anyone can help debug 68k code, here's what we need clarified: * exception processing (though it mostly has been reversed engineered with the Nanokernel) * emulator initialization code, especially the part that ta...

https://github.com/dingusdev/dingusppc/tree/debug-68k

Quick branch to help us debug 68k startup code in the Old World ROMs. Capstone is required for this, so you will have to pull that first.

If you're using a build based off kanjitalk755's branch, I think I might have an explanation.

There were a couple of floating-point instructions that were not emulated or emulated improperly - fres and frsqrte. These were fixed by jmaebe near the end of 2019.

Good news - We fixed some crash bugs, inserted some basic video implementation (though it still won't display anything yet), and have some keyboard work started. Bad news - To get the keyboard working requires a very timing-specific auto-polling implementation and it's required for emulation to prog...

Make sure you disable illegal opcodes - Seems like you came across a twi opcode.

I do have a 4 MB Gigabit Ethernet ROM, but it doesn't resemble the Old World ROMs much. I'd like to see if anyone can find the page you're mentioning.

While it is possible to make a clean-room implementation, that takes a lot of time and effort to code.

We now have audio playback. We've managed to get the boot-up jingle and crash jingle from the Power Mac G3 Beige ROM to play.

The thing is I can't find the 2400 or 3400 ROM anywhere. I looked in all the available collections and neither of them appeared, hence why I listed those as missing.

If the “Apple Audio Extension” happens to be installed in the Extensions folder, remove it.

The sound preferences seem to be right. As for RR, it's mostly for legality reasons, but there can also be issues with the hard disk images themselves.

While I understand this site does not allow links to ROMs, it's still worth noting for preservation purposes that several Macs don't have ROMs dumped. These include, but are not limited to: * Twentieth Anniversary Macintosh (codename Spartacus) * PowerBook 2400c (codename Comet) * PowerBook 3400c (c...

While it's mostly the G3 instruction set, the 601 does have limited support at the moment (several of the exclusive bit-shifting ops are not yet implemented). We have included a small dummy ADB emulation, which allows us to complete loading a OpenFirmware bytecode image and it starts going into the ...

We improved our debugger significantly, including a disassembler. CPU tests have also been performed, which helped fixed hundreds of small bugs that might not have been noticed otherwise.

Right now, we're slowly approaching the point to where we can reach OpenFirmware. However, we also need a lot more work to be done. Here's just some of the things to complete: VERY HIGH PRIORITY *Flesh out the debugger to include a disassembler, a memory dumper (in progress), more sophisticated logg...

It would be somewhat difficult, but DingusPPC is largely coded like a C program with some C++ bits here and there and encapsulated. We would mostly just stick with C++ for the initial conversion, but use the Rust toolchain to aid us in development.

So, on two different Macs so far, the Power Mac G3 Beige and the Power Mac 6100, we've gotten up to the point where it starts playing the boot chime. That said, we're also considering moving this project from C++11 to Rust. Mainly because Rust is a bit more modern in so many ways (dependency managem...

With bit of a tweak, it now performs at slightly under 200 MHz. The change will be merged soon, along with another commit that will deal with both NuBus and PCI PowerMac memory mapping.

So, the ROMs get a little farther, but it will be some time before it's ready. Right now, at best, the emulator runs slightly faster than a PowerPC 601 at 60 MHz. And that's with an Intel Core i7. Needless to say, I'll need to optimize this some before progressing. Also, dynamic memory mapping will ...

You can modify it by single-clicking on the app you want to modify, going into the File menu, get the program's info, and changing the memory section so that the minimum and preferred sizes are enough to get it running.

More info here.

Error 1 is a bus error in Classic Mac OS. Most likely, it's running out of memory or is trying to access memory it cannot. Try modifying the amount of memory available to those programs and see if that helps.