ClassicWB GAEE

[nickoteen]

Hello ... again.
 
After sucessful ide68k and ClassicWB GAEE installation, more questions arise.
 
To really cut the long story short ... does anyone know why is my Amiga booting into this ... bluish kind of palette
 

 
when it should instead boot into Green Amiga Alien one.
 
like this
 

 
At startup it's blue. The moment I click workbench->prefs->palette, everything turns green, even before I click on "USE" or "SAVE".
 
Thanks in advance.
 
Oh, yeah. Clicking the "USE" or "SAVE" button accomplishes nothing. The Workbench is green until next boot. Then it's blue again.

[fitzsteve]

Are you using 3.1 Rom?  GAAE is based on Workbench 2.05 for 2.0 Rom.

For 3.1 Rom you should use Classic Workbench 68k as it's built in OS3.1

There is no Green Alien theme for 68k but you can use the awesome 1.3 theme:

http://classicwb.abime.net/classicweb/68k.htm

[nickoteen]

Er, yes. I'm using 3.1 rom. Ah, I see. I decided to install the wrong version of cwb. Man, of all the choices ... well, I guess I'll have to prep myself another card than. This time with the right version of Classic WB. Thanks.

[nickoteen]

You're right FitzSteve. I ran the current setup under winuae, this time choosing A600 as the target machine, and yes, all palette issues vanish. Darn ! But, is there a way to "make" this problem go away whilst still using 3.1 rom ? I checked out cwb 68k and although it is more advanced in many ways (I can set a custom image as a wb background in opposite to wb 2.1 which offers only colours or patterns for example), I kinda like the gaee version more. It has that nice app dock at the bottom and stuff.
 
So, any tweak/fix on this palette thingie that's been bothering me, perhaps ? Anyone ? Thanks.

[Oldsmobile_Mike]

Not using ClassicWB so I'm not sure if this answer is relevant, but I'd think you could just go into your Palette prefs and adjust them to the colors you want?  But then again, ClassicWB does do some funky stuff...

[mfilos]

On ClassicWB GAAE installation it asks you if you want the Alien Palette or an Earthlink Blue palette.
If you choose the Alien one... then you'll have the Green one or else the Blue.

If you like to change when installation if done... you can do this anytime.
Just head to System --> Prefs --> Palette
Then from the right click menu head to Project --> Open and double click the Palette drawer that you'll see.
Inside the drawer there are some palettes you might use like the Blue or Green or even Purple. The default palette is a classic MagicWB palette.

I guess you're set now

[nickoteen]

Yes mfilos, you're right. I did choose the Alien green. But this is something to do with ROM(s), 3.1 vs 2.0x. If you take a closer look at the 1st picture, the icon colours are all messed up. That pinkish touch is not supposed to be there. When I take my card out of the real Amiga and hook it up in winuae as a hdd, but choose A600 (ks 2.05) as a target machine, everything is ... well, green.
 
And to answer to Mike at the same time, yes, i can choose whatever palettes/colours available under prefs, but they apply to the current boot only. When I reboot my machine, everything goes back to the (messed up icon colours) beggining. Hmm ...

[mfilos]

Aha I see your point now
If you load GAAE under Kickstart 3.1 you get the distorted colors (non compatible MWB palette) but when you click on the Palette Prefs... the colors go back to normal
Whether you press save or not... on next reboot you have the same effect.
No problem with 2.05 kickstart though.

I guess using FullPalette program which locks down the palette, you wouldn't have had this issue but since you're having a real 2.05 kickstart I guess you're set
Just need to load the 2.05 kickstart as well in WinUAE to have the same environment.

[paul1981]

Looks like an incompatibilty between Workbench2.x IPrefs and Kickstart 3. Interesting. :elvis:

[nickoteen]

I'm not having the real 2.05 ks. I' m having the real 3.1 (40.63) ks. If it was the other way around i wouldn' be having this problem at all. : )

[nickoteen]

I was actually hoping there was some wb config file in which i could manually set the palette properties ... or something simillar.

[paul1981]

I was actually hoping there was some wb config file in which i could manually set the palette properties ... or something simillar.

You really would be better off using Workbench3.1. Infact you could install 3.1 over the top of what's already there. As I said earlier, Workbench2 prefs isn't playing well with Kickstart3.
But like mfilos states in his post, try FullPalette from aminet first, or something similar.
Or, softkick 37.300/37.350 (A600 Kickstart2) and that should fix it. That's what I'd be doing in your situation.

[mfilos]

Yeah I agree with Paul...
What I would have done if I were you is to use ClassicWB Full and since you're fond so much for a dock you could either get Amidock from GAAE and copy it to 3.1 installation or use ToolManager which ROX!

I wrote a guide about how to set it up which you can check it out here:
https://dl.dropboxusercontent.com/u/939939/Guides/Install%20%26%20Configure%20ToolManager.pdf

You can check how it looks on my own setup:

[nickoteen]

Awsome tutorial mfilos. Will try that asap. Thanks.

[nickoteen]

Mfilos, help please. I walked thru your tutorial, did as described, got tmanager up and running but none of the apllications wont start. I've tried protracker and final copy II which both run when i start them manually, but not when i try and start them by clicking on the dock icon. Theres something called the startup method or simillar which can be shell, workbench etc., and  i tried em all but to no avail. In the command parameter i' ve put the correct path and at this point am not sure what to do next.