Nice util, should be integrated to OS4 by default imho

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@Samo79
Yes i agree, we should use Ringhio for all system alert and notifications

_________________
ikir

What it catches errors it is really appreciated. With a USB mouse, proper alerts are a case of waiting a few seconds, and invariably another alert comes up straight after. This patch (or something like it) should be part of OS4.

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

Very cool. I agree with the others it should be integrated into os4 and Ringhio should be used for all system messages too. Looks very modern.

Guru's yellow or red are part of the Amiga DNA, I don't agree to loose them or convert them to Ringhio, Grim etc. I would move instead to have those poverfull tools with an output remembering the guru messages.

Many thanks. I will install this right away . I rarely get these alerts, but when I do it is rather annoying the mouse is ignored.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

I'd like my XE back before commenting but never loose Guru's as it's part of the WB.
Still good if not comming. Explanatory is good and more colours. From the A500 it told something with blinking the lights. Never broke down like machines today..

@ChrisH

Yeah, the main problem is that currently you can't skip these errors (almost with an USB device) some time ago i open a report to the Hyperion forum and if i remember correctly a ticket was opened aswell so let's see if they fix it or not in the future, for now even if reported it wasn't fixed yet but almost they know

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

Good riddance to the yellow alerts which you can't cancel with a USB mouse and take ages to timeout. At least now you can do a quick soft reboot if things get nasty, rather than waitng for the eternal timeout or having to press the reset button.

This should officially be incorporated into the OS.

@ilbarbax 

The OS4 yellow alerts look fake and overtwrite the screen. That is not a real Amiga guru!

Plus if you have only USB mouse it lies to you when it says to press left mouse button. Because that doesn't work anymore. Not when I got one. I expect an Amiga to react instantly to mouse buttons like it has always done.

AFAIK the original routine hardware banged the CIA register so why doesn't it still do that now? OS4 includes CIA mouse emulation so it should work anytime!

Last edited by Hypex on 09-Sep-2012 at 03:36 PM.

@Hypex

Quote:

The OS4 yellow alerts look fake and overtwrite the screen. That is not a real Amiga guru!

They are not "fake", the design you refer to is only true of gurus on 1.3, after they were not called gurus anymore and were different, if the alrts for AmigaOS 2.04 and up can differ in appearance from AmigaOS 1.3 why shouldn't the design for AmigaOS 4 differ slightly again?


Quote:

Plus if you have only USB mouse it lies to you when it says to press left mouse button. Because that doesn't work anymore. Not when I got one. I excpet an Amiga to react instantly to mouse buttons like it has always done.

You know very well this is because alerts run in a forbid state and thus USB cannot work, PS2 do work as they are hardware interupt driven.


Quote:

AFAIK the original routine hardware banged the CIA register so why doesn't it still do that now? OS4 includes CIA mouse emulation so it should work anytime

I've no idea if the original alerts banged hadware or not, but one reason why they can't no is that there is no CIA to bang. If the cia is emulated as you descfribe (really not sure about that) then clearly the emulation wont work in a forbid state.

@thread

I would recomend against this patch. Why? Because the with is the alert is not in a forbid state! Whilst this is what make them a pain, it's clearly done for a reason. Alerts usually happen when low level things have gone wrong, they are quite rare now, but the most common is corrupt memeory list (0x01000005) imagine if you memlists are corrupted and another application can happily carry on accessing them, because of the lack of forbid? If that's not a route to loss of data I don't know what is.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Quote:

They are not "fake", the design you refer to is only true of gurus on 1.3

I'm not talking about design or whatever the alerts call themselves. I'm talking about how they are placed on screen. Alerts push the screen down on AmigaOS up 3.x. OS4 just writes them over the top, which isn't the correct way to do an alert.

Quote:

You know very well this is because alerts run in a forbid state and thus USB cannot work,

Yes I do know but why doesn't USB run on a higher level than a task? For things like input this is now a major design flaw. It's also not an Amiga thing to be unable to read input like this.

USB input should be running as a soft interrupt in that case but I haven't been told why it doesn't.

Quote:

If the cia is emulated as you descfribe (really not sure about that) then clearly the emulation wont work in a forbid state.

Yes it still would. Hitting the CIAs will cause a DSI and generate a hardware interrupt. The Exec handler would be called and the hit intercepted above the task level.

Quote:

I would recomend against this patch.

After some preliminary testing I would agree with you. I tried it with DvPlayer on my X1000 that is causing yellow alerts when I try to open a DVD with it. With this there is no alert but the system becomes unstable and eventually freezes. So it's no different than before!

Quote:

Because the with is the alert is not in a forbid state!

I would forbid the task that acted badly.

BTW, how would a task corrupt the memory list? Can it happen indirectly? No task should be touching it directly.

@Hypex
Quote:

Quote: They are not "fake", the design you refer to is only true of gurus on 1.3 I'm not talking about design or whatever the alerts call themselves. I'm talking about how they are placed on screen. Alerts push the screen down on AmigaOS up 3.x. OS4 just writes them over the top, which isn't the correct way to do an alert.

From the autodocs:

	New for V36: Alerts are always rendered in Topaz 8 (80 column font),
	regardless of the system default font. Also, RECOVERY_ALERTs are
	displayed in amber, while DEADEND_ALERTs are still red. Alerts
	no longer push down the application screens to be displayed. Rather,
	they appear alone in a black display.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

Quote:

I would recomend against this patch. Why? Because the with is the alert is not in a forbid state! Whilst this is what make them a pain, it's clearly done for a reason. Alerts usually happen when low level things have gone wrong, they are quite rare now, but the most common is corrupt memeory list (0x01000005) imagine if you memlists are corrupted and another application can happily carry on accessing them, because of the lack of forbid? If that's not a route to loss of data I don't know what is.

That's way you have the --suspend option for noalert.elf, to kill of tasks before they do anymore harm,

the data is lost anyway if you can't click away the alert.

its not alert that should kill the task but but the errror handling routines that calls the alert.

In --suspend mode the task will be suspended, and forbid will be broken after task was suspended, in this mode you will not be able to run legacy crap, but your system will stay relatively safe (It will suspend all task and processes even the recoverable alerts).

NOTE:
This does not effect DisplayAlert(), I consider displayalert relatively a safe alert, only for displaying stupid messages like missing font or stuff like that.

Last edited by NutsAboutAmiga on 09-Sep-2012 at 11:50 PM.
Last edited by NutsAboutAmiga on 09-Sep-2012 at 11:48 PM.
Last edited by NutsAboutAmiga on 09-Sep-2012 at 11:35 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Quote:

Absolutly! Yellow alerts are rarely gratiutus, the best way to eradicate the problem they cause is to fix the software that caused them! You have ofcourse checked the serial output and file a suitable bugreport?

It's is not a magical fix, it does not repair broken programs, it only helps agents system locking up's.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Quote:

By doing somethng nasty like, free memeory that was never allocated in the first place (unitialsed pointer) freeing memory twice

ARexx does that, check out AmiPodder.
Its so easy to read the errors when you have my patch

Quote:

buffer over/underuns that corrupt adjacent memory, in particulr the 'cookie' which decribes the memory block, writing into memory at random becauseof a stackoverflow or other similar source of dud data.

Grim Reaper will catch this errors.
DSI / ISI errors.

Last edited by NutsAboutAmiga on 09-Sep-2012 at 11:57 PM.
Last edited by NutsAboutAmiga on 09-Sep-2012 at 11:46 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS