| … | |
… | |
| 76 | |
76 | |
| 77 | =back |
77 | =back |
| 78 | |
78 | |
| 79 | The target audience for this program is professionals and tinkerers who |
79 | The target audience for this program is professionals and tinkerers who |
| 80 | are ready to invest time into learning how it works. It is not an easy |
80 | are ready to invest time into learning how it works. It is not an easy |
| 81 | program to use and requires patience and a good understanding of BCD data |
81 | program to use and requires patience and a good understanding of BCD |
| 82 | stores. |
82 | stores. |
| 83 | |
83 | |
| 84 | |
84 | |
| 85 | =head1 SUBCOMMANDS |
85 | =head1 SUBCOMMANDS |
| 86 | |
86 | |
| … | |
… | |
| 112 | |
112 | |
| 113 | =item C<edit> F<path> I<instructions...> |
113 | =item C<edit> F<path> I<instructions...> |
| 114 | |
114 | |
| 115 | Load a BCD data store, apply some instructions to it, and save it again. |
115 | Load a BCD data store, apply some instructions to it, and save it again. |
| 116 | |
116 | |
| 117 | See the section L<EDITING BCD DATA STORES>, below, for more info. |
117 | See the section L<EDITING BCD STORES>, below, for more info. |
| 118 | |
118 | |
| 119 | =item C<parse> F<path> I<instructions...> |
119 | =item C<parse> F<path> I<instructions...> |
| 120 | |
120 | |
| 121 | Same as C<edit>, above, except it doesn't save the data store again. Can |
121 | Same as C<edit>, above, except it doesn't save the data store again. Can |
| 122 | be useful to extract some data from it. |
122 | be useful to extract some data from it. |
| … | |
… | |
| 146 | |
146 | |
| 147 | With C<--json> it prints similar information as a JSON object, for easier parsing. |
147 | With C<--json> it prints similar information as a JSON object, for easier parsing. |
| 148 | |
148 | |
| 149 | =item C<export-regf> F<path> |
149 | =item C<export-regf> F<path> |
| 150 | |
150 | |
| 151 | This has nothing to do with BCD data stores - it takes a registry hive |
151 | This has nothing to do with BCD stores - it takes a registry hive |
| 152 | file as argument and outputs a JSON representation of it to standard |
152 | file as argument and outputs a JSON representation of it to standard |
| 153 | output. |
153 | output. |
| 154 | |
154 | |
| 155 | Hive versions 1.2 till 1.6 are supported. |
155 | Hive versions 1.2 till 1.6 are supported. |
| 156 | |
156 | |
| … | |
… | |
| 709 | seems to be always there on this kind of entry. |
709 | seems to be always there on this kind of entry. |
| 710 | |
710 | |
| 711 | If you have some good examples to add here, feel free to mail me. |
711 | If you have some good examples to add here, feel free to mail me. |
| 712 | |
712 | |
| 713 | |
713 | |
| 714 | =head1 EDITING BCD DATA STORES |
714 | =head1 EDITING BCD STORES |
| 715 | |
715 | |
| 716 | The C<edit> and C<parse> subcommands allow you to read a BCD data store |
716 | The C<edit> and C<parse> subcommands allow you to read a BCD data store |
| 717 | and modify it or extract data from it. This is done by executing a series |
717 | and modify it or extract data from it. This is done by executing a series |
| 718 | of "editing instructions" which are explained here. |
718 | of "editing instructions" which are explained here. |
| 719 | |
719 | |
