You can use mode.com in DosBox I think, but dont know if it solves your problem.

[Überhaupt schlechter Stil, Umlaute in Filenames zu verwenden 😀.]

Thx for your input. I think this is keyboard and display releated.

As far as I understood, file name conversion (from WIN-XP UTF-8) is handled in a different way in DOSBOX.

Live long and prosper
Jam

It is not supported, mainly because there is no easy possibility to
map dos-characters to OS characters. cp437 might even be possible
but would just create a lot of problems/confusion when people use
different dos keyboard layouts or codepages.

Now I'm a bit confused...

The following command is not supported in DOsBox (check out - no file will be created):

C:\>echo "Test" >ä.txt

Accessing a previously created file with special characters is not supported in DosBox (in the attached screen shot you should see äÄöÖüÜß.txt).

Special characters are used in many many countries, I think my prob is not a very specific one. So, is there really no solution out there?????

improve DOSBox ?

Anyway if you can post the ascii number of those umlaut posts then we might add them to the allow table for files.

Here's an ASCII table I managed to find. There aren't any numbers to go with the characters, but given each line is 16 characters long, the additional characters which are not used in English start at 128.

Don't think that it'll work like Qbix said, because the character mapping
(OS to/from dosbox cp437) is not 1-to-1. It will only result in strange
file names on the host OS.

These characters are in the ansi charset so maybe some simple tranlation may work?

Well the target characters change when the codepage is changed in dosbox,
and i think it'd require some deeper changes to the file names (as the
mapping is the last thing to take place).

I made some new testings.

1. I started WIN98 floppy disc with all the german codepage-stuff:

device=c:\win98\command\display.sys con=(ega,,1)
country=049,850,c:\win98\command\country.sys
install=mode con codepage prepare=((850) C:\WIN98\COMMAND\ega.cpi)
install=mode con codepage select=850
install=keyb gr,,C:\WIN98\COMMAND\keyboard.sys

2. I created the äÄöÖüÜß.txt file on the floppy disc
3. chcp shows up with code page 850 active (see 850.jpg)
4. dir shows up with ÄÄÖÖÜÜß.TXT - everything ok

5. I started PC-DOS 7.0 without any codepage modifications
6. chcp shows up with code page 437 active (see 437.jpg)
7. dir shows up with ÄÄÖÖÜÜß.TXT - suprisingly!

All (my) special characters are included in the standard ASCII charset. So no translation has to be done (both charset output are the same).

The only thing what has to be done is to use an ASCII charset translation table to display file names in DOSBox. I would suggest this is already done.

So what are we talking about? A feature request or a bug fix 😊?

Regards
Jam

> All (my) special characters are included in the standard ASCII charset

But they do not match the host OS charset.
Feel free to provide those mapping tables.

qv90 wrote:

All (my) special characters are included in the standard ASCII charset.

Jam, this characterset translation thing is not easy. Lots of little details that can wrong, like when IBM created a Danish character-ROM for their matrix-printers, and somehow managed to put a ¥ (Yen) where it should have been a ø.

And regarding your statement that the German characters is included in the standard ASCII charset, I say No way there are. ASCII is short for American Standard Code for Information Interchange, and only covers 127 characters, so there simply isn't room for neither German, Danish or Greek characters there.

I can understand your desire to have DOSBox understand the names of your old files, but I don't think it will be implemented soon. In the mean time, you have 2 choices:

1) Use DOSBox to load and run a copy of real MS-DOS. Once you get everything set up, it should be an okay solution, but it requires a lot of work to prepare disk images, install MS-DOS in the disk images, copy your old DOS files to the images, etc.

2) If you have Windows XP Professional or Windows 2000 Professional, you can download and install Microsoft Virtual PC. But then again, you have the same problems as with running MS-DOS in DOSBox: A lot of work and fiddling to create disk images, install MS-DOS, copy files, etc.

i believe it's not easy to implement. microsoft didn't even manage to read "umlauts" correctly in windows 3.11 on a dos that shows them correctly.

Ok MiniMax, Thx for the input.

I tried to follow Sample usage of a harddisc image in DOSBOX. I took an old MS-DOS 6.22 (and later a WIN98 SE) boot disk (with changes to support german display/keyboard). Using http://www.chrysocome.net/rawwrite, I created a bootable disk image. Then I stumbled.... when I start DosBox (out of the box configuration), I got a GRP5 with Illegal call 7...

I tried with Win 98 SE boot disk and got the same result...

1. What's wrong?
2. If I can get the image boot working, will I then get the "umlaute"?

Jam

Don't have keyb loaded when booting.

Doe you mean in disk image or in dosbox?

dosbox.conf cointains:

[autoexec] mount y: c:\Progra~1\DOSBox-0.65\dos y: boot dos622.img […]
Show full quote

[autoexec]
mount y: c:\Progra~1\DOSBox-0.65\dos
y:
boot dos622.img

(dos622.img = floppy boot image)

Jam

It was about using keyb before boot but you are not doing that.
Try

[autoexec]
imgmount a c:\Programme\DOSBox-0.65\dos\dos622.img -t floppy
boot -l a

If that doesn't work there is something wrong with the boot sector of your image.

I tried your setup and got the same error. The image must be ok, since I can use that image file with VMware (4.5.2) and it works fine.

Error message:
Mounted FAT volume is FAT12 with 2847 clusters
Exit to error: CPU:GRP5:Illegal call 7

Is my AMD Venice 3500+ or my Win-XP Prof SP2 not suitable for DosBox?
Any suggestions?
Jam

> Mounted FAT volume is FAT12 with 2847 clusters

Please try a standard 1440 floppy.