Help - Workbench 3.1 error during boot

[Immortal]

Hi,


After doing a rescan on igame, i received a guru meditation error

After restarting my a1200, i got this error during the boot process...

HDEnv: object not found

...It continues to boot and it enters workbench, but the icon of my external cf (PCMCIA) appears messed up, it was working great before.



Does any one know why this error happened and how can i fix it?


Im sending in attachment my Startup-Sequence and my User-Sequence,
for a better analysis.


Thanks in advance

[Daedalus]

HDEnv isn't a standard workbench thing, so it's a 3rd-party add-on that was included with whatever bundle you have installed, and redirects ENV: to a hard drive directory. That being the case, perhaps something has changed on the boot partition, since it's looking for a directory to use for its assign. The scripts are messy, non-standard affairs, but it would appear that simply renaming C:HDEnv to something else will revert to the standard method of using the RAM disk instead.

My guess though is that the crash resulted in a validation failure of the boot partition, meaning that Env stuff can't be written any more (part of the reason for putting it in RAM is to avoid that sort of issue). See if the drive is being validated, and if so, just let it finish and reboot. The Info command in a Shell will tell you the status of all your devices. Validation will take a good while, and if you reboot before it finishes, it has to start again.

[Immortal]

Thanks for your insight Daedalus.
At my first reboot it tried to validate it indeed, and it took a while to enter workbench, but nothing changed, it stills give me that error during boot.

Did you find any entrance to hdenv on my startup/user sequence?

Following your hints, ive opened a newshell and typed the info command, here's the result:



HDenv: doesnt appear in there, so i guess its not being validated

[daxb]

The U-S and S-S are looking ugly/messy. Seems some classicwb stuff with user changes.

[Immortal]

On the part of the classicwb entries, ive never changed a line.

The extra entries in there, are in most part the internet stuff: miamidx, classact, reqtools, wireless manager, prism2.device, etc...
i also have magicwb 2.1, mui 3.8 and acatune in there...

[Immortal]

After some deeper search, ive found where HDEnv is located.
I have it on my C drawer and a entry on my Startup-Sequence. (see images below)

What should be my next step?
Should i execute HDEnv_enable command? or that drive mount isnt important, and i should execute the disable command instead?

[DamienD]

On a freshly installed "ClassicWB Lite 3.1 .HDF" here's the part that you've shown from the "S/Startup-Sequence". It's not using "HDEnv" but "L:env-handler":



Where did you get this "HDEnv" from and why do you need it?

Also, it's not in the C folder on a fresh install.

Edit: ok, found HDEnv on http://aminet.net/; still not really sure what advantage there is for using this?

[Immortal]

Thanks for sharing Damien
I really dont know where that HDEnv comes from, maybe its from magicwb? IDK

EDIT: well from aminet description it does this:
"HDEnv is a little program for your Startup-sequence, which allows you to keep your ENV: directory on harddisk, and still have it behave exactly the same way, as if it would be on RAM Disk."

But i didnt installed it separately, i guess it came packed with some program installer.

[Immortal]

Whats the advantage of using it? can someone pls explain?
Anyway ive executaded the HDEnv_disable command, and now workbench boots perfectly with no errors, and my Pcmcia CF icon appears also ok

[daxb]

In short: There is no advantage. The main reason for it it is to save some RAM space what is only interesting for very low end systems. Env-handler already mentioned by DamienD is the better choice. I would recommend to remove HDEnv and use the original ENV system or env-handler.

[Immortal]

Thanks for clarifying daxb
Meanwhile i also removed any entry i had on my Startup-Sequence regarding HDEnv and replaced with the default classicwb ENV entries, that DamienD shared here, thanks bro!

My problem is solved, thanks everyone!

[AMIGASYSTEM]

If you use a real Amiga better to use "env-handler" in this way your RAM will be empty and clean, "Env-handler" it must be inserted in the startup-sequence after setpatch

L:Env-handler ADDVOLNODE

[Immortal]

@AMIGASYSTEM
Thanks for the tip!