Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Miloo on January 02, 2009, 05:53:22 PM

Title: Insert volume ENV
Post by: Miloo on January 02, 2009, 05:53:22 PM

I've just installed 3.1 and there was an error, when I boot from the CF I get an 'insert volume ENV' and I go straight into dos.

Where is ENV?

Title: Re: Insert volume ENV
Post by: ZeBeeDee on January 02, 2009, 06:05:53 PM

Just add the following line to your startup-sequence after the SETPATCH command and all will be well

c:Assign ENV: RAM:

Title: Re: Insert volume ENV
Post by: weirdami on January 02, 2009, 06:39:44 PM

or he could remove the line asking for that volume in the first place, too

Title: Re: Insert volume ENV
Post by: Miloo on January 02, 2009, 07:17:07 PM

There isn't a startup-sequence file so I made one and typed

SETPATCH
c:Assign ENV: RAM:

But the machine boots into dos?

Title: Re: Insert volume ENV
Post by: ZeBeeDee on January 02, 2009, 07:23:05 PM

Quote

Miloo wrote:
There isn't a startup-sequence file so I made one and typed

SETPATCH
c:Assign ENV: RAM:

But the machine boots into dos?

Add the following to the above:

c:Loadwb
c:EndCLI

Title: Re: Insert volume ENV
Post by: Miloo on January 02, 2009, 08:59:44 PM

Cheers, works ok now 8-)

Title: Re: Insert volume ENV
Post by: ZeBeeDee on January 02, 2009, 09:02:52 PM

No probs  :-)

Title: Re: Insert volume ENV
Post by: nOw2 on January 02, 2009, 09:04:31 PM

It sounds more like the OS is not properly installed. LoadWB is, by default, in the standard startup-sequence (along with a hundred or so other lines).

Title: Re: Insert volume ENV
Post by: jmbattle on January 03, 2009, 01:45:49 AM

Yes, it sounds to me that a piece of software is searching for environment configuration files, usually stored in ENVARC: .  Simply assigning ENV: to RAM: is a workaround to prevent the requesters from appearing, however it is not the ideal solution.

The original WB3.0/3.1 startup-sequence copies the contents of ENVARC: to RAM:env and assigns it as ENV: . This process consumes memory however, and can be replaced entirely by using the excellent HappyEnv/MountEnv packages.

Cheers,
James
x