Closed acepow3r closed 7 years ago
It works for me in 2.0.10 and 2.0.11 beta. Are you using an image file or a real floppy disk? If the latter, what operating system do you use? There have been some patches contributed by others to fix issues on recent versions of Windows, but I did not test these since I no longer have a PC with a floppy drive. If you used an image file, then was it formatted? The automatic configuration normally reads the disk geometry from the FAT file system header.
Thanks for the reply! I talk about disk images, 800k formatted and usable on 2.0.9.1. Your answer troubled me, so I did further tests: I discovered that the problem is Windows oriented and occurring only when the disk image is at a folder or path with a greek localized name eg. C:\Users\Χρήστης\Documents\ROMs gives the error. So D:\test\ROMs is OK but D:\τεστ\ROMs it isn't. Any hope to fix that?
Thanks for the information, I can reproduce the error now. It seems to be caused by fopen() not supporting UTF-8 on Windows, while newer versions of FLTK use UTF-8. It may not be easy to fully fix this, however, since all the file I/O would need to be changed, the issue is not specific to disk images.
The problem is now fixed in the Git source code, although not for all types of file I/O: the installer, configuration file paths and utilities still do not support Unicode characters on Windows.
The bug occurs from version 2.0.10 stable till today: Whenever the values of "Tracks", "Sides" and "Sectors per track", under Configure, are set to -1, for auto calculate, ep128emu returns an error saying "FDD: cannot determine size of disk image" This is not the case with stable 2.0.9.1