3 ms·
> There's no obvious way to create a lower-case filename on CP/M That's because the FAT file system used by CP/M didn't allow lower case letters, at all. In t
by mark-r 2y ago
> There's no obvious way to create a lower-case filename on CP/M
That's because the FAT file system used by CP/M didn't allow lower case letters, at all. In this case "no obvious way" == "impossible".
The stack problems mentioned were real. The stack size was set at compile time, and there was no way to extend it. Plus the stack was not just used by your software, but also hardware interrupts and their functions.
- blueflow 2y agoNot FAT, but something even more rudimentary.
- mark-r 2y agoSorry, my bad.
- whartung 2y ago> That's because the FAT file system used by CP/M didn't allow lower case letters, at all. That's not true. You could use lowercase file names. Just fire up MS-BASIC, and save your file as "test.bas". You now have a lower case file name. The problem is that all of the CCP utilities implicitly upshifted everything from the command line. So, with the stock set, you were out of luck. You can go back into BASIC and KILL the file, so all was not lost. But, the file system was perfectly capable of coping with lower case file names, just nothing else was.
- nils-m-holm 2y ago> That's because the FAT file system used by CP/M didn't allow lower case letters, at all. Sure it did. Just start Microsoft BASIC on CP/M, type a program and save it as "hello". It will appear in the directory as "hello.BAS". Of course the CCP, the console command processor, will convert all file names to upper case, so you can neither type nor copy nor erase the file, but still it exists. You can even load it from MBASIC using LOAD. You can have any characters you like in your CP/M file names. Sometimes I ended up with file names consisting of all blanks. I usually used a disk editor to deal with those, but there were lots of more convenient tools for the job.
- CodeWriter23 2y agoCP/M was FCB/Extents not FAT
- fortran77 2y agoCP/M was not fat.