AmiCygnix on Workbench Glitch

Hi cygnusEd,

First, THANKS for you work on AmiCygnix! I installed the
latest version on my SAM and it all went flawlessly.

I tried the new GUI and it's a nice addition!

I've mainly been using Gnumeric and that's also been
going well.

But I mostly want to run AmiCygnix on the Workbench
using the P96 Window driver and I always get a pink
colored AmiCygnix window contents. This remains the
same whether I'm on a RGB16 or ARGB32 screen.

Any idea whether this a configuration issue, something
in the OS/P96 or in AmiCygnix?

Thanks,

PJS

@pjs

I guess you are a OS4 beta-tester?? I was told, that there are problems with the next update, but I can't check this. I have to wait for the release of the update. Hope I can fix it then.

@pjs

Quote:

New GUI???
Where?

@cygnusEd

Sorry to dig up a months-old thread, but I'm messing about with this now under AOS4.1u2 and I observe the same pink coloration when opening AmiCygnix inside a Window on Workbench using the picassoa96pip driver.

Has this been fixed, or am I doing something wrong? Thanks!

And thanks also for all your good work!!!

new GUI? what, where, when

@Elwood

Wasn't there a "myX11Setup" program in your AmiCygnix
directory? Maybe I got it from somewhere else?

hmmm....

PJS

Just found this thread from early 2009 on AW, so it's not a new problem....

http://amigaworld.net/modules/newbb/v ... _id=28172&forum=32#477909

My system is a Sam440ep-flex with Radeon 9250.

@mbrantley

I still have no solution for this problem. It seems, that the overlay window does not support th R5G6B5 pixel format anymore.

The only way to solve this at the moment is to replace the file "Sys:Kickstart/ATIRadeon.chip" with the one from the first release of OS4.1 (I do it this way). But I can't tell you, which disadvantages it has.

@cygnusEd

Quote:

Thanks! I'll give that solution a go.

@mbrantley

The pip driver gives me a pink screen as well on my micro, try the picasso96 driver, that works for me without changing kickstart.

@sundown

Yeah that does work, as well as the driver that clones WB. But the point of trying the pip driver is to run AmiCygnix on the Workbench screen. Not sure if it's worth dropping back to an earlier system file, as you say, however.

Haven't had time to try because I've been letting my Sam devote itself to two days of rendering frames for a long, high-def VistaPro animation. Don't want to reboot until it's done.