AGA,FBLIT=problems:)

[VooDoo]

Ahoy ppl..

I have problem whit my brothers Amiga..problem is on wb screen..you can see probelm here -> http://www.inet.hr/~iteskera/error.jpg

And problem goo on screen when i click on directory Icon...Config: a1200/040/40/32mb-AGA/OS3.9+bb2..patches: BlazeWCP,FBlit..maybe I need bettre Fblit settings..please help!!

[bloodline]

Ahhh I remember Gfx trashing well! I never cured the problem.

Consider it a "feature" :-D

[VooDoo]

ohhh nooo...that is not true...maybe I need patch for fblit patch:))

[adolescent]

Could be an overheating Alice chip, or some other problem.  Does the problem just happen in MULTISCAN mode, or all modes?  

[leirbag28]

Get SnoopDos and run it, and start disabling programs one by one and rebooting to see wich one conflicys with FBlit.

Fblit ruins the AntiAlias Level for on SCALA MM300. I emailed the Fblit guy about it, and we talked a little but didnt really finish talking.

something must be causing a conflict.

[Piru]

Could be an overheating Alice chip, or some other problem. Does the problem just happen in MULTISCAN mode, or all modes?

No it couldn't.

It's clearly FBlit related bug, either FBlit itself or some app borking on fastmem buffer when it expects chipmem one.

[VooDoo]

..I only testing MULTISCAN MOD..and when i remov FBLIT from startup-sequenc problem is gone...all works ok..Fblit is problem..I don't have good settings..

Have you tried "Prefs/WorkBench",
Images in : Other memory.
I had the same problem, and this solved it.
Otherwise, you have to change your FBlit settings.
And trie this:
Download "WBCtrl" from Aminet and put this
in the C: directory.
Then put this command right after the FBlit command
in Startup-Sequence:
WBCtrl IMT=ICONFAST.
That should do the trick...
 :-D

[VooDoo]

I resolve the problem...And problem is in FBlit Config,,,now Cap`^HIT send to me his config files and all works OK..once Tnx to Cap!!You are AGA/Fblit expert:)

[adolescent]

Can you send me the config file also?  I have an old A1200 that does the same, I had assumed (until now, thanks Piru) that it was the notorious Alice overheat.

Edit:  Never mind, after booting the computer up mine is definately another problem and heat related.