Date: Sun, 16 Feb 1997 16:30:00 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: "'OpenDOS newsgroup'" <opendos AT mail DOT tacoma DOT net>
Subject: Re: [opendos] BAD Filesystems
In-Reply-To: <19970216.122945.8487.0.chambersb@juno.com>
Message-ID: <Pine.GSO.3.95.970216162748.16718B-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Sun, 16 Feb 1997, Benjamin D Chambers wrote:
> <cwg01 AT gnofn DOT org> writes:
> >On Sat, 15 Feb 1997 mharris AT blackwidow DOT saultc DOT on DOT ca wrote:
> >> On Sat, 15 Feb 1997, Colin W. Glenn wrote:
> >\Extended_Filesystem_Number_2.Dynamically_Loaded_Driver_Module
> >> > > What if I allready have a file called EXTEFN~2.DLD in that
> >> It would be something like EXTEN#KR.001 or something close.  If a
> >Ok, that's close enough, but I don't like the extension handling, I'd
> >existing filename otherwise.  Maybe an upper ASCII character?
> A trick to use spaces in filenames, use ASCII-char 255.  This is a blank
> char (which is why it is used instead of a space).  However, this char
> could also work as a flag to indicate name hashing.

And then the user, (not realizing that it's not a space), merrily keeps
trying to access file 'EXTEFN 2.DLD'.


  <! PrePared HTML!  Just export as a HTML file and Click!>
A Christian Web Site!  The Light 
  <a href="http://www.thelight.org/">.</a><br>
A neat place to visit. HotSpot 
  <a href="http://www.hspro.com/hotspot/">.</a><br>
Caldera, Inc. / Makers of OpenDOS
  <a href="http://www.caldera.com/">.</a><br>
Caldera's OpenDOS page
  <a href="http://www.caldera.com/dos/dos.htm">.</a><br>