From: mstaben@comtch.spk.wa.us (Matthew Staben)
Newsgroups: comp.os.os2.misc
Subject: Re: Shutdown failure (?)
Date: 6 Oct 92 02:08:11 GMT
Organization: Waffle BBS at CompuTech Spokane, Washington

adhir@cygnus.umd.edu (Alok Dhir) writes:

> In article <1aq5fiINNltr@usenet.INS.CWRU.Edu> jms20@po.CWRU.Edu (John M. Sull
> >
> >In a previous article, dic5340@hertz.njit.edu (David Charlap) says:
> >
> >>
> >>Some (poorly written) apps don't recognize the shutdown message.  They
> >>don't pass it to the default handler, and they don't respond properly.
> >>This effectively places the entire shutdown process on hold.  Try
> >>killing various apps and seeing which one has to go before shutdown
> >>proceeds. 
> >>
> >
> >hmmm...interesting.  I've had this problem as well, but all I had
> >running at the time was the system clock, DOS window and and OS/2 window.
> >			     ^^^^^^^^^^^^
> 
> That stupid clock does this to me all the time!  The OS/2 system clock, as
> neat as it looks, is written very poorly.  The settings page doesn't come
> up unless you go to the original program object (not when you have the title
> bar hidden, anyway), and it FREQUENTLY gets itself lost in the system somhow
> so that you can't shut down.  And not only can you not shut down, you can't
> even kill the process...not with the task manager, not with killem21.exe,
> not with anything.
> 
> What OS/2 really needs is a kill command which will KILL NO MATTER WHAT.
> I know you can do this in Unix using either kill -KILL or kill (9) or
> something like that...
> -- 
>  ============================================================================
>  Al Dhir                      			   Technical Consulting Staff
>  Internet: adhir@cygnus.umd.edu	  	 University of Maryland, College Park
>  Bitnet:   adhir%cygnus.umd.edu@Interbit      (301) 405-1500 * (301) 405-3014

 
Before you folks really go haywire, you should consider the properties of
the clock program.
 
A. The clock program sinks a cassion into the workplace shell which helps
   it defy removal, ugly winds, and whatever.  
 
B. Once the clock program is successfully moored, it then becomes, 
   effectively, a integral part of the workplace shell.
 
Taking A & B into effect, it becomes quite intuitive what it requires to 
remove the clock.  Remove the workplace shell to which it is moored.  
This essentially is an os/2-quake.
 
The recommended steps:
 
If you try to shutdown and os/2 verifies you wish to shut down, and then 
goes back to business, or
 
If you use a miniapp to shutdown, and OS/2 goes into CPU HOG mode (use 
PMLOAD) (it really isn't hoggin', but PMLOAD thinks it is),
 
You've got the clock on the bedrock.  
 
A.  Open up a OS/2 FULLSCREEN session.  
B.  Execute RUNNING2, and view the apps and their associated PIDs.
C.  SLAY both PMSHELL processes.  You will not be interrupted so feel
    free to take your time.
D.  Wait about 10 seconds.
E.  Type ALT-ESC (swap windows).  
F.  You will then be dumped to the workplace shell and a window which
    asks whether you want to kill the current fullscreen session.  If
    you decline, the system goes on as before, except all you can access
    is the icon which you declined to kill.

Once you accept that the fullscreen session be closed, the system will 
then go into shutdown.

I've done this routine a few times - and discovered it due to the nature
of the cloc.  It works for me almost every time.
 
Matt


mstaben@comtch.spk.wa.us
 
- A warning to anyone, still in command...