Well been a MorphOS user for just over 2 weeks now. :) Loving it!


Question 1:
What to do first when the system stops responding. I do have MorphOS just stop responding, mainly when I'm using OWB. The only thing I have found to do is to reastart, but is that really the only thing? I am looking for the MorphOS version of "Ctrl + Alt + Del" Also whasn't there something about some new software/feature that would keep a program from freezing the whole system? Girmm Reaper or something, or was that OS4??

Question 2:
Possibly the most important question. Can I play Lemmings? If so, how?

Thanks

David

> What to do first when the system stops responding. I do have MorphOS just stop
> responding [...]. The only thing I have found to do is to reastart, but is that
> really the only thing?

Yes.

> I am looking for the MorphOS version of "Ctrl + Alt + Del"

On m68k Amiga, this works hardware-based without support by the OS. Of course, that's not the case on Mac hardware, so when the OS is completely locked up, you cannot reset the machine via keyboard.

> Girmm Reaper or something, or was that OS4??

OS4.

> Can I play Lemmings? If so, how?

http://www.elizium.nu/scripts/lemmings/ ;-)

I'm wondering the same.. I tried killing a task with Scout, but it never worked. Do we not have an actual task killer?

I use an Apple Bluetooth keyboard (A1016) and once that has been 'paired' via the dual boot system using MacOSX 10.4.11 usually I can allow the default 1st choice boot-up of MorphOS.

So, when MorphOS locks-up (not totally - meaning as long as the keyboard is active - which I can tell by pressing the Caps Lock key to check it is active/lights) I can reboot/reset MorphOS with the Ctrl+LCmd+RCmd (L+R Apple keys) as I would have done with an Amiga.

If the machine has totally locked-up then I have to switch off to cold-reboot, but that is not so often, on my MacMini by holding the power button down for about 4 seconds, and then a few seconds later press it again to switch it back on.

Task Manager will disable some processes I have found, but it is lacking in the regard of total process control, and would be a great improvement if it allowed greater control by shutting down/releasing some processes once they had 'Frozen' which is usually how they look when they have become inactive, and tied up resources (CPU/Memory).

Quote:

There is one tool for application that have a visible window : ikill

There is also another tool, freeze, that has to be used with great care as it can lock up the whole system on a random basis when used (for example, if the task has acquired a semaphore locking some system structure and freezing it at the same time, this will lead to a lockup of the system. Sorry.)

With MorphOS, you're running almost fully naked on a bike at 300Km/h... You've been warned. :)

Quote:

Grimm Reaper is indeed an OS4 thing, but on MorphOS if program has crashed (window title tells something like application is meditating or something, can't remember for sure), you can try to quit it once more from the close gadget and MorphOS asks if the program should be closed and its resources free'ed.

And more about the iKill program here: http://library.morph.zone/Shell_Commands/iKill

But if it has taken the whole system with it, you can't do much. And in any case if some program crashes, it's safer to reboot, because it may have trashed some other memory areas, which can cause nasty behaviour elsewhere sooner or later (you don't want to trash filesystem when writing into it, for example).

So, the simple rule: reboot if anything crashes in any case.

If the system hasn't crashed, you should be able to boot with ctrl-command-command keyboard combination, and with fn-alt-alt keyboard combination on laptops with an ADB keyboard.

Instead of killing programs after the crashes, you should pay more attention how the programs behave before the total crash/lockup. Look regularly the debug log if there are hits (hundreds of lines "cryptic" text). When you build and use your system, you should avoid programs making those. If you see some program hitting, and you don't absolutely need to use it, stop using the program and find a better working alternative for it. Or learn to avoid program's features which cause the hits. If program is not replaceable, like OWB, you should just check the log occasionally and reboot before it crashes totally if there are hits. OWB shouldn't do those all the time, but I'd disable the flash plugin if you're using it...

Quote:

With E-UAE at least. The Amiga version needs Amiga's custom chips, so it doesn't work directly under MorphOS on other computers. I don't know if there are any SDL ports or similar nowadays...

Thanks everyone.

http://www.morphos-files.net/find.php?find=lemmings

its not lemmings but its funny and has the same gameplay.

If your program crashes then its not written for Morphos maybe there is already a ppc port of it?
There has been a list of 68k programs that have been tested on ppc as far as I remember:
http://morphos.lukysoft.cz/

have fun

> If your program crashes then its not written for Morphos

It's not like MorphOS-native programs can't crash :-)

Quote:

it is allways the problem when you edit your text after you are done with it ...

If your program crashes then its maybe because it is not written for Morphos,
there could be allready a ppc port of it.

... thats what i wanted to write