graphics.library 40.25 beta series

[FOL]

Originally Posted by Ratte

OK, lets push the development a bit ...

Manufacturer ID
$089e = ELBOX
Product ID
$0033 = Mediator 4000Di (confirmed, my own hardware)
other known Mediator-Product IDs for PCI-Bridges are
$0031 / $0032 / $0040 / $0048 / $0049 / $0060

best source for PCI-Vendor and Device IDs is
www.pcidatabase.com
take care about Radeons ... not all of them are
VendorID $1002 (ATI/AMD)
Sapphire is using a own VendorID !!!

And some GFX-Cards are using "mobile" Chips .. other DeviceID!

=> 1 billion combinations for pci / radeon ...

Think colour issues need sorting first.
This red tint is annoying.

[Ratte]

Originally Posted by arnljot

PCI Solutions:
Prometheus (Picasso96)
Mediator (Picasso96)
GRex (CGX3, CGX4)

...

P96 exclusive card (on classics)
Radeon92xx
....

http://www.a1k.org/forum/showthread.php?p=441792

=> 1 zillion combinations

[Cosmos]

@Fol

Since which beta this bug is there ?

[FOL]

Originally Posted by Cosmos

@Fol

Since which beta this bug is there ?

Beta 8 I believe.

As I said its only noticable when black areas are present.
On a guru, the guru box is tinted red instead of black.

Also when a black border is visable, its tinted red to.
It also happens in normal screen content, but not all the time.

I first thought hardware fault, but with my roms removed and 3.1 in its place, its working fine, colour wise.

[JimmySage]

I'm also getting a red tint / flicker to the whole screen on Mediator/Radeon with beta 8 and was about to take the machine apart.

I'll try an earlier version and see if it still happens.

[FOL]

Originally Posted by JimmySage

I'm also getting a red tint / flicker to the whole screen on Mediator/Radeon with beta 8 and was about to take the machine apart.

I'll try an earlier version and see if it still happens.

I just remembered, Im also getting curruption when dragging box over things, bits of the box remain.

[_mandark_]

Anyone using graphics.library 40.25 beta on a plain AGA machine together with FBlit? I thought the beta ought to replace FBlit, but without FBlit I have chip-ram issues.

On my A1200/ACA1230/OS 3.9 I built a 1mb ROM-Image with graphics.library 40.25 beta11. In Prefs/Workbench I chose "Images in other memory". With this startup-sequence

[...]
C:FBlit
C:WBCtrl IMT=FAST
C:LoadWB SIMPLEGELS

I have about 1.720 KiB Chipram free, after opening a directory with 160 drawers I still got 1.680 KiB left.

With this startup-sequence

[...]
;C:FBlit
C:WBCtrl IMT=FAST
C:LoadWB SIMPLEGELS

I have about 1.680 KiB Chipram free, after opening a directory with 160 drawers I got only 600 KiB Chipram left.

[mfilos]

I thought that with the new graphics.library you're not supposed to use Fblit etc.
I might be wrong though on this.

[Cosmos]

@mandark

Not all FBlit's functions are into this new graphics.library

Only :
FBlit_BltBitMap
FBlit_BltTemplate
FBlit_SetRast
FBlit_Draw
FBlit_BltClear
FBlit_BltPattern

So, could you try with the original v40.24 and these FBlit's ones enable (in FBlitGUI) and all the other disable. Have you only 600 Kb of Chipram left ??

[_mandark_]

Originally Posted by Cosmos

So, could you try with the original v40.24 and these FBlit's ones enable (in FBlitGUI) and all the other disable. Have you only 600 Kb of Chipram left ??

Ok, tested it. With original v40.24 + FBlit & only this patches enabled I have about 1600 KiB Chipram left after opening the directory.

[wXR]

Jesus Cosmos, do you plan to reimplement all of AmigaOS?

[FOL]

Cosmos aint had time to setup. Will try it as soon as I can.

[Bamiga2002]

Do you need to use WBCtrl under OS 3.9? I thought it was only for 3.5 ?

[_mandark_]

Originally Posted by Bamiga2002

Do you need to use WBCtrl under OS 3.9? I thought it was only for 3.5 ?

I know it's a OS 3.5 utility. But without it, Icons take Chipram on Workbench. If there is some in-built OS 3.9 utility with the same functionality please let me know.

[Bamiga2002]

in WB prefs, icons-->other mem i recall.

[_mandark_]

Originally Posted by Bamiga2002

in WB prefs, icons-->other mem i recall.

Yep I know, and I have set it to "other mem". But still ChipMem is used for icons without WBCTRL.

It is a bit complicated actually: http://www.gregdonner.org/os39faq/compatibility.html#9

[NovaCoder]

Originally Posted by _mandark_

Yep I know, and I have set it to "other mem". But still ChipMem is used for icons without WBCTRL.

It is a bit complicated actually: http://www.gregdonner.org/os39faq/compatibility.html#9

You need 'C:WBCtrl IMT=ICONFAST' to avoid icon corruption when using FBlit with icons in FASTRAM.

Quote:
You need to download WBCtrl, add it to your startup-sequence directly before LoadWB:

WBCtrl IMT=ICONFAST
LoadWB SIMPLEGELS

If you don't do the above, and choose "other memory" in WB prefs, you will get the nasty lines when opening drawers. Otherwise it should work fine - there will be a little speedup when opening drawers (icons are displayed faster), and icons will use very little chipram.

[_mandark_]

Originally Posted by NovaCoder

You need 'C:WBCtrl IMT=ICONFAST' to avoid icon corruption when using FBlit with icons in FASTRAM.

Thanks! I have overlooked this detail. Now the screen corruption lines disappeared. But that was not much of a problem anyway. My original intention was to replace FBlit + Systempatch with graphics.library beta, but this doesn't work out because of the ChipRam-loss described above.