I'm revisiting Mac emulation on my Amigas inspired by your A-Max review video from a year ago. This is a better thread to post in since it concerns troubleshooting as well.
I dug through my Amiga floppy archives and found an appropriate Amax 2.5x disk (cracked, of course). I never owned any A-Max hardware in the past. The installation went smoothly on my Parceiro-II and Rejuvenator-equipped A1000 (1MB chip, 8MB fast) running Workbench 1.3. I knew booting the Mac system would be a challenge since I recently discovered that I erased my set of A-Max formatted System 7 disks. I also seem to have misplaced my original Apple System 7 disks in HD format. Sigh.
Then something stood out in my "amax" archive directory. It was two files called strt605a.wrp and strt605b.wrp. I only vaguely recalled what this .wrp extension was so I had to look into that further. At first I thought the "a" and "b" meant two full disks but it turned out to be part 1 and 2 of a single disk that ended up being in the A-Max format. The Amiga "unwarp" program was used to write "strt605a" to a blank diskette (the first 40 tracks) then unwarp strt605b to write the remaining part. Not sure what the reason behind this was. Perhaps this was how to retain the A-Max format but still have it in files. I should try making an .adf out of the resulting bootable A-Max System 6.0.5 since .adf was not a format that existed back then but could perhaps handle it today.
Moving on-- A-Max booted up this disk just fine and I was surprised at how responsive the Mac emulation was on a non-accelerated 68000 Amiga. My testing concluded quickly here since I have no other A-Max disks to try and no drive partition I can create. Yes, I too would love an A-Max driver for Parceiro. Alas, even if David was free to investigate this, I am skeptical that it can be done since the storage interface on the Parceiro is not a true SCSI implementation. I forgot how David described it exactly. Since A-Max expects to speak the more common drive interface language, this could be an issue.
My dual boot A3000 is up next for the A-Max install. It will be installed on both sides and a single AMAX drive will be shared. To this end, a small virtual drive file was created and placed on my ZuluSCSI SD card. I also stuck with less than 250MB. At first A-Max did not automatically detect it but then I caught a step I missed in HDToolBox. You gotta "save" any changes that show up...even on other drives you are not presently configuring.
The drive (not partition in this case) was detected by A-Max now. When I booted from my System 605 disk, I was able format the A-Max drive just fine. The contents of the boot floppy was copied over and I was able to boot from it! A-Max is even better with an '030 and fast storage.
But there's a snag-- I have something going on that I believe is related to RAM but it is only affecting the OS 3.2.2 side. You see, I have 4MB on the A3K motherboard and then a 128MB GottaGoFaZt3r RAM in a Zorro slot. Despite lowering the RAM amount, A-Max crashes on launch. I may need more motherboard RAM since it has priority over bus expansions. The Workbench 1.3 side only sees 2mb chip and 4MB fast and doesn't have any problem starting the emulation. Not a big deal at the moment but it could explain some other weirdness I have with regard to the Zorro RAM.
Thanks to the info provided here, I think I have everything I need to create some System 7 disks for A-Max. I will get cracking on that soon.
Also be on the look out for a future post about my ShapeShifter problems. More gory details to amuse and confuse you.