Derek_Stewart wrote: ↑Sun Feb 11, 2024 8:05 pm
Maybe using using a modified file name substitution for the directory tree to a device, like SUB implements. But this would need a change to the operating system, DV4 ?
That's exactly what HPR's vfs does. It translates long file names to shorter ones that fit into the QL's limits and hides the short ones. Still, application programs will have a hard time using those names because they don't assume long names.
It's a quite nice aproach that works similarily to long filename support in DOS VFAT, but a bit fragile because the translation is not based on rules but rather stored in files.
I had another look at QVFS, I think I understand the process, I will have play with it to see if I can get it to work.
Pity the source code was not supplied, maybe a candidate for disassembly.
I'm not sure if that really solves the problem or is adding even more illusion on top of the QL's already illusional subdirectories (I fear the latter).
I had another look at QVFS, I think I understand the process, I will have play with it to see if I can get it to work.
Pity the source code was not supplied, maybe a candidate for disassembly.
I'm not sure if that really solves the problem or is adding even more illusion on top of the QL's already illusional subdirectories (I fear the latter).
Okay, looks like long file names are not required.
I'm not sure if that really solves the problem or is adding even more illusion on top of the QL's already illusional subdirectories (I fear the latter).
Okay, looks like long file names are not required.
I will move on to something else...
They are. But I (personally, you don't have to share my opinion, of course) don't feel like they are that easily achievable.
tofro wrote: ↑Mon Feb 12, 2024 5:43 pm
They are. But I (personally, you don't have to share my opinion, of course) don't feel like they are that easily achievable.
How does your (yet unreleased) native FAT32 driver behave with regard to long file/path lengths?
tofro wrote: ↑Mon Feb 12, 2024 5:43 pm
They are. But I (personally, you don't have to share my opinion, of course) don't feel like they are that easily achievable.
How does your (yet unreleased) native FAT32 driver behave with regard to long file/path lengths?
If it finds a pathname that doesn't fit into a file header (i.e. one that was generated by another OS), it will add a "+" as the last character of the part of the name it can fit and disallows access to that name.
I have a half-baked implementation of a "prefix" to a path that you can add by a BASIC command which allows you to peek deeper into the directory structure from QDOS, but that doesn't work too well up to now.
