Archived from groups: microsoft.public.windowsxp.basics (
More info?)
OK. I thought I had something called eTrust EZ Armor from CA. Anyway, this
True Vector error then, could it be causing the stalling then?
"Ken Blake" <kblake@this.is.an.invalid.domain> wrote in message
news:uWyQ3h0LFHA.3512@TK2MSFTNGP15.phx.gbl...
> In news:1141hhs932485f6@corp.supernews.com,
> AIANDAS <Aiandas@Odysseia$.com> typed:
>
>> You responded like I know what ZoneAlarm is.
>> Please explain.
>
>
> Sorry. ZoneAlarm is a firewall program, and since you're apparently
> running it, I thought you'd know what it is.
>
> --
> Ken Blake - Microsoft MVP Windows: Shell/User
> Please reply to the newsgroup
>
>
>
>> "Ken Blake" <kblake@this.is.an.invalid.domain> wrote in message
>> news:e9y4k6zLFHA.2888@TK2MSFTNGP12.phx.gbl...
>>> In news:11418j913mui01c@corp.supernews.com,
>>> AIANDAS <Aiandas@Odysseia$.com> typed:
>>>
>>>> OK I have accessed the Event Viewer and one consistent error I am
>>>> getting is in re: TrueVector Service. What is this service's impact
>>>> and how does it adversely affect the situation?
>>>
>>>
>>> It's part of ZoneAlarm.
>>>
>>> --
>>> Ken Blake - Microsoft MVP Windows: Shell/User
>>> Please reply to the newsgroup
>>>
>>>
>>>> "CWatters" <colin.watters@pandoraBOX.be> wrote in message
>>>> news:qRD%d.42690$dV5.3643528@phobos.telenet-ops.be...
>>>>>
>>>>> "AIANDAS" <Aiandas@Odysseia$.com> wrote in message
>>>>> news:113tllqj1pavvf0@corp.supernews.com...
>>>>>> I use on a regular basis Ad-Aware and have an anti-virus program
>>>>>> as well. Waiting long enough is not an issue, since by the time
>>>>>> this happens the pc
>>>>>> simply does not continue to boot up. It freezes on that user log
>>>>>> on screen. How do I access the Event Viewer?
>>>>>
>>>>> Log on as an administrator user and then....
>>>>>
>>>>> Start -> Control Panel -> Performance and maintenance ->
>>>>> Administrative Tools -> double click Event Viewer.
>>>>>
>>>>> In the right hand pane double click "System" and see if there are
>>>>> any errors
>>>>> listed. Normally there will ba alot or entries marked
>>>>> "Information". These are harmless. Look for those marked "error"
>>>>> with a date and time around when
>>>>> you last had a failed log on attempt.
>>>>>
>>>>> After looking in the system log have a look in the Security and
>>>>> Application
>>>>> logs.
>>>>>
>>>>> It's possible there will be no errors listed but worth a look.
>>>>>
>>>>>> Would the Event Viewer tell me what startup program is creating
>>>>>> the problem?
>>>>>
>>>>> It might do.
>
>