Original from  Herbert Rosenau  to IVAN TODOROSKI on 12-08-1998
Original Subject: TCP/IP

                         ---------------------------------------

  IT>   The mouse freezes?!? Ouch! I don't think WathcDog can help you
  IT> then...   My experience with OS/2 is that as long as the mouse
  IT> works, you know   that at least a part of the system still works,
  IT> especially background   programs like WatchDog, even if the PM
  IT> hangs. But if the mouse   freezes, then either you pulled your
  IT> mouse cable too hard :) or the   system is totally, completely
  IT> and utterly dead. The mouse is one of   the last things to go...
 
HR> No. You can see it if you have a node and your keyboard AND 
HR> mouse are without any reaction - an then comes an incoming 
HR> call -> you'll see your modems activity and - after you 
HR> reboot or telnet - you can look in your mailer and tosser 
HR> log for the activity.
HR> 
HR> Altough your keybord and mouse are dead you my login over 
HR> telnet from another computer or terminal and work with your 
HR> system! For that your telnetd must be active and running. 

 Depends on what you mean by the mouse being "dead". If it won't even 
move around, then you are in a disabled loop - usually in a device 
driver (cli and loop). Either that or the mouse HARDWARE is "dead". 
 If the mouse moves, but the clicks are not accepted then you have a 
PM application hang. Keyboard input is in the same situation as mouse 
"clicks". 
 The mouse movement is handled by the mouse device driver and the PMDD
device driver. As long as the CPU is enabled for handling interrupts, 
the mouse will always "move". 

 In most cases where people are describing a "dead" mouse, they are 
describing the situation where the mouse does not move. 



   Denis       

 All opinions are my very own, IBM has no claim upon them
. 
. 
.
 

 




--- Maximus/2 3.01