Xref:	news2.mv.net comp.os.ms-windows.nt.pre-release:11359 comp.os.msdos.djgpp:7399
From:	abealby AT hookup DOT net (Alan Bealby)
Newsgroups:	comp.os.msdos.djgpp,comp.os.ms-windows.nt.pre-release
Subject:	Re: Duplicate posts and MSNEWS wierdness Was: Re: NT4.0 and long filenames under DOS
Date:	Fri, 16 Aug 1996 20:43:10 GMT
Organization:	HookUp Communication Corporation, Oakville, Ontario, CANADA
Lines:	68
Message-ID:	<4v2mb6$5lp@loki.tor.hookup.net>
References:	<1996Aug14 DOT 0415260128 DOT 85 DOT 214 AT UPPSSNEWSPUB05> <32120C9A DOT 4A1D AT btmaa DOT bel DOT alcatel DOT be> <4ute2j$ce9 AT rs18 DOT hrz DOT th-darmstadt DOT de> <32138941 DOT 2712360 AT nnrp DOT wat DOT hookup DOT net>
NNTP-Posting-Host:	abealby.tor.hookup.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Re: Something wrong with MSNEWS server.  I run Free Agent 1.0 and am
experiencing problems with it.  I have seen some messages saying that
when Microsoft did some maintenance work last week they removed some
messages from the system but left some on with a high message number and
then restarted the system with new messages being given low message
numbers.  Apparently Free Agent keeps track of new messages by comparing
new message numbers to the highest on the server in the group.  New
messages are therefore not showing up as new messages.  This could
explain what is happening because I can get Free Agent to show messages
after last week if I reset everything but on the next access no new
messages sho up.   One message said ask Free Agent to show all messages,
not just unread ones.  A very painful way to try to use a News system.

Not very satisfactory.  I will probalby leave MSNEWS for awhile until it
is fixed.

Alan

alrudder AT hookup DOT net (Al Rudderham) wrote:

>On 14 Aug 1996 20:48:19 GMT, lehmann AT mathematik DOT th-darmstadt DOT de (Alexander
>Lehmann) wrote:

>>In comp.os.ms-windows.nt.pre-release Nico Holvoet <holvoetn AT btmaa DOT bel DOT alcatel DOT be> wrote:
>>
>>: Hey, Dude,
>>
>>: How many times you think you are going to post this again ???
>>
>>: (I already counted more than ten (10))
>>
>>Actually, I have posted the article only once with the message-ID
>><4uqcok$25qs AT rs18 DOT hrz DOT th-darmstadt DOT de>, it seems that some system
>>called UPPSSNEWSPUB05 (no domain in the messsage-ID, so I don't know
>>what that is) has reposted the article, different followups have
>>different MSG-IDs with UPPSSNEWSPUB05 after the @ as first Reference.
>>
>>I haven't seen any of the repost articles, maybe they cleaned up their
>>spew already.

>Originally, you posted this to microsoft.public.windowsnt.40beta on
>msnews.microsoft.com as well as comp.os.msdos.djgpp and
>comp.os.ms-windows.nt.pre-release.

>I think something has gone seriously wrong with MSNEWS.  In the last few
>days there have been many posts showing up in "regular" newsgroups that are
>heavily duplicated.  (Although yours does seem to be the worst.)

>As well, I have been unable to access MSNEWS for the last 3-4 days.  At
>first it did not respond for a day.  Then it came back online, and I saw a
>huge number of new headers, although most were duplicated.  Since then I
>can reach it, but there are NO new headers to retrieve, in normally busy
>newsgroups.

>As an aside, I use Agent .99e under NT, and Agent does not support multiple
>news servers.  To work around that I start a 2nd copy from a 2nd directory.
>This works fine normally.  But it leaves me with 2 seperate views of
>newsgroups - those served by my ISP (which does not carry
>microsoft.public.*) and those served by msnews.microsoft.com.

>All of the "regular" newsgroups (those from my ISP's server) I watch are
>working fine.  Except that there are some duplicated posts, like yours.
>I've noticed that in every case those duplicates were crossposted to at
>least one microsoft.public group too.

>I suspect that something has gone seriously wrong with MSNEWS...

- Raw text -