This solution worked up until High Sierra, but Mojave threw new spanners into the works. In reality this is simply the Windows installer in a pre-built wrapper that has all the right settings so users don't have to set anything up. The problems here stem from Mac OS changes, making it ever harder to both provide a ready to run installer, such as the current 'Mac' installer. This will include a new Java-based installer which such run on Mac's/Linux provided the JRE is installed. If you can't use Windows or an older version of Mac OSX as a workaround, you'll just have to wait for the NAM 37 release. Therefore you'd not only need to be able to emulate Windows, but also 32-bit applications as well. Since it's a 32-bit installer, I'd say you've very little chance of running it under Catalina, because my understanding is that 32-bit support has been stripped from the OSX codebase entirely. If there is something the installer needs to do but your emulator can't process, that's likely why you are seeing CTDs. Issues like this are somewhere between a general compatibility issue within your emulation environment (for example, WINE) and it's related settings.

After all, it is a Windows installer that simply does not have these problems when run in the correct environment.

It would be unfair to think of these problems as some sort of fault in the NAM installer.

It wouldn't surprise me if it doesn't work under Catalina either. Like it simply would NOT work. Most of us (myself included) had to run the Windows installer under Wine/Wineskin and select the 'use for Mac install' option (or whatever the wording is). The last Mac NAM installer was notoriously crashy & buggy in Mojave.

Simcity 3000 emulator mac