Printable View
What did I do now! When I try to run sysedit, it takes forever to open, I can't close pages to for ex. get to system.ini page. I opened up task manager processes page and spoolsv.exe uses appox 24 and sysedit.exe is bouncing around 70. I have to use task manager to close it each time. I am running win2k with 640mb ram 1.2amd T-bird on an Abit KT7a Raid mobo. My Norton V-scan is up to date and all else seems to be fine!
c'mon, someone must have seen this! I can run sysedit in safemode but not when in normal mode. I no longer need to get in here it just makes me wonder what is going on with my system. I have run trends on line v-scan and all is clean, disk scan and defrag all ok. The only programs I am running at start are my norton v-scan and Ad Muncher.
hmmm - if you turn off norton and other start up stuff, what happens.
What processes are you running aside from the standard startup?
Thanks for the reply NooNoo. On startup I have 24 Processes running and they all appear to be "normal" with one exception. wowexec.exe is the only one I haven't noticed before. I have a screen capture but am to stupid to figure how to post it on here! Disableing Norton doesn't do anything to improve it either
You need to link the image from your webspace, if you don't have webspace you cannot do it. click the img button in the reply window and type in the url of the image on your webspace.
This is what WOWEXEC is
wowexec - wowexec.exe - Process Information
Process File: wowexec or wowexec.exe
Process Name: Windows On Windows Execution Process
Description: Windows On Windows Execution Support Process provides support for 16-bit Windows applications together with ntvdm.exe
Common Errors: N/A
System Process: No
NTVDM is a virtual dos machine for NT - what dos proggies are you running at startup?
Ok I don't have web space that's why no pic. I have stopped all processes that I am allowed by my system to stop and sysedit is still using 100% of my cpu. I have zero programs in start up and still sysedit locks up
NooNoo I didn't see the last part of your post till now. wowexec.exe doesn't start till I try to run sysedit. and I don't see NTVDM in the processes anywhere. Oops that starts along with sysedit. I do notice that I have entries in my config.sys for files and buffers but as expected the autoexec.bat is empty. Does the entries in config mean I have a dos proggy running I don't know about?
your config.sys should be empty....
To stop those lines from running type REM followed by a space before each line in config.sys. This changes the line to a "remark" and is not run. See what effect that has.
I rem'd the config.sys and still no change. I didn't use caps --does that make a difference? I changed to cap's--no change
Time to list ALL the processes and all the items showing in your startup tab of MSCONFIG.
ok here are my processes:
sytem idle
system
smss.exe
csrss.exe
winlogon.exe
sevices.exe
lsass.exe
capture.exe
svchost.exe
spoolsv.exe 25
sagent2.exe
svchost.exe
ghost~2.exe
navapsvc.exe
ntvdm.exe 01
sysedit.exe 73
wowexec.exe
regsvc.exe
mstask.exe
taskmgr.exe
winmgmt.exe
mspmspsv.exe
svchost.exe
explorer.exe 01
navapw32.exe
detection.exe
the numbers next to the processes are the CPU numbers
i don't have MSCONFIG loaded on this 2K machine but i do have startup control and only things loading are scanner, norton, printer status check
If I were you I wouldn't be using sysedit or msconfig to affect chenges to your startup. Just run services.msc or right click on the My Computer icon and select manage and drill down to the services section.
Some good advice from Black Viper's site...
He has a good listing of Windows 2000 services and what they do and advice on which ones you can disable etc.Quote:
Why can't I use msconfig to change my services?The reason is because with msconfig, you can disable a service that is vital to boot your system - Remote Procedure Call. With the management console (services.msc) you cannot.
here
good luck~
sagent.exe is known to cause issues... since sysedit opens notepad, and therefore the ability to print, it might have an effect... tenuous I know....
ghost~2.exe, I find no information on at all.... you sure it is part of norton ghost?
detection.exe - another process that seems to be out of place
capture.exe - is part of your scanner startup? There are several - including a dos redirect printer prog.
NooNoo the ghost does seem to be part of Norton Ghost, Detection.exe does have me wondering....I did a search for it and can find it no where! It isn't listed under sevices.msc and don't know what it belongs to. My scanner is an old IBM maybe it is part of that?!? Capture I thought was the Analog X program I used for my desktop snapshot.
PS--I don't run that capture at startup
So, kill detection.exe... what happens?
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.
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
I like Startup Control Panel for my systems.
Works on W2k/XP systems too. :)
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.
Well I guess according to this the 98 version of msconfig won't work properly and will do what it's doing to you.
They recommend you use the XP version available here at the bottom "msconfig from WinXP: Ripped from WinXP, can be used in Win2k"Quote:
ignore the error messages you get about not finding the following files
config.sys
autoexec.bat
win.ini
system.ini
Doesn't solve the initial problem with sysedit but maybe it gets you a little ahead of the game.