Message-Id: <199708201936.PAA07562@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, lfnbeta AT caldera DOT com
Date: Wed, 20 Aug 1997 16:57:05 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: LFN Problem
Reply-to: mwebb AT mail DOT enterprise1701 DOT com
Precedence: bulk

I was doing some experiments with the LFN command.com and utilities 
at work today and encountered a problem I haven't seen before. Maybe 
it's a bug?

There were two Windows 95 machines side-by-side. 

One was a Pentium 133 with a 1 gig hard drive, which had been fully 
configured.

The other was a Pentium MMX 166 with a 2 gig hard drive, straight 
from the factory (no local configuration done yet).

I booted each machine with the same Caldera OpenDos 7.01 disk with 
the LFNB1A command.com and longname.exe. On the 133 LFN's read just 
fine. On the 166, while I got an extra column in the directory for 
long file names, the short file name appeared in that column. Where I 
should have seen "Program Files" as the name of a directory, I saw 
"PROGRA~1". Using DOSLFNBK to capture the long filenames also failed 
on the 166 while it worked on the 133.

I even went back out to the OpenDOS UK site and found an LFNB1C 
update but had no success. Is this a problem with the utility or is 
it a config thing (does Win95 have the long filenames available 
before full configuration)?

Thanks.