RE: More detail... Help with copying D64 files to Disk

Anders, 

Thanks tons for the reply and info. 

> http://personalpages.tds.net/~rcarlsen/cbm/c64cdiag.txt

Odd as it is, none of failures seem to describe what mine was doing. It seemed everything worked fine until I ran a program that scrolls the boarders, screen or both with multi colored bars. This is where it would lock. I'm not sure why the boarders scroll with multi colored bars, but I think it when the file is being decompressed. Every once in a while I would get a random character on reset or when a game was loading and it did happen right before the scroll would normally start (I'm comparing it to running the program on an emulator).

The program below, being the non programmer I am, would I just need to type it in and then compile it. I typed in a lot of Compute Gazette programs but it's been a long time ago.  

Thanks again. 


-----Original Message-----
From: owner-cbm-hackers@musoftware.de [mailto:owner-cbm-hackers@musoftware.de] On Behalf Of Anders Carlsson
Sent: Tuesday, November 03, 2009 08:03
To: cbm-hackers@musoftware.de
Subject: Re: More detail... Help with copying D64 files to Disk

Scott wrote:

> Now that I've got a working 64C, what would you recommend changing in the 
> defected 64C. the Processor (6510), PLA or both?

Ray Carlsen writes:

"Unlike the one in the C64, the PLA in the C64C runs cool to the touch. I've 
never seen a bad one. Of course new and old versions are not 
interchangeable. The older 6510 MPU seems to work in the C64C as a sub for 
the 8500. I have tried an 8500 in an old C64 and it worked (diagnostic test 
only), but I don't know how well these chips interchange in actual use. All 
of the 8500 series chips run cooler than the older 6500 series."

http://personalpages.tds.net/~rcarlsen/cbm/c64cdiag.txt

It seems remarkable if the 906114-01 (82S100) PLA in the breadbox C64 very 
often breaks but the 251715-01 (LH5062B, YM3535) PLA in the newer C64C 
almost never breaks.

It should be fairly easy to construct a test program which swaps Basic, 
Kernal and Char ROMs in/out and see exactly what causes the machine to 
crash. This program should be written in machine code, possibly entered as 
DATA statements:

SEI
LDA $01
AND #$FE ; disable Basic ROM
STA $01
INC $D020
LDA #$37 ; default value
STA $01
CLI
RTS

10 DATA 120,165,1,41,254,133,1,238,32,208,169,55,133,1,88,96,-1
20 I=679
30 READ A:IF A>0 THEN POKE I,A:I=I+1:GOTO 30
40 SYS 679

To disable Kernal, I suppose you replace 254 by 253. To switch in Character 
ROM you replace 41,254 by 9,2 (ORA #$02). Please correct me if I made any 
mistake here.

I don't know if there is any need to check the data direction register at 
$0000, would programs often change it?

Good luck!

-- 
Anders Carlsson


       Message was sent through the cbm-hackers mailing list


---
avast! Antivirus: Inbound message clean.
Virus Database (VPS): 091103-1, 11/03/2009
Tested on: 11/3/2009 6:17:10 PM
avast! - copyright (c) 1988-2009 ALWIL Software.
http://www.avast.com





---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 091103-1, 11/03/2009
Tested on: 11/3/2009 7:42:24 PM
avast! - copyright (c) 1988-2009 ALWIL Software.
http://www.avast.com




       Message was sent through the cbm-hackers mailing list