[RC5] RC5- NT Nightmare

Jeff Hinrichs jlh at home.com
Fri Jan 30 20:53:36 EST 1998

IMHO, I would strongly suggest not to run this on a mission critical
server - unless you are looking for a new job anyway.  No matter how safe
the client looks, and I haven't run into any troubles myself, I would 
wager the company jewels.

-----Original Message-----
From: David <holowisk at cadvision.com>
To: RC5 at lists.distributed.net <RC5 at lists.distributed.net>
Date: Friday, January 30, 1998 4:56 PM
Subject: [RC5] RC5- NT Nightmare

>Today, i rebooted my nt workstation for the first time since installing
>des nt service, and got the following error:
>STOP: c000021a {Fatal System Error}
>   The Session Manager Initialization system process terminated
>   unexpectedly with a status of 0xC000003a (0x00000000 0x00000000).
>   The system has shutdown.
>When booting up. The microsoft help desk says this about it: "If you
>the drive letter of the system drive to "unassigned", after rebooting the
>following error message appears:" Is it even remotley possible that the
>client caused this? i know that it writes to the registry to install
>as a service, could it have written over a registry entry? The solution
>to deltree winnt and reinstall, the emerg. recovery disks didnt even work.
>Im worried that this will happen again, and dont want to install it on my
>mission critical server until i know for sure.
>Dont forget to visit http://www.eyegive.com and sign up to make some money
>for d.net
>To unsubcribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
>rc5-digest subscribers replace rc5 with rc5-digest

To unsubcribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest

More information about the rc5 mailing list