Implement a force-quit feature for Sheepshaver?

yksoft1 · Post by **yksoft1** » Sat Jan 01, 2011 3:24 am

Currently the close window button of Sheepshaver window is mapped to Mac "Power" key. When the emulated Mac hang (not Sheepshaver itself), the only way to exit SS is to terminate its process. I wonder that how could the close window button just quit SS.
By the way, my MinGW/MSYS toolchain could not run "make links" step required for building SS because of the incomplete implementation of ln command. Hope that someone familiar with Makefiles implement a new target to copy the required BasiliskII files to Sheepshaver directory instead of making links of them.

kikkoman · Post by **kikkoman** » Sat Jan 01, 2011 4:40 am

I was just wondering about a Force-quit feature myself. Because when I'm in the emulated Mac OS, pressing the CMD+OPT+ESC (on my keyboard, it's ALT+WinKey+ESC) never actually brought up the old force-quit box. Instead, it "tabbed-out" into the host OS... in my case, Windows Vista.

kelvin31415 · Post by **kelvin31415** » Thu Jan 06, 2011 3:45 am

Control-Escape is an "emergency quit".

24bit · Post by **24bit** » Thu Jan 06, 2011 12:42 pm

Control-Escape is an "emergency quit".

Yea, thats true. I think Kikkoman was looking for a possibility to kill a hanging process, like it is done on real Macs running
Classic OS. This procedure was not very successful though, as classic had no real memory protection scheme implemented.
A hanging app most often would pull down the complete system, with no chance to save your work and even corrupting
the catalog-B tree of your hard disk.
So probably Apple was right to switch to the Unix kernel, but I wish there would have been another way to have memory protection
and preemptive multitasking.

Thu Jan 06, 2011 3:45 pm

24bit wrote:Yea, thats true. I think Kikkoman was looking for a possibility to kill a hanging process, like it is done on real Macs running Classic OS. This procedure was not very successful though, as classic had no real memory protection scheme implemented.
A hanging app most often would pull down the complete system, with no chance to save your work and even corrupting
the catalog-B tree of your hard disk.

Even when one succeeded in force quitting a separate hanging application and keeping the system and other applications running, it was advised to restart the machine anyway and check file system integrity. Only since MacOSX one can force quit an application and be confident that everything else is unaffected.

kelvin31415 · Post by **kelvin31415** » Thu Jan 06, 2011 4:16 pm

24bit wrote:
Control-Escape is an "emergency quit".
Yea, thats true. I think Kikkoman was looking for a possibility to kill a hanging process, like it is done on real Macs running Classic OS.

Agreed, but my comment was intended for yksoft1. I don't think the two of them are talking about the same thing.