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

From: Scott <>
Date: Fri, 23 Oct 2009 06:01:02 -0400
Message-ID: <002401ca53c7$ba5f8560$2f1e9020$@net>
Hey Groepaz, 

> oh ofcourse it does. if you set vice to ntsc then it works like a ntsc c64 :)

> the "64 forever" emulator IS vice :)

So much for hoping :). If this is the case then I really have problems. 

> by now there really arent many programs left that do run on a c64 but not in 
> emulation, the emulators really became damn good in the past few years.

The emulators are great but it just not the same and playing on the original equipment / Joysticks. 

> ... and there is a possible cause, the fastload cart :) remove the fastload 
> cart, and remove all devices from the iec bus except the floppy drive. then 
> try again :)

I just recently bought it off Ebay (back in the day I owned a Mach 5 Cartridge). But these problems started way before I receive the Fast load cartridge. But I will def pull it and try again. I had disconnected the C64TPC last week sometime thinking it may be impacting the load. 

> there is also a very slight chance that you have one of the rare 64 cycle VICs 
> (normally ntsc VICs have 65 cycles per line) - in that case take that c64, 
> store it safely, and get another one - hardly anything will work on it, but 
> its a nice collectable :) you can try the "ntsc (old)" setting in vice and 
> check if it then behaves like your c64 ... or open your c64 and read the chip 
> markings on the vic (forgot what revision/number the old ntsc vic is though).

How cool, I didn’t even know these existed. Would these be the Bread Box style? Mine is the C64 C in the Beige/white 128 looking case. If it is, I'll open er up and let you know the rev of the VIC chip. Also, I'll check out the NTSC (old) setting and see if it matches how my 64C is acting. 

And again, thanks!!

avast! Antivirus: Outbound message clean.
Virus Database (VPS): 091022-0, 10/22/2009
Tested on: 10/23/2009 6:01:02 AM
avast! - copyright (c) 1988-2009 ALWIL Software.

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

Archive generated by hypermail 2.2.0.