Changeset 64 for trunk/doc/reglookup.1.docbook
- Timestamp:
- 07/23/06 12:02:53 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/reglookup.1.docbook
-
Property
svn:keywords
set to
Id
r63 r64 1 1 <?xml version="1.0" encoding="UTF-8"?> 2 2 <refentry id='reglookup.1'> 3 <!-- $Id :$ -->3 <!-- $Id$ --> 4 4 <refmeta> 5 5 <refentrytitle>reglookup</refentrytitle> … … 12 12 </refnamediv> 13 13 14 <refsect1 id='syn tax'>14 <refsect1 id='synopsis'> 15 15 <title>SYNOPSIS</title> 16 16 <para> 17 <command>reglookup [options]</command> <replaceable>registry-file</replaceable> 17 <command> 18 reglookup [options] <replaceable>registry-file</replaceable> 19 </command> 18 20 </para> 19 21 </refsect1> … … 30 32 </refsect1> 31 33 32 <refsect1 id=' caveats'>34 <refsect1 id='options'> 33 35 <title>OPTIONS</title> 34 36 <para> … … 222 224 </para> 223 225 <para> 224 MTIME and SID conversions haven't been checked for accuracy. 226 The SID conversions haven't been carefully checked for accuracy. 227 </para> 228 <para> 229 The MTIME conversions appear correctly produce the stored UTC timestamp. 230 However, due to the periodicity of registry writes, and the complexity 231 of the conversion, a small amount of error (on the order of seconds) may 232 be possible. The documentation available online from Microsoft on 233 this field is very poor. 225 234 </para> 226 235 <para> … … 231 240 <para> 232 241 You'll notice that registry paths aren't all the same as the 233 ones the equivalents you see in the windows registry editor.234 Don't ask me whythat is. I just work here.242 equivalents you see in the windows registry editor. Don't ask me why 243 that is. I just work here. 235 244 </para> 236 245 <para> … … 266 275 </para> 267 276 </refsect1> 277 278 <refsect1 id='seealso'> 279 <title>SEE ALSO</title> 280 <para> 281 reglookup-timeline(1) 282 </para> 283 </refsect1> 268 284 </refentry> -
Property
svn:keywords
set to
Note: See TracChangeset
for help on using the changeset viewer.