Open rayrapetyan opened 2 months ago
XCOPY is imported from FreeDOS which doesn't support Long file names. https://github.com/FDOS/xcopy
I see, thanks. Do you know if there is a pure-DOS copy implementation supporting long file names?
Looks like LCOPY from LFN tools works as expected in dosbox-x with disabled virtual memory flag, but is there something else, maybe more stable and mature? Also, since dosbox-x declares LFN support, why XCOPY was chosen?
Nope, LCOPY is failing to copy from mounted folder drives, it works only with image drives :(
For certain cases, e.g.:
LCOPY E:\*.avi D:\APP /V
LCOPY produces this:
LOG: CDROM: GetAudioTracks, stTrack=1, end=1, leadOut.min=56, leadOut.sec=15, leadOut.fr=55
LOG: 4614980 ERROR IOCTL:DOS:IOCTL Call 0D:4A Drive 3 volume/drive locking IOCTL, faking it
LOG: CPU_Exception: Exception 5 already in progress, triggering double fault instead
LOG: CPU_Exception: Double fault already in progress == Triple Fault. Resetting CPU.
LOG: Removing UMB block 0xcc00-0xdfff
LOG: Rebooting the system
Using /C option (disable cache) solves this issue. So in any case when using LCOPY in dosbox-x, always use /V and /C options, then it works pretty stable.
Describe the bug
XCOPY command replaces part of the filename with the "~" symbol for all files with long names it copies over.
Steps to reproduce the behaviour
Actual: E:\Game\Loc35\001_ROD_01.WAV copied as D:\Game\Loc35\001_RO~3.WAV
Expected behavior
File E:\Game\Loc35\001_ROD_01.WAV should be copied as D:\Game\Loc35\001_ROD_01.WAV
What operating system(s) this bug have occurred on?
Debian Bookworm
What version(s) of DOSBox-X have this bug?
2024.03.01
Used configuration
Output log
No response
Additional information
No response
Have you checked that no similar bug report(s) exist?
Code of Conduct & Contributing Guidelines