[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Making the //c more //e-compatible - really stupid idea
- Subject: Making the //c more //e-compatible - really stupid idea
- From: lyricalnanoha@dosius.ath.cx (Steve Nickolas)
- Date: Tue, 6 Jul 2010 00:27:49 +0000 (UTC)
- Newsgroups: comp.sys.apple2
- Organization: Mac GUI
- User-agent: Mac GUI City Usenet Posting
- Xref: g2news1.google.com comp.sys.apple2:16883
This is a really stupid idea, but I thought it up.
I've noticed ever since the //c came out that some programs weirded out on
the //c and not on the //e. This was the Enhanced //e, for note. One of
them was Copy ][+ 4.3 Bitcopy - so you can see what I mean. (4.4 is fixed)
I've had a few other programs do different things on a //c than a //e too
because of firmware differences.
I started to wonder, if by removing the self-test and possibly the tape
code, moving some code around, the //e monitor and slot firmware can be
modified to run on //c hardware, and if it'll work better than the //c's own
firmware, or at least in comparison to "version 255".
-uso.