XP PRO SP3 Unable to activate (tick) zclient (ZoneAlarm) in msconfig startup - resolved

[atandhmb]

I will not go thru the permutations I tried.
Finally, I re-installed ZoneAlarm as an update (about 20 minutes) and this
put zlclient back into the Systray - so OK.
However, the entry for zclient in Startup remained unticked and I could not
resolve, so that I was permanently in Selective Startup. Now this didn't
really matter as the real problem was resolved.
However, as I decided I would uncheck something else in Startup to ascertain
if that would also re-act similarly to zlclient I noticed there was a
duplicate entry for zclient which was checked..
Now, being honest I don't know whether the duplicate was there before I
re-installed ZoneAlarm or not or whether it was added because of the
install: what is unarguable is that following the re-install zclient was now
being activated at startup.
I decided that I would like to get rid of the duplicate entry, first of all
by removing the target with Regedit but wasn't sure how MSCONFIG would
re-act.
Instead found free routine in google - "Msconfig cleanup" which is
wonderfully simple and effective.
Whatever you leave unchecked in Startup, it will give you option to clear.
I will now go thru MSCONFIG to get rid of extraneous items.
Thanks to P A BEAR especially who has given much time to another problem
which might have been associated. Following advice I decided to open new
thread (even although it was tempting not to do so as the matter is
resolved).

 

[PA Bear [MS MVP]]

ALWAYS reply to only your original thread, please, so that everyone's fully
aware of your (previous?) problems & issues:
http://groups.google.com/group/micr...3c458f8ea1/113cf8a4fc64e9dc?#113cf8a4fc64e9dc

<QP>
Even though you may have resolved your original problems, I think it'd be
best to post in that hijackware-specific forum at bleepingcomputer.com
anyway to make SURE the machine is 100% clean (despite what Jose's been
telling you in this thread).
</QP>
Source:
http://groups.google.com/group/microsoft.public.windowsxp.general/msg/90b310906790107d

PS: ZA User Forums
http://forums.zonelabs.com/zonelabs

 

[Jose]

ALWAYS reply to only your original thread, please, so that everyone's fully
aware of your (previous?) problems & issues:http://groups.google.com/group/microsoft.public.windowsxp.general/bro...

<QP>
Even though you may have resolved your original problems, I think it'd be
best to post in that hijackware-specific forum at bleepingcomputer.com
anyway to make SURE the machine is 100% clean (despite what Jose's been
telling you in this thread).
</QP>
Source:http://groups.google.com/group/microsoft.public.windowsxp.general/msg...

PS: ZA User Forumshttp://forums.zonelabs.com/zonelabs

Whatever.

The problem in the original post was resolved and then work was
started on a new unrelated problem in the same thread. I spent a lot
of time on it also. You were not the one to point to the resolution
of the problem, remember?

By creating a new topic with a subject that makes sense, it may make
it easier for other people with a similar problem to find. At least
that made sense to me and still does.

Now we have a new thread with a specific topic related to a specific
problem and a solution all in one message.

If I give bad advice, tell me why it is bad.

<EOM>

 

[PA Bear [MS MVP]]

Jose wrote:

If I give bad advice, tell me why it is bad...

One can never assume or presume that a machine is 100% clean simply because
an OP here says, "Everything's OK now." (If everything's OK, why is our OP
here having issues with enabling his ZA app?)

It is patently unethical to point an OP to someone else's newsgroup or forum
thread in the assumption that the OP's problem (and resolution of same) is
identical to that of the person who started the other thread.

Every single case is unique. You do a disservice to everyone if you assume
otherwise, Jose.