you are out of luck. dosbox will not load files with these characters.

You can view them in dosbox though by setting the correct keyboardlayouy/codepage

I managed to make the chars visible, but DosBox still cannot load them 🙁

Will there be a fix in future releases?

You could try to hexedit the program file...

When I hex edit the game, it stops and returns a bad checksum error... So this don't seem to be possible 🙁

(I changed all Ü to U and Ö to O etc...)

Will there be a fix in future releases?

No there won't.

Oh! wd is a psychic. He can tell the future.

There's an old thread about this game and issue: DOSBOX doesn't work with umlauts (in files!)!

As Qbix points out in that thread, it's fairly easy to modify the DOS_MakeName() function in dos_files.cpp to add characters that you would like to have in your own build of DOSBox. The accented letter characters (diacriticals) are in the range of 0x80-0xA5, which includes some other stuff like monetary signs that you could filter out if you want to be precise. The Greek symbol for beta (ß) is also used in some German words, which is 0xE1.

I'm not sure why the devs are opposed to including support for diacriticals in filenames, but there must be a good reason... possibly some platform issues. In the current code of DOSBox, there is support for 0xA0 (á); there must be some story behind why only that one is allowed.

Probably because a game needed it.

I'm not sure why the devs are opposed to including support for diacriticals in filenames

Because "just passing strange characters" through doesn't work, you need
translation tables from OS codepages to dos codepages. Look at the explorer
screenshot he posted above where the dosbox screenshot has an umlaut.
In the reverse, when in the explorer there's an umlaut your it's-so-easy
passthrough idea would result in surely no umlaut in dosbox.

I knew there must be some reason; thanks for sharing it with us. Now if you would be so kind as to explain why 0xA0 is supported (which must also be undergoing some codepage translation).

cvs logs should tell, was some game that didn't like the error code or so.

historically the limited amount of allowed characters is a safegaurd against trying to open files when the memory gets corrupt.
In that light exceptions were added for games that needed them. However correct support would be more tricky.

Quote from the thread above:

Qbix wrote:

what basicly is written there: if character doesn't exist in that table so not a normal character like abcdefghi.... or a numb […]
Show full quote

what basicly is written there:
if character doesn't exist in that table
so not a normal character like abcdefghi.... or a number or one of the special characters listed in
that case '\\': case '$' : .....................

then dosbox reports "path_not _found /illegal character in name". and the game can't open the file.

So there is no way around it unless Somebody adds those characters you describe in this table.

To do this: I would need the ascii values and some example games to try it on.

Simply copy some dos files like COPY.COM etc... to CÖPY.COM (cannot be too complicated) 😁 😕

The game Bazooka Sue would work only from CD, and I don't wanna upload a 600mb iso (illegally)
BTW I own the original CD

maybe this link will help:
http://www.torsten-horn.de/techdocs/ascii.htm