From:	mharris AT blackwidow DOT saultc DOT on DOT ca
Date:	Tue, 25 Feb 1997 18:12:31 -0500 (EST)
Reply-To:	mharris AT blackwidow DOT saultc DOT on DOT ca
To:	jamesl AT albany DOT net
cc:	opendos AT mail DOT tacoma DOT net, opendos-developer AT mail DOT tacoma DOT net
Subject:	Re: [opendos-developer] Potential serious FS problem
In-Reply-To:	<199702191424.JAA17066@keeper.albany.net>
Message-ID:	<Pine.LNX.3.95.970225180646.597Y-100000@capslock.com>
Organization:	Total disorganization.
MIME-Version:	1.0
Sender:	owner-opendos AT mail DOT tacoma DOT net

On Wed, 19 Feb 1997, Jim Lefavour wrote:

> I just realized - whatever FS we use, we have to be careful.  Most 
> DOS programs expect filenames to be uppercase, and many are written 
> so that filenames are all treated that way - if we introduce a 
> case-sensitive fs, we may BREAK many programs, however, as files may 
> be installed  in varied case (some lower, some upper, etc. )
> 
> How can this problem be avoided?  Should we disable case sensitivity 
> in our fs?  We are trying to maintain compatibility with dos 
> software, after all... :)

Any of the name mangling methods being discussed will convert ANY
filename long/short/whatever, lowercase/uppercase/mixedcase/whatever
into a valid 8.3 filename.  For example:

LongFilename_____.TEXtfile-number1   will become something like...
LONGF#WQ.000   in DOS legacy apps.

Read the past discussions about the MACH name mangling algorithm
used in DOSemu.  Archives of past discussions are available on
DJ's server.


Mike A. Harris        |             http://blackwidow.saultc.on.ca/~mharris
Computer Consultant   |    My webpage has moved and my address has changed.
My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
mailto:mharris AT blackwidow DOT saultc DOT on DOT ca

LINUX: Lost access to your keyboard after a game?  Email me for fix.

- Raw text -