From: Gerry on
Neil

On closing Outlook Express 100 times. On some systems something changes
the counter in the Registry when it is not intended so automatic
compacting can be triggered quite a bit earlier. The counter is meant to
increment by one on closure but something else cause the counter to
increment at other times. Bruce Hagen writes about this regularly. It
doesn't happen here.

--



Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Neil wrote:
> "Gerry" <gerry(a)nospam.com> wrote in message
> news:OOOV3e4gJHA.2384(a)TK2MSFTNGP04.phx.gbl...
>> Robert
>>
>>>> Also, what's the point of having a "Delete news messages X days
>>>> after being downloaded" if OE is just going to delete them anyway,
>>>> regardless of the setting. Again, doesn't make sense.
>>>
>>>
>>> Makes perfect sense if someone only wants to keep a weeks worth
>>> of posts in his cache instead of a much larger number that the
>>> server might support.
>>
>> Your comment is correct . It was logical. It was also part of one of
>> the most disastrous and problematic features of Outlook Express.
>> Compacting. Checking this feature was blamed for countless losses of
>> messages. Automatic compacting was abandoned by users in favour of
>> manual compacting Offline. The changes made to automatic compacting
>> not so long ago improved the situation but did not totally resolve
>> the problem. Manual compacting before automatic compacting is
>> triggered remains the safest option. The option to "Delete news
>> messages X days after being downloaded" should have been removed
>> when the other changes were made.
>
>
> When does automatic compacting take place?


From: PA Bear [MS MVP] on
[OMG, now Gerry's got MasterPosts! <eek>]

Gerry wrote:
> Neil
>
> An extract from one of my posts from February 2004.
>
> A factor in storing messages is the time news messages are held on the
> news server...
From: Ron Sommer on


"Neil" <nrgins(a)gmail.com> wrote in message
news:Ys%gl.3457$%54.20(a)nlpi070.nbdc.sbc.com...
>
> "Gerry" <gerry(a)nospam.com> wrote in message
> news:OOOV3e4gJHA.2384(a)TK2MSFTNGP04.phx.gbl...
>> Robert
>>
>>>> Also, what's the point of having a "Delete news messages X days
>>>> after being downloaded" if OE is just going to delete them anyway,
>>>> regardless of the setting. Again, doesn't make sense.
>>>
>>>
>>> Makes perfect sense if someone only wants to keep a weeks worth
>>> of posts in his cache instead of a much larger number that the server
>>> might support.
>>
>> Your comment is correct . It was logical. It was also part of one of the
>> most disastrous and problematic features of Outlook Express. Compacting.
>> Checking this feature was blamed for countless losses of messages.
>> Automatic compacting was abandoned by users in favour of manual
>> compacting Offline. The changes made to automatic compacting not so long
>> ago improved the situation but did not totally resolve the problem.
>> Manual compacting before automatic compacting is triggered remains the
>> safest option. The option to "Delete news messages X days after being
>> downloaded" should have been removed when the other changes were made.
>
>
> When does automatic compacting take place?
>
On the 101st closing after the last compaction.
--
Ronald Sommer

From: Ron Sommer on


"Neil" <nrgins(a)gmail.com> wrote in message
news:zSZgl.19281$Ws1.7880(a)nlpi064.nbdc.sbc.com...
>
>> OE is doing what a newsreader is supposed to do, keep the messages on
>> your
>> computer synched with the newsgroup server.
>
> Again, that was not the way OE used to work. It used to retain all msgs
> that were downloaded.
>
>> I don't know of any newsreaders that do not sync with the server.
>> You have not mentioned what news server that you are using.
>
> Why is that germane to the discussion?
>
>
>
>> The Microsoft server has a 90 day retention period.
>> --
>> Ronald Sommer
>
>

It is very germane.
You are incorrectly basing your idea of the operation of OE on a news server
that had a long retention period.
I have news servers that have a long retention period.
Because you insist on saying that OE used to keep all posts without saying
what news server that you were using, you haven't proved that your version
of OE works the way that you say.
--
Ronald Sommer

From: Gerry on
Neil

Loss of newgroup messages. This can happen if something happens to cause
the folder (file) to corrupt. A power failure could cause corruption if
data was being written to the file and the process was interupted.
Newsgroup folders can get very large so that a system lacking resources
in terms of memory and CPU capacity can have difficulty handling the
file. In this situation the chances of interuption and corruption are
greater. Interupting the automatic compaction process is the most common
cause of file corruption. Normally users report loss of messages from
the inbox or sent items folders. These messages are irreplaceable,
whereas messages in newsgroup folders can easily be replaced. As a
consequence loss of newsgroup messages is not commonly reported.

The delete option when compacting was also a common cause of file
corruption because it could be working when Outlook Express was amongst
other things Online. Compacting was supposed to work in the background
allowing the user to continue to use Outlook Express for reading,
writing and posting messages. It was a disaster. The opportunities for
interupting the compaction process were significantly increased and file
corruption was common until the user of Outlook Express learnt how to
adopt practices to minimise the risk. In the absence of measures from
Microsoft to resolve the problem Steve Cochran, posting in this
conversation, wrote his first message recovery utility, DBXtract, to
help users recover messages from corrupted dbx files. The delete option
was specifically designed to work with Compacting messages in the
Background. You had to select the option to Compact Messages in the
Background for the delete option to work. When Microsoft eventually
removed the option to Compact Messages in the Background they overlooked
the delete option and it became a redundant relic.

Another way to lose newsgroup messages is to unintentionally delete
messages by clicking on the wrong button. In Tools, Options,
Maintenance, CleanUp now are four buttons. One is Compact but the other
three buttons all remove the contents of the selected folder.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Neil wrote:
>> It does make sense. Apart from differences only available by using
>> a synchronize command the main thing that you need to be aware of
>> is the Get 300 headers... option and the fact that its value is
>> used to do
>> an automatic Get Next 300... every time you enter a newsgroup when
>> you are in a Working Online state.
>
> I don't have any problem getting headers. OE gets them for me
> automatically when I enter a newsgroup. No problem. And I have it set
> to 1,000, not 300. So the Next 1,000 command works fine too. No
> problem there. But that has nothing to do with what I'm saying.
>
>
>> If you don't want that to happen,
>> either don't enter that newsgroup or enter it with Work Offline set.
>
> I do want it to happen. And it's happening. No problem.
>
>
>> If you don't have the Get next 300... option checked the automatic
>> Get next done for you has the equivalent effect of a Synchronize
>> Newsgroup command done while the Synchronize settings are
>> Headers Only.
>
> OK.
>
>
>>> And, like I said, didn't used to be that way. I remember a point
>>> where OE would keep downloaded headers indefinitely.
>>
>>
>> Was this with a different NNTP server? In any case servers change
>> how they act over time and they may also be set up to serve different
>> newsgroups differently.
>
> I can't say if it was a different one, or when exactly it changed. I
> remember, though, that headers would stay indefinitely, and I had at
> least a years' worth of headers in one particular newsgroup. One day
> I was playing aroudn with the synchronization settings, and then I
> lost all my headers! I was aghast. So I changed it back to No
> Synchronization. But ever since then, it kept deleting old headers,
> though it never did it before I played around with the
> synchronization settings.
> But that was on a different PC anyway. This laptop is only about six
> months old, and that was a few years ago that it happened. So
> anything that happened on that PC wouldn't affect what happens on
> this PC (and I didn't bring my message stores over from another PC or
> anything). So, even though I can trace the point in time when it
> changed to when I changed the synchronization settings (and then
> changed back to No Synchronization), that wouldn't explain why it's
> happening on this PC, which had a new install of OE.
>
> Neil


First  |  Prev  |  Next  |  Last
Pages: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Prev: Error code 0x800CCC0E & 0X8000CCC78
Next: errore