Workbench Prefs Error in WinUAE

[Peter]

I've got the latest version of WinUAE installed together with the latest version of BetterWB

I am getting a problem with... well, check out my picture - this message comes up every time I boot, anyone know what would get rid of this?

I get it when I try and change the background colour in WB also.

[Steve]

Does the file actually exist? Have you checked?

[Peter]

I have checked it in "System/Prefs/Env-Archive/Sys" and it's there - I even renamed it thinking WB would create a new version - WB did create a new version but the error still persists.

I get confused here because I think it has something to do with the file being created in Ram - but it doesn't look like it is being created... I'm confused.

[Toni Wilen]

I am quite sure it has nothing to do with emulation (ENV: pointing to RAM and so on = can't be anything filesystem related). Probably messed up WB setup or mismatched library versions etc..

[Peter]

I'm guessing it may be BetterWB latest version is playing up - I will have to test further... but if anyone knows a fix I would be grateful.

[thomas]

BetterWB was a good idea in the beginning. It added datatypes, libs, utilities and such which didn't exist in the original WB installation. You cannot do much harm by adding files which didn't exist before.

But at some point it began to replace existing files by third-party versions without asking. Since then you better call it WorseWB.

[PeterK]

Originally Posted by thomas

But at some point it began to replace existing files by third-party versions without asking. Since then you better call it WorseWB.

Your comment sounds a little unfair, IMO

I've just made a fresh installation of BetterWB 3.6 from scratch on WinUAE 2.8.1, using a Kickstart 40.63 for 68000 CPUs. Everything during the installation was executed flawless. And I didn't get any errors while booting the system. At that time, there is still no ENVARC:Sys/wbpattern.prefs on the harddisk. When you try to save from Prefs/WBPattern you will get this requester complaining about the missing wbpattern.prefs file. You can just ignore it. It will be created in ENV: and ENVARC:.

I'm not sure if the installation files of BetterWB are working correctly when you just update a previous setup. In such a case you have to use the special update packs, but never install the full set of ADF disks again over an existing setup. With one of the previous updates BetterWB has introduced the Env-Handler, which should replace the Assign of ENV: to RAM:Env/ and the copying of ALL the preferences and config-files during the startup of the system.

Using Env-Handler: If the startup-sequence lines
Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Assign >NIL: ENV: RAM:Env
still exist, then comment them out with a ";" and try again, because the assign would prevent the Env-Handler from mounting ENV:

The Env-Handler from Stephan Rupprecht was modified by me in order to work on a 68000 CPU. If there are problems with this modified ENV-Handler then please post your current startup-sequence, your WinUAE config file and the version of your Kickstart.

On the other hand, you can also try to fix the problem by commenting out Env-Handler and inserting the normal startup-sequence lines:

Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Assign >NIL: ENV: RAM:ENV

However, just make sure that not both methods of using ENV: are activated at the same time.

[BigFan]

Originally Posted by PeterK

Your comment sounds a little unfair, IMO

Please! It's his opinion and it it somewhat true.

Using Env-Handler:

I'd installed env-handler on A1200 and in WinUAE. Both configs failed. It's definitely not worth the trouble it causes. WB works fine without. I don't blame you or Stefan for this. Shit happens. That's kinda "unfair"

[PeterK]

Yes, every nerd has his likes and dislikes. And I belong to those who like gulliver's BetterWB. He did a good job for all the owners of LowEnd-Amigas.

On my WinUAE OS 3.9 system, I'm using the original Env-Handler for more than 10 years now without any problem (and if I remember it correctly, I used it even before on my older OS 3.1 systems).

Shit happens, sometimes it's just the laziness of the users to spend some time and efforts on finding the reason for these software conflicts.

[BigFan]

Sure. Nobody minds.

If gulliver is the same who put some effort in BB3 and BB4, thanks but for 4.
Those f*cked up libraries from the cosmos dude crashed badly.
It wasn't his (gullivers) fault, he is trying to improve system.

As a complete opposite, your icon.library is not only usefull, it never crashed or corrupted my systems.

Do you expect every user to be fond of bug tracking? Guess not.

And our systems are aging to rust. They become more and more picky. It reminds me of elderly care.

oops, this is going of topic.
i must apologize