Closed ImJezze closed 4 years ago
No, it is not detected as CRT either. That is just the regular order of things that VICE does when it fails at each step. It clearly does say "Cannot open file" multiple times and "is not a valid file", so something is wrong with the file.
Here it goes like this:
[libretro INFO] Arg0: x64sc
[libretro INFO] Arg1: s:\emu\c64\img\beli\Wizard.d64
[libretro INFO] Autodetecting image type of `s:\emu\c64\img\beli\Wizard.d64'.
[libretro INFO] Attached file `s:\emu\c64\img\beli\Wizard.d64' as a disk image.
[libretro INFO] Autodetected image type 1541.
[libretro INFO] Resetting the machine to autostart '*'
[libretro INFO] `s:\emu\c64\img\beli\Wizard.d64' recognized as disk image.
[libretro INFO] Image for autostart: s:\emu\c64\img\beli\Wizard.d64
[libretro INFO] Image list is active for drive #8
[libretro INFO] Image list has 1 file(s)
[libretro INFO] File 1: s:\emu\c64\img\beli\Wizard.d64
The file is valid, and I found out the real reason for the problem, which is kind of weird.
The problem was the minus sign in the file path. It was not the usual minus sign (HYPHEN-MINUS, U+002D), but somehow I managed to use the "soft" variant (SOFT HYPHEN, U+00AD) when creating the folder.
Heh, nice. RA also has issues with some other special characters like scandinavian umlauts, so not a lot can be done about it in the core, I reckon.
I close this issue then. Thanks!
I try to load a D64 disk image with the vice_x64_libretro core on Windows. But the D64 disk image seems to be detected a CRT cartridge image and cannot be opened. If I do the same with the regular Vice executable x64.exe the D64 disk image can be loaded without problem.
This is the retroarch-log.txt