Systemworks 2003

fable · Post by **fable** » Mon Oct 28, 2002 8:47 am

Whenever I boot my Windows 98 OS, a small window opens containing three SW 2003 non-executable icons. I don't know why the window appears, or what to do to prevent it showing up. There is nothing I can configure in SW 2003 to stop it. I can find nothing under my Startup group that triggers it, and MSCONFIG yields nothing, as well. I close it, and it appears again the next time.

Any ideas how to get rid of this, short of uninstalling SW 2003?

Mr Sleep · Post by **Mr Sleep** » Mon Oct 28, 2002 8:57 am

What kind of window, is it an explorer window or an IE window? What about task scheduler, is there anything in that?

<edit>It could be something to do with a liveupdate mechanism, the automatic liveupdate with NAV2002 would quite often start a dialup connection at startup.

fable · Post by **fable** » Mon Oct 28, 2002 9:30 am

Window was a poor choice of words. I meant folder.

And before you ask, no, there's no such folder in the Program Menu.

Mr Sleep · Post by **Mr Sleep** » Mon Oct 28, 2002 10:02 am

That is very strange, I assume you have a fully up to date copy? Which folder is it opening, what is the directory? Is it a common files directory?

There might be a simple solution like moving the directory to another place and seeing what effect that has

HighLordDave · Post by **HighLordDave** » Mon Oct 28, 2002 10:59 am

Have you checked with Symantec to see if this is a known issue?

fable · Post by **fable** » Mon Oct 28, 2002 6:08 pm

The folder is entitled Symantec, and contains the following files:

S32stat.dll
symevent.sys
symevnt.386

I am not running eny event that would trigger their appearance. As I said, the folder only shows up when the screen is rebooted.

Mr Sleep · Post by **Mr Sleep** » Tue Oct 29, 2002 6:00 am

What is the path to that folder? C:\windows\common files\symantec perhaps?

fable · Post by **fable** » Tue Oct 29, 2002 8:26 am

D:/program files/symantec (I run my program files directory off the D: drive)

Mr Sleep · Post by **Mr Sleep** » Tue Oct 29, 2002 8:42 am

Curiouser and Curiouser, are you running Norton Crashguard from the systemworks package?

fable · Post by **fable** » Tue Oct 29, 2002 8:50 am

Originally posted by Mr Sleep
Curiouser and Curiouser, are you running Norton Crashguard from the systemworks package?

No, can't say I am. Well, I could; but I'm not.

Mr Sleep · Post by **Mr Sleep** » Tue Oct 29, 2002 9:28 am

When you originally installed the program did the uninstallation of the previous Norton work correctly? I apologise for not being more helpful but I can't really think what is causing your problem.

Mr Flibble · Post by **Mr Flibble** » Tue Oct 29, 2002 12:50 pm

There's another location for running startup items in the registry that doesn't show up in MSCONFIG. Run regedit and go to Hkey_current_user > software > microsoft > windows > currentversion > run. You might find it in there instead.

fable · Post by **fable** » Tue Oct 29, 2002 11:21 pm

Oddly enough, there's nothing resembling that registry entry in there. (You've been right every other time.)

Perhaps I will uninstall and reinstall it, as Sleep suggests. Barring any suggestions in the next 24 hours for something else to try.

Mr Flibble · Post by **Mr Flibble** » Wed Oct 30, 2002 12:16 am

Originally posted by fable
Oddly enough, there's nothing resembling that registry entry in there. (You've been right every other time.)

Hmmm, my 98SE system here has that entry. I've got user profiles set up, so it might be created from that instead.

Sleep's suggestion of reloading it is the only other thing I can think of too.

Mr Sleep · Post by **Mr Sleep** » Wed Oct 30, 2002 3:55 am

I think you should probably have that entry, unless of course Norton moves or renames it since the entry of run is where most viruses propogate themselves from, so who knows, fortunately with Norton you aren't losing any data just settings when you uninstall.

Ned Flanders · Post by **Ned Flanders** » Wed Oct 30, 2002 11:47 am

by flibs
There's another location for running startup items in the registry that doesn't show up in MSCONFIG. Run regedit and go to Hkey_current_user > software > microsoft > windows > currentversion > run. You might find it in there instead.

If he isn't using user profiles, maybe he should substitute Hkey_Local_Machine for Hkey_Current_User. Worth a shot but the probable best bet is to uninstall and reinstall.

Not to insult your intelligence fable, but have you perused symantec's web site knowledge base for problems regarding NSW2k3. I've found their online support to be one of the best around.

fable · Post by **fable** » Wed Oct 30, 2002 12:46 pm

Originally posted by Ned Flanders
If he isn't using user profiles, maybe he should substitute Hkey_Local_Machine for Hkey_Current_User.

Using this, I found:

D:\Program Files\Symantec Shared\ccApp.exe
D:\Program Files\Symantec Shared\ccRegVly.exe

Either of them qualify for removal?

Ned Flanders · Post by **Ned Flanders** » Wed Oct 30, 2002 1:24 pm

Flibble might be more qualified to answer that one as I have no experience with NSW2k3.

Locate the .exe's you mention above in windows explorer and run them from there. What is the effect? Do they output an app you use? The exe's are definitely running at startup, however, these may execute services vital to NSW2k3

Mr Flibble · Post by **Mr Flibble** » Wed Oct 30, 2002 4:02 pm

Originally posted by fable
Using this, I found:

D:\Program Files\Symantec Shared\ccApp.exe
D:\Program Files\Symantec Shared\ccRegVly.exe

Either of them qualify for removal?

Keep both of them. They are both part of the email and realtime scanning in Norton Antivirus 2k3, and removing these registry entries will stop NAV from working properly.

Hve you tried searching the registry for the text string "symantec"? That will reveal where that folder is being referenced from. Note down the paths to these entries and post them. Just a warning, there might be quite a few of them.

Mr Sleep · Post by **Mr Sleep** » Thu Oct 31, 2002 6:03 am

It might also be lodged in the runonce string in the registry.