Subj : Re: DOSBOX-X and lowercas
To   : NIGEL REED
From : Mike Powell
Date : Mon Mar 24 2025 08:31 am

>  > I checked the "universal" conf file and didn't see that setting. I have now
>  > tried it.  Files written are still all in UPPERCASE on the host os.

> I think I did have that problem once and the way I got around it was to create
> a vfat filesystem for that directory.

> You can use dd to create a small file and then format it as vfat, mount it to
> /mnt and copy your files over, and unmount and remount to the new location and
> add it to fstab. This is one way I found around the issue, but I'm sure sure
> it's going to help in your case.

That is another idea worth trying.

> You could create a symlink from the lower to upper case name if you know what
> it's going to be in advance or after the dos program has run? I'd need to know
> more about how it's used I guess.

In my case, the datasets in question are being created by an FTN tosser,
squish.  Squish, for some reason, writes the pathnames in the flo files in
UPPERCASE, but is writing out the actual dataset names in the flo files in
lowercase.

When linux binkd reads the flo file, it cannot find the dataset because the
case in the flo file (lower) doesn't match the case that DOSBOX-X has
written out (UPPER).

I am not sure if I would know for sure the names each time. I would also
suspect that, after sending the dataset, binkd might delete the symlink it
found that matched the proper case.


 * SLMR 2.1a * Arnold Layne, don't do it again!
--- SBBSecho 3.20-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

.