Date: Sat, 22 Feb 1997 12:13:07 -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.970215132028.2330D-100000@capslock.com>
Message-ID: <Pine.GSO.3.95.970222121004.20184D-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:
> > Ok, that's close enough, but I don't like the extension handling, I'd
> > existing filename otherwise.  Maybe an upper ASCII character?
> It would *HAVE* to be a character that DOS supports in filenames so that
> legacy apps would still work properly.  Also, some programs filter
> filenames so hi-ascii isn't a good idea.  Most users wouldn't know how
> to enter something like ALT-234 (OMEGA), and would be screwed.  (Unless

What about using a sequence, say like if there's a crash in the bash the
filename produce would look 'almost' like a W(% bash, but using the
character sequence of '=n' where n is the collision number.  And while I
thinking of it, don't produce an error with the first bash, that will give
more information to the user as to what the collisions were.

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