Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

.NET/dll/win200 question

Status
Not open for further replies.

DoraC

Programmer
May 7, 2002
98
US
Hi,

I created a COM class via ATL in order to wrap the API for some software I'm dealing with (a C-language API). I then accessed this coclass with C# (unmanaged, I know - but not created for distribution). Shortly thereafter, my machine (a thinkpad T20 running Win2000) started to crash with corrupted ntoskrnl.exe errors... Is there any way that my COM/.NET development could have impacted this? And - if so - how? Are there steps I can take to protect myself against this in the future (barring "don't use that software")? Or might this problem be due to something completely unrelated? And... just what *is* the "ntoskrnl.exe"?

Thanks - any help super-appreciated!
dora c
 
I don't think your development had any impact on your machine. However, you might want to address some pointed questions to the DLL vendor...

"ntoskrnl" is the NT Operating System Kernel. This is the executable that is the core of the operating system, and the fact that it's corrupted is a Bad Thing. You can attempt a repair re-installation of 2000, but it's been my experience that you're on borrowed time right now. Make a backup of your critical files and wipe the drive, then reinstall the OS, and run Windows Update until there are no more service packs/hotfixes remaining.

Of course, all this might have come about via a virus. Make sure you reinstall your AV package when you reinstall the OS. Do you still have your product recovery CD from IBM? That'll save you some time getting back up, anyway.

Chip H.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top