Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    BINKD    |    Support for the Internet BinKD mailer    |    8,958 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,846 of 8,958    |
|    Mike Powell to NIGEL REED    |
|    Re: DOSBOX-X and lowercas    |
|    24 Mar 25 08:31:00    |
      TZUTC: -0500       MSGID: 1770.binkd@1:2320/105 2c469bd7       REPLY: 3765.fido_binkd@1:124/5016 2c45db18       PID: Synchronet 3.20a-Linux master/acc19483f Apr 26 202 GCC 12.2.0       TID: SBBSecho 3.20-Linux master/acc19483f Apr 26 2024 23:04 GCC 12.2.0       BBSID: CAPCITY2       CHRS: ASCII 1       > > 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)       SEEN-BY: 10/0 1 102/401 103/1 705 104/119 105/81 106/201 120/302 616       SEEN-BY: 124/5016 128/187 129/215 305 153/757 7715 154/10 30 50 110       SEEN-BY: 154/700 203/0 214/22 218/0 1 215 601 700 720 840 860 880       SEEN-BY: 218/940 220/20 90 221/0 6 226/18 30 44 50 227/114 229/110       SEEN-BY: 229/114 200 206 275 300 307 310 317 426 428 470 550 664 700       SEEN-BY: 229/705 240/1120 5832 266/512 280/464 5003 5006 5555 291/111       SEEN-BY: 292/854 8125 301/1 310/31 320/219 322/757 341/66 234 342/200       SEEN-BY: 396/45 423/120 460/58 467/888 633/280 712/848 770/1 902/26       SEEN-BY: 2320/0 105 3634/12 5020/400       PATH: 2320/105 154/10 280/464 103/705 218/700 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca