how to disable Grim/DSI window ?

As i know it's possible to swith-off showgin of Gr/DSI window ? It's sometime a bit annoing, becouse some programms works fine, but sometime do DSI. So just want to disable it for some time. How i can do it ?

@kas1e

You can't. Any errors generated by software that envoke the Grim Reaper are bad enough to warrant informing the user.

Simon

You sure that i can't ? I know that for morphos you can off/on this kind of options for somethink like that GR errors. For sure it's possible to off somehow, and i just think about arexx programm which will be automatically press on "ignore dsi errors button", but it's ugly solution of course. I just think some kind of 1/0 value to some file somethere is present to on/off gr windowses.

@kas1e

The quick n' dirty solution to "disabling" the Grim Reaper
is to go into SYS:System and then delete or rename the
Grim Reaper file. Of course, this is not recommended,
but you'll get rid of the Grim Reaper.

Regards,
Kotler

@Kotler

Indeed :) thanks

@Kotler

Quote:
This solution reminds me of the all-time best stain remover: Hydrochloric acid. Sure, it removes the fabric as well, but the stain is definitely gone.

Best regards,

Niels

@kas1e

And now remember to never report any bugs, as you don't know what happens in your system.

@Elwood

I know what i do and for what :)

@all

There are settings for just having usefull informations on grim reaper when the crash arrive ???? (for a les long log, for allways have the log not saved on ram: per default,......)

An related to crash on AOS4.1, another tools could be ued on AOS4.1 to have other or better crash informations ???? (like sashimi and muforce on AOS3.x).

Explain me how you catch problems reports on aos4.1 and the tools you use if other than grim reaper, thanks...

@Mrodfr

MemGuard+SashimiPPC, download from OS4Depot...

@kas1e

I know what i do and for what ...
Wow, I thought this universe allowed only one 'Kernal Guy' who was qualified to say that!

@ShInKurO

OK. I will try that soon....

@ShInKurO

MemGuard will only catch access to memory outside what has been allocated by the program. While usefull, it can never replace the functionality of GrimReaper.

Simon

@Snuffy
Some old 68k programms do almost in 50% of the times some DSI which are not so necessary to see for me anymore. So, it's good that i just can disable GR (even by this dirty way), and have working programms visually.

@kas1e

Memguard + sashimi look like detailed reports like with sashimi + muforce on AOS3.x

IMHO this tools should be used on AOS4.X, when using actually developped AOS3.x programs on PPC amiga, and found problems when running the 68k program.

Interesting to know if AOS4.x programmers found an addtionnal interest with a sashimi+ memguard report with the Grim Reaper report...

@Mrodfr

As Rigo just said, Memguard only traps errors of one single type - using memory outside the edges of an allocated area. It is of no use for anything else, like references to unallocated or non-existent memory.

Sashimi is only a program to capture serial port output and write it to a file. It doesn't add any information.

The kernel traps (and the Grim Reaper to report them) give you a lot more information.

I tried to trap the errors using the command given by you. But still my problem is solved. Show me some other way please !!!!!

@deanhanson

Your problem is solved, but you are still looking for another way?

To do what?
Continue to spam the forums?

Shame on you, botty, go away and play elsewhere...