When importing or exporting files that end in one of more non-breakable spaces (0xFF), they are trimmed from the filename

[Digitoxin1]

This is a limitation of .NET. All file operations in .NET run filenames through a trim function which trims a set of characters off of the end of a filename including non-breakable spaces.

This could be fixed by bypassing .NET and accessing the Windows API directly, but I'm not sure how this will affect users who are running DiskImageTool under Wine on Linux and MacOS.

[albertus82]

Why is this a problem? Thanks.

[Digitoxin1]

It changes the filename. There could be potential issues if someone copied files out of an image to use in DOSBox and the title was looking for a file with that specific filename. Unfortunately, it has been a while and I did not document which image had this issue.