Welcome, Guest. Please login or register.

Author Topic: Insert volume ENV  (Read 3639 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline MilooTopic starter

  • Full Member
  • ***
  • Join Date: Mar 2007
  • Posts: 165
    • Show only replies by Miloo
Insert volume ENV
« 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?
A1200/68882/AMD Slot A 1Ghz in EZPC case, Blizzard 060@66Mhz/SCSI IV, PortJnr, 194Mb fast ram, 4Gb CF HD, OS 3.9, Indivision AGA
 

Offline ZeBeeDee

  • Hero Member
  • *****
  • Join Date: Jan 2007
  • Posts: 1081
    • Show only replies by ZeBeeDee
Re: Insert volume ENV
« Reply #1 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:
To err is human ... to BOING divine!

[SIGPIC][/SIGPIC]
 

Offline weirdami

  • Hero Member
  • *****
  • Join Date: Jan 2003
  • Posts: 3776
    • Show only replies by weirdami
    • Http://Bindingpolymer.com
Re: Insert volume ENV
« Reply #2 on: January 02, 2009, 06:39:44 PM »
or he could remove the line asking for that volume in the first place, too
----
Binding Polymer: Keeping you together since 1892.
 

Offline MilooTopic starter

  • Full Member
  • ***
  • Join Date: Mar 2007
  • Posts: 165
    • Show only replies by Miloo
Re: Insert volume ENV
« Reply #3 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?
A1200/68882/AMD Slot A 1Ghz in EZPC case, Blizzard 060@66Mhz/SCSI IV, PortJnr, 194Mb fast ram, 4Gb CF HD, OS 3.9, Indivision AGA
 

Offline ZeBeeDee

  • Hero Member
  • *****
  • Join Date: Jan 2007
  • Posts: 1081
    • Show only replies by ZeBeeDee
Re: Insert volume ENV
« Reply #4 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

To err is human ... to BOING divine!

[SIGPIC][/SIGPIC]
 

Offline MilooTopic starter

  • Full Member
  • ***
  • Join Date: Mar 2007
  • Posts: 165
    • Show only replies by Miloo
Re: Insert volume ENV
« Reply #5 on: January 02, 2009, 08:59:44 PM »
Cheers, works ok now 8-)
A1200/68882/AMD Slot A 1Ghz in EZPC case, Blizzard 060@66Mhz/SCSI IV, PortJnr, 194Mb fast ram, 4Gb CF HD, OS 3.9, Indivision AGA
 

Offline ZeBeeDee

  • Hero Member
  • *****
  • Join Date: Jan 2007
  • Posts: 1081
    • Show only replies by ZeBeeDee
Re: Insert volume ENV
« Reply #6 on: January 02, 2009, 09:02:52 PM »
No probs  :-)
To err is human ... to BOING divine!

[SIGPIC][/SIGPIC]
 

Offline nOw2

  • Full Member
  • ***
  • Join Date: Jul 2002
  • Posts: 194
    • Show only replies by nOw2
Re: Insert volume ENV
« Reply #7 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).
 

Offline jmbattle

  • Sr. Member
  • ****
  • Join Date: May 2005
  • Posts: 324
    • Show only replies by jmbattle
    • http://www.amigainabox.co.uk
Re: Insert volume ENV
« Reply #8 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