BestClassicWB v2.0 for OS3.2

[rabidgerry]

Originally Posted by samplist

@512k MiamiDX comes bundled with BestClassicWB and there is no option to not install it (as it's the case with any other component as well).
You can install Roadshow or any other TCP stack though, I don't think there will be any issue.

@rabidgerry I actually use WinUAE to create and test BestClassicWB and didn't notice any such issues.
Make sure you have AGA and a 030 CPU in your setup.

Oh I do, in fact it's the exact same 060 setup I use for all my cards, 060, 64mb ram etc.

[rabidgerry]

Definitely something wrong, as soon as I boot into the HDF the CPU goes crazy.

[rabidgerry]

So no one has any ideas why this is happening? Look at the CPU? I just did ANOTHER fresh install from scratch. Thankfully I saved a copy of the hard file before installed BestClassicWB.

So is there something that might be installed that would cause this behaviour?

And why is Dopus saying it's already in resident memory do you want to bring to front? WTF is that all about?

[samplist]

@rabidgerry I'll try to replicate your WinUAE setup, maybe I can find something out.

[samplist]

Try removing items from WBStartup, I would remove Tinymeter, maybe it constantly pings the CPU...

[Cobe]

Wbdock wont save config for me. I edited config and added/removed what I want. But I dont know whats the syntax for aligment, pattern and similar I'd like to change.

Also, is it not possible with 3.2 to put icon so low on the screen that its text is not visible? I kinda remember that I was able to do that with 3.9.

[rabidgerry]

@samplist

see attached my config file

Nothing crazy in this, just 060, 64mg ram, you will see for yourself.

Obviously you will need to map to your own rom 3.2 as that will contain my path to the roms.

[rabidgerry]

could find tinymeter to test removing it from startup-sequence. Checked wbstartup and user-startup also.

When I went into wbstartup drawer and removed from there which got rid of it and yes you were right it was the cause of the CPU issue. So does no one else get this issue?

If I installed this on my real Amiga am I going to be having my CPU working overtime because of this program?

Also the intuition seems to draw everything really slowly. I shouldn't really have this problem using a 060. Why would this be? Even dropped colour down to 16. I normally run is at 124 in Classic WB 3.1.

[jeff b00toNic]

@samplist

It seems to me you are using an old rtg.library with the native driver.

If that's the case, then the blitter replacement functions won't work as intended.

[samplist]

thanks @jeff b00toNic, where I can find the latest version of rtg.library?

[rabidgerry]

@samplist does Tiny meter also make your CPU in WINUAE go beyond 100%?

[samplist]

@rabidgerry I tried the config file you attached and indeed the CPU usage goes beyond 100%. Removing Tinymeter is the only thing that solves it for me right now.

[UberFreak]

I could never make Tinymeter work properly on my 060 setup (real HW).

[crazyc]

Having read these comments I installed new meter on my 3.2 setup and was surprised to see around 40% cpu utilisation on that on my 1230?
Despite not doing anything. Not sure if this is just something I have not been aware of or if it is the meter function generating the usage.

[daxb]

As far as I know Tinymeter has a CPU usage function. What happen if it is disabled? On the other hand I would check the documentation about how it works. Maybe it is just normal.

[cloverskull]

I'm at 100% CPU in WinUAE either with or without Tinymeter. So not sure what (if anything) is the issue.

FWIW the emulated environment and software all feels like it works fine

[rabidgerry]

When I take tinymeter out of the WBstartup drawer (WINUAE) it does indeed stop the CPU going crazy, however I would not say the enviroment works as it should for me. The laggy mouse is still there and dOPUS still says it is already in resident memory would I like to bring to the front (unless this is normal??).

I can't put this onto a CF card yet until I know it's safe

@samplist your efforts to provide such a supplementary pack for OS3.2 btw are much appreciated so don't get me wrong, I just want it all to work befor I use with beloved real hardware

[fitzsteve]

All works fine for me under emulation but no 3.2 roms to test in a real Amiga at the moment, I actually intended it to use with my PiStorm. (Not got that working yet)

I'll have a look and see if I can use it with my Vampire 500, that could work assuming it can have a custom Rom.

I too have noticed the CPU usage going over 100% in WinUAE I had just assumed this was a bug in the JIT. I usually disable Tinymeter anyway in CWB.

Steve

[guybrush]

Thanks for the package! I tried it on vanilla 3.2 install and I can confirm that there are some issues with performances.

The refresh of the screen on a 030/50 is sluggish; comparing this to CWB ADVSP is like night and day... CWB goes twice as fast as 3.2 with this pack, so I guess there is something that is chomping resources.

I removed everything in the wbstartup folder, except what is coming with 3.2 and the refresh is still lagging behind and same goes for the mouse sometimes. What could be causing this? I get that it works fine on the emulator, but I want to run this on my actual hardware; and I would assume that 3.2 with this pack would still be much faster than 3.1 CWB, while it does not seem to be the case. I suspect the issue is the RTG; if you do not have the actual card on the real hardware, it may end up slowing things down.
Thanks

[samplist]

Thank you all for trying to figure this out. I have updated the pack to version 2.0.2 that removes the included mmu.lib and adds a newer version of rtg.library. I don't think this solves the performance issue though.

I'm also suspecting it could be the P96 native driver not playing nicely with OS3.2.
Here are some things to try one-by-one:
- Remove the Native monitor driver from Devs/Monitors
- Remove all WBStartup items
- Remove S:User-Startup
- Comment FPPrefs line in S:Startup-sequence