I have not had this issue, but after reading the article, I would agree that
this is best. In addition, at some of my shops I created a ghost image of
an NT workstation with two instances of NT workstation 4.0. One was
production, and the other was the "Admin Repair version" for things like
recovering a corrupted SAM or driver or whatever. Perhaps an ERD, but that
would be my only other suggestion. Good luck, and I hope this helps
____________________________________________
Andre Correa
Senior NT Engineer
Lexitron, Inc
(201) 892-6399
-----Original Message-----
From: Sean Martin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 30, 2001 7:13 PM
To: NT System Admin Issues
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
