DustyShinigami wrote on 2025-02-12, 15:33:

Okay, so I recently learnt about DOSLFN, downloaded it, and I have it set up in my autoexec.bat file, but how exactly do you use it? I checked over the readme, which only seems to explain about its background, but not how you configure/use it. Even with it enabled, I've noticed that existing folders are still 8.3 long and folders are structured like CDIMAG~1. Is there a way of configuring it so it changes existing folders? Or does it only work for new folders?

Thanks

You do not have to configure it. But you need software that explicitly supports long file names under DOS. DOSLFN cannot magically enable long file names for software that does not support long file names.
Among the classic DOS based file managers e.g. Volkov Commander (VC) supports long file names. And some DOS based compilers e.g. DJGPP does not work properly without DOSLFN.

Falcosoft wrote on 2025-02-12, 16:10:

DustyShinigami wrote on 2025-02-12, 15:33:

Okay, so I recently learnt about DOSLFN, downloaded it, and I have it set up in my autoexec.bat file, but how exactly do you use it? I checked over the readme, which only seems to explain about its background, but not how you configure/use it. Even with it enabled, I've noticed that existing folders are still 8.3 long and folders are structured like CDIMAG~1. Is there a way of configuring it so it changes existing folders? Or does it only work for new folders?

Thanks

You do not have to configure it. But you need software that explicitly supports long file names under DOS. DOSLFN cannot magically enable long file names for software that does not support long file names.
Among the classic DOS based file managers e.g. Volkov Commander (VC) supports long file names. And some DOS based compilers e.g. DJGPP does not work properly without DOSLFN.

Oh. Missed that nugget of info. I just figured the later versions of DOS supported LFNs...? So I'd have to be using some third-party file managers or something like FreeDOS?

Thanks

DustyShinigami wrote on 2025-02-12, 16:16:

Falcosoft wrote on 2025-02-12, 16:10:

DustyShinigami wrote on 2025-02-12, 15:33:

Okay, so I recently learnt about DOSLFN, downloaded it, and I have it set up in my autoexec.bat file, but how exactly do you use it? I checked over the readme, which only seems to explain about its background, but not how you configure/use it. Even with it enabled, I've noticed that existing folders are still 8.3 long and folders are structured like CDIMAG~1. Is there a way of configuring it so it changes existing folders? Or does it only work for new folders?

Thanks

You do not have to configure it. But you need software that explicitly supports long file names under DOS. DOSLFN cannot magically enable long file names for software that does not support long file names.
Among the classic DOS based file managers e.g. Volkov Commander (VC) supports long file names. And some DOS based compilers e.g. DJGPP does not work properly without DOSLFN.

Oh. Missed that nugget of info. I just figured the later versions of DOS supported LFNs...? So I'd have to be using some third-party file managers or something like FreeDOS?

Thanks

MS-DOS never supported long file names but Win9x does. And Win9x used the same file systems (FAT16/32) that are also used by MS-DOS. DOSLFN implements the same long file name (LFN) API in plain DOS as Win9x. But you need software that is aware of and explicitly use this LFN API.
So that is the main point of DOSLFN: you do not need a DOS version that is aware of long file names since DOSLFN implements it.

Falcosoft wrote on 2025-02-12, 16:27:

DustyShinigami wrote on 2025-02-12, 16:16:

Falcosoft wrote on 2025-02-12, 16:10:

You do not have to configure it. But you need software that explicitly supports long file names under DOS. DOSLFN cannot magically enable long file names for software that does not support long file names.
Among the classic DOS based file managers e.g. Volkov Commander (VC) supports long file names. And some DOS based compilers e.g. DJGPP does not work properly without DOSLFN.

Oh. Missed that nugget of info. I just figured the later versions of DOS supported LFNs...? So I'd have to be using some third-party file managers or something like FreeDOS?

Thanks

MS-DOS never supported long file names but Win9x does. And Win9x used the same file systems (FAT16/32) that are also used by MS-DOS. DOSLFN implements the same long file name (LFN) API in plain DOS as Win9x. But you need software that is aware of and explicitly use this LFN API.
So that is the main point of DOSLFN: you do not need a DOS version that is aware of long file names since DOSLFN implements it.

Ahhh, I see. Gotcha. Guess there's no point in me keeping that utility then. Shame. Thanks anyway.

Just be aware that the Windows 9x version of the DOS programs and commands (COPY, DIR, DELTREE, .etc) are LFN aware.

Gmlb256 wrote on 2025-02-12, 16:40:

Just be aware that the Windows 9x version of the DOS programs and commands (COPY, DIR, DELTREE, .etc) are LFN aware.

I think I remember reading something about that. I've not tried it, but does that mean if I were to delete or copy a folder, along with its contents, I can type in the full name?

DustyShinigami wrote on 2025-02-12, 16:43:

I think I remember reading something about that. I've not tried it, but does that mean if I were to delete or copy a folder, along with its contents, I can type in the full name?

Yes, in quotes if the name contains spaces. The final quote may be omitted if it's at the very end of the command.

e.g. copy longfilename.txt "even longer filename.txt"
(use xcopy for folders)

Works in Windows 9x's command prompt. Doesn't work out of the box in MS-DOS mode (when Windows isn't running) but starts working again if you load DOSLFN.

I used to use it with 4DOS, I think you might have to start it with some parameter for LFN support.
The FreeDos command prompt has has some support as does the one from OPENDOS.

If you have Win9x, then the version of EDIT from there supports long filenames.

Support is a little spotty for LFNs in general, but being able to see them in the commandline and edit files with them is a start.