Message-Id: <199707242358.TAA21680@mail.enterprise1701.com>
Comments: Authenticated sender is <mwebb AT mail DOT enterprise1701 DOT com>
From: "Michael E. Webb" <mwebb AT mail DOT enterprise1701 DOT com>
To: caldera-opendos AT caldera DOT com, opendos AT delorie DOT com
Date: Thu, 24 Jul 1997 21:29:24 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Long Filenames; What Went Wrong?
Reply-to: mwebb AT mail DOT enterprise1701 DOT com
Precedence: bulk

I tried an experiment today with the OpenDOS longname.exe and command.com 
which didn't work out like I thought it would. Hopefully someone here can 
give me some advice.

What I was trying to do is see the OpenDOS LFN functions in action, and 
possibly use it in connection with backing up the Win95 machines we're 
starting to get at work. My present procedure, klunky as it seems, is 
to use the Info-ZIP utility to archive an entire hard drive to the LAN, 
which I subsequently copy to my PC and then to a ZIP disk; it works for 
me! Of course, on a Win95 machine I have to be able to capture the long 
filenames to do a proper backup.

I had previously downloaded the LFNB1.EXE archive. I formatted an OpenDOS 
boot diskette, then copied longname.exe and its special command.com to 
the floppy (overwriting the existing command.com). I then booted up a new 
PC with the disk, loaded longname.exe and executed a DIR on C:\. I saw an 
additional column in the directory on the far right, which I assumed to 
be the long filename list. However, when I got to a directory with a long 
filename (I think the SFN was C:\PROGRA~1), the extra column gave the 
same name as the SFN.

Any hints or ideas? Thanks.