A latency-hating emulator of: the Acorn Electron and Archimedes, Amstrad CPC, Apple II/II+/IIe and early Macintosh, Atari 2600 and ST, ColecoVision, Enterprise 64/128, Commodore Vic-20 and Amiga, MSX 1/2, Oric 1/Atmos, early PC compatibles, Sega Master System, Sinclair ZX80/81 and ZX Spectrum.
Using the latest code in git today, building for SDL on macOS using cmake, starting a Macintosh emulator by specifying a Macintosh disk image on the command line when launching clksignal works, but once it gets to the Finder and mounts the disk on the desktop, it seems to find the same disk image in the external drive and mounts it on the desktop a second time. I immediately exit Clock Signal at this point, assuming that doing anything that might write to the disk images could corrupt them.
The problem does not occur if I use the --new=Macintosh command line flag—either in addition to specifying a disk image on the command line or if I don't specify a disk image on the command line but drag it onto the window later.
This problem also does not occur in the macOS Cocoa interface built using Xcode.
Using the latest code in git today, building for SDL on macOS using cmake, starting a Macintosh emulator by specifying a Macintosh disk image on the command line when launching
clksignalworks, but once it gets to the Finder and mounts the disk on the desktop, it seems to find the same disk image in the external drive and mounts it on the desktop a second time. I immediately exit Clock Signal at this point, assuming that doing anything that might write to the disk images could corrupt them.The problem does not occur if I use the
--new=Macintoshcommand line flag—either in addition to specifying a disk image on the command line or if I don't specify a disk image on the command line but drag it onto the window later.This problem also does not occur in the macOS Cocoa interface built using Xcode.