NETOPRHM@NCSUVM.BITNET (Hal Meeks) (09/02/87)
Saw something unusual the other day, and am hoping someone can
clarify it for me.
Is there a known compatability problem with early 128's running
in 64 mode? The one in question is marked '85 on the case. It will
run some 64 stuff just fine, but some things (Print Shop, for example)
just attempt to boot and leave the drive whirring away into limboland.
I verified that the drive is fine, and the software in question boots
fine on a 64, or for that matter on another 128 of later vintage. One
thing that disturbs me is a mention by the owner that one of the games
in question occasionally would boot fine, but has now quit altogether
even though it still boots on another 128 or 64.
Strange......
Please respond.
Hal
daveh@cbmvax.UUCP (Dave Haynie) (09/04/87)
in article <159NETOPRHM@NCSUVM>, NETOPRHM@NCSUVM.BITNET (Hal Meeks) says: > > Saw something unusual the other day, and am hoping someone can > clarify it for me. > Is there a known compatability problem with early 128's running > in 64 mode? No. There are a VERY few early ones that might have trouble with very unusual cartridge port hardware. The internal software, however, hasn't changed on the C64 side, EVER. > The one in question is marked '85 on the case. It will > run some 64 stuff just fine, but some things (Print Shop, for example) > just attempt to boot and leave the drive whirring away into limboland. > I verified that the drive is fine, and the software in question boots > fine on a 64, or for that matter on another 128 of later vintage. One > thing that disturbs me is a mention by the owner that one of the games > in question occasionally would boot fine, but has now quit altogether > even though it still boots on another 128 or 64. If you're really sure that the drive is fine, and that you ALWAYs have the drive in 1541 mode when booting C64 programs, I'd suspect that the C128 in question has something internally wrong with it. There's just nothing that can cause a computer to gradually stop working with a particular program, other than some piece of hardware, maybe a memory chip or custom chip, going bad. Your best bet would be to take this sucker in to a service center, with a full explanation of what's going wrong. Wouldn't hurt to bring in the offending software, either, since the repair shop probably doesn't have it, and given a system there that it runs on, they may quickly determine why it doesn't run on your friend's unit. > Strange...... That be true, fer shur. > Hal -- Dave Haynie Commodore-Amiga Usenet: {ihnp4|caip|rutgers}!cbmvax!daveh "The A2000 Guy" PLINK : D-DAVE H BIX : hazy "God, I wish I was sailing again" -Jimmy Buffett