First of all hello all.

I have recently set up MorphOS 3.5 on a Mac mini G4 and installed the Chrysalis Ultimate Pack and an having no end of trouble trying to enable transparency on the launcher. I right click on the bar and tick 'bar settings', then I tick 'transparency' and the bar goes from a white background to a black one.

Any words of advice for a MorphOS newbie and A500 user from about 25(?) years ago?

It's frustrating the hell out of me as I really want a transparent launcher!

Hi madCrow,

Try to active Enhanced display in MorphOS prefs -> Screens -> Edit Ambient screen

Quote:

You could have just used the internal one with the background set to 100% transparency.

Preferences->Ambient->Panels

Papiosaur,

Sorry, I should have mentioned that I have already activated Enhanced display.

Kronos, I'll take a look at the internal launcher, thanks.

I know this might be a really stupid question, but how do I set the background of the standard panel to 100% transparency?

Just select the panel root in Ambients panel settings and move the transparency slider on the first page to the left.

Geit

If you're on a slower (<1.5GHz) Mac mini and running a high resolution, there isn't enough video memory for enhanced display. Try lowering the screen depth to 16 bits.

@madCrow

Go to Ambient Settings --> Panels and look for "Alpha". Push the setting to "0".

Jacadcaps it seems you're right, my 32MB of video memory doesn't seem to be enough for enhanced display.

Can I ask though how I set video depth to 16 bits, as the option seems to be greyed out.

I did make a panel though and I like it far more than the Polynet launcher, thanks for your help all.

You have to open the Screens System Preferences and change the Ambient screen to a 16 bit screenmode.

Next question....

Can someone tell me how to un-install polynet launcher as it keeps starting up at boot and I cannot figure out how to stop it from doing so, I thought Grunch would be the way to install/un-install but I cannot find it in the list?

If I remember it right it's started in user-startup or startup-sequence.

I worked it out, for future reference to help all the newbies such as myself out there, you need to go to System > WBstartup and delete Add-Startup, all good now.

Now if I could just work out why rhLaunch doesn't recognise my kick12.rom and kick13.rom even though FS-UAE on my Linux Mint 16 rig recognises the ROM's just fine....

....Recognises the 2.04, 3.0 and 3.1 ROM's just fine, just refuses to recognise the 1.2 and 1.3 ROM's....

I've obviously got the path right in the cfg files as the other ROM's are being recognised fine...Anyone got any pointers?

Quote:

It sounds like "Add-Startup" might have had other things to do too, not just launching one program. So, for other users it might be worth check it better first before just deleting it. But I'm not that familiar with Chrysalis, just guessing here :)