REL file copy stopped working with 3.14d

[8BitBoyz]

Describe the bug
Copying (good working) REL files between u64 virtual drive to another virtual drive, or copying REL files from u64 virtual drives to real drives (1541, CMD Fd-4000) will error 64 on many REL files. The files it errors out on were copying just fine last week and beyond on the previous firmware version before updating firmware to 3.14d.

This issue has also been confirmed by another user on his u64 trying to copy the same type of REL files, he confirmed last week it worked but now with 3.14d he too gets errors copying.

*reference to u64 1581 = using the virtual drives in the u64 as a 1581

To Reproduce
Steps to reproduce the behavior:
u64 1581 to physcial FD-4000:

1. mount .d81 with original REL files (for Image BBS)
2. load fcopy+, setup source as the u64 1581, set destination as Physcial FD-4000
3. Select RELs from u64 1581
4. select copy
5. same set or REL files stop copy with error 64

u64 1581 to u64 1581:

1. mount .d81 with original REL files (for Image BBS)
2. load fcopy+, setup source as the u64 1581, set destination as u64 1581
3. Select RELs from u64 1581
4. select copy
5. same set or REL files stop copy with error 64

All above steps were repeated with the same result using Mcopy+, Jimbutter Fields Copy
All above steps were repeated multiple times with the same issue copying to:
u64 1541, multiple different disks on the FD-4000 from 1581 format, HD format & ED format

Expected behavior
As with previous firmware, expect files to copy but after updating to firmware 3.14d this is not happening instead error 64 happens.

Screenshots
N/A at the moment

Applies to (please complete the following information):

• Hardware type: u64, u46 virtual 1581 and 1541 drives, real 1541, real CMD FD-4000
• Firmware Version 3.14d

Additional context
Anything that comes to mind I left out will be added to this thread.
Any additional information need for this please let me know, I will provide asap.

Thank you!

[8BitBoyz]

System feature configuration

I forgot to add that I ran test with both Turbo on and off, with Jiffydos and without Jiffydos.
All configurations produced same failed result.

[8BitBoyz]

Put this on hold for the moment, due to more testing with myself and 2 others it turns out the issue is what I had in January. The USB stick .d81 rel files got corrupt. As we were able to copy the same files from a new disk (not from the .d81 in the u64) on a NEW USB stick to both the FD-4000 drive and a .d81 U64 drive.

This would be the 2nd USB stick to get corrupt in the u64. this one was a sandisk usb 32gig stick with a fat32 filesystem.

[8BitBoyz]

I am revisiting this ticket as the issue has been tested for a week plus in many different ways.

Findings:

If you have a REL file on a u64 .d81, .64, (physical) FD-2000/4000 drive it will copy to and from following drives OK:

PASS RESULTS:
FD-2000 & FD-4000 (Physical Drives)
1541, 1581 (U64 virtual mounted drives)

If you have a REL file on a u64 .d81, .64, (physical) FD-2000/4000 drive it will copy to and from following drives FAILING:

FAILED RESULTS:
SD2IEC (physcial drive)
SoftwareIEC (u64 virtual drive)

• I understand the SD2IEC does not have 100% REL compatability but some RELS copy okay to the SD and the more dynamicly used RELs seem to not copy correct ever.

** The SoftwareIEC is reported to be 100% REL compatible but it fails at time worse than the physical SD2IEC in test restults.

When the failure happens, it does put a file on the drive, how ever the file is wrong size and missing a lot of the data but also filled with a lot of garble data.

U64 SETTINGS TESTED
This has been tested with the follow u64 setting and the out come is the same as stated above in the FAIL and PASS resultswith all the following settings:

• Turbo mode on & off
• Bus Opperation Mode, all mode settings
• JiffyDOS on & off
• RAM Expansion Unit on & off
• Serial Bus Mode, all mode settings
• IEC Printer on & off

The REL files being used are the REL files on the Image 3.0 install disk #2. the most comon REL files that will fail 100% of the time are:

• e.data
• e.say
• e.say (small)

[GideonZ]

• It is not clear on which platforms this occurs. U64? U64E2? Cartridges?
• It is not clear how to reproduce. Apparently a copy program was used, but which one?
• Nothing has changed in regards to REL file support in 3.14d.
• Nothing has changed in the drives themselves.
• When you say "softwareiec" where is the REL file located?

[radius75]

2. load fcopy+, setup source as the u64 1581, set destination as Physcial FD-4000

Is fcopy+ really the right tool for copying RELs? I've never been able to successfully copy REL files between two 1581 drives using fcopy+ on the Vice emulator.
For RELs, I use the copy-all.64l, program from the 3.0 utilities.d81 floppy disk.

[8BitBoyz]

@GideonZ @radius75
"It is not clear on which platforms this occurs. U64? U64E2? Cartridges?"
These findings were done by myself and 2 others using (3) u64's (1) U64E2

"It is not clear how to reproduce. Apparently a copy program was used, but which one?"
Programs used for copy with same type of results were: fcopy+, copy all, I.cp rel (An image bbs rel copier with in image bbs)

"Nothing has changed in regards to REL file support in 3.14d."
This is has held true for the past couple versions of the firmwares

"Nothing has changed in the drives themselves."
No change to any of the drives other than we brought in the physical FD serise drives to test with also.

"When you say "softwareiec" where is the REL file located?"
This is would be copying the RELs from 1581 (the original installer disks) and also on the FD drives to the SoftwaeIEC
In turn to this on the the softwareIEC gets a bit more complicated in that you can copy the RELs that have copy issues to the SoftwareIEC with out error but the files are corrupt and unreadable by Image REL editors and readers. Also if you then try to copy the bad REL back to the 1581 or FD drive it will either Error Out or just corupt the REL more.

I hope that helps with your questions if not let me know I will try to get more examples via additional testing.

Thank you guys!

[radius75]

For testing purposes, I tried copying the REL of the MASTER D2 231231.d81 ‍ using fcopy+ on the Vice 3.10 emulator.
Strangely enough, it seems that the newer Image3.0 disk images are corrupted in some way.
I was able to successfully copy the first three REL files from the old version MASTER D2 201111.D81 <---
The newer ones always have some errors.
The latest Master D2 260125.d81won't even open in Vice 3.10. I don't know why...
https://8bitboyz.com/dl/downloads-bbs-software/downloads-image-bbs/

[8BitBoyz]

@radius75 That disk #2 was fixed let me check on it, the working files version was uploaded a week or two ago. I will test and verify. Im also not only working with those disks but also files from the image authors who we confirmed the files used for coping are working. Let me dig and get back on this...

[8BitBoyz]

@radius75 Here is the disk with the fixed e.data, e.say, e.say (small) from X-Tec 2 weeks ago. try those files we have confirmed the are working but have the copy issue with stated drives.

MASTER D2 230318.zip

[radius75]

The latest Master D2 260125.d81won't even open in Vice 3.10. I don't know why...

Vice log ..\?Master D2 260125.d81' is not a valid file. - the file name probably contains some special character which causes a problem on Windows, after changing the name the file opens in the Vice emulator

[8BitBoyz]

I can fix the vice issue seperatly but for here on the u64s, these disks work for reading and the REL's on them have been verified by Xtec as valid working RELs. they just have the issue at hand when copying on the u64 between certain drives.

@GideonZ I pulled my Commodore 64 U and it too has the same issue coping the stated REL's as above.

[8BitBoyz]

@radius75 per the Image D2 disk on 8bitboyz.com. I just downloaded it, extracted it and mounted it in vice no issue. you might need to try again on your end. I am attaching video of test.

@GideonZ I will try to put together a download with the files im testing and how to verify the copied file if it is good or bad. will take me a bit but I will get that for you in hopes it helps better on your end.

Test Video PART 1:
https://github.com/user-attachments/assets/673b6a4b-4697-4e9c-ba07-8a46a148fde4

Test Video PART 2:
https://github.com/user-attachments/assets/85884a18-9a20-4bd7-a0e7-f6b7ca9de359

[8BitBoyz]

@radius75 On the U64 & Commodore 64 U the title for the .d81 had funny random characters but not on our test vice beds just on the U64 c64u hardware. I just fixed the download on 8bitboyz.com and tested it and now the funny characters on D2 of the .d81 are gone. give that updated download a try, you will know its the updated download as the file name has the word "INSTAL" with only one L. Hope this fixes it for you too. ;)

Here are before images of the funny characters on the u64/C64u for D2 .d81 NOT FIXED

Here are after images of the funny characters on the u64/c64u for D2 .d81 FIXED.

Mounted D2 .d81 listing directory ok.

[radius75]

File name starts with an invisible control character (U+200D). Windows OS is having trouble opening this .d81 file in Vice. I fixed it by renaming the file. But that's unrelated to the topic.

[8BitBoyz]

@GideonZ Here is a .d81 image i created with some files needed for testing of one of the root issues which is copying of some REL files to softwareIEC will copy but are corrupt on the softwareIEC.

Setup:

• U64 firmware 3.14d
• SoftwareIEC Device 11
• virtual 1581 (.d81) device 10
• FD-4000 (physical drive) device 9
• SD2IEC device 8

Process done:

1. Copied "e.data", "e.say", "e.say (small)" from FD-4000 (device 9) to .d81 1581 (device 10)
2. Loaded "edata edit 3.0.PRG" from Device 10 (.d81) told it to read "e.data" from Device 10 (.d81) then told it to list. It listed all 50+ lines of the REL file list as it should. PASS
3. Copied "e.data" from Device 10 (.d81) to SoftwareIEC Device 11
4. Loaded "edata edit 3.0.PRG" from Device 10 (.d81) told it to read "e.data" from Device 11 (SoftwareIEC) then told it to list. It listed line 1, paused for a bit then syntax errored out. Thus REL file currupt copying to SoftwareIEC FAILED
5. Copied "e.data" from Device 10 (.d81) back to the FD-4000 (Device 9) using a different floppy, fresh formated.
6. Loaded "edata edit 3.0.PRG" from Device 10 (.d81) told it to read "e.data" from Device 9 (FD-4000) then told it to list. It listed all 50+ lines of the REL file list as it should. PASS

Notes:

• I did this process with both FCOPY+ and COPYALL
• All tests were done with same result having the SD2IEC both plugged in and not plugged in
• All the same results happen to the SD2IEC also doing the same test with multiple copy programs
• All test produced same results with TURBO, JIFFY, RAM on and off
• All required files for this test from copy, rel edit and data files are located on this attached .d81 image
• File e.data is not found on any Image install disks as Image BBS creates e.data during initial setup of BBS

Please let me know if you need anything else. ;)

Test .d81 Disk

u64_rel_test.zip