I'm trying to save a BASIC file that already exists to a .d64.
I've got the 1541 on continuous update, but to no avail.
I'm using the
save "@0:name",8
convention, which should save the new file over the old one.
Is this supported by CCS64, or am I doing something wrong?
Save problem
Moderator: Håkan Sundell
update:
I tested the @0: save with a blank disc and bogus program, and it works fine. So more details:
I've got a .d64 with a game on it. The boot sequence is written in BASIC. I need to delete a line from the loader to get it to work. When I load it, delete the line, and do
save "@0:prgname",8
it doesn't replace the program. Also,
open 1, 8, 15, "s0:prgname":close 1
won't delete it. So it's like the disc is write protected. I've hunted through the options on CCS64, and haven't found a write-protect option for discs. Am I just being stupid here?!?
I tested the @0: save with a blank disc and bogus program, and it works fine. So more details:
I've got a .d64 with a game on it. The boot sequence is written in BASIC. I need to delete a line from the loader to get it to work. When I load it, delete the line, and do
save "@0:prgname",8
it doesn't replace the program. Also,
open 1, 8, 15, "s0:prgname":close 1
won't delete it. So it's like the disc is write protected. I've hunted through the options on CCS64, and haven't found a write-protect option for discs. Am I just being stupid here?!?
Last edited by Almo on Wed May 26, 2004 10:28 am, edited 1 time in total.
Almo!
First, due to a bug in the original Commodore 1541 disk drive, saving with @ doesn't always work right on a disk that's nearly full. It's safe most of the time, though, so I doubt this is the problem.
It may be possible (although unlikely) that the D64 file itself is write-protected on your hard drive. Try locating it with Windows Explorer, clicking on it with the right mouse button, and selecting Properties. Near the bottom of the "General" tab, there will be a check box labelled "Read-only". If there's a check mark there, you probably won't be able to modify that file.
I believe CCS64 also has a disk write protect feature, but you'd have to enable it for it to work.
Individual files on a disk can be write-protected as well. These files are marked with a < after the file type. For example:
This ability is very rarely used, though, due to having to edit the disk data directly to do it.
It's also possible for the emulated drive to have a disk error, but it's easy to tell when this happens because the light will flash. CCS64 3.0 uses the Scroll Lock light to emulate the disk drive light. If you're using CCS64 2.0, you may need to enable the 1541 status display in the options to determine whether the light is flashing or not. (In fact, you might want to enable that feature anyway, so you can see what the disk drive does when you try to save.)
It may be possible (although unlikely) that the D64 file itself is write-protected on your hard drive. Try locating it with Windows Explorer, clicking on it with the right mouse button, and selecting Properties. Near the bottom of the "General" tab, there will be a check box labelled "Read-only". If there's a check mark there, you probably won't be able to modify that file.
I believe CCS64 also has a disk write protect feature, but you'd have to enable it for it to work.
Individual files on a disk can be write-protected as well. These files are marked with a < after the file type. For example:
Code: Select all
1 "JUST AN ORDINARY FILE" PRG
15 "WRITE PROTECTED FILE" PRG<
15 "NOT WRITE PROTECTED" PRG
33 "CANT TOUCH THIS" PRG<It's also possible for the emulated drive to have a disk error, but it's easy to tell when this happens because the light will flash. CCS64 3.0 uses the Scroll Lock light to emulate the disk drive light. If you're using CCS64 2.0, you may need to enable the 1541 status display in the options to determine whether the light is flashing or not. (In fact, you might want to enable that feature anyway, so you can see what the disk drive does when you try to save.)
okay, the .d64 isn't write protected.
None of the files have "<" after them.
I'm using V3.0 beta 1.3, and the scroll lock light doesn't do anything.
But I've turned on the Drive status indicator. When I try the @0: save, it stops at track 18, and the red light blinks.
when I try to s0: the file, it also stops on track 18 and blinks.
None of the files have "<" after them.
I'm using V3.0 beta 1.3, and the scroll lock light doesn't do anything.
But I've turned on the Drive status indicator. When I try the @0: save, it stops at track 18, and the red light blinks.
when I try to s0: the file, it also stops on track 18 and blinks.
Almo!
That blinking definitely means the emulated drive is detecting an error of some sort. A real drive would do that if a disk develops bad sectors or other damage, but this shouldn't happen with emulated disks. It's still possible that the D64 is corrupted somehow, or possibly using a non-standard file system.
To get slightly more error information from the disk drive, you can use this little program (typed from memory so I'm not completely sure I got it right):
(Reading the drive's error status will also stop the blinking light.)
One thing you could try is to download the game from another source, such as the "Arnold" site. There may be a slightly different version out there that will work in CCS64 without modification.
To get slightly more error information from the disk drive, you can use this little program (typed from memory so I'm not completely sure I got it right):
Code: Select all
10 OPEN 15,8,15
20 INPUT#15,A$,B$,C$,D$
30 CLOSE 15
40 PRINT A$:PRINT B$:PRINT C$:PRINT D$One thing you could try is to download the game from another source, such as the "Arnold" site. There may be a slightly different version out there that will work in CCS64 without modification.
-
iAN CooG/HF
- Posts: 12
- Joined: Sat Jan 03, 2004 11:42 pm
- Contact:
Re: Save problem
Almo wrote:Is this supported by CCS64
Yes it is , but sometimes fails to refresh the contents of the disk currently loaded in memory.
Select another d64 then back to your d64, or simply reselect your d64 after saving.
Also enable true drive emulation by selecting f9/drive8/emulation mode NORMAL, which should do the trick for everything related to disk problems.
-=[]=--- iAN CooG ---=[]=-