xylog:

The Win2K Recovery Console **DOES** work.  We tried it last night because of
unforeseen problems on one of our NT servers.  In order to use it, you must
have at least SP4 on the server, and know what your admin password is.

Reference MS TechNet article Q293314 for details.

> Glenn M. Dowling
> IBM Global Services @ Lucent Technologies
> Work: 732.949.6456
> Fax: 732.834.6413
> Email: [EMAIL PROTECTED]


-----Original Message-----
From: xylog [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 31, 2001 09:39
To: NT System Admin Issues
Subject: Re: Blue Screen STOP message C0000135 Appears at Startup


This is definitely looks like a job for the ERD commander from Winternals. I
also read you can use the new Windows 2k Recovery Console feature on a
crashed NT system if you boot from the Win 2K CD but I have not tried this
personally.

xylog

----- Original Message -----
From: "Sean Martin" <[EMAIL PROTECTED]>
To: "NT System Admin Issues" <[EMAIL PROTECTED]>
Sent: Thursday, August 30, 2001 7:13 PM
Subject: Blue Screen STOP message C0000135 Appears at Startup


> This may be a shot in the dark.....
>
>
> I'm experiencing the exact problem stated in article
> http://support.microsoft.com/support/kb/articles/Q173/3/09.ASP and I was
> wondering if any has, 1)  had this same issue and, 2) knows a quicker way
to
> resolve. The DLL referenced is in fact winsrv.dll
>
> The pc is a Compaq Deskpro EP, PII300 128mb RAM. NT Wrkstn 4 sp6a.
>
> Regards,
>
> Sean Martin, MCSE
> Network Administrator
> Ribelin Lowell & Company
> Insurance Brokers, Inc.
> 3111 C Street, Suite 300
> Anchorage, Alaska 99503
> Ph: (907) 561-1250
> Fax: (907) 561-4315
> Cell: (907) 229-0885
> Email: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> DO NOT read, copy or disseminate this communication unless you are the
> intended addressee. This e-mail communication contains confidential and/or
> privileged information intended only for the addressee. If you have
received
> this communication in error, please call us immediately at (907) 561-1250
> and ask to speak to the sender of the communication. Also, please e-mail
the
> sender and notify the sender immediately that you have received the
> communication in error.
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
>


http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

Reply via email to