Tetris Max 2.9.1 and Macintosh System 6.0.8 Bugs
bigmessowires.com
bigmessowires.com
The old Inside Macintosh volumes are sometimes difficult to follow. New features got added to newer system software versions, and new features got added to newer ROM versions, and if you want to support older Macs, then you sometimes have to search through the volumes until you find when a particular feature was introduced. (The original Inside Macintosh volumes are organized in chronological order, corresponding to major ROM or system software updates.) If you just look at the description of one of the functions in the OS or toolbox, there’s no mention of when it was introduced.
I also discovered that despite my efforts to make a program compatible with the Mac 128K and 512K, my programs won’t run on those systems. The 128K and 512K have the very first ROM version, with the 64K ROMs, and I suspect that the application startup code which ships with CodeWarrior checks for a 64K ROM and aborts the program. So even if I’m careful to only use functions that are available in the 64K ROM, my program won’t run on a 64K ROM unless I use a different toolchain or rewrite the startup code.
If it doesn’t get called, disassemble the startup code. It can’t be long.
I would use a version of ResEdit that has a built-in disassembler (advantage: you won’t have to run that on a 512k Mac, but can use a beefier one or an emulator)
You also may want to use the earliest version of CodeWarrior you can find, as support for System 6 may have stopped at some time.
Some of the other difficulties—no MaxApplZone, the segment manager behaves differently, and if you really want Mac 128K support, you have to copy to an MFS formatted disk. Some versions of the OS ship with broken MFS implementations, presumably because nobody cared whether it worked. I suspect that the segment manager behavior is a particularly thorny issue because it affects the location of code segments in memory, and you have to be careful when you only have 128K.
But yeah, Executor was pretty awesome. Used to use it to make stacks in HyperCard on my DOS PC.
* Sound only works under the SDL1 build - but getting it to work requires passing in the --nosound switch.
* Crashes far more than the original did. For now, the original binary is superiour.