![]() ![]() 5.51 does sort of support LFN but only with an external TSR program Norton Commander article, see section 1.1įrom my testing NC 5.51 behaves as follows (it's sufficient to exit NC before testing each option, no need to restart DosBox): In my tests it appears that enabling LFN support breaks NC giving the issues described. I agree to follow the code of conduct and the contributing guidelines.Īfter some testing I suspect that may have Long Filenames enabled. ![]() I have searched and didn't find any similar bug report.Ĭode of Conduct & Contributing Guidelines.No response Have you checked that no similar bug report(s) exist? The few latest versions, I don't remember which version started this. What operating system(s) this bug have occurred on?Īny Windows 10 What version(s) of DOSBox-X have this bug? I expect the executable to start, while in Norton Commander. It's not the first time it's happened, I know, so this thread should never be closed, in case it happens again. The same thing happens when I type a command line and press enter. I'm using Norton Commander version 5.51 (the latest) in DOSBox-X, but in the latest versions - including Development Builds, I can't launch any software from NC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |