FR> Because the server didn't stop.  It caught the crash, notified
 FR> everyone on the server that a critical error had occurred and the
 FR> server would be restarted in 2 minutes, waited 2 minutes, then
 FR> rebooted itself.
 FR> All why we watched with open mouths.
 FR> Really worked well.
 GD> Cool.  How does it handle client server applications?  How does it close
 GD> them out?
 FR> By removing the server.  I know, brute force.  If a workstation has
 FR> files open and doesn't close them, they are automatically closed when
 FR> the server dismounts the volume.  Which may lead to some corruption.
 FR> And is the reason the server sends a message out that says the server
 FR> is going down in xx minutes (configurable from 2 to 60); to give folks
 FR> a chance to logoff smoothly.
Could be a problem if everyone happens to be out for lunch.  Could cause
MAJOR corruption... :(
Gerry Danen
  email: gdanen@accessweb.com
  moderator STN.Y2K: Year 2000 issues and information
--- Maximus 3.01
---------------