BetterWB 4.3

[gulliver]

@thyslo

Hi, I am happy you enjoy BetterWB.
I could reproduce your issue with success.

I did all kinds of weird tests, and found out:
It does not seem to be a bug of BetterWB nor WinUAE.
A clean Workbench 3.1 installation suffers from the same issue given your parameters.
I believe it boils down to that Maxxon C++ 4.0 is hardcoded not to use more than 8 colors under RTG, or their graphic display routines are not programmed in a clean way.
So if you limit your RTG screenmode to 8 or less colors it will work.

Have fun

[PeterK]

On a system with 68020 or better I would recommend to install the 68020 version of my library as Libs:icon.library. I guess, BetterWB installs the 68000 version by default. Using the latter should not cause a bug, but it does not support all features, like direct drawing on 15 - 32 bit screens.

I can not give you a guarantee, that MinStack increases the stack in 100 % of all possible configurations. That's the reason why I removed it from Aminet already. Use StackAttack instead.

[thyslo]

First, thank you all for your help and hints

Anyway I had to search step by step for the problem and now I found it: It is the SYS:Classes/Datatypes/picture.datatype

Before installing BetterWB I had installed
picture.datatype, size 32028 Byte from 20-Dec-98

After installation it is:
picture.datatype, size 9664 Byte from 18-Apr-02

Replacing the '02 picture.datatype with the '98 one helps on my system. MaxonC++ on UAEGFX with 1280 x 720 runs fine now regardless how many colors I set:-)

Maybe it's an incompability or bad coding of MaxonC++ but this is a workaround.

[ProfPlum]

I have a question regarding installation.
My Setup: A2000, kick/wb 3.1, 68030.

I try to install from adf images on gotek from as df1:
I've tried twice and the install fails at the end of installing 1st disk. There is a message on the screen but I've missed it twice - windows closes too quickly.

After this point, my system is in an unusable state because many files don't have the executable bit set.

Has anyone seen such an issue before? Should I create floppies and try to install from df0: ?

[ProfPlum]

Originally Posted by ProfPlum

I have a question regarding installation.
My Setup: A2000, kick/wb 3.1, 68030.

I try to install from adf images on gotek from as df1:
I've tried twice and the install fails at the end of installing 1st disk. There is a message on the screen but I've missed it twice - windows closes too quickly.

After this point, my system is in an unusable state because many files don't have the executable bit set.

Has anyone seen such an issue before? Should I create floppies and try to install from df0: ?

Nevermind. I examined the installer script, made some minor changes, all is good.

[Faerytale]

Betterwb is missing CF0 and CF0.info in devs/DOSdrivers folder.

Thats why CF-PCMCIA wont work on default install.

[fitzsteve]

Originally Posted by Faerytale

Betterwb is missing CF0 and CF0.info in devs/DOSdrivers folder.

Thats why CF-PCMCIA wont work on default install.

Are you sure they're not in storage/dosdrivers? All you need to do in that case is double click or open shell and type mount cf0:

[Faerytale]

Originally Posted by fitzsteve

Are you sure they're not in storage/dosdrivers? All you need to do in that case is double click or open shell and type mount cf0:

yes, your right ,they are in the storage/dosdrivers folder. But i have to copy them to devs/dosdrivers for the cf-pcmcia to mount.

It was hard to figure that one out after long time since i did any Amiga hacking .

edit:yes that CLI cmd "mount cf0:" did also work.

[redneon]

Does anyone know why the DontShowIBorder commodity isn't working for me? When I run it or copy it to WBStartup the borders are still appearing for all icons.

[PeterK]

DontShowIBorders just removes the outer frame line around the icons, but it doesn't make the gray background transparent. Therefore it only works as expected as long as your window/screen background is still gray, too. It won't be useful if you use a wallpaper or a window background pattern.

In order to get real transparency with WB 3.0/3.1 you first need at least a 68020+ CPU and then also the NewIcons patch, which allows to configure transparent backgrounds. You can check out my IconDemoA1200.adf to see how that all can be installed:

http://eab.abime.net/showthread.php?t=64079

[redneon]

Yeah, it's not even removing the border around the icon. I'm not fussed about transparency just yet.

[PeterK]

Did you enable DontShowIBorder with the Prefs/WBStartup tool?

Is there only an icon DontShowIBorder.info in the WBStartup but not the program file itself. Is the "executable" flag set? Check that and the program "Bytes" size with Workbench=>Icon=>Information or SwazInfo.

[redneon]

Yeah, I used the tool and both the executable and .info are there. As far as I can see everything looks right. Although, it doesn't appear in the commodity exchange which doesn't seem right.

I've posted a photo of my screen and included everything I think might be relevant.

[PeterK]

It looks all ok.

Stupid question: Do you have a Hyperion ROM and a workbench.library v40.6 ?

If I remember it correctly, there was something wrong with that WB v40.6, but I'm not sure. You could try to copy another workbench.library into Libs:, like v40.5 and then use "RemLib >NIL: workbench.library" in a line above SetPatch.

If the workbench.library is not in the Hyperion Rom, but loaded from Libs: anyway, then you won't need the RemLib tool, just replace the library in Libs:.

Cloanto will be happy to help you, I guess ... If that works, thank Mike and forget Hyperion!
https://www.amigaforever.com/classic/download/

https://eab.abime.net/showthread.php...47#post1277147

[redneon]

No, I haven't bothered upgrading to 3.1.4 or 3.2. I'm not really sure what I'd get out of it, to be honest.

Trying to find out which version of workbench.library I have... There's no workbench.library in Libs: and when I go to "About" in the Workbench menu I get:

3.1 ROM
Kickstart version 40.68
Workbench version 40.42

Is this right?

[PeterK]

Hmm, that's strange, with Kickstart v40.68 it doesn't work on your system !?!

It should work, but with an old Hyperion OS 3.1 Kickstart v40.72 it is known not to work with DontShowIBorder and similar tools. That has nothing to do with OS 3.1.4 or 3.2.

https://eab.abime.net/showthread.php...71#post1277071

Please check the version of workbench.library from a shell:

Version workbench.library FULL

Is that v40.5 or v40.6 ?
Is there a copyright string in the WB title bar or the About requester? Commodore, Hyperion or whatever?

Or boot your system with my IconDemoA500.ADF. Does it show borders or not? Usually, there are no borders with Kickstart v40.68.
http://eab.abime.net/showthread.php?t=64079

[redneon]

I get "workbench.library 40.5 (24/05/93)".

Copyright in the About box is "Amiga International, Inc".

This does sound very odd! I'm heading off out now but I'll try the icon demo disk when I get back.

[redneon]

Yeah, I'm getting borders when I run the A500 demo. But not when I run the A1200 demo.

[PeterK]

Originally Posted by redneon

Yeah, I'm getting borders when I run the A500 demo. But not when I run the A1200 demo.

Then it's the best to use the NewIcons patch, ENVARC:newicons.prefs plus NiPrefs in WBStartup, and if you have FBlit installed then you would also need NiRTGset. You can compare my IconDemoA1200, the startup-sequence and files that I've installed with your setup.

There are other "NoBorder" tools on Aminet, but with the WB v40.6 nothing wanted to work anymore. Unfortunately, I can't find the original documentation for DontShowIBorder. Maybe it has something to do with this high ToolPri setting in the tooltypes of the icon. You could play with other ToolPri and StartPri values, but I won't expect any wonders.

[tFt]

So I installed BetterWB on my A600 with 2MB and vanilla A1200.
After startup, running 4 colors there is only 415.904 bytes left. Is this normal, or am I doing it wrong.

I have 5 partitions on my Disk On Module device, but just that shouldn't eat up that much memory.

I am going to install my Apollo1260 soon, so will have plenty of memory then, but I was weirded out that it ate up so much memory, can't run anything really before your down to 80kb, and Im wondering how much it will be left even with the 32Mb from the apollo. The A600 2MB is basically useless as it stands now.