Hyperion Entertainment Message Boards

Starting OS 4.1 (update six, maybe five earlier), Grim Reaper opens for Workbench before Workbench windowscreen is open. It is a DSI, I ignored it the last time and ISI prevented continuing.
I have had the DSI happen at least twice.

Having perused my startup-sequence which looks quite standard indeed, I thought of something. I did disable the startup sound nine days ago not in startup-sequence but the Sound preferences. I can't remember if the first occurrence was before that. I should make a note of any unlogged crashes if they seem severe.

Thematic wrote:Starting OS 4.1 (update six, maybe five earlier), Grim Reaper opens for Workbench before Workbench windowscreen is open. It is a DSI, I ignored it the last time and ISI prevented continuing.

Please, when you get the DSI, save the crash log with stack trace from Grim Reaper (on HD) before letting it go on to the ISI. After rebooting, post it here (inside "hidden" tags).

Best regards,

Niels

If this happens again I will write stuff the old fashioned way, unless I don't have time for that. Or can I choose to save to HDD after the fact? I lose anything in RAM: because of reboot.

edit: Grim Reaper docs? It's a bit onerous to bring this one up for a look.

Thematic wrote:If this happens again I will write stuff the old fashioned way, unless I don't have time for that. Or can I choose to save to HDD after the fact? I lose anything in RAM: because of reboot.

edit: Grim Reaper docs? It's a bit onerous to bring this one up for a look.

Once you're inside the full Grim reaper window, there's a button to set the path to save your crash log file to, just set that to a location on disk instead of the default in RAM:. Then save your log file and wait a few seconds to make sure all disk activity is finished. After that you can move on and get your ISI and reboot.

Best regards,

Niels

There is a 'LOGDIR" tooltype in the sys:system/grimreaper icon.
It would be appropriate to set it to somewhere more permanent.

colinw wrote:There is a 'LOGDIR" tooltype in the sys:system/grimreaper icon.
It would be appropriate to set it to somewhere more permanent.

Good point. Although I personally prefer having it set to RAM: and only change it to HD when I know that I will be able to save the log and have the system stay up long enough to not invalidate the disk. But I'm probably over-cautious .

Another possibility, of course, if the system stays up long enough, is to save the log in RAM: and then copy it (with WB, Shell or whatever) to HD, before moving on to the ISI.

Best regards,

Niels

I had a freeze when browsing AW.net which made TuneNet loop its buffer and input devices to lock up, all the while scrolling the browser to the bottom of the page which took maybe two seconds. And after I pressed the reset button, up comes the Workbench DSI again but as a knee-jerk reaction I press it again, wanting to carry on with what I'm doing.

This however does look like it could be a hardware platform (motherboard) specific problem. And yes, I think it's been over three months without this happening.