Long file names in a DOS window?

[Bill]

How do I get long file names to work in a DOS window? I've managed to
get them to work when I initially start the window, but the first DOS
operation of any kind causes everything to revert to 8.3 names. I've
tried the CONFIG.NT "NTCMDPROMPT" command but it does not work.

Thanks, Bill

 

[R. C. White]

Hi, Bill.

Which version of the "DOS" window are you using? Command.com (16-bit
version) or Cmd.exe (32-bit version)?

Without going into details, let's just say that LFNs are handled differently
between the two versions of the "DOS" window.

RC

 

[Bill]

Hi, Bill.

Which version of the "DOS" window are you using? Command.com (16-bit
version) or Cmd.exe (32-bit version)?

Without going into details, let's just say that LFNs are handled differently
between the two versions of the "DOS" window.

RC

Hello RC,

I've tried both but am now using CMD.exe. This is the one that starts
out showing LFN's, but reverts to 8.3 as soon as I enter just about
any DOS command.

- Bill

 

[CS]

How do I get long file names to work in a DOS window? I've managed to
get them to work when I initially start the window, but the first DOS
operation of any kind causes everything to revert to 8.3 names. I've
tried the CONFIG.NT "NTCMDPROMPT" command but it does not work.

Thanks, Bill

Hi Bill:

By default, long file names are displayed in a command prompt window.
However, there are two ways to display a command prompt: One is to
use "command.com", the other "cmd.exe".

You can test this for yourself by clicking on "RUN". First enter the
command: "command.com", press enter. Notice no long file name
support.

Now do the same but enter "cmd.exe". You now have long file name
support.

Be sure your command prompt display is using "cmd.exe" and not
"command.com". Right click on your MS-DOS icon or shortcut and
select properties.

Regards.

 

[Bill]

Hi Bill:

By default, long file names are displayed in a command prompt window.
However, there are two ways to display a command prompt: One is to
use "command.com", the other "cmd.exe".

You can test this for yourself by clicking on "RUN". First enter the
command: "command.com", press enter. Notice no long file name
support.

Now do the same but enter "cmd.exe". You now have long file name
support.

Be sure your command prompt display is using "cmd.exe" and not
"command.com". Right click on your MS-DOS icon or shortcut and
select properties.

Regards.

I've done all that but my original statement still holds: I start out
with LFN's but the first DOS command causes the names to revert to
8.3.

- Bill

 

[CS]

I've done all that but my original statement still holds: I start out
with LFN's but the first DOS command causes the names to revert to
8.3.

- Bill

What DOS commands are you using? I just tried it using several
different DOS commands from a cmd.exe prompt and the long file names
are still displayed. I even used the "copy" command to copy a long
file name file from one drive to another and it works fine.

 

[Bill]

What DOS commands are you using? I just tried it using several
different DOS commands from a cmd.exe prompt and the long file names
are still displayed. I even used the "copy" command to copy a long
file name file from one drive to another and it works fine.

PKZIP 2.50 comes to mind immediately.

Thanks, Bill

 

[CS]

PKZIP 2.50 comes to mind immediately.

Thanks, Bill

I think I understand now. You're really referring to some DOS
programs - not a specific DOS command per se. PKZip 2.50 for DOS will
truncate long file names as will some other DOS utilities. CMFiler,
which I use, likewise will truncate a LFN from within a cmd.exe
prompt.

As for other DOS programs that you may have, you'll have to experiment
with them. But generally, DOS utility programs that are not LFN
"aware" when run from within a Win9X DOS window or from an XP cmd
prompt window, shouldn't be used.

 

[Bill]

How do I get long file names to work in a DOS window? I've managed to

I think I understand now. You're really referring to some DOS
programs - not a specific DOS command per se. PKZip 2.50 for DOS will
truncate long file names as will some other DOS utilities. CMFiler,
which I use, likewise will truncate a LFN from within a cmd.exe
prompt.

As for other DOS programs that you may have, you'll have to experiment
with them. But generally, DOS utility programs that are not LFN
"aware" when run from within a Win9X DOS window or from an XP cmd
prompt window, shouldn't be used.

Now we're getting the the reason for my original post. PKZip 2.50 was
in fact LFN aware under Windows ME. For some reason it's lost this
capability under XP, as have a number of other programs.
Additionally, once a non-LFN aware program such as PKZip runs, ALL DOS
programs are no longer LFN aware!

I know that Microsoft wants to kill DOS, and with XP they may have
finally done it for me!

- Bill

 

[Malke]

Now we're getting the the reason for my original post. PKZip 2.50 was
in fact LFN aware under Windows ME. For some reason it's lost this
capability under XP, as have a number of other programs.
Additionally, once a non-LFN aware program such as PKZip runs, ALL DOS
programs are no longer LFN aware!

I know that Microsoft wants to kill DOS, and with XP they may have
finally done it for me!

- Bill

NT-kernel-based operating systems - NT, Windows 2000, and Windows XP -
have never included DOS. Windows XP has a DOS emulator and some DOS
programs can successfully be run under it, but certainly you wouldn't
want to use any sort of shell manipulation DOS program in XP.

HTH,

Malke

 

[I'm Dan]

Now we're getting the the reason for my original post.
PKZip 2.50 was in fact LFN aware under Windows ME.
For some reason it's lost this capability under XP, as have
a number of other programs.

Hmm, pkzip25.exe is the heart of my automatic data backup system, and still
works fine under XP-Pro, preserving all LFN's. Must be something configured
differently between your XP and mine.

 

[Bill]

Hmm, pkzip25.exe is the heart of my automatic data backup system, and still
works fine under XP-Pro, preserving all LFN's. Must be something configured
differently between your XP and mine.

Probably so - would you send me a copy of your .PIF for me to
experiment with?

Bill(at)AA4M.Com
E-mail: Change "(at) to "@"

 

[I'm Dan]

Probably so - would you send me a copy of your .PIF for
me to experiment with?

..PIF for what? My pkzip25.exe is a Win32 executable, so doesn't use a .PIF.
My pkzip25.exe is 339,456 bytes, dated 4/15/98. Do you have something
different?

I was thinking that there might be something different in the registry. I'm
willing to look through my registry, but don't know what I'd be searching
for.

 

[Guest]

I would like to get into this also as I have been having the same problems with displaying full file names. In mycomputer and opening folders, some will display the long name, and others only the 8.3 versions. I have looked at all the view options and this type of thing, and can not find an answer. I have tried command.com and cmd.exe and only the 8.3 names are diplayed. I use xp home editoin.