frog357

I have seen processes that can't be killed, normally they are being debugged by dwwin.exe or similar. Check to see if you have a doctor watson active the next time you can't kill a process. Also try using a root-kit scanning program like "Rootkit Unhooker" and see what hooks are active on your system. Have you tried Windows Installer Cleanup Utility? I think if you become more familiar with Process Explorer you'll find a way to terminate your tasks. If this program can let you terminate winlogon.exe and cause a blue screen, I am fairly confident it should be able to kill your stuck task. If not, close the thread or handle and forcefully crash the program.

I've seen this before when repairing computers for people. Try searching Google for "xp logoff after login" Have you ever messed with BartPE or use a WindowsPE disk before? This might be your easiest route to get back into that computer!

Did you install SP3 by any chance? There is a news article on this site regarding troubles people are having to uninstall IE7 after installing SP3.

Besides for disable service, you could set each log to 64k and have it overwrite events as needed. Or you could move the logs to another location (possibly network share?) (or is it possible to write to nul?). http://support.microsoft.com/kb/315417 I tried to save a file to \\.\nul just to see what it'd do, it sat there for a few seconds and didn't return anything but also didn't close the save file box. It might be worth a try if you can safely test the theory, to set the paths to \\.\nul It appears you need the event file name, but it's worth some tests!

What you are looking for sounds like it would be best asked on a hacking board or some other forum. Any file on your computer can be accessed using the \\.\ method, so I don't see what you are trying to do here. It would be different if you were asking for help to fix something, but it sounds like you are asking for help to break something.

The shutdown temp should be much higher than 70, If I am not mistaken, the CPU will normally be running around 100. At least thats what I have seen before. Are you seeing a blue screen before the computer restarts itself? I have fixed this in the past using a WinPE cd with a remote registry editor. The thing was to disable reboot upon blue screen so that you could see what the blue screen says and attempt to go further from there. A lot of times, you just need to run chkdsk with the repair options and that normally solves it (this can also be done from WinPE).

Are you using any COM components or ActiveX or calling .dll files or anything? I write a lot of VB 6 programs that work on all versions of windows and I don't think I've seen much of what you say, I do see it the other way, works in XP but not in 98, that's common but going the other way not much is missing or changed to prevent it from working. Do you have the vb6 runtimes updated on the XP machine? Also, do you have your VB environment updated to the latest SP on your dev machine? Compile from the 98 machine, does it make any difference?

Reverse engineer this process: http://support.microsoft.com/kb/120716 Basically you create a directory like this: mkdir \\.\d:\temp\com1

The spuninst should be located in: C:\WINDOWS\ie7\spuninst I found the following: http://support.microsoft.com/?kbid=318378 Reinstall Internet Explorer 6 by using the Ie.inf file If you already have Windows XP Service Pack 2 installed, and you do not want to install Internet Explorer 7, you may be able to resolve problems with Internet Explorer 6 by using the Ie.inf file to reinstall Internet Explorer 6. To do this, follow these steps: 1. Click Start, click Run, type %systemroot%\inf, and then press Enter. 2. Find the Ie.inf file that is located in Windows\Inf folder. 3. Right-click the Ie.inf file, and then click Install. 4. Restart the computer when the file copy process is complete. I'll keep looking for you if you need!

In the past I have always used a "WinPE" bootdisk to do my dirty work. With a Windows PE boot disk, you could load up your computer and ghost it over the network real easy like! Do a google search for "BartPE" and then a little research will have you opening new doors you didn't know were available to ya

Well sorry about the noise but this post might help someone in the future, I did a lot of searching and was unable to solve this with what Google showed me. If anyone has a problem with Explorer.exe not starting up, it is very possible it's malware related, and an install of XP SP3 seemed to fix whatever the removal of the malware broke. Also, errors about files in use while trying to install the SP3 was another sign something was up, as I had turned off every possible non-system startup program and still had the error.

I am working on a friends computer, it started off with a massive spyware / virus infection that I cleaned using Spybot, Hijack This, Ewido Micro Scanner, Super Anti-spyware and a few virus scanners. The current problem is when the computer starts up and you select the user, explorer.exe does not appear to load. I can use Task Manager to start it manually and everything "appears" to be fine. Upon reboot still no explorer.exe I have checked Google and followed all the instructions I was able to find, but I am still having this problem. (Shell is set properly in registry) To help me solve this, I attempting to install SP3 to see if this helps anything and I am getting to the point of setup that says: "Performing Inventory" and then I get an error message of: ntoskrnl.exe is in use by another application. At this point I suspected a Rootkit, so I went and ran Rootkit Unhooker and found my suspicions were correct. I am fairly sure I have cleaned up the rootkit, as I no longer see hooks in RKUH. I am now installing SP3 without any troubles. I posted the information above to help out other people who get the error "ntoskrnl.exe is in use" as I searched for help on this and was not able to find anything. I will post a follow-up if SP3 fixes my troubles.