search

GideonZ / 1541ultimate

Official GIT archive of 1541 ultimate II sources
GNU General Public License v3.0
178 stars 45 forks source link

JaffyDOS d64 Copy fails #302

Open Jusalak opened 1 year ago

Jusalak commented 1 year ago

Hello,

I tried JaffyDOS copier:

https://csdb.dk/release/?id=206019

Copying

Source 11 [*IEC] Target 08 [1541] Source D64 Target Dir Tracks: 35

gives "Source Error".

Pressing F4 gives the error string as "61, FILE NOT OPEN,00,00". The D64 file can be selected, but fails when attempting to copy.

When D64 file is opened from RAM disk, the result is the same.

Jussi Ala-Könni

GideonZ commented 1 year ago

Hi Jussi!

Thank you for reporting. What is not clear for me is what the program is supposed to do, what the order of operations is, when the error appears, etc.. Could you be a bit more specific?

Target = 1541, Target = Dir... but... the 1541 doesn't support DIRs? You are trying to copy a file into a disk? Is that something JaffyDOS copier can do? You are trying to copy from SoftIEC. Does JaffyDOS copier try to upload code to it, or does it use DOS functions only through kernal calls?

Gideon

Grrrolf commented 1 year ago

@Jusalak wrote:

I tried JaffyDOS copier:

You do not mention if you have the jaffydos kernel installed or not. Jaffydos is a patched jiffydos for use with SD2IEC.

Jusalak commented 1 year ago

Hello,

Trying to copy a D64 image to a real 1541-II. DIR displays the directory of the real drive - works fine.

I tried stock C64 Kernal, I conclude from below that it should work:

http://blog.worldofjani.com/?p=6617

"Fast I/O. Copying a 35 track disk takes approximately 2 min with Jiffy/JaffyDOS and 4 min 30s with CBM kernal." I don't know what it does internally. Some kind of direct IEC programming?

Would be very handy if works, I have a lot of trouble trying to copy disk images back to real floppies.

markusC64 commented 1 year ago

Well, it isn't that important to know that it does on the iec device. Could simply add logging to an developer version of the firmware, so the ultimate will tell us. IEC commands and 'open's and 'close's should be enough to log.