home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!cbnewsi!cbnewsh!att-out!oucsboss!oucsace!tratclif
- From: tratclif@oucsace.cs.ohiou.edu (Tracy Ratcliff)
- Newsgroups: comp.sys.cbm
- Subject: Re: SX-64 chip replacement
- Keywords: 99-44/100% compatible
- Message-ID: <1992Dec28.215045.1417@oucsace.cs.ohiou.edu>
- Date: 28 Dec 92 21:50:45 GMT
- References: <1992Dec28.181415.24282@Princeton.EDU>
- Distribution: na
- Organization: Ohio University CS Dept,. Athens
- Lines: 20
-
- In article <1992Dec28.181415.24282@Princeton.EDU> hswoolve@phoenix.Princeton.EDU (Helen S. Woolverton) writes:
- >I got a RamLink recently, and have run into a _lee-tle_ problem with
- >the proverbial SX-64-is-not-quite-a-C-64 incompatability. Way back when
- >the machine was half its current age, a friend told me of reading about
- >a one-chip replacement that would turn my SX-64 into a "real C-64". I
- >paid little attention at the time, since what I used worked without
- >trouble.
- >
-
- The only thing I can think of that fits this description is the kernal ROM.
- The SX-64 kernal had the routines of the 64 ROM version of the time but in
- a different order (the tape routines were all brought together in one chunk).
-
- Since you're trying to use a RamLink, I would contact CMD. They'll probably
- recommend you buy a JiffyDOS chip, which replaces the kernal.
-
-
- -------------------------------------------------------------------------------
- We must be open-minded, but not so open-minded our brains fall out - anonymous
- -------------------------------------------------------------------------------
-