AfA OS 4.7 interference with IconEdit 44.19

[LoadWB]

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.

[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

[LoadWB]

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.

Interesting.  I would have expected it to translate across.

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

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.

>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

I will work on getting a screen shot for you.  Most likely around Sunday-ish.  I am about to end a 23 hour day

[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.

[mfilos]

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.

[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.

[mfilos]

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.

Thanks a lot for the reply Bernd...
Sadly setting a wait statement didn't make any difference.

Let me explain a bit better, for you to have better understanding of my freezing issue:
I also included my Startup-Sequence in order to check if something is not right. Checking it you will see that except AfA OS 4.7... I have also installed the unofficial BB3 (alas the LoadModule declarations) plus registered HSMathLibs (althought I installed them today so they don't do any harm), plus QuickROM (that even without doesn't make any difference).
...
Some time ago: With AfA 4.6+BB3 installed, I classically started the system and after the first reboot of ROM Update, system restarted and after some time, I got the CGX bootpic (by CGX installer - not any other program that puts a boot picture) and workbench appeared just fine.
Now: With AfA 4.7+BB3 installed, I start the system but ROM Update's reboot doesn't happen! Apart from that I get the CGX bootpic like SetPatch haven't run... and rest of the Startup-Sequence continued loading... :S
- If I leave it like that it stays frozen to the CGX bootpic.
- If I reset by Ctrl-Amiga-Amiga then the system boots like a normal ROM Update restart occured, then I get the CGX bootpic and then workbench appears just fine.

Dunno what the hell is going wrong but it's kinda irritating.

Thanks in advance my friend for your replies.

[mfilos]

Ok just found out after making some tests that AfA OS had nothing to do with it!

My 1200 consists of an 16GB CF mounted via an ACard to BPPC's SCSI interface (950mb partition for OS3.9, 950mb partition for MOS PuP and 13GB partition for Work/Games etc)

Recently I've added an 4GB CF mounted along with an IDE DVD-RW to an 4way buffered inteface into 1200's native IDE interface (950mb partition for OS4.0, 3GB for Work/Games of OS4.0) since OS4.0 doesn't support BPPC's SCSI.
I can choose whatever Partition I like in Early Startup Menu and have the OS of my choice...

...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.

Today I removed it just to check it out and everything work like it should be! I know that this is irrelevant with the original thread... but does someone has any clue of why this might happen? Is any sort of delay that is needed or blizzppc.device has any conflict on startup with pure scsi.device?

[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)

[mfilos]

you can add in startupsequence after setpatch

c:morelibspace REBOOT  

and remove the line before setpatch.

I'll be damned!!! It worked! :roflmao:
Everything worked just fine my friend Bernd with that approach (despite not being the politically correct one).

I'm attaching a screenshot of my WB running WhichAmiga, SetPatch command as you said, along with About and SysSpeed's ShowInfo. I don't see the SetPatch loading the ROM Update like the one you posted :S Damn!
Hmmmm, in my previously attached Startup-Sequence if you check, you'll see I run it as SetPatch SKIPROMMODULES..... as BB3 said. You think that could be an issue? Something I declared wrong?

Really odd, but till I find a better solution... THANKS TONS mate!

[mfilos]

Okey... That is an embarassing moment...
Since I saw that ROM Update wasn't happening... I checked my DEVS folder and remembered... that I have moved the "AmigaOS ROM Update" to another folder since I was experimenting recently with some home-made custom ROMS.
WELL, you can't have a ROM Update without the actual ROM Update file can you? :hammer::hammer::hammer:

Anyway, putted the file back in DEVS and returned the Startup-Sequence back to what it was in the first place (Morelibspace on top and SetPatch as it was) and everything works like a charm and SetPatch now declares clearly the ROM Update.... DUHHHH!

Thanks for all the help Bernd! I can go hide now :laughing: