How to put a leash on MS updates

Is there a way to put a leash on MS updates. I'm happy to get them
though most are for Word or something that I actually never use, but
what they do is download when I don't ask them to and when they
finally finish that, they start in install in 15 minutes, counting
down .

As long as I'm sitting here , I can keep posponing things for ... I
don't know how long Later pospones it for, but if I want to eat dinner
or take a bath, how can I stop it from messing me up.

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

I'm talking about XP of course.

Micky wrote:
Is there a way to put a leash on MS updates. I'm happy to get them
though most are for Word or something that I actually never use, but
what they do is download when I don't ask them to and when they
finally finish that, they start in install in 15 minutes, counting
down .

As long as I'm sitting here , I can keep posponing things for ... I
don't know how long Later pospones it for, but if I want to eat dinner
or take a bath, how can I stop it from messing me up.

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

I'm talking about XP of course.

Look for "Automatic Updates" in Control Panels.

https://s14.postimg.org/u0zu1hcup/winxp_wu.gif

Paul

Micky wrote:

Is there a way to put a leash on MS updates. I'm happy to get them
though most are for Word or something that I actually never use, but
what they do is download when I don't ask them to and when they
finally finish that, they start in install in 15 minutes, counting
down .

Do why did you not configure the WU client to "notify only"? That will
notify you of updates but not download any nor install them until you
decide. However, Microsoft still manages to push some updates whether
the WU client is configured to "notify only" or even when set to
"never". That's why you have to disable the services involved.

Disable the BITS (Background Intelligent Transfer Service) and WU
(Windows Updates) services until whenever YOU are prepared to check for
Windows updates. When you have the time and are ready, save a backup
image of the OS partition, reenable those services, run the WU client to
check for updates, review EACH ONE to determine which you want to
install (and hide the others), install the ones you selected, reboot
Windows (even if not prompted to do so), and disable the services.

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

In message , VanguardLH
writes:
Micky wrote:

Is there a way to put a leash on MS updates. I'm happy to get them
though most are for Word or something that I actually never use, but

If you truly never use it, it might be worth uninstalling it; I _think_
you won't get those updates then. (If you only use it to _view_ files
sent by others etc., MS do free viewers - though I'm not sure if they
have {free viewers for the .docx versions} that run on XP. [I'm also not
sure if _any_ of the free viewers that _will_ run on XP are still
available from MS, but if not they should still be available somewhere,
possibly wayback.])

what they do is download when I don't ask them to and when they
finally finish that, they start in install in 15 minutes, counting
down .

Do why did you not configure the WU client to "notify only"? That will
notify you of updates but not download any nor install them until you
decide. However, Microsoft still manages to push some updates whether
the WU client is configured to "notify only" or even when set to
"never". That's why you have to disable the services involved.

Disable the BITS (Background Intelligent Transfer Service) and WU
(Windows Updates) services until whenever YOU are prepared to check for

Will disabling BITS break anything else?

Windows updates. When you have the time and are ready, save a backup
image of the OS partition, reenable those services, run the WU client to
check for updates, review EACH ONE to determine which you want to
install (and hide the others), install the ones you selected, reboot
Windows (even if not prompted to do so), and disable the services.

And then make another image (-:. [_Separate_ from the one you had
before, so you can still go back to that if you find you need to.]

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

Although Micky wasn't clear there, I _think_ his second to fourth
sentences there were back to talking about Windows updates, rather than
Forte ones.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Correct me if I'm wrong ... everybody else does.

"J. P. Gilliver (John)" wrote:

VanguardLH WROTE:

Micky wrote:

Is there a way to put a leash on MS updates. I'm happy to get them
though most are for Word or something that I actually never use, but

If you truly never use it, it might be worth uninstalling it; I _think_
you won't get those updates then.

Microsoft keeps offering me updates to Skype.
Skype is not installed.
Microsoft keeps offering me updates to Silverlight.
Silverlight is not installed.
Microsoft keeps offering me updates to software that is not installed.
I have to keep hiding those new update offerings.

I do agree with you, though, that if the OP never uses Word (he must
prefer some other installed word processor) then he should uninstall it.
No point on wasting disk space on never-used software.

Will disabling BITS break anything else?

Any process can use the BITS service for its own downloads. For
example, Windows Defender uses BITS even if you configure the WU client
to never update. As yet, Microsoft is the only company that I've heard
of that uses BITS. Other authors utilize their own download manager.

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when
you are using an ancient version (the last one that was free) of
Forte Agent.

Although Micky wasn't clear there, I _think_ his second to fourth
sentences there were back to talking about Windows updates, rather
than Forte ones.

I wasn't sure, either. A bit of rambling there. Since he put the
entire paragraph within parenthesis, the presumption is that it was all
related as a side issue.

VanguardLH on Fri, 24 Mar 2017 20:28:51 -0500 typed in
microsoft.public.windowsxp.general the following:

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

OTOH, Agent kept bringing out new bells, whistles and dancing
rabbits, none of which _I_ saw a need for me to get.
Now Forte Agent Newsreader Users are running into a hard coded
limit: all temporary filters (aka the Kill file) rest to Zero days
once the count reaches or exceeds June 6, 2017. NO word on if this
might be fixed in a new release, although a home brew patch has been
posted.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?

pyotr filipivich wrote:

VanguardLH on Fri, 24 Mar 2017 20:28:51 -0500 typed in
microsoft.public.windowsxp.general the following:

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

OTOH, Agent kept bringing out new bells, whistles and dancing
rabbits, none of which _I_ saw a need for me to get.
Now Forte Agent Newsreader Users are running into a hard coded
limit: all temporary filters (aka the Kill file) rest to Zero days
once the count reaches or exceeds June 6, 2017. NO word on if this
might be fixed in a new release, although a home brew patch has been
posted.

Look at the headers of the OP's post. He is using 1.93 of Forte Agent.
I thought the last free version was 3.3 (but maybe is a self-expiring
full version that cripples itself after the trial period ends). I see
3.3 is what you are using.

I remember trialing a free version of Forte Agent but that was years ago
so I don't recall its version. Maybe it was the same 1.93 version that
the OP is still using. A huge deficiency was not handling multiple
servers. I had to create a different config file for each server and
use batch (.bat) file to load Agent with the config selected by a
command-line parameter in the shortcut. So I could see one server at a
time. Might not be important to someone that uses only a single NNTP
server but I cannot to several where some are private ones (they do not
peer with the worldwide mesh network that is Usenet so their articles
aren't found elsewhere).

Its GUI was reminiscent to ancient programs that came out when Windows
3.11 was new: blocky and clutzy. That does not mean it isn't usable
(other than lack of multi-server support). Would you buy a new Ford Bel
Aire if it were available today? Well, some folks would because they're
into classic styling. That number is small so it wouldn't be offered
for long. Today it would be a flop like the Edsel was back in its day.

Another deficiency was the lack of filters. I even asked in the Forte
Agent newsgroup about this. I was told that the only way to make the
filters permanent was instead to use saved searches and that I would
have to manually run those searches. No thanks. The point of software
is to automate those repetitive and inane tasks.

If those were deficiencies back in version 1.93 then maybe the OP should
look at moving up to 3.3 since I recall multi-server support got added
(but don't know in which version it was added). The "classic" GUI was
still there (since I see in Google Images that it was still used in
version 4.2, and probably beyond). I had heard that Forte did not offer
the 3.3 download from their site back then but I see it there now at:

http://www.forteinc.com/agent/download-all.php

I take it by your comment that the user can define "temporary" filter.
Presumably that means they self-expire but you're saying the countdown
won't survive past June 6, 2017. Is that a fixed date or is it a
maximum survival time from now? 3+ months seems overly long for a
temporary filter.

If the OP wanted to get a better version of Forte Agent beyond the 1.93
he is using now, you're claiming that there were no improvements after
the version the OP uses up to the 3.3 you are using?

VanguardLH on Sat, 25 Mar 2017 16:55:07 -0500 typed in
microsoft.public.windowsxp.general the following:


I take it by your comment that the user can define "temporary" filter.
Presumably that means they self-expire but you're saying the countdown
won't survive past June 6, 2017. Is that a fixed date or is it a
maximum survival time from now? 3+ months seems overly long for a
temporary filter.

If the OP wanted to get a better version of Forte Agent beyond the 1.93
he is using now, you're claiming that there were no improvements after
the version the OP uses up to the 3.3 you are using?

I bought 3.3 for the filters. It has the option to filter per
newsgroup or global. It also has the ability to make a filter
permanent (never expire) or to expire after N days or N days of
no-activity. Those last two are useful for marking a subject or
poster you know will end in the next N days, or for waiting N days
after their last appearance to delete the filter. Default was 30
days, I upped it to 90 days to catch some quarterly spammers.

Right now - today March 27 - any filter set to expire more than 70
days out, resets to 0 days, and expires today Tomorrow, it will be
any filter set to expire more than 69 days out, resets to 0 days, and
expires on that day. The day after tomorrow N=68, lather rinse repeat
until N=1. What happens when '$today= Jun 6 2017' (day Zero) I do not
know. Nor do I know what will happens when $today = Z+1.


--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?

On Sat, 25 Mar 2017 13:04:16 -0700, pyotr filipivich
wrote:

VanguardLH on Fri, 24 Mar 2017 20:28:51 -0500 typed in
microsoft.public.windowsxp.general the following:

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

OTOH, Agent kept bringing out new bells, whistles and dancing
rabbits, none of which _I_ saw a need for me to get.
Now Forte Agent Newsreader Users are running into a hard coded
limit: all temporary filters (aka the Kill file) rest to Zero days
once the count reaches or exceeds June 6, 2017. NO word on if this
might be fixed in a new release, although a home brew patch has been
posted.

You had me really worried until 3/4s of the way through my reply, I
realized I never use temporary filters. Maybe I should but I don't.
For years I didn't know they existed, either because they didn't when
I started, or because I was in a hurry when I started.

So I guess now is not the time to start using them. FTR, what about
after June 6?

On Sat, 25 Mar 2017 13:04:16 -0700, pyotr filipivich
wrote:

VanguardLH on Fri, 24 Mar 2017 20:28:51 -0500 typed in
microsoft.public.windowsxp.general the following:

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

OTOH, Agent kept bringing out new bells, whistles and dancing
rabbits, none of which _I_ saw a need for me to get.
Now Forte Agent Newsreader Users are running into a hard coded
limit: all temporary filters (aka the Kill file) rest to Zero days
once the count reaches or exceeds June 6, 2017.

This sounds really bad, but maybe it's not as bad for me and people
like me as it sounds.

First, I'm not sure the difference between a temporary filter and any
other kind.

Second, while traveling, I don't real usenet as much as otherwise, so
I only have 4 filters, on the four most stupid sickest people out
there (If you're reading, you should know who you are. If you're not
certain, ask whoever locks you in at night.)

So if they expire on June 6, can I just recreate them on June 7 and
they'll last another 100 years?

NO word on if this
might be fixed in a new release, although a home brew patch has been
posted.

On Sat, 25 Mar 2017 16:55:07 -0500, VanguardLH wrote:

pyotr filipivich wrote:

VanguardLH on Fri, 24 Mar 2017 20:28:51 -0500 typed in
microsoft.public.windowsxp.general the following:

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

OTOH, Agent kept bringing out new bells, whistles and dancing
rabbits, none of which _I_ saw a need for me to get.
Now Forte Agent Newsreader Users are running into a hard coded
limit: all temporary filters (aka the Kill file) rest to Zero days
once the count reaches or exceeds June 6, 2017. NO word on if this
might be fixed in a new release, although a home brew patch has been
posted.

Look at the headers of the OP's post. He is using 1.93 of Forte Agent.
I thought the last free version was 3.3

I don't know, but I paid for 1.93. I paid for version 6 too and at
first used it only for the Firefox ng but after I moved to Vista, I
put my big-boy pants on and used it for everything. Then Vista
self-destructed last July, and I went back to 1.9 because I had better
backups. Maybe I did something wrong because some of the groups I
read are empty even though I moved the data back. So the plan is to
review my old data files, get it all in a row, and upgrade to v.4,
which might have added features I want but not what I couldn't get
used to about 6. Because you can't go back from 4 to 1.9, I can't
move to 4 until I'm happy with the data.

But you know, I still like 1.9, even though each time I start it, I
have to open each ng I plan to r ead. But unlike at home, while
travelilng that's usually 4 or less and no more than 6, so it's less
of a problem.

for all its faults (see below) I still like it better than 6.

(but maybe is a self-expiring
full version that cripples itself after the trial period ends). I see
3.3 is what you are using.

I remember trialing a free version of Forte Agent but that was years ago
so I don't recall its version. Maybe it was the same 1.93 version that
the OP is still using.

My version was free until I paid for it.

A huge deficiency was not handling multiple
servers.

Yes, you are so right.

I had to create a different config file for each server and
use batch (.bat) file to load Agent with the config selected by a
command-line parameter in the shortcut. So I could see one server at a

This is a very good idea. I still don't know if I'll like 4 better
than I liked 6, and if I don't, this is an excellent idea.

time. Might not be important to someone that uses only a single NNTP
server but I cannot [connect, I think you mean!] to several where some are private ones (they do not
peer with the worldwide mesh network that is Usenet so their articles
aren't found elsewhere).

Its GUI was reminiscent to ancient programs that came out when Windows
3.11 was new: blocky and clutzy. That does not mean it isn't usable
(other than lack of multi-server support). Would you buy a new Ford Bel
Aire if it were available today? Well, some folks would because they're
into classic styling. That number is small so it wouldn't be offered
for long. Today it would be a flop like the Edsel was back in its day.

Another deficiency was the lack of filters. I even asked in the Forte

I think the free version didn't have filters but the paid version
does.

But what is still bad is that Ignore ignores the whole thread, I'm 99%
certain, while in ver. 6 it would ignore only the subthread of the
post marked ignore (even when a filter did that.) Although I think
Ralph taught me a partial work around but one that only applis for
version 3 or 4 and higher.

Agent newsgroup about this. I was told that the only way to make the
filters permanent was instead to use saved searches and that I would
have to manually run those searches. No thanks. The point of software
is to automate those repetitive and inane tasks.

If those were deficiencies back in version 1.93 then maybe the OP should
look at moving up to 3.3 since I recall multi-server support got added
(but don't know in which version it was added). The "classic" GUI was\

Ralph said something about v.4, but I have dl'd v.3 and I plan to test
it too, especially after what you say here, but all this is only after
I get home and catch up with home-stuff, so some time in June if I'm
lucky.

I've been told my version 6 password will work on v3 and 4, but if it
doesn't and one of them answers my problems, I'll buy it anyhow.

still there (since I see in Google Images that it was still used in
version 4.2, and probably beyond). I had heard that Forte did not offer
the 3.3 download from their site back then but I see it there now at:

http://www.forteinc.com/agent/download-all.php

I take it by your comment that the user can define "temporary" filter.
Presumably that means they self-expire but you're saying the countdown
won't survive past June 6, 2017. Is that a fixed date or is it a
maximum survival time from now? 3+ months seems overly long for a
temporary filter.

If the OP wanted to get a better version of Forte Agent beyond the 1.93
he is using now, you're claiming that there were no improvements after
the version the OP uses up to the 3.3 you are using?

On Mon, 27 Mar 2017 09:30:43 -0700, pyotr filipivich
wrote:

VanguardLH on Sat, 25 Mar 2017 16:55:07 -0500 typed in
microsoft.public.windowsxp.general the following:


I take it by your comment that the user can define "temporary" filter.
Presumably that means they self-expire but you're saying the countdown
won't survive past June 6, 2017. Is that a fixed date or is it a
maximum survival time from now? 3+ months seems overly long for a
temporary filter.

If the OP wanted to get a better version of Forte Agent beyond the 1.93
he is using now, you're claiming that there were no improvements after
the version the OP uses up to the 3.3 you are using?

I bought 3.3 for the filters. It has the option to filter per
newsgroup or global.

I hate to tell you this, but so does 1.93.

It also has the ability to make a filter
permanent (never expire) or to expire after N days or N days of
no-activity.

I hate to tell you this, but so does 1.93.

Those last two are useful for marking a subject or
poster you know will end in the next N days, or for waiting N days
after their last appearance to delete the filter. Default was 30
days, I upped it to 90 days to catch some quarterly spammers.

Right now - today March 27 - any filter set to expire more than 70
days out, resets to 0 days, and expires today Tomorrow, it will be
any filter set to expire more than 69 days out, resets to 0 days, and
expires on that day. The day after tomorrow N=68, lather rinse repeat
until N=1. What happens when '$today= Jun 6 2017' (day Zero) I do not
know. Nor do I know what will happens when $today = Z+1.

Do you think Forte can bring the end of the Earth?

Micky on Mon, 27 Mar 2017 21:01:23 +0300 typed in
microsoft.public.windowsxp.general the following:
On Mon, 27 Mar 2017 09:30:43 -0700, pyotr filipivich
wrote:

VanguardLH on Sat, 25 Mar 2017 16:55:07 -0500 typed in
microsoft.public.windowsxp.general the following:


I take it by your comment that the user can define "temporary" filter.
Presumably that means they self-expire but you're saying the countdown
won't survive past June 6, 2017. Is that a fixed date or is it a
maximum survival time from now? 3+ months seems overly long for a
temporary filter.

If the OP wanted to get a better version of Forte Agent beyond the 1.93
he is using now, you're claiming that there were no improvements after
the version the OP uses up to the 3.3 you are using?

I bought 3.3 for the filters. It has the option to filter per
newsgroup or global.

I hate to tell you this, but so does 1.93.

It also has the ability to make a filter
permanent (never expire) or to expire after N days or N days of
no-activity.

I hate to tell you this, but so does 1.93.

Dang - I upgraded for no reason.

Those last two are useful for marking a subject or
poster you know will end in the next N days, or for waiting N days
after their last appearance to delete the filter. Default was 30
days, I upped it to 90 days to catch some quarterly spammers.

Right now - today March 27 - any filter set to expire more than 70
days out, resets to 0 days, and expires today Tomorrow, it will be
any filter set to expire more than 69 days out, resets to 0 days, and
expires on that day. The day after tomorrow N=68, lather rinse repeat
until N=1. What happens when '$today= Jun 6 2017' (day Zero) I do not
know. Nor do I know what will happens when $today = Z+1.

Do you think Forte can bring the end of the Earth?

Nope. "End if the Internet - Gifs at 0x0b!"


--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?

Micky on Mon, 27 Mar 2017 20:53:53 +0300 typed in
microsoft.public.windowsxp.general the following:
On Sat, 25 Mar 2017 13:04:16 -0700, pyotr filipivich
wrote:

VanguardLH on Fri, 24 Mar 2017 20:28:51 -0500 typed in
microsoft.public.windowsxp.general the following:

(For one thing my old version of Agent only keeps position in one ng.
For another, I can't remember what has been started and what hasn't
been. Why should I have to? Why don't they do updates when I want
them to? )

Limitations, deficiencies, and lack of updates are what happen when you
are using an ancient version (the last one that was free) of Forte
Agent.

OTOH, Agent kept bringing out new bells, whistles and dancing
rabbits, none of which _I_ saw a need for me to get.
Now Forte Agent Newsreader Users are running into a hard coded
limit: all temporary filters (aka the Kill file) rest to Zero days
once the count reaches or exceeds June 6, 2017.

This sounds really bad, but maybe it's not as bad for me and people
like me as it sounds.

First, I'm not sure the difference between a temporary filter and any
other kind.

Permanent: no expiration date. From now until the program is not
used, do action A.
Temporary: for the N, N-1, N-2, ... N=0 days do action A (with the
option to reset the count if Action A is performed). Good for
ignoring threads / authors you don't care about. Advantage over using
a Permanent filter - you don't have years of entries for things which
had their 15 minutes of Fame years (and years) ago. (does one really
need filters related to "current events" in 2004?)

Second, while traveling, I don't real usenet as much as otherwise, so
I only have 4 filters, on the four most stupid sickest people out
there (If you're reading, you should know who you are. If you're not
certain, ask whoever locks you in at night.)

So if they expire on June 6, can I just recreate them on June 7 and
they'll last another 100 years?

Nope. After June 6, temporary filters expire after 0 (zero) days.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?

pyotr filipivich on Mon, 27 Mar 2017 09:30:43
-0700 typed in microsoft.public.windowsxp.general the following:
VanguardLH on Sat, 25 Mar 2017 16:55:07 -0500 typed in
microsoft.public.windowsxp.general the following:


I take it by your comment that the user can define "temporary" filter.
Presumably that means they self-expire but you're saying the countdown
won't survive past June 6, 2017. Is that a fixed date or is it a
maximum survival time from now? 3+ months seems overly long for a
temporary filter.

If the OP wanted to get a better version of Forte Agent beyond the 1.93
he is using now, you're claiming that there were no improvements after
the version the OP uses up to the 3.3 you are using?

I bought 3.3 for the filters. It has the option to filter per
newsgroup or global. It also has the ability to make a filter
permanent (never expire) or to expire after N days or N days of
no-activity. Those last two are useful for marking a subject or
poster you know will end in the next N days, or for waiting N days
after their last appearance to delete the filter. Default was 30
days, I upped it to 90 days to catch some quarterly spammers.

Right now - today March 27 - any filter set to expire more than 70
days out, resets to 0 days, and expires today Tomorrow, it will be
any filter set to expire more than 69 days out, resets to 0 days, and
expires on that day. The day after tomorrow N=68, lather rinse repeat
until N=1. What happens when '$today= Jun 6 2017' (day Zero) I do not
know. Nor do I know what will happens when $today = Z+1.

I reset the date to June 7, 2017 (and June 9th) - 90 day filters
expire after zero days. I know that is not an exhaustive test, but it
severs well enough for me.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?