Date:	Tue, 27 May 1997 09:16:36 -0400 (EDT)
From:	"Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>
Reply-To:	"Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>
To:	yeep <yeep AT xs4all DOT nl>
cc:	OpenDOS Mailing List <opendos AT delorie DOT com>
Subject:	Re: FSSTD (was Re: DOS utilities)
In-Reply-To:	<199705252125.XAA13658@magigimmix.xs4all.nl>
Message-ID:	<Pine.LNX.3.95.970527091523.13320T-100000@capslock.com>
Organization:	Total disorganization.
MIME-Version:	1.0

On Sun, 25 May 1997, yeep wrote:

> > > Yes, I'd rather follow my own standard as well.
> > > as a matter of fact, we discussed this already, and there were some
> idea's
> > > about env-vars or some ascii-file-env-var-extention, which saves
> memory.
> > > I myself prefer a standard which you can fill in yourself, like in a
> file
> > > called FSSTND.OD or somehting, which could probably be included in a
> > 
> > But then there is nothing standard about it.
> 
> Yeah there is.
> A program checks the LIB_PATH env-var to find where to put the library
> files.
> But each user can fill in it's own directory.
> This way I can name the directories how I want and put them were I want and
> still not screw up any programs that want to use the FSSTND

Another thought against this method...

What if the "special file" gets corrupted or deleted, and there
is no way to recover it?  Keep in mind, this file could have as
many as 50 or more directory paths in it...

I rest my case.

Mike A. Harris        |             http://blackwidow.saultc.on.ca/~mharris
Computer Consultant   |                  Coming soon: dynamic-IP-freedom...
My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
Email: mharris at blackwidow.saultc.on.ca  <-- Spam proof address

DOS must have's: 4DOS 5.50c  ftp://ftp.std.com/vendors/jpsoft

- Raw text -