AfA OS 4.7 interference with IconEdit 44.19

[unusedunused]

I was trying to change icon types using IconEdit v44.19 tonight and discovered that I could not save icons.  As well, I noticed that the "selected" image would not load and the Old Icon images were corrupted.

I rebooted and disabled AfA OS with the LMB, and I could use IconEdit normally.

What should I be looking for here to help with more in-depth troubleshooting?  Has anyone else experienced this oddity?

I have also noticed that there are times when GlowIcon images are corrupt when selecting before I release the mouse button.  Again, disabled AfA OS and the problem goes away.

A4000D, PIV/P96, CSMKIII, OS3.9 BB2, AfA OS 4.7.

for change Icon types you need no Icon Edit.This work in Icon Information.
The save of a Icon on Iconeditor does not work thats right and stand in the AFA FAQ

The problem is the AROS Picture dataype does not contain Code to save a iff image.
so programs that do this fail also on AROS.

but there are not important programs out that do it, so nobody add it.

normaly somebody with IFF image save knowledge and datatype knowledge should add it to AROS.

If its important for you to use IconEdit, you can remove AROS picture datatypem but then you miss alpha support.

>I have also noticed that there are times when GlowIcon images are corrupt when >selecting before I release the mouse button.  Again, disabled AfA OS and the problem >goes away.

have you a screenshot ?.look if this happen on always the same icons.
maybe there are some Icons out that AROS iconlib show wrong.

but when you send me the icon i can maybe fix that if there is problem

[unusedunused]

I only use it on GlowIcons, so I am not missing alpha.  I have not gotten around to playing with PNG icons, yet.  I have created a few using GIMP, but that is all.

for the icon view is the alpha feature of picture datatype not need.
It is need for programns that use aias Icons for example YAM 2.6 do that.

and here you get without new picture datatype black or pink icon backgrounds.but work also not on AOS.here you need old YAM skin.

[unusedunused]

Bernd I want to express 2 issues that I'm having with 4.7 so far...

1. I have removed picture_datatype.exe in 4.6 (moved to a temporary folder) cause with it, I had freezing issues when watching images through registered WarpDT datatypes (PPC).
Once i removed the picture_datatype.exe images were showing just fine.
(I haven't tested it on 4.7 though I'm sorry if it's being solved already)
EDIT: No freezing on 4.7. Just tested it. (Either 4.7 solved the issue, or the new WarpDT datatypes)


2. Getting some weird issues with CGX4 (despite I haven't changed anything in my Startup-Sequence since my 4.6 installation along with Unofficial BB3).
 - On 4.6: I started my Amiga and it booted just fine. After the reboot of ROM update I saw the CGX boot pic (cgxbootpic.library) and workbench started just fine.
 - On 4.7: I start my Amiga and it boots into CGX boot pic (without doing the reboot of ROM update) and freezes there. If I reset (Ctr-Amiga-Amiga) then it boots just fine and no issues after that
Do I miss something here?
I'll downgrade to 4.6 to check it out again (since I took a full backup pre 4.7 update) but I didn't have any similar issue before...

Thanks again for an outstanding software mate.

For your first Problem stand in AFA 4.7 history that it is fixed.also there is a fix in newest warpdt that is trigger because draw 2 times 4.6

i think the 2. Problem come because you use now new picture.datatype.
does this happen always when you start your amiga that it freeze ?

Without AFA too, there is know when you use visual prefs and Trap, that iprefs can crash, depend on load timing.and when AFA load, this maybe change the timing.

you can add a little wait with this command before iprefs is start.

C:Wait 1  ;prevents IPrefs from crashes. Increase the value if IPrefs still crashes.
C:IPrefs  

its also possible that you start the program that show the bootpic before AFA is full load.maybe you start it later.

[unusedunused]

...BUT after I putted that CF+DVD-RW combo I have this strange lockup (like SetPatch not rebooting for ROM Update) and having to manually reboot in order for 3.9 to boot correctly.

If setpatch fail to reboot, is bad, because AOS is then in buggy state because not patched.it can work instable and crash sooner or later.

maybe the setpatch try to search on CF for romupdate because it have same drive name.But it find no romupdate and so no reboot is do

you can add in startupsequence after setpatch

c:morelibspace REBOOT  

and remove the line before setpatch.

then you get the reboot.if not its sure there is something that block the reset vector

but later you need call setpatch in a shell to see if all patches are correct install but only the reboot is not do.look if setpatch show is already been installed

16.h0:wbstartup> setpatch
AMIGA ROM Operating System and Libraries
Copyright © 1985-2002 Amiga, Inc.
All Rights Reserved.

SetPatch (V44.38) has already been installed.  Patch list:
        68040 Support Code Loaded
        Enabled Advanced Graphics Modes
        HWG IEEE Single Precision Mul/Div/FPU Fix
        ramlib signal usage
        stack size check for CON:, RAW:, RAM:, PAR:, PRT:, SER:
        graphics/WritePixelLine8()
        graphics/WriteChunkyPixel()
        Enabled data cache
ROM updates installed by SetPatch:
        shell, shell 45.7 (13.01.2002)
        console.device, console 44.8 (12.6.2001)
        ram-handler, ram 44.23 (8.4.2001)
        FileSystem.resource, filesysres 45.10 (3.8.2001)
        filesystem, fs 45.13 (3.8.2001)
        bootmenu, bootmenu 44.7 (25.2.2002)
        exec.library, exec 45.20 (6.1.2002)
        AmigaOS ROM Update, ROMUpdate 44.57 (25.2.2002)