Hi Dmitry,
In answer to your question, Dave Patrick is right - if you can, it is
far preferable to deal with this matter using the supplier user
interface (ie: device manager in control panel0 On win2k+ you may need
to 'unhide' devices to get the full picture, as he described in his posting.
If you must do this by editing the registry, you need a clear picture in
your mind of what is going on - have a read of
http://nt4ref.zcm.com.au/mansd.htm as a starting point. In Win2k+ you
will find additional content in the registry not mention in my article -
it primarily deals with the situation with NT4.
As Dave Patrick also pointed out, you only need to worry about
HKLM/System/CurrentControlSet. CurrentControlSet is a 'hard link' (ie:
it doesn't exist as such, CurrentControl Set is an alias pointing to one
of the ControlSets - ControlSet001, ControlSet002 etc..) which is
currently in use by the system. If you really want to know which set is
currently in use you can find out by examining the key
HKLM/System/Select/Current - the data value here tells you which
ControlSet is currently aliased as 'CurrentControlSet' You will also
find the keys here for which set (if any) has failed, which is the
default set and which is the 'LastKnownGood'
When you make changes to CurrentControlSet, after the next successful
system reboot, the changes will also be replicated in the
'LastKnownGood' control set - so there is no need to edit their content,
and even if you do, you changes will be overwritten at next reboot with
whatever is in the CurrentControlSet.
Hope this info helps.
Calvin.