Slow window rendering ClassicWB OS 3.5
 

Hell
I have problems with my Amiga 4000 that runs ClassicWB 3.5.
When i close a window it slows down so much that i can se how it renders the individual parts of the scrollbar and window.
I have made a video of it but it's in swedish but you can still see the problem:
A4000-problem del 1 - YouTube
Any ideas what i should do?

I thought that it was a power supply issue so i borrowed a refurbished but that didn't help.

Damn it, it's much slower than my 020 a600.
Do you have newest icon library (by Peter K) installed?
Do you use graphic card or flickerfixer?

No flickerfixer or graphics card in the machine.
In the video there is only a RGB to VGA-adaptor, power supply, keyboard/mouse and a IDE HDD connected to the motherboard.

The display is a 4:3 plasma from 1998 that have a scaler box that accepts a great variety of input resolutions and then converting them to 640x480.

I have a indivision AGA MK2 but that is not connected in the video.

I use a standard 3.5 installation where i have installed CWB. How can i check what icon libary is installed?

Replace your icon.library (libs folder) with this http://eab.abime.net/coders-system/6...-versions.html and report back. Use newest .289 version it made my amiga much faster. Also connect that flickerfixer and see if that makes any difference?
However it looks too slow even for unmodified 3.5 and might be hardware problem.
Good luck.

Try to disable some of the components in Classic Workbench in case you have a conflict somewhere.

Also what screen mode are you using? It looks higher than 640x512 and maybe that's just why it's so slow.

What processor are you using in your A4000 by the way?

When i first got these issues i thought that it was some kind of hardware problem. I have since then removed as much as i can of the system but the problem is still there.
I have tried with another power supply and with a two CPU boards (A3630). I have also tried some RAM test tools.

I tried to use the system and it worked. Then i discovered that the floppy drive wasn't connected. I connected the floppy drive and i got the same old problems again. I removed the drive and the problems was still there.

I guess that is a hardware problem. I have read there may be a crystal problem with the A4000. The crystals have connection problem with the mainboard and have to be soldered.

I changed to another hard drive that contains a old 3.5 installation. It works without any problem.

You still didn't say what screen mode you're using with OS3.5 Classic, it looks very large, much higher than the 640x512 that is is normally set to.

This is probably why it's so slow. AGA can't do high resolutions like 'Super High Res Laced' very well with lots of colours.

It was 1024x768 16 colors but the problem is still there at 640x512

You could try Classic Workbench 3.9 instead or ADV SP which looks the same as 3.5 but is based on WB3.1

I'm not running 3.5 based on the look of it. I like the look of 3.1 but 3.5 is much easier to use with big hard drives. That is the reason i switched to 3.5.

With ADV SP (and all CWB packs based on 3.1) all you have to do is put the updated SCSI.Device in 'Devs' and you have proper support for drives over 4gb:

http://classicwb.abime.net/classicweb/tutorials.htm

See bottom Video.

It makes no difference in speed when you use 3.1 or 3.5/3.9 with the same icons. That what I found anyway. That 3.1 icons are lame ;)

I will give 3.9 a try then.

Be sure to also grab the latest icon library as mentioned in the thread earlier, it makes a huge difference to Icon loading times :great

You wont regret CWB 3.9 it's a very nice pack, my favorite of the Classic Workbench's :)

Guess what! Same problem with a 3.9 installation!

That's strange, I'm running CWB 3.9 with the same hardware (minus the Indivision) but I have one I can install for tests, I don't expect to see the same problem though.

http://www.youtube.com/watch?v=SVXbyQtlOrI

I thought you nailed the problem? Your hard drive is slow.

The drive is fast when connected to my PC running WinUAE

It looks exactly like the problem I got with my a 4000 disabling the CyberBugfix fixed it for me.