gryphel
- Karma
- 13
- Created
- September 14, 2010 (15y ago)
- Submissions
- 0
The goal of the Gryphel Project is to help preserve software made for early Macintosh computers, the computers that Apple sold from 1984 to 1996 based upon Motorola’s 680x0 microprocessors.
website: http://www.gryphel.com/
The current main public key used by the Gryphel Project is:
----- BEGIN GRY PUBLIC KEY -----
Gry+PKAIAAA/hReeyoqMWvvoh0VY19erGoYgiW9znPX7Xkw6AQFECPyMdMv5+hEX
1z3GfTo/04FXiXVBy+yZhV0Ibs1KtuHVh4iGuU4LiiJTE+00w59V4qFZ3DSidtqe
NzlTUsMYleL/8h3mjXpJClrozRSy6TZzPH2H2GPugWfclXi3eJfxnK8RAQABuy+Z
------ END GRY PUBLIC KEY ------
The Mini vMac download page (https://www.gryphel.com/c/minivmac/dnld_std.html) includes binaries for Macintosh, Windows, Linux, and other platforms. As recently noted in the build documentation, compiling it yourself is…
If anyone is interested, I ported this source code to compile in MPW Pascal. The modified source and binary are available from: http://www.gryphel.com/c/sw/general/macpaint/index.html
Yes exactly, the problem is non determinism. But I think it should be possible to have deterministic execution while still keeping compatibility with existing software, by replacing the real time with a "fake" time that…
I'm not seeing the issue with a long running process. If the fake time is regularly synced to real time, it should not matter how long the process runs. If passing data involves frequent switches between processes,…
The fake time can be synced to real time at the beginning of the time slice of a process. So the process never sees the real time, but the fake time is fairly close to it.
Rather than changing OoOE, wouldn't it be much simpler to prevent unprivileged processes from seeing the real time? For maximum compatibility with existing software, a CPU could provide fake time, that on average passes…
It should be able to run Mac OS software using an emulator, similar to a previous project that used a Raspberry Pi: http://retromaccast.ning.com/profiles/blogs/honey-i-shrunk-t...…