English Amiga Board

English Amiga Board (http://eab.abime.net/index.php)
-   Coders. System (http://eab.abime.net/forumdisplay.php?f=113)
-   -   icon.library 46.4 test versions (http://eab.abime.net/showthread.php?t=64079)

PeterK 07 September 2017 18:22

FullPalette usually is only recommended for 16 color screenmodes to get a better balanced palette.

You could try to call Prefs/Palette and save that, because maybe ENVARC:sys/palette.prefs could be damaged. At least the 4 system colors, which are used for windows, menus and so on, should never appear wrong. Are you using HappyEnv? Better use ENV-handler instead.

Phantom 07 September 2017 18:27

Yes, that was a nice guess. I'm using HappyENV because I had problems with ToolManager's prefs file. I will try ENV-Handler instead then, thanks for that tip.

PeterK 07 September 2017 18:36

Another tool affecting the menu colors is MagicMenu, of course. Maybe some wrong settings in MagicMenuPrefs can make the color palette unstable???

Phantom 07 September 2017 18:41

Will try MagicMenu settings as well, but MagicMenu is installed over a year now without the slightest problem (in all my Amigas), so I guess that's not the perpetrator I'm looking for. :D

But I will start by removing HappyENV and installing ENV-Handler and resave my palette.prefs again.

daxb 07 September 2017 19:26

Quote:

Originally Posted by PeterK (Post 1183120)
FullPalette usually is only recommended for 16 color screenmodes to get a better balanced palette.

Why? I would say FullPalette ist useful from 1 bit to 8 bit screens.

Phantom, I guess your problem comes from a bad config and not from Peters icon.library. Check out at least BB3-4 stuff, P96 settings and everything suspect running.

nogginthenog 07 September 2017 19:43

Phantom, a A4000/060 with a PicassoIV should handle 16bit modes fine.
I have a A4000/060 with CV63/3D (PicassoIV is faster) and 16bit modes are fast (24bit is a little slow). I use cybergraphics, but I used Picasso96 in the past.

Any possibility your 68060.library is missing or bad? Maybe it's worth trying Thor's one in the mmu.library.

Phantom 07 September 2017 19:49

I used to have 68060 library 46.20 from Cosmos installed, but I got Gurus often (warm or cold boot), so I switched back to the official library from Phase5 (46.15) and Gurus vanished.

What's your current resolution then in HiColor? Do you use the last unofficial Picasso libraries (2.1e) or the official ones?

nogginthenog 08 September 2017 00:06

I find it strange that in your configuration: the fastest cpu, zorro 3 the (fastest?) gfx card is slow in 16 bit modes.

Maybe try: http://aminet.net/package/util/libs/MMULib

p.s. I use Cybergraphics, not P96.

PeterK 08 September 2017 01:29

A dumb question: Is Prefs/Workbench really set to Images="In other memory"? (Chunky screenmodes may run very slow from ChipMem)

And you could also check if AsyncWB causes any problems.

Phantom 08 September 2017 01:29

@ PeterK

I have removed HappyENV and installed ENV-Handler instead. Since then, and after 5 or 6 reboots everything seems to be back to normal again.

Regarding by 3 libraries you asked earlier:

intuition.library 40.85
graphics.library 40.24
workbench.library 45.137

Are there any recent updates for the first two libs?

Phantom 08 September 2017 01:32

@ Peterk

Of course images are set to other memory in Workbench preferences and ASyncWB is v45.23.

PeterK 08 September 2017 01:41

I'm using exactly the same libraries on OS 3.9.

Many of the intuition.library updates from Cosmos were buggy, that's why I don't try them anymore, and I couldn't see any advantages.

There is a graphics.library update from Don Adan, but never tried that since most of the important functions are replaced by P96 anyway.

AsyncWB is ok as long as it makes no problems. I still use it, too.

Phantom 08 September 2017 02:10

I think that I re-created the problem again, and I'm possibly sure that this behavior of mine causes this wrong colors situation.

I have created my custom ROM with all the recent updates with Remus, which in return is blizkicked on boot. The problem is (what I did a while ago) is after I updated my custom ROM I did a warm reboot. And that's how the problem came again. Even after 2-3 warm reboots still the same problem.

I turned off my Amiga for approximately 20-30 seconds and boot again. Everything is normal and as it should be.

Yes, my behaviour to always do a warm reboot (especially with updated custom ROM) seems to be the problem so far.

PeterK 08 September 2017 03:07

It may depend on the versions of ROMsplit and Remus whether your new custom ROM is working correctly or not. I didn't use both for a very long time.

But recently I noticed a small difference between a workbench.library v40.5 extracted with an older version of ROMsplit and one that was offered by Cloanto. The one from Cloanto has two sections: code and data, but the one that I extracted myself with an early ROMsplit version created only a code section. Everything else was identical, but I guess that my version was not correct. Similar bugs may also be included in other libraries that have been extracted with early ROMsplit versions.

The latest ROMsplit version is the beta version 1.9a, but I've no permission from Jeff Weeks (of DoobreyNet
) yet to make that public.

The latest Remus version is 1.51.

Phantom 08 September 2017 07:48

Yes, I'm using Remus 1.51 and ROMSplit 1.0rc15.

PeterK 08 September 2017 18:40

Sorry Phantom, but I can't help you further to solve your problem, because I don't have enough information about your custom ROM, your startup-sequence, user-startup etc. and I'm not an expert for ROMsplit and Remus.

Better open another new thread to discuss your problem or why should it be icon.library related?

Phantom 08 September 2017 19:07

No need to apologise Peter, your tips were accepted with joy, including other members as well. I don't think that's icon.library's fault after all, but what you said earlier:

Quote:

But recently I noticed a small difference between a workbench.library v40.5 extracted with an older version of ROMsplit and one that was offered by Cloanto. The one from Cloanto has two sections: code and data, but the one that I extracted myself with an early ROMsplit version created only a code section. Everything else was identical, but I guess that my version was not correct. Similar bugs may also be included in other libraries that have been extracted with early ROMsplit versions.
Makes me thing if that's the case, but I have the impression that turning off the Amiga after modifing ROM with Remus helps a lot.

PeterK 08 September 2017 19:20

Maybe the word "bugs" is wrong in my statement about early versions of ROMsplit. I just noticed this difference, but then never tested either versions of the mentioned workbench.library 40.5.

And of course, there are hundreds of other reasons possible for color problems after a reboot.

I would suggest to boot with a standard 3.1 ROM and then load one library after another step by step with LoadModule or LoadResident or SetPatch until the problem appears again.

Phantom 12 September 2017 00:25

@ PeterK

I found it. It has to do with pointer prefs. I'm using one of the pointers found in Prefs/Pointers (supplied with AmigaOS 3.9 obviously), because the default one is really small for my resolution stated earlier. Are those pointers buggy or should I try to install Full Palette first? I'm asking because those pointers seems to be transparent in some areas.

When I did a reboot, I had the same problem with colors. I run Pointer prefs and selected reset to defaults and all colors came back to normal!

PeterK 12 September 2017 01:51

2 Attachment(s)
In Prefs/Pointers switch to LowRes mousepointer and save.

In PVS (PicassoVariableSettings) set the ToolTypes to BigSprite=ON and SoftSprite=OFF.

Also check if you have "Planes To Fast" enabled and "Direct ColorMask" off under Environment, because your HiColor and TrueColor screenmodes were so slow. Don't know if this setting can help to speed things up? Usually, HiColor is the fastest screenmode!


All times are GMT +2. The time now is 05:58.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.

Page generated in 0.22125 seconds with 11 queries