Message-Id: <199706031534.LAA21720@mail.enterprise1701.com>
Comments: Authenticated sender is <mwebb AT mail DOT enterprise1701 DOT com>
From: "Mike Webb" <mwebb AT mail DOT enterprise1701 DOT com>
To: OPENDOS AT delorie DOT com
Date: Tue, 3 Jun 1997 12:59:13 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: OpenDOS is _already_ case-sensitive?
Reply-to: mwebb AT mail DOT enterprise1701 DOT com
In-reply-to: <01IJMQCMI11K9MH2ZH@cc.usu.edu>
Precedence: bulk

> From:          Roger Ivie <IVIE AT cc DOT usu DOT edu>
> MORRIS JP wrote:
> > It seems that at least part of the filesystem is already case-sensitive
> > internally.  I found this on my HDD the other day:
> [[[ snip ]]]
> > MAiN     tXT     7347 28/05/97 16:37 
> [[[ snip ]]]
> > Check out MAiN.tXT, (7347 bytes, 28/05/97)
> >
> > No program will touch it with a bargepole, they just reference MAIN.TXT instead.I could remove it with Norton, but it's so odd, I've decided not to for
> > the moment.
> The traditional way of deleting this sort of file in CP/M is to load MBASIC
> and issue kill "MAiN.tXT"; MBASIC does not uppercase file names and is therefore
> both the leading creator of filenames with lower case and the easiest and
> quickest way to deal with them. If I ever experimented with GWBASIC to determine
> whether it worked this way, it was so long ago that I forgot the result...

Another way to do it is use a sector editor and zap the directory 
entry, converting it to a standard filename. That's how I dealt with 
a file someone created in Concurrent DOS once which somehow acquired 
a backslash as the lead character in the filename. But that's brain 
surgery; be very, very careful and you should probably update your 
backup first!