System config. editor

[asm481]

No change with detection.exe shut down. Guess I will just live with it as is....about due for my semi annual reinstall anyhow. Actualy I am surprized my system hasn't fallen apart sooner due to all the freeware I sample and uninstall. This win2K is a much better system then 98 ever could be.

[NEPATEC]

I read this post with interest, since I recently experienced similar problems with a W2k box.

The fix was surprisingly simple once I ran FileMon & RegMon (freely available at http://www.sysinternals.com ) while troubleshooting the issue. What I had discovered was that performance counter libraries that load with Windows were being corrupted by the Norton installation. Since Symantec (in their infinite wisdom) chooses to overwrite system files without bothering to prompt you that there are newer versions already present on your machine, the workaround was to either deep-six NSW -or- find a way to get the software to work without gagging Windows.

Since my customer was a bonehead who failed to comprehend that SystemWorks causes more grief than good, I could not talk him into removing the software. If you are in a similar situation, here are the steps you can take to implement a fix:

1) Download and install a utility from the Microsoft Windows 2000 Resource Kit called exctrlst.exe. You can find this as a free download at:

http://www.microsoft.com/windows2000...exctrlst-o.asp

2) Install the tool (preferably to the \winnt\system32 directory, so that it can easily be called from the command line) and uncheck ALL the boxes for the perf libs that may be installed on the affected machine

3) Rename the following files in the \winnt\system32 directory from *.DAT to *.DA~ (or anything other than *.DAT):

perfc009.dat
perfd009.dat
perfh009.dat
perfi009.dat

4) Open regedit, navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug, and modify the value data for "Auto" from '1' to '0'

5) Close regedit and restart the computer

After you have rebooted, see if you still encounter the problem. Chances are that you will discover that the issue has been resolved.

Another quick nugget o' wisdom is to copy the msconfig.* files off a Windows XP machine & park them in the \system32 directory on your Win2k machine. You will find that although these do not ship with Windows 2000, the XP versions of these files will work without a hitch on your W2k box.

Hope this helps

-mike

[craigmodius]

I like Startup Control Panel for my systems.

Works on W2k/XP systems too.

[asm481]

I know about XP's MSCONFIG and startup control panel for changing startup programs. What started this whole deal here was another thread in the forums here. Fact is I don't recall what I was looking for now but I read something about where to find something in win.ini and typed in sysedit just to take a look-see! I do generally stop programs from starting at startup while I install them or in their own properties so I have little use for MSCONFIG but with this going on I loaded it and it will not start properly! It gives me error messages saying the path can't be found to autoexec.bat, then config.sys and so on. After ok'ing the messages it opens with 2 tabs--the general tab and start-up which in my case does only show my V-scan (norton).

NEPATEC--you talk about NSW which I assume you mean norton system works. I only have installed the norton V-scan. Do you think your post still relates to my problem. Haven't had a chance to try your fix yet but I will just to help me keep learning.

[craigmodius]

Well I guess according to this the 98 version of msconfig won't work properly and will do what it's doing to you.

ignore the error messages you get about not finding the following files
config.sys
autoexec.bat
win.ini
system.ini

They recommend you use the XP version available here at the bottom "msconfig from WinXP: Ripped from WinXP, can be used in Win2k"

Doesn't solve the initial problem with sysedit but maybe it gets you a little ahead of the game.