Re: More detail... Help with copying D64 files to Disk - compare file sizes

From: B Degnan <>
Date: Fri, 23 Oct 2009 08:34:42 -0400
Message-ID: <>
Peter Rittwage wrote:
> OK, it sounds like your C64 is defective to me.  There must be some issue with
> the PLA or the IO port ($00/$01) on the 6510 so it crashes when it changes
> memory configurations.  Someone else had this problem recently where their C64
> would run some programs, but anything that changed the RAM config port would
> crash.  Unfortunately, you'll need another C64 to troubleshoot that completely.
More thoughts.  Before you get another C64, did you run a directory of 
the disk to see if the file sizes matche the file sizes in an emulator 
or original directory?  Someone here can build an image from the same 
D64 you're using (I can do this if you post someplace) to conclusively 
make sure that the D64 you're trying to use is OK for a *stock* C64 
system.   I have a lot of D64s that are tested and extractable on my web 
site if you need some test programs 
from another source.

Here is a D64 that I have tested and is both NTSC and PAL compatible 
that you can use for testing the file sizes before and after.
You can use the D64 editor (also found on my web site) to check the 
before and after blocks.
(side note) If you're interested in using the programs on the disk only 
cbm-wilmington.prg and golden13.prg are final versions, this was a dev 
disk I used for testing, the rest are dev copies.

My point is that there are two variables.  The process to copy the files 
and the computer itself.  I am not 100% convinced that your copy process 
is working correctly.  If as I understand you can run original disk's 
programs on you c64 without issue, why only the D64's your creating have 
problems unless it was the process to make the copy?

If you already did this testing sorry I missed that point, just trying 
to help.  :-)


       Message was sent through the cbm-hackers mailing list
Received on 2009-10-23 13:00:21

Archive generated by hypermail 2.2.0.