Date: Sat, 15 Feb 1997 01:55:39 -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.970215002449.900K-100000@capslock.com>
Message-ID: <Pine.GSO.3.95.970215015106.25290F-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 Sat, 15 Feb 1997 mharris AT blackwidow DOT saultc DOT on DOT ca wrote:
> On Fri, 14 Feb 1997, Colin W. Glenn wrote:
> 
> > > CTRL-J in PINE.
> > Or add a verification: ARE YOU SURE! [Y/N]
> And then after you type 'YES' out in full and hit enter, it asks
> you to type in the volume label from C: in DOS for confirmation.

Hmmm, getting a >little< extreme?

> > > > We could call them something else, call them DLD, Dynamicly Loaded Driver.
> > > How about the extension ".Dynamically_Loaded_Driver_Module".
> >     \Extended_Filesystem_Number_2.Dynamically_Loaded_Driver_Module
> > This _jams_!!, by utilizing the algorithm I proposed of using the first
> > becomes EXTEFN~2.DLD to a dos 8.3 program!
> 
> What if I allready have a file called EXTEFN~2.DLD in that
> directory?  I mean the chances are very small, however I could
> simply create one just to prove my point.  Then the algorithm
> would break.  A better method is the mangled name method that
> DOSemu uses in LREDIR.
> 
> \ would be interpreted as a directory path, so if you said:
> COPY FILE1.txt \

No, only if the line is _longer_ than the the width of the screen, it'd
pop the entire line from the parsed point so you don't have a, (lets say)
critical filename split from right to left.

> / would be interpreted as a switch character, so if you said:
> COPY FILE.TXT .. /

same reason.