Warning

To my understanding this is the place to come to with questions concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question instead. And that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As soon as I install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the service, when in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

Harry.

If it is not EZ Armor, what exactly causes this phenomenon?

You appear to experience a myriad of problems perhaps only matched by
those of Sean. Others do not, (KB891711 and Symantec induced problems
aside) so ask yourself what the common factor might be. Not all problems
are caused by the operating system or even the programs you have installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an error after
installing a firewall is usually the result of either a botched install or
the user having failed to configure the firewall correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with questions
concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question instead. And
that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As soon as I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the service, when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

You mention two possibilities and only one of them does apply, because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this phenomenon?

You appear to experience a myriad of problems perhaps only matched by
those of Sean. Others do not, (KB891711 and Symantec induced problems
aside) so ask yourself what the common factor might be. Not all problems
are caused by the operating system or even the programs you have installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an error after
installing a firewall is usually the result of either a botched install or
the user having failed to configure the firewall correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with questions
concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question instead. And
that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As soon as I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the service, when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

With all due respect to your configuration abilities, I must suggest that
you make another run at verifying thier correctness. As your installation
was apparently successful, the software is working for many others, the
configuration aspect remains highly suspect.
Running ZAPro myself, I am not familiar with the firewall in EZ Armor,
although, I understand it is the same basic engine. However, I do not know
what you have as "options" or what settings are available to you. Maybe
someone else could assist in that department.
Heirloom, old and humble pie don't taste so bad

"webster72n" wrote in message
...

You mention two possibilities and only one of them does apply, because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this phenomenon?

You appear to experience a myriad of problems perhaps only matched by
those of Sean. Others do not, (KB891711 and Symantec induced problems
aside) so ask yourself what the common factor might be. Not all
problems
are caused by the operating system or even the programs you have
installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an error after
installing a firewall is usually the result of either a botched install
or
the user having failed to configure the firewall correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with questions
concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question instead. And
that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As soon as I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the service, when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

Heirloom:

With all due respect here also, but I had this thing running before the
upgrade with no side affects and all of a sudden it is supposed to be
"misconfigured"?
The only way you can possibly do that is, if you activate things you know
will get you in trouble.
You don't put me in that category, I hope.
Maybe I'll be well advised to pick a different route finding my answers.

Harry.


"heirloom" wrote in message
...
With all due respect to your configuration abilities, I must suggest that
you make another run at verifying thier correctness. As your installation
was apparently successful, the software is working for many others, the
configuration aspect remains highly suspect.
Running ZAPro myself, I am not familiar with the firewall in EZ Armor,
although, I understand it is the same basic engine. However, I do not
know
what you have as "options" or what settings are available to you. Maybe
someone else could assist in that department.
Heirloom, old and humble pie don't taste so bad

"webster72n" wrote in message
...

You mention two possibilities and only one of them does apply, because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this phenomenon?

You appear to experience a myriad of problems perhaps only matched by
those of Sean. Others do not, (KB891711 and Symantec induced problems
aside) so ask yourself what the common factor might be. Not all
problems
are caused by the operating system or even the programs you have
installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an error after
installing a firewall is usually the result of either a botched
install
or
the user having failed to configure the firewall correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with questions
concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question instead. And
that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As soon as I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the service,
when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

Harry,
You just answered your own question......."this thing running before
the upgrade with no side affects and all of a sudden it is supposed to be
"misconfigured?" The upgrade may well have set something back to a default
or left something out of the picture.
Yes, the easy way out would be to keep trying different AV's and
firewalls until something works......especially, if you are steadfast in
your conviction that the settings could not possibly be the issue.
Heirloom, old and may the gods of silicon be with
you


"webster72n" wrote in message
...

Heirloom:

With all due respect here also, but I had this thing running before the
upgrade with no side affects and all of a sudden it is supposed to be
"misconfigured"?
The only way you can possibly do that is, if you activate things you know
will get you in trouble.
You don't put me in that category, I hope.
Maybe I'll be well advised to pick a different route finding my answers.

Harry.


"heirloom" wrote in message
...
With all due respect to your configuration abilities, I must suggest
that
you make another run at verifying thier correctness. As your
installation
was apparently successful, the software is working for many others, the
configuration aspect remains highly suspect.
Running ZAPro myself, I am not familiar with the firewall in EZ Armor,
although, I understand it is the same basic engine. However, I do not
know
what you have as "options" or what settings are available to you. Maybe
someone else could assist in that department.
Heirloom, old and humble pie don't taste so bad

"webster72n" wrote in message
...

You mention two possibilities and only one of them does apply, because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this phenomenon?

You appear to experience a myriad of problems perhaps only matched
by
those of Sean. Others do not, (KB891711 and Symantec induced
problems
aside) so ask yourself what the common factor might be. Not all
problems
are caused by the operating system or even the programs you have
installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an error after
installing a firewall is usually the result of either a botched
install
or
the user having failed to configure the firewall correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with questions
concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question instead.
And
that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As soon as
I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the service,
when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

Heirloom:

The reason I am certain about the configuration is, my settings after the
upgrade were no different from those before. And I am sceptical now to
install it again, because of the reoccurring error message.
But there is sunlight behind the clouds and those gods of silicone may have
something to do with it.
In internet options under the advanced tab, there are three security options
and one of them should be unchecked.
The first two, SSL 2.0 and SSL 3.0 may be checked but
TLS 1.0 must be unchecked.
I was under the impression that I always had it checked
but don't know for sure. It's a restrictive feature, as I found out the hard
way.
All indications are, EZ Armor may not be guilty of
misbehavior, as I had suspected and as soon as I find the opportunity, I
will confirm and exonerate it.

Harry.


"heirloom" wrote in message
...
Harry,
You just answered your own question......."this thing running
before
the upgrade with no side affects and all of a sudden it is supposed to be
"misconfigured?" The upgrade may well have set something back to a
default
or left something out of the picture.
Yes, the easy way out would be to keep trying different AV's and
firewalls until something works......especially, if you are steadfast in
your conviction that the settings could not possibly be the issue.
Heirloom, old and may the gods of silicon be with
you


"webster72n" wrote in message
...

Heirloom:

With all due respect here also, but I had this thing running before the
upgrade with no side affects and all of a sudden it is supposed to be
"misconfigured"?
The only way you can possibly do that is, if you activate things you
know
will get you in trouble.
You don't put me in that category, I hope.
Maybe I'll be well advised to pick a different route finding my answers.

Harry.


"heirloom" wrote in message
...
With all due respect to your configuration abilities, I must suggest
that
you make another run at verifying thier correctness. As your
installation
was apparently successful, the software is working for many others,
the
configuration aspect remains highly suspect.
Running ZAPro myself, I am not familiar with the firewall in EZ Armor,
although, I understand it is the same basic engine. However, I do not
know
what you have as "options" or what settings are available to you.
Maybe
someone else could assist in that department.
Heirloom, old and humble pie don't taste so
bad

"webster72n" wrote in message
...

You mention two possibilities and only one of them does apply,
because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this phenomenon?

You appear to experience a myriad of problems perhaps only matched
by
those of Sean. Others do not, (KB891711 and Symantec induced
problems
aside) so ask yourself what the common factor might be. Not all
problems
are caused by the operating system or even the programs you have
installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means
CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an error after
installing a firewall is usually the result of either a botched
install
or
the user having failed to configure the firewall correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with questions
concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question instead.
And
that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As soon
as
I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the
service,
when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

Hate to cloud up your sunny day, but, all three of mine are checked.
Heirloom, old and something ain't setting good

"webster72n" wrote in message
...

Heirloom:

The reason I am certain about the configuration is, my settings after the
upgrade were no different from those before. And I am sceptical now to
install it again, because of the reoccurring error message.
But there is sunlight behind the clouds and those gods of silicone may
have
something to do with it.
In internet options under the advanced tab, there are three security
options
and one of them should be unchecked.
The first two, SSL 2.0 and SSL 3.0 may be checked but
TLS 1.0 must be unchecked.
I was under the impression that I always had it checked
but don't know for sure. It's a restrictive feature, as I found out the
hard
way.
All indications are, EZ Armor may not be guilty of
misbehavior, as I had suspected and as soon as I find the opportunity, I
will confirm and exonerate it.

Harry.


"heirloom" wrote in message
...
Harry,
You just answered your own question......."this thing running
before
the upgrade with no side affects and all of a sudden it is supposed to
be
"misconfigured?" The upgrade may well have set something back to a
default
or left something out of the picture.
Yes, the easy way out would be to keep trying different AV's and
firewalls until something works......especially, if you are steadfast in
your conviction that the settings could not possibly be the issue.
Heirloom, old and may the gods of silicon be
with
you


"webster72n" wrote in message
...

Heirloom:

With all due respect here also, but I had this thing running before
the
upgrade with no side affects and all of a sudden it is supposed to be
"misconfigured"?
The only way you can possibly do that is, if you activate things you
know
will get you in trouble.
You don't put me in that category, I hope.
Maybe I'll be well advised to pick a different route finding my
answers.

Harry.


"heirloom" wrote in message
...
With all due respect to your configuration abilities, I must suggest
that
you make another run at verifying thier correctness. As your
installation
was apparently successful, the software is working for many others,
the
configuration aspect remains highly suspect.
Running ZAPro myself, I am not familiar with the firewall in EZ
Armor,
although, I understand it is the same basic engine. However, I do
not
know
what you have as "options" or what settings are available to you.
Maybe
someone else could assist in that department.
Heirloom, old and humble pie don't taste so
bad

"webster72n" wrote in message
...

You mention two possibilities and only one of them does apply,
because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this phenomenon?

You appear to experience a myriad of problems perhaps only
matched
by
those of Sean. Others do not, (KB891711 and Symantec induced
problems
aside) so ask yourself what the common factor might be. Not all
problems
are caused by the operating system or even the programs you have
installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means
CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an error
after
installing a firewall is usually the result of either a botched
install
or
the user having failed to configure the firewall correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with
questions
concerning
general WinME issues.
To put up a warning sign may have been a bit inappropiate
and I appologize for that.
It should have been presented in the form of a question
instead.
And
that's
the intent of this post.
There does not seem to be any problem without EZ Armor. As
soon
as
I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated the
service,
when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this phenomenon?
I am open for suggestions.

Now ya got me wondering because the first two only are checked on my
system.

Dan

"heirloom" wrote in message
...
Hate to cloud up your sunny day, but, all three of mine are checked.
Heirloom, old and something ain't
setting good

"webster72n" wrote in message
...

Heirloom:

The reason I am certain about the configuration is, my settings
after the
upgrade were no different from those before. And I am sceptical
now to
install it again, because of the reoccurring error message.
But there is sunlight behind the clouds and those gods of silicone
may
have
something to do with it.
In internet options under the advanced tab, there are three
security
options
and one of them should be unchecked.
The first two, SSL 2.0 and SSL 3.0 may be checked but
TLS 1.0 must be unchecked.
I was under the impression that I always had it checked
but don't know for sure. It's a restrictive feature, as I found
out the
hard
way.
All indications are, EZ Armor may not be guilty of
misbehavior, as I had suspected and as soon as I find the
opportunity, I
will confirm and exonerate it.

Harry.


"heirloom" wrote in message
...
Harry,
You just answered your own question......."this thing
running
before
the upgrade with no side affects and all of a sudden it is
supposed to
be
"misconfigured?" The upgrade may well have set something back
to a
default
or left something out of the picture.
Yes, the easy way out would be to keep trying different
AV's and
firewalls until something works......especially, if you are
steadfast in
your conviction that the settings could not possibly be the issu
e.
Heirloom, old and may the gods of
silicon be
with
you


"webster72n" wrote in message
...

Heirloom:

With all due respect here also, but I had this thing running
before
the
upgrade with no side affects and all of a sudden it is
supposed to be
"misconfigured"?
The only way you can possibly do that is, if you activate
things you
know
will get you in trouble.
You don't put me in that category, I hope.
Maybe I'll be well advised to pick a different route finding
my
answers.

Harry.


"heirloom" wrote in message
...
With all due respect to your configuration abilities, I must
suggest
that
you make another run at verifying thier correctness. As
your
installation
was apparently successful, the software is working for many
others,
the
configuration aspect remains highly suspect.
Running ZAPro myself, I am not familiar with the firewall in
EZ
Armor,
although, I understand it is the same basic engine.
However, I do
not
know
what you have as "options" or what settings are available to
you.
Maybe
someone else could assist in that department.
Heirloom, old and humble pie don't
taste so
bad

"webster72n" wrote in message
...

You mention two possibilities and only one of them does
apply,
because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this
phenomenon?

You appear to experience a myriad of problems perhaps
only
matched
by
those of Sean. Others do not, (KB891711 and Symantec
induced
problems
aside) so ask yourself what the common factor might be.
Not all
problems
are caused by the operating system or even the programs
you have
installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means
CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an
error
after
installing a firewall is usually the result of either a
botched
install
or
the user having failed to configure the firewall
correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with
questions
concerning
general WinME issues.
To put up a warning sign may have been a bit
inappropiate
and I appologize for that.
It should have been presented in the form of a
question
instead.
And
that's
the intent of this post.
There does not seem to be any problem without EZ
Armor. As
soon
as
I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated
the
service,
when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this
phenomenon?
I am open for suggestions.

Ditto! DD - My (two) boxes are set (by default at installation??) like yours
and Harry's. I've never played with these settings as I've never
managed/bothered to work out the importance of these settings for my
requirements. They just work! Sorry HL g

Mart


"Dapper Dan" wrote in message
...
Now ya got me wondering because the first two only are checked on my
system.

Dan

"heirloom" wrote in message
...
Hate to cloud up your sunny day, but, all three of mine are checked.
Heirloom, old and something ain't
setting good

"webster72n" wrote in message
...

Heirloom:

The reason I am certain about the configuration is, my settings
after the
upgrade were no different from those before. And I am sceptical
now to
install it again, because of the reoccurring error message.
But there is sunlight behind the clouds and those gods of silicone
may
have
something to do with it.
In internet options under the advanced tab, there are three
security
options
and one of them should be unchecked.
The first two, SSL 2.0 and SSL 3.0 may be checked but
TLS 1.0 must be unchecked.
I was under the impression that I always had it checked
but don't know for sure. It's a restrictive feature, as I found
out the
hard
way.
All indications are, EZ Armor may not be guilty of
misbehavior, as I had suspected and as soon as I find the
opportunity, I
will confirm and exonerate it.

Harry.


"heirloom" wrote in message
...
Harry,
You just answered your own question......."this thing
running
before
the upgrade with no side affects and all of a sudden it is
supposed to
be
"misconfigured?" The upgrade may well have set something back
to a
default
or left something out of the picture.
Yes, the easy way out would be to keep trying different
AV's and
firewalls until something works......especially, if you are
steadfast in
your conviction that the settings could not possibly be the issu
e.
Heirloom, old and may the gods of
silicon be
with
you


"webster72n" wrote in message
...

Heirloom:

With all due respect here also, but I had this thing running
before
the
upgrade with no side affects and all of a sudden it is
supposed to be
"misconfigured"?
The only way you can possibly do that is, if you activate
things you
know
will get you in trouble.
You don't put me in that category, I hope.
Maybe I'll be well advised to pick a different route finding
my
answers.

Harry.


"heirloom" wrote in message
...
With all due respect to your configuration abilities, I must
suggest
that
you make another run at verifying thier correctness. As
your
installation
was apparently successful, the software is working for many
others,
the
configuration aspect remains highly suspect.
Running ZAPro myself, I am not familiar with the firewall in
EZ
Armor,
although, I understand it is the same basic engine.
However, I do
not
know
what you have as "options" or what settings are available to
you.
Maybe
someone else could assist in that department.
Heirloom, old and humble pie don't
taste so
bad

"webster72n" wrote in message
...

You mention two possibilities and only one of them does
apply,
because
misconfiguration does not.
That leaves the "botched" installation.
How do I know it is botched?
There were no apparent signs of it?
Everything seemed to have proceeded smoothly.
Would the bootlog analyzer be of any help?Thanks.

Harry.


"Mike M" wrote in message
...
If it is not EZ Armor, what exactly causes this
phenomenon?

You appear to experience a myriad of problems perhaps
only
matched
by
those of Sean. Others do not, (KB891711 and Symantec
induced
problems
aside) so ask yourself what the common factor might be.
Not all
problems
are caused by the operating system or even the programs
you have
installed
so you may need to look elsewhere for a possible answer.

For example the error 0x800CCC0F means
CONNECTION_DROPPED/Connection
closed. Now why do you think that might be? Such an
error
after
installing a firewall is usually the result of either a
botched
install
or
the user having failed to configure the firewall
correctly.
--
Mike Maltby MS-MVP



"webster72n" wrote ...
To my understanding this is the place to come to with
questions
concerning
general WinME issues.
To put up a warning sign may have been a bit
inappropiate
and I appologize for that.
It should have been presented in the form of a
question
instead.
And
that's
the intent of this post.
There does not seem to be any problem without EZ
Armor. As
soon
as
I
install
it, I receive the error message#
0x800CCC0F, where the server unexpectedly terminated
the
service,
when
in
reality he didn't.
Why would that be?
If it is not EZ Armor, what exactly causes this
phenomenon?
I am open for suggestions.