Date:	Sat, 15 Feb 1997 11:54:35 -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:	<Pine.LNX.3.95.970215031204.900U-100000@capslock.com>
Message-ID:	<Pine.GSO.3.95.970215115102.25092B-100000@sparkie.gnofn.org>
MIME-Version:	1.0
Sender:	owner-opendos AT mail DOT tacoma DOT net

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
> > > > This _jams_!!, by utilizing the algorithm I proposed of using the first
> > > 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
> What ever method that gets implemented, it should be totally
> transparent to the user (not ask questions) and it should be

Ok, that's close enough, but I don't like the extension handling, I'd
prefer somemeans to identify the type of file it is.  Also, we could
modify my idea so that a really strange character is use, ie one you would
never use in a regular filename but would serve as an indicator to the
user that namebashing had occured and the entry would of matched an
existing filename otherwise.  Maybe an upper ASCII character?

<! 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>

- Raw text -