When I look into the Registry then I find four similar branches in HKLM\SYSTEM\:

- CurrentControlSet
- ControlSet001
- ControlSet002
- ControlSet003

Are the branches with the numbers generation driven backups of the leading CurrentControlSet?

In other words: if I change something in CurrentControlSet will it be automatically shifted
at a later time to the ControlSet001, 002, 003?

Can I somehow force immediately shifting?

Peter

"Peter Swindon" <p-(E-Mail Removed)> wrote in message
news:4d76075b$0$6890$(E-Mail Removed)...
> When I look into the Registry then I find four similar branches in
> HKLM\SYSTEM\:
>
> - CurrentControlSet
> - ControlSet001
> - ControlSet002
> - ControlSet003
>
> Are the branches with the numbers generation driven backups of the
> leading CurrentControlSet?
>
> In other words: if I change something in CurrentControlSet will it
> be automatically shifted
> at a later time to the ControlSet001, 002, 003?
>
> Can I somehow force immediately shifting?
>

AAIU, you can have up to 3 ControlSet00x branches: One for Current,
one for Failed, and one for Last Known Good. Look at the
HKLM\SYSTEM\Select key and you'll see values for each of those control
sets (as well as one for Default, but I confess I don't have a good
understanding of what that is used for).

CurrentControlSet is a pointer to one of the other control sets - that
is, it doesn't really exist at all, it is just another way of
referring to the control set that is currently in use. Typically,
that is ControlSet001 unless you've had a failure to boot and resorted
to the last known good configuration. Again, look to
HKLM\SYSTEM\Select to see which that is.

So, really the only one you need to be concerned with is
CurrentControlSet. Make your changes there, they automatically and
immediately "shift" to the correct ControlSet00x branch, and you don't
need to make changes to any of the others (and probably shouldn't in
the case of LastKnownGood just in case that makes it no longer
"good").

Oh, and in the future, you probably should announce if you are setting
a followup to a specific newsgroup, otherwise those in the other
newsgroup(s) won't see their (or any other) replies and can't follow
the thread without figuring out what happened...

Followups reset back to the original group list.
--
Zaphod

Arthur Dent, speaking to Trillian about Zaphod:
"So, two heads is what does it for a girl?"
"...Anything else he's got two of?"

Zaphod Beeblebrox wrote:
>
> Oh, and in the future, you probably should announce if you are setting
> a followup to a specific newsgroup, otherwise those in the other
> newsgroup(s) won't see their (or any other) replies and can't follow
> the thread without figuring out what happened...

Not only that, but using the Folowup-to header is extremely inconsiderate, I
would even say rude. It is *not* for someone else to decide where *my* replies
go. I may change the group list if I think what I write is relevant (or not) to
some of the groups; the previous poster has no way of knowing that.


> Followups reset back to the original group list.

Thanks for doing it.

--
You'd be crazy to e-mail me with the crazy. But leave the div alone.
*
Whoever bans a book, shall be banished. Whoever burns a book, shall burn.

Note: It is rude to yank away the thread from those of whom you ask for
help. Don't shotgun your post to groups where you don't intend to
continue your discussion. If you don't want to continue a discussion in
a group then don't post there.

FollowUp-To: (ignored)
microsoft.public.windowsxp.help_and_support

Original & restored newsgroups:
microsoft.public.windowsxp.general
microsoft.public.windowsxp.help_and_support


Peter Swindon wrote:

> When I look into the Registry then I find four similar branches in
> HKLM\SYSTEM\:
>
> - CurrentControlSet
> - ControlSet001
> - ControlSet002
> - ControlSet003
>
> Are the branches with the numbers generation driven backups of the
> leading CurrentControlSet? In other words: if I change something in
> CurrentControlSet will it be automatically shifted at a later time to
> the ControlSet001, 002, 003? Can I somehow force immediately
> shifting?

http://support.microsoft.com/kb/100010

"The CurrentControlSet subkey is really a pointer to one of the
ControlSetXXX keys."

HKEY_LOCAL_MACHINE\SYSTEM\Select tells you to which controlset the
CurrentControlSet (current) is pointing.

Zaphod Beeblebrox wrote:

> Oh, and in the future, you probably should announce if you are setting
> a followup to a specific newsgroup, otherwise those in the other
> newsgroup(s) won't see their (or any other) replies and can't follow
> the thread without figuring out what happened...

Luckily I use a newsreader that alerts me when someone tries to use the
FollowUp-To header. There are extremely few groups where this header
should be used, like where you post only an exhibit in one group but it
gets discussed in a different group. It also alerts me to the jokers
who use the X-No-Archive header to punch holes in the thread. Obviously
they consider their posts as valueless.

As to the FollowUp-To header, and while I have a long pre-canned rant on
the topic, the short version is "Don't be rude by yanking away the
discussion. If you don't want to continue your thread in a newsgroup
then don't post there."

> Followups reset back to the original group list.

When using the FollowUp-To header (which requests a newsreader to change
the Newsgroups header) or when you change the Newsgroups header
yourself, you should note that election. It is polite to add the note
at the top of your post. Tell or warn upfront, not at the end. It was
appreciated that you noted why you ignored the FollowUp-To header.

Patok wrote:
> Zaphod Beeblebrox wrote:
>>
>> Oh, and in the future, you probably should announce if you are setting
>> a followup to a specific newsgroup, otherwise those in the other
>> newsgroup(s) won't see their (or any other) replies and can't follow
>> the thread without figuring out what happened...
>
> Not only that, but using the Folowup-to header is extremely
> inconsiderate, I would even say rude. It is *not* for someone else to
> decide where *my* replies go. I may change the group list if I think
> what I write is relevant (or not) to some of the groups; the previous
> poster has no way of knowing that.
>
>
>> Followups reset back to the original group list.
>
> Thanks for doing it.
>

You do realize you're wasting your breath, don't you ?

The OP of this thread, is a nym shifter, and has used the
same quirky header pattern for eons. Once the OP "wears out
a name", he'll be back with a new nym.

One of the characteristics of the OP, is he/she/it never
comes back to respond to anything stated in the thread.
So you can't "have a debate" about setting followups, because
the OP won't be back. But, the OP will be back with a new
question, at a frequency of roughly once a week.

Other names, "Cindy" something, or "Herbert Meister". The
fact that OP never posts back, is one of the weight factors
for concluding it's our hero, in a new disguise.

Paul

Paul wrote:
>
> You do realize you're wasting your breath, don't you ?
>
> The OP of this thread, is a nym shifter, and has used the
> same quirky header pattern for eons. Once the OP "wears out
> a name", he'll be back with a new nym.
>
> One of the characteristics of the OP, is he/she/it never
> comes back to respond to anything stated in the thread.
> So you can't "have a debate" about setting followups, because
> the OP won't be back. But, the OP will be back with a new
> question, at a frequency of roughly once a week.
>
> Other names, "Cindy" something, or "Herbert Meister". The
> fact that OP never posts back, is one of the weight factors
> for concluding it's our hero, in a new disguise.

Hah. Indeed, I hadn't noticed. Weird. His (its) questions seem genuine,
though, and the answers (when there are any) are informative. It would be much
worse if it was inane drivel; now, I don't know...

--
You'd be crazy to e-mail me with the crazy. But leave the div alone.
*
Whoever bans a book, shall be banished. Whoever burns a book, shall burn.

Paul wrote:

> The OP of this thread, is a nym shifter, and has used the
> same quirky header pattern for eons. Once the OP "wears out
> a name", he'll be back with a new nym.

And just what is this "quirky header pattern" of which you mention?
Other than news.arcor.de as the injection point in the Path header, what
other headers are "quirky"? Just what do you think constitutes a
fingerprint of this supposed nymshifter on which a kill filter could be
based?

VanguardLH wrote:
> Paul wrote:
>
>> The OP of this thread, is a nym shifter, and has used the
>> same quirky header pattern for eons. Once the OP "wears out
>> a name", he'll be back with a new nym.
>
> And just what is this "quirky header pattern" of which you mention?
> Other than news.arcor.de as the injection point in the Path header, what
> other headers are "quirky"? Just what do you think constitutes a
> fingerprint of this supposed nymshifter on which a kill filter could be
> based?

The setting of the followup. As far as I know, only one person
does this frequently. And is going by the name "Peter Swindon"
and the moment. But has also made appearances as Herbert Meister
and many others. I'm not sufficiently interested, to keep a file
on this. It's not exactly "high grade troll" material. It's only
annoying if you post an answer to a question of his, don't see
your response, post the answer again, then figure out something
is wrong, look at the original header, and realize you've been
blindsided.

It does mean, since running into this annoying habit, I've had to
do more checking of headers before replying to people.

Paul

Paul wrote:

> VanguardLH wrote:
>
>> Paul wrote:
>>
>>> The OP of this thread, is a nym shifter, and has used the
>>> same quirky header pattern for eons. Once the OP "wears out
>>> a name", he'll be back with a new nym.
>>
>> And just what is this "quirky header pattern" of which you mention?
>> Other than news.arcor.de as the injection point in the Path header, what
>> other headers are "quirky"? Just what do you think constitutes a
>> fingerprint of this supposed nymshifter on which a kill filter could be
>> based?
>
> The setting of the followup. As far as I know, only one person
> does this frequently. And is going by the name "Peter Swindon"
> and the moment. But has also made appearances as Herbert Meister
> and many others. I'm not sufficiently interested, to keep a file
> on this. It's not exactly "high grade troll" material. It's only
> annoying if you post an answer to a question of his, don't see
> your response, post the answer again, then figure out something
> is wrong, look at the original header, and realize you've been
> blindsided.
>
> It does mean, since running into this annoying habit, I've had to
> do more checking of headers before replying to people.
>
> Paul

I visit about 50 newsgroups and participate in about 30 of them. My
newsreader colorizes (as violet) any post that uses the FollowUp-To
header along with showing a bolded copy of that header in the header
pane section of the preview pane showing the post. In wandering through
all those newsgroups, I see LOTS of violet colored posts (I won't see
the bolded header unless I select the post) and far too many to be from
just one poster. That this poster used the FollowUp-To header is far
from sufficient as a fingerprint to identify them under other nyms.

Sorry, but after about 2 decades of participation, I learned long ago
that I shouldn't expect any ego stroking in the form of a reply (to say
if my help was good, bad, off the mark, or whatever). If they reply,
it's good for others (so they know one of the responses was a solution).
If they don't reply, no big deal. In fact, MOST users are not regulars
in Usenet and they do not return after getting a solution to add a reply
to tell us what happened. It depends on the newsgroup where you
replied. Some exhibit more probability of getting reply but don't
expect one and don't come to think it is even required. They got a
solution, they went forward, they don't come back here with an update.
That is v-e-r-y normal in newsgroups.

Feedback shouldn't be to help you feel good about responding. Feedback
is to help others researching the same problem know that one of the
responses was beneficial; however, that feedback is not required for
others to also make use of a solution found in a thread.