Now I can see them. Thanks!

Now the links work!

Quote:
Yes magorium, i agree, i also had this error, to reproduce the error is simple just click on AmiStart "FULL". In practice with AmiStart FULL, when you run an application, this It is "iconified" over bar Amistart, to reproduce the error just click twice application "iconified" attach screenshot where it is shown OWB "iconized". With AmiStart COMPACT i did not have the error, or so it seems

Found that VMware IcarOS he sees and runs smoothly on HD external USB with two partitions one of which is devoted to the launch IcarOS, and a second partition in FAT32 for data exchange ICAROS-Windows ;)


http://www.amigapage.it/index.php?pl=image-view&modo_view=3&categoria=computer&name=I01112015-1

http://www.amigapage.it/index.php?pl=image-view&modo_view=3&categoria=computer&name=I01112015-2

Of course. a bug is a bug.

It's just that it might not always something that's high on the priority list. For example Amistart does a lot of things quite out of the ordinary.

The 'zipping' of a program is something that's quite unstable in AROS. Sometimes when a program is iconified on the desktop, it completely disappears (OWB has a nag of that).

But in this case there are a lot of more 'parameters' that might be problematic. For instance, using wanderer as desktop behaves differently from using Dopus Magellan or ScalOS as desktop.

Not saying your finding is unimportant, just that it might not get to be addressed. If you like you can always file a bug-report at the bug-tracker (if it isn't reported already).

fwiw: loads of improvements were made in Wanderer, but they will probably (only) be seen with some new AROS distribution based on abiv1.

Literally, all I did was minimize (or iconify in Amiga speak) a window, and click its button on the Amistart taskbar to try to restore it. When I do that, Amistart crashes with that error. I have tweaked a few settings, and I don't know if any of them have anything to do with the crash. Any program crash is a bug, nevertheless.

Is there anyway to reproduce this error that you ran into (e.g. which steps did you take to get this error, and can it be reproduced) ?

Yes the turning off not working is designed by default (actually is wasn't, but for some machines this turned out to be the case with the new changes. very unfortunate, and more people suffer from that (including myself)).

Just hold down the powerbutton a bit longer to actually power down the machine (as you figured out yourself).

Here's a log of the AmiStart crash (captured by Sashimi).

[MM] Pool manager error
[MM] Attempt to allocate 32 bytes
[MM] Requested to allocate from pool 0xffffffff which is not marked as valid
*** Logged alert:
Program failed
Task : 0x05FFDAE0 - amistart
Error: 0x8100000F - Memory header not located
PC : 0x013F55B7
Module Kickstart ELF Segment 1 .text (0x013E3000) Offset 0x000125B7
Function InternalAllocPooled (0x013F5550) Offset 0x00000067
Stack trace:
0x013ED99E Kickstart ELF Function Exec_118_AllocPooled + 0x0000004E
0x013F1B31 Kickstart ELF Function Exec_149_AllocVecPooled + 0x00000031
0x0160D436 Kickstart ELF Function DoASyncAction + 0x00000056
0x015F90B4 Kickstart ELF Function Intuition_140_ShowWindow + 0x00000034
0x0613C9E2 AmiStart Function NewShowWindow + 0x00000025
0x0613CC7F AmiStart Function CallTaskCMD + 0x0000029B
0x0613D070 AmiStart Function StartProg + 0x00000262
0x0615BA6C AmiStart Function ProcessLayer + 0x00004587
0x0615E38C AmiStart Function MainProg + 0x00000058
0x06164D23 AmiStart Function main + 0x000012EF
Sashimi installed ([Ctrl]+C or "Break 1" to remove)
Sashimi removed.

Is Icaros supposed to turn off when the power button is pressed? Icaros 1.5.2 would power off immediately when I pressed my laptop's power button. But with Icaros 2.0.3, I have to hold it down for 5 seconds to forcefully turn off my laptop. I'm not sure if this is an ACPI bug or if it's just by design.

Quote:
If not mistaken then you can 'catch' that with sashimi (must be running before pressing log).

AmiStart has many bugs, but there's a particularly nasty one where it crashes when trying to restore a minimized window by clicking on its button in the taskbar. I'd attach a log file if I knew where the crash handler saves log files when I click "More" and "Log"...