You will have another problem with the compiler. The change to OS 9.1 introduced a new Memory Management causing the compiler to stop with an internal error. (advice from macintoshrepository.org)
The Mac
Suppository Repository page as usual only cloned the description (and the whole page) from the corresponding Garden page. In either case, it is wrong, and that was later fixed
in the Garden page. You can compile with Symantec C++ 8.6 under even Mac OS 9.2.2 without any problems. Personally tested successfully.
If there
are issues with the compiler under 9.1+, then they are not general, meaning there must be specific circumstances in order for it to manifest. As it is, so far, this is completely false.
In the Symantec Project Manager (the main IDE), it throws an error message when opening Project->Options... menu item.
"Couldn't complete the last command because a required resource is missing.
Result Code =-192"
Anybody have any ideas?
if it is not yet solved I had a similar problem. On OS 9.1 I needed to activate the Apple Guide system extension.
Yeah, I noticed the problem on my end, as well, under 9.2.2. I have the "Apple Guide" extension in the Extensions folder, but that doesn't address the issue at all.
I can say every other menu option and aspect of the IDE that I could test works 100% with Mac OS 9.2.2, though. Of course, that doesn't mean I covered every possible combination of settings etc., but generally everything worked, such as compiling, live debugging, building etc.. Even the built-in source control, which seems to be based on Apple's "Projector", works. Selecting "Edit > Preferences..." also works completely fine.
So it is odd how nothing but "Project > Options..." is giving us issues...
Could it be that setting is making use of resource decompression, which Apple inexplicably removed in Mac OS 9.1, hence the error?
The error message we get suggests that is possibly the case: it says "a required resource is missing", which suggests it could not find a resource even if it is there, such as if it tries to decompress a resource, the error is then caught in the code and dealt with so that it doesn't crash the program, but then that causes the program to throw the error message we see, incorrectly "thinking" the resource wasn't there.
Could we fix this bug by hacking the "Symantec Project Manager" app so that whatever resource is there compressed, if any, is replaced with a decompressed one? I have no idea on how to go on about that idea, though, even ResEdit is something I'm not (yet) familiar with.