| From: | Craig Blackman |
| Date: | 13 Mar 2001 at 12:43:53 |
| Subject: | Re: [D5] Re: Stall while loading |
On 10-Mar-01 01:51:15, [D5] Re: Stall while loading, Keith Halstead typed:
>Hi,
>On 09-Mar-01, Jeff Gilpin wrote:
>>> you could simply assign
>>> ENV: to ENVARC: and not bother to copy anything at all.
>>
>> Actually, I tried that and it doesn't work. Either IPrefs or
>> WorkBench.library is hard coded to look for the system prefs
>> in ram:ENV instead of ENV:.
>For several years I have kept ENV: and ENVARC: permanently on my hard disc
>and not copied anything during boot-up. I just assign ENV: to HD0:ENV and it
>has worked flawlessly. (I have OS 3.1 but never use "Workbench" - so I don't
>know if the later versions have changed this. It would seem a bit bizarre
>and Microsoftesque to hard-code RAM:ENV instead of ENV: though.)
ENVARC: has always been on your HD. Look in sys:prefs/env-archive. By
simply doing the assignment you are still letting the startup-sequence
copy all of env-archive to ram:
>Apart from the much reduced boot up time and RAM: usage (20 sec and 900k -
>even though it is only 300k on the disk) it also has the advantage that
>"USEd" settings are still there after a reboot along with the "SAVEd" ones in
>ENVARC:
Actually, if you want the ENV: ENVARC: relationship to work properly use
HDENV. It allows you to keep ENV on your HD and retain all the proper
AOS relationships.
_____________________________________________________________
"Everyone is entitled to my opinion."
| mailto: (2craig2@home.com) |
Cheers from Craig of Tucson, Arizona, USA
--------------------------------------------------------------
"The only mystery in life is why the kamikaze pilots wore helmets."
- Al McGuire, former coach