On Thu, 22 Jan 2004, Dave Korn wrote:
> > -Original Message-
> > From: cygwin-owner On Behalf Of Charles L. Werner
>
> > My XP Professional SP1 system had a kernel crash apparently
> > related to the tcpip, related I believe to the inetd
> > service running Here is the event information
> -Original Message-
> From: cygwin-owner On Behalf Of Charles L. Werner
> My XP Professional SP1 system had a kernel crash apparently
> related to the tcpip, related I believe to the inetd
> service running Here is the event information
>
> Symbolic name:
> ER_KRNLCRASH_LOG
> Erro
Since Cygwin is doing nothing which should result in a BSOD, I doubt
that Cygwin is the actual cause of that problem. So far I never
experienced a BSOD which I could trace back to Cygwin or inetd or
it's services. Actually I never had a BSOD since I'm using XP.
Corinna
On Jan 22 11:05, Charles
I forgot to include the Error message in the XP event viewer from inetd
prior to the crash:
The description for Event ID ( 0 ) in Source ( inetd ) cannot be found. The local
computer
may not have the necessary registry information or message DLL files to display
messages
from a remote computer. Y
4 matches
Mail list logo