From: Neil on

"NormanM" <spammers.are(a)immoral.invalid> wrote in message
news:r0l4rxj1a062$.dlg(a)on-line.service.invalid...
> On Fri, 30 Jan 2009 09:09:56 -0600, Neil wrote:
>
>> "Steve Cochran" <scochran(a)oehelp.com> wrote in message
>> news:2ED77F93-0FFA-4FE0-8F34-27EC8C06B294(a)microsoft.com...
>
>>> It never made sense and its been a problem since OE4. It won't be
>>> fixed,
>>> so if you wish to keep NG messages, you have to copy them to local
>>> folders. That is the only way. People complained about this for many
>>> years and MS just ignored them.
>
>> And MS wonders why they're sinking faster than the titanic while Google
>> acquires their empire (apologies for the mixed metaphor; but maybe in
>> this
>> case a mixed metaphor is fitting, given the absolutely absurd state of
>> the
>> software).
>
> Very mixed up. Google does not publish software. Microsoft is only losing
> on
> the web search front.

Really? What year are you living in? Google has Google Docs to compete with
Word, Google Spreadsheet to compete with Excel, Google Calendar to compete
with Outlook, and Gmail to compete with Outlook, and they are providing
functionality to use all of those OFFLINE. Furthermore, Google came out with
their own browser, Chrome, which not only competes with Internet Explorer,
but is designed from the ground up specifically for running web apps (i.e.,
once it matures it will probably be a full-fledged operating system,
replacing Windows, just as Windows once supplemented but then eventually
replaced DOS).

All of these are in their infancy, and their maturity is many years away.
But Microsoft sees the writing on the wall. It's not about Internet search;
it's about a paradigm shift away from desktop apps to web-based apps. And
Google is far ahead of Microsoft in the battle.

The year is 2009. Keep up with what's going on.


From: Neil on

"PA Bear [MS MVP]" <PABearMVP(a)gmail.com> wrote in message
news:%23lVZEIvgJHA.4220(a)TK2MSFTNGP06.phx.gbl...
> Devil's Advocate: If posts were not removed from OE (in its current design
> state) when they were removed from the server and a heavy newsgroup user
> never deleted any posts manually, consider how bloated and ripe for
> corruption the message store would become over time!

This is why OE has the option to remove messages which are more than X days
old when the message store is compacted. But it doesn't seem to respect
that, and just deletes messages.

Furthermore, a "heavy newsgroup user" would probably just download headers,
which take up almost no space, and only get messages for headers that are
read. That wouldn't result in a lot of bloat.

But as a newsgroup user, I'd like to be able to have messages that I've
already stored on my harddrive remain on my harddrive, rather than having
them deleted against my will by the software. If bloat is a problem, then
let ME manage it. Don't force me to have my messages deleted simply because
you're connecting to the server, for crying out loud.

You and a few others are trying to justify Microsoft's action, like as
though it makes sense. It doesn't make sense to delete messages without user
authorization. It's just a stupid thing that OE does.


From: Neil on
> These resistant pogues couldn't get their noodles around that one
>
> Keep OE = Outlook EXPRESS.
>
> Don't Bloat It.
>

This "pogue" believes he's intelligent enough to be able to manage his own
software without being forced to lose messages every time they scroll off
the server. Face it: this is a glitch, a flaw. You're trying to justify it
with some nonsense about keeping OE lean and mean; but the bottom line is
that it doesn't make any sense to delete messages against the user's will.

Imagine if OE did that on the mail side. Why not keep that "lean and mean"
as well?

Obviously your argument is ridiculous.


From: Neil on

"VanguardLH" <V(a)nguard.LH> wrote in message
news:glvf19$av4$1(a)news.motzarella.org...
> PA Bear [MS MVP] wrote:
>
>> Devil's Advocate: If posts were not removed from OE (in its current
>> design
>> state) when they were removed from the server and a heavy newsgroup user
>> never deleted any posts manually, consider how bloated and ripe for
>> corruption the message store would become over time!
>
> How true. There is still the 2GB maximum file size for the .dbx files
> used by OE. That means you cannot store more than 2GB worth of headers
> and bodies in a .dbx file for a newsgroup. Exceeding that threshold
> results in a corrupted .dbx file. So with NNTP servers with extreme
> retention intervals and with a user that downloads all headers and also
> all their bodies then it becomes more likely the 2GB threshold gets
> exceeded.
>

So you're saying that the software isn't intelligent enough to just say:
"Hey, you've reached the limit. Can't download anymore. Would you like me to
clear some messages for you"? Instead it has to automatically delete
messages, just to avoid the 2 GB limit??? Ridiculous!

For what it's worth, all of my newsgroup DBXs are less than 10 MB! Not even
anywhere close to 2 GB!!!!!

And, again, if it ever did come close, a simple message prompting to delete
old messages would be fine (similar to what Windows does when your hard
drive gets near capacity).



From: PA Bear [MS MVP] on
Neil wrote:
>> Devil's Advocate: If posts were not removed from OE (in its current
>> design
>> state) when they were removed from the server and a heavy newsgroup user
>> never deleted any posts manually, consider how bloated and ripe for
>> corruption the message store would become over time!
>
> This is why OE has the option to remove messages which are more than X
> days
> old when the message store is compacted. But it doesn't seem to respect
> that, and just deletes messages...

If enabled, that option will ONLY delete downloaded message bodies. It does
NOT remove the downloaded headers.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Prev: Error code 0x800CCC0E & 0X8000CCC78
Next: errore