newgroup posting show up as unread the session after I read them

Hi, Al.

Yes, sadly, it happens to me fairly often. As nearly as I can tell - or
guess - it's because I shut down the previous WLM session before it had a
chance to do its cleanup housekeeping. This can happen when I exit too
quickly after an operation like Sync Everything. Today it happened because
my grandson hit Shut Down instead of Switch User when he wanted to switch to
his user account to visit his schools' first grade website.

I usually give WLM some time to do its closing homework by making sure no
send/receive activity is going on when I Exit WLM. Then, just to be sure, I
play a game of Free Cell before hitting Shut Down. That usually works. ;<)

RC
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8064.0206) in Win7 Ultimate x64 RC 7100

"Al Dunbar" wrote in message
news:

At first I thought I was clairvoyant, as I would start following a thread
and intrinsically know what the next person's response was. Then I
realized that, even though they were marked as having been read after I
read them, the next time I started WLM they would appear as unread.

Is this a common problem? Is there a fix?

/Al

"Al Dunbar" wrote in message news:

At first I thought I was clairvoyant, as I would start following a thread
and intrinsically know what the next person's response was. Then I realized
that, even though they were marked as having been read after I read them,
the next time I started WLM they would appear as unread.

Is this a common problem?

Yes. For me it is mostly in the PowerShell NG.
It's not just the read indicator either that gets lost.
I have tried marking the threads involved in other ways too
to try to find a way to make its messages stay read and marked.

However, I suspect that the only reason it's that NG
is because that is the one I read last. E.g. once I figured
that factor out I started opening last chat type NG that I don't
care about as much.

Is there a fix?

I'll let you know later. My WLMail Message Store was
the victim of XP's arbitrary disk cleanup procedure
when I had accidently left ProcMon's BootLogging
active for so long that it filled my %SystemDrive% partition.
That's a good reason for giving WLMail's Message Store
it's own partition. ; )

Before that what I had been doing is using Task Manager
or Process Explorer to check that WLMail was not doing
any writes before I closed it. Anyway, I suspect that it loses
queued writes when I close it. BTW I remember that NT
used to have a registry tweak about this but can't remember
what it was nor do I know whether XP would need the same
thing.

So which OS are you using that this is happening on? <eg>


HTH

Robert

Al

Happens here also. I also find the same as R.C. and Robert posted

Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Al Dunbar" wrote in message
news:

At first I thought I was clairvoyant, as I would start following a thread and
intrinsically know what the next person's response was. Then I realized that, even
though they were marked as having been read after I read them, the next time I
started WLM they would appear as unread.

Is this a common problem? Is there a fix?

/Al

"Robert Aldwinckle" wrote in message
news:

"Al Dunbar" wrote in message
news:

At first I thought I was clairvoyant, as I would start following a thread
and intrinsically know what the next person's response was. Then I
realized
that, even though they were marked as having been read after I read them,
the next time I started WLM they would appear as unread.

Is this a common problem?

Yes. For me it is mostly in the PowerShell NG.
It's not just the read indicator either that gets lost.
I have tried marking the threads involved in other ways too
to try to find a way to make its messages stay read and marked.

However, I suspect that the only reason it's that NG
is because that is the one I read last. E.g. once I figured
that factor out I started opening last chat type NG that I don't
care about as much.

Is there a fix?

I'll let you know later. My WLMail Message Store was
the victim of XP's arbitrary disk cleanup procedure
when I had accidently left ProcMon's BootLogging
active for so long that it filled my %SystemDrive% partition.
That's a good reason for giving WLMail's Message Store
it's own partition. ; )

Before that what I had been doing is using Task Manager
or Process Explorer to check that WLMail was not doing
any writes before I closed it. Anyway, I suspect that it loses
queued writes when I close it. BTW I remember that NT
used to have a registry tweak about this but can't remember
what it was nor do I know whether XP would need the same
thing.

So which OS are you using that this is happening on? <eg>

XP Pro.

/Al