Ye Haw....it worked

It worked and *Windows confirmed* the change at the second boot after the
change. What a pleasant discovery, Mike.
You deserve a trophy for that.
I knew that it worked earlier, quite earlier, but to see windows'
confirmation topped it off.
Thanks again, Mike.

Harry.

"N. Miller" wrote in message
...
On Sun, 11 Mar 2007 17:17:25 -0400, webster72n wrote:

It worked and *Windows confirmed* the change at the second boot after
the
change. What a pleasant discovery, Mike.
You deserve a trophy for that.
I knew that it worked earlier, quite earlier, but to see windows'
confirmation topped it off.
Thanks again, Mike.

I have no clue what you are talking about. There are no "References" to
"Message-ID" strings, so your post is just a new message. Couldn't you
have
appended this post to the proper thread?

The idea was, to just let Mike and everyone know, without *getting lost in
the shuffle*, using '' in the subject line.
If that's inappropriate, I offer my apologies. H.


--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.

Much too complicated for me, Norman.
I shall refrain from using this method in the future.
Thanks for the *clarification*.

Harry.


"N. Miller" wrote in message
...
On Sun, 11 Mar 2007 22:42:01 -0400, webster72n wrote:

"N. Miller" wrote in message
...

On Sun, 11 Mar 2007 17:17:25 -0400, webster72n wrote:

It worked and *Windows confirmed* the change at the second boot after
the change. What a pleasant discovery, Mike.
You deserve a trophy for that.
I knew that it worked earlier, quite earlier, but to see windows'
confirmation topped it off.
Thanks again, Mike.

I have no clue what you are talking about. There are no "References" to
"Message-ID" strings, so your post is just a new message. Couldn't you
have appended this post to the proper thread?

The idea was, to just let Mike and everyone know, without *getting lost
in
the shuffle*, using '' in the subject line.
If that's inappropriate, I offer my apologies. H.

A post which has a verbal clue that it belongs in a thread, but no
references header pointing to the thread it belongs in, is useless without
the context of that thread. Some of us don't use the MSFT toy new reader,
MSOE, but real news readers, such as 40tude Dialog. Unlike MSFT's toy,
real
news readers treat different posts with similar subject line as different
posts. They use the references headers to thread the conversation.

Your posting headers of the post I replied:

| From: webster72n
| Subject: Ye Haw....it worked
| Date: Sun, 11 Mar 2007 17:17:25 -0400
| Lines: 10
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1478
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
| Message-ID:
| Newsgroups: microsoft.public.windowsme.general
| NNTP-Posting-Host: node74.198.100.208.1dial.com 208.100.198.74
| Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
| Xref: TK2MSFTNGP01.phx.gbl microsoft.public.windowsme.general:287475

Note the lack of a references header line; and compare it with the headers
of your reply to mine:

| From: webster72n
| References:

| Subject: Ye Haw....it worked
| Date: Sun, 11 Mar 2007 22:42:01 -0400
| Lines: 31
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1478
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
| Message-ID:
| Newsgroups: microsoft.public.windowsme.general
| NNTP-Posting-Host: node188.198.100.208.1dial.com 208.100.198.188
| Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
| Xref: TK2MSFTNGP01.phx.gbl microsoft.public.windowsme.general:287488

Second line contains the Message-ID strings of the preceding posts in the
thread.

MSOE *will* thread unrelated posts with the same subject line, 40tude
Dialog, and most other real news readers, will not.

Heh. And Windows Live Mail Desktop (Beta) is just as broken. Maybe I need
to
sign up so I can "bug" this useless MSFT "feature".

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.

Norman......it didn't *thread properly* with my OE either. OTOH, Harry
took out the second "E" in the subject YEE HAW.......which changed the
threading.

But I will say that he should have left some clue in the message as to
who in heck he was talking to. I knew because I started that subject
thread......and you should have known as well.

YEE GODS......it is such a mickey mouse item anyway and you wasted a lot
of time and bandwith on it. Does "N" stand for "Netcop"?? (G)

HF
"N. Miller" wrote in message
...
On Sun, 11 Mar 2007 22:42:01 -0400, webster72n wrote:

"N. Miller" wrote in message
...

On Sun, 11 Mar 2007 17:17:25 -0400, webster72n wrote:

It worked and *Windows confirmed* the change at the second boot
after
the change. What a pleasant discovery, Mike.
You deserve a trophy for that.
I knew that it worked earlier, quite earlier, but to see windows'
confirmation topped it off.
Thanks again, Mike.

I have no clue what you are talking about. There are no "References"
to
"Message-ID" strings, so your post is just a new message. Couldn't
you
have appended this post to the proper thread?

The idea was, to just let Mike and everyone know, without *getting
lost in
the shuffle*, using '' in the subject line.
If that's inappropriate, I offer my apologies. H.

A post which has a verbal clue that it belongs in a thread, but no
references header pointing to the thread it belongs in, is useless
without
the context of that thread. Some of us don't use the MSFT toy new
reader,
MSOE, but real news readers, such as 40tude Dialog. Unlike MSFT's toy,
real
news readers treat different posts with similar subject line as
different
posts. They use the references headers to thread the conversation.

Your posting headers of the post I replied:

| From: webster72n
| Subject: Ye Haw....it worked
| Date: Sun, 11 Mar 2007 17:17:25 -0400
| Lines: 10
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1478
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
| Message-ID:
| Newsgroups: microsoft.public.windowsme.general
| NNTP-Posting-Host: node74.198.100.208.1dial.com 208.100.198.74
| Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
| Xref: TK2MSFTNGP01.phx.gbl microsoft.public.windowsme.general:287475

Note the lack of a references header line; and compare it with the
headers
of your reply to mine:

| From: webster72n
| References:

| Subject: Ye Haw....it worked
| Date: Sun, 11 Mar 2007 22:42:01 -0400
| Lines: 31
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1478
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
| Message-ID:
| Newsgroups: microsoft.public.windowsme.general
| NNTP-Posting-Host: node188.198.100.208.1dial.com 208.100.198.188
| Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
| Xref: TK2MSFTNGP01.phx.gbl microsoft.public.windowsme.general:287488

Second line contains the Message-ID strings of the preceding posts in
the
thread.

MSOE *will* thread unrelated posts with the same subject line, 40tude
Dialog, and most other real news readers, will not.

Heh. And Windows Live Mail Desktop (Beta) is just as broken. Maybe I
need to
sign up so I can "bug" this useless MSFT "feature".

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.

"N. Miller" wrote in message
...
On Mon, 12 Mar 2007 12:59:56 -0400, Heather wrote:

Does "N" stand for "Netcop"?? (G)

Asks the "Bandwidth Cop"!

Chuckle......couldn't resist, "N"......8-))