| From: | Robert Cranley |
| Date: | 26 Jun 2001 at 21:12:25 |
| Subject: | Re: setenv |
Hi Jan-Erik,
On 23-Jun-01, you wrote:
> 1) you really should disable the resident setenv (the built-in one) it
> doesn't hurt to have it enabled but then you have to call the new setenv
> with c:setenv instead of just purely setenv (and you could also make it
> resident of course :-)
So could you not then remove the resident one and put the new version
resident at the beginning of the startup-sequence? Surely that would make
the update transparent, you could use setenv just like before, without the
C: path.
> 2) the command should be like this for instance
> c:setenv powerpc/memprot SAVE 1
>
> meaning the save keyword HAS to be between the actual variable and the
> string this is a bug in
> my opinion (the save keyword really should be last
Well, it should really be picked up anywhere in the command line, though
that itself could cause problems should a variable need to be set to "SAVE"
temporarily...
Regards,
Rob
AIM: Daedalus2097 ICQ: 103366205 IRC: Daedalus on ARCNET
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Quote carefully and read all ADMIN:README mails
To unsubscribe mailto:amigactive-unsubscribe@yahoogroups.com
Anyone sending unsubscribe messages to the list will be SHOT!
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/