A600 Workbench 3.1 mouse color

demolition · 21 October 2012, 20:04

I just updated the WB 2.1 on my A600 to 3.1 (using KS3.1) and now my mouse pointer looks very weird.

In the picture I have opened the pointer preferences and you can see the actual pointer just below the title bar while the program shows the correct colors. If I press Use or Save, the pointer gets updated to the correct colors and it all looks right again, until next reboot. It looks the same on composite and RGB.

This happens in both my A600's so it must be a software thing? The only thing I have in my startup-sequence is Acatune and QuikClik (launcher), while I have a NoClick in WBStartup, all of which I also used in WB2.1, where the pointer looked fine.

So what is happening here?

thomas · 21 October 2012, 23:41

Run Prefs/Palette and save it. Does that change something?

Did you upgrade both A600s from 2.1 or is one of them a fresh 3.1 installation? If both are upgrades, can you make a fresh installation?

demolition · 22 October 2012, 09:36

I will try saving the palette and see if it changes anything.

I only have one WB installation and I moved the CF card to the other Amiga for testing.

thomas · 22 October 2012, 13:07

I just recreated the problem in WinUAE. Saving palette prefs does not help. But if you delete envarc:sys/palette.prefs and reboot, the problem is gone.

Photon · 22 October 2012, 15:59

(devs):system-configuration should be overridden if LoadPrefs (or whatever) is called in the WB startup. And if deleting palette.prefs helps, it can't be that.

thomas · 22 October 2012, 16:52

During upgrade from 2.1 to 3.1 palette.ilbm is converted into palette.prefs. This conversion does not work correctly as it seems. Devs:system-configuration has nothing to do with it.

demolition · 22 October 2012, 22:50

Quote:

Originally Posted by thomas

I just recreated the problem in WinUAE. Saving palette prefs does not help. But if you delete envarc:sys/palette.prefs and reboot, the problem is gone.

Thanks, that did the trick.

21 October 2012, 20:04	#1
demolition Unregistered User Join Date: Sep 2012 Location: Copenhagen / DK Age: 43 Posts: 4,190	A600 Workbench 3.1 mouse color I just updated the WB 2.1 on my A600 to 3.1 (using KS3.1) and now my mouse pointer looks very weird. In the picture I have opened the pointer preferences and you can see the actual pointer just below the title bar while the program shows the correct colors. If I press Use or Save, the pointer gets updated to the correct colors and it all looks right again, until next reboot. It looks the same on composite and RGB. This happens in both my A600's so it must be a software thing? The only thing I have in my startup-sequence is Acatune and QuikClik (launcher), while I have a NoClick in WBStartup, all of which I also used in WB2.1, where the pointer looked fine. So what is happening here? Last edited by demolition; 02 May 2013 at 16:00.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Color Saturation and Color Tint/Hue	Retro-Nerd	support.WinUAE	22	02 August 2018 10:38
Printing in color with WinUAE on color laser	source	support.Apps	7	14 April 2013 00:32
ISO true color to 256 color algorithm	Lord Riton	Coders. General	19	15 April 2011 17:49
A600 on 1702 monitor color problems	TomVS	support.Hardware	4	28 December 2007 11:04
Using Mouse-Wheel Scroll in Workbench 3.1	vroom6sri	New to Emulation or Amiga scene	4	31 May 2007 11:06

21 October 2012, 23:41	#2
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,002	Run Prefs/Palette and save it. Does that change something? Did you upgrade both A600s from 2.1 or is one of them a fresh 3.1 installation? If both are upgrades, can you make a fresh installation?

22 October 2012, 09:36	#3
demolition Unregistered User Join Date: Sep 2012 Location: Copenhagen / DK Age: 43 Posts: 4,190	I will try saving the palette and see if it changes anything. I only have one WB installation and I moved the CF card to the other Amiga for testing.

22 October 2012, 13:07	#4
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,002	I just recreated the problem in WinUAE. Saving palette prefs does not help. But if you delete envarc:sys/palette.prefs and reboot, the problem is gone.

22 October 2012, 15:59	#5
Photon Moderator Join Date: Nov 2004 Location: Eksjö / Sweden Posts: 5,604	(devs):system-configuration should be overridden if LoadPrefs (or whatever) is called in the WB startup. And if deleting palette.prefs helps, it can't be that.

22 October 2012, 16:52	#6
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,002	During upgrade from 2.1 to 3.1 palette.ilbm is converted into palette.prefs. This conversion does not work correctly as it seems. Devs:system-configuration has nothing to do with it.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)