From: mharris AT blackwidow DOT saultc DOT on DOT ca
Date: Tue, 4 Feb 1997 23:48:18 -0500 (EST)
Reply-To: mharris AT blackwidow DOT saultc DOT on DOT ca
To: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
cc: dg AT dcs DOT st-and DOT ac DOT uk, opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] OpenDOS + Win95 w/FAT32 
In-Reply-To: <Pine.GSO.3.95.970203172157.24246E-100000@sparkie.gnofn.org>
Message-ID: <Pine.LNX.3.95.970204234729.166F-100000@capslock.com>
Organization: Total disorganization.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Mon, 3 Feb 1997, Colin W. Glenn wrote:

> On Mon, 3 Feb 1997 dg AT dcs DOT st-and DOT ac DOT uk wrote:
> <Applying Text Whacker 2001!>
> > >Have you folks thought about giving the inode number to 8.3 filenames?
> > Okay, so you download some documentation and save it:
> > Now you want to browse it with your favourite file viewer. This isn't LFN 
> > Now, which one was the tutorial? Ummmm...
> > A better solution is to use some sort of hashing. For example, the above under 
> > but GEOS doesn't use them. I hate to say this, but the Win95 way:
> 
> Ok, we're getting somewhere now, what you would need is a popup utility
> which would let you 'browse' the inode numbers and see what the names
> really are, something like a pig95 open dialog.  (sorry)

Again, we get into the issue of non-interactive usage and
graphical applications that are unaware of the LFN's.  

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

Xwindows: Forget '95.  Use a REAL GUI.