Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Enviroment (was Re: Yea, but can an Amiga Shell do this....)
Message-ID: <8808232058.AA28033@cory.Berkeley.EDU>
Date: 23 Aug 88 20:58:22 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 23

:created in your Startup-Sequence.  This means that if you boot up with an
:old floppy, or simply forget to create ENV:, any program that asks for it
:will pop up a "Please insert volume ENV in any drive you stupid klutz."
:'SetEnv' is also little more than a front-end for 'copy * ENV:var'.

	Huh?  so either don't boot up with an old floppy, or take the
time (a whole 30 seconds!) to add an assign ENV:.  The hell, if you
boot up under an old floppy you aren't even running 1.3, so what's the point?

	And, it seems to me that the system is giving you a second chance
when it puts up that requestor: "Hey, this program is expecting to be run
under 1.3 but you are running a 1.2 enviroment!"... so you pop up another
shell, assign ENV:, and hit retry on the requester, then make the assign
permanent in your startup-sequence or whatever.

>	Shouldn't ENV: be part of the standard start-up assigns, like LIBS:
>or L: or C:?  Or am I getting in on this game too late?

	Yah, you put it in your startup-sequence.  What difference does it
make if the system does it, or you do it?  I have to reassign all those
defaults anyway for my HD.

			-Matt