tools: Fix documentation for CurrentControlSet (thanks Yuval Kashtan).
authorRichard Jones <rjones@redhat.com>
Fri, 30 Apr 2010 08:46:40 +0000 (09:46 +0100)
committerRichard Jones <rjones@redhat.com>
Fri, 30 Apr 2010 08:46:40 +0000 (09:46 +0100)
tools/virt-win-reg

index 9ce84b5..91a1673 100755 (executable)
@@ -151,8 +151,23 @@ Paths and value names are case-insensitive.
 
 Registry keys like C<CurrentControlSet> don't really exist in the
 Windows Registry at the level of the hive file, and therefore you
 
 Registry keys like C<CurrentControlSet> don't really exist in the
 Windows Registry at the level of the hive file, and therefore you
-cannot modify these.  Replace this with C<ControlSet001>, and
-similarly for other C<Current...> keys.
+cannot modify these.
+
+C<CurrentControlSet> is usually an alias for C<ControlSet001>.  In
+some circumstances it might refer to another control set.  The way
+to find out is to look at the C<HKLM\SYSTEM\Select> key:
+
+ # virt-win-reg WindowsGuest 'HKLM\SYSTEM\Select'
+ [HKEY_LOCAL_MACHINE\SYSTEM\Select]
+ "Current"=dword:00000001
+ "Default"=dword:00000001
+ "Failed"=dword:00000000
+ "LastKnownGood"=dword:00000002
+
+"Default" is the one which Windows will choose when it boots.
+
+Similarly, other C<Current...> keys in the path may need to
+be replaced.
 
 =head1 OPTIONS
 
 
 =head1 OPTIONS