WinHex编辑工具模板教程
Winhex有一个查看数据结构的强大功能（模板），但经常被用户所忽略。用户可以使用winhex相应的模板文件编辑文件的数据结构。用户同样可以用自己设计的模板文件来查看指定文件的数据结构。
为了演示如何使用模板，这里我们引入比较常见的“dbf”以及“xbase”数据库文件。样本文件中提供了包含美国50个州的信息的dbf文件。
样本dbf文件中包括三个部分
文件头
域信息
数据记录
头文件的长度为32字节，未使用的位置用0填充。
BYTES DESCRIPTION
00 Version (see below)
01-03 Last update, format YYMMDD
04-07 Number of records in file (32-bit number)
08-09 Length of header (16-bit number)
10-11 Number of bytes in record (16-bit number)
12-13 Reserved, fill with 0x00
14 Incomplete transaction flag (dbase IV)
Begin Transaction sets it to 0x01
End Transaction or RollBack reset it to 0x00
15 Encryption flag, encrypted 0x01 else 0x00
16-27 dBaseIV multi-user environment use
28 Production index exists - 0x01 else 0x00
dBaseIV language driver ID
30-31 Reserved, fill with 0x00
版本通常为03
0xf5表示FoxPro
0x8b表示dBaseIV
0x8e表示dBaseIV
首先用winhex打开数据库文件，然后从工具菜单下打开模板管理器，通常修改一个现有的模板会比自己重新编写要来的简单和方便。
模板文件通常以template开头，随后加上模板的名字。另起一行输入description之后便是模板文件的描述。打开模板编辑器会显示相应模板的模板名以及描述。同样，你也可以利用这个原理在模板中添加注释（和c编程一样，在双斜杠“//”之后便是注释）
template "dbf header"
// Sample template by Paul Mullen
description "First 32 bytes of a dBase/xBase .dbf file"
接下来将详细的讲下模板文件的编写方法：
先看下面一段代码。
appliesto file
requires 30 "00 00"
代码的第一句告诉我们此模板匹配于文件结构而不是磁盘结构，第二句检查了文件的头部信息，判断文件是否有效。The second is a check for validity of the file format, and just checks that the header ends with two zero bytes.
现在，我们就该进入模板文件的执行部分，即：begin和end之间的代码。
代码由数据类型和描述组成，可以用以下数据类型（常用）来描述区块类型：
hex
uint8 (byte)
int8 - signed byte size integer
int (int16) - 16 bit signed integer
uint (uint16, word) - 16 bit unsigned integer
int32 (long) - 32 bit unsigned integer
uint32 (dword) - 32 bit unsigned integer
int64 (longlong) - 64 bit signed integer
float (single) - 32 bit (single precision) floating point
real - 48 bit floating point
double - 64 bit (double precision) floating point
longdouble (extended) -128bit floating point
char (string) - ASCII text
char16 (string16) - Unicode
接下来，我们来看一个描述dbase文件头的模板文件代码：
begin
hex “Version”
byte 3 “Last update, format YYMMDD”
uint32 “Number of records in file”
uint16 “Length of header”
uint16 “Data Record length”
hex 2 “Reserved, fill with 0”
byte “Incomplete transaction”
byte “Encryption flag”
hex 12 “dBaseIV multi-user”
byte “Production index exists”
byte “dBaseIV language”
hex 2 “always 0x00”
end
当我们在一行代码前加上“read-only”标志后，则我们打开模板文件后此行将会灰色显示（只读，无法编辑）
好了，让我们来看一下states.dbf文件，此文件的版本为3，最后更新时间为96年6月11号，在第257个字节之后包含51个数据记录。每条数据的长度为69字节。
257个字节中除了文件头，还有域描述（每条32个字节，以一个0字节结尾）。计算一下可以得出有7个域在文件中(32 + 7*32 + 1 = 257)
以下是域的详细解释：
BYTES DESCRIPTION
0-10 Field Name ASCII padded with 0x00
11 Field Type Identifier (see below)
12-15 Offset of field in record
16 Field length in bytes
17 Field decimal places
18-19 Reserved
20 dBaseIV work area ID
21-30 Reserved
31 Field is part of production index - 0x01 else 0x00
xbase fields types:
Code Description
C Character
D Date, format YYMMDD
F Floating Point
G General - FoxPro addition
L Logical, T:t,F:f,Y:y,N:n,?-not initialized
M Memo (stored as 10 digits representing the dbt block number)
N Numeric
P Picture - FoxPro addition
需要注意的是dbase文件中数字不是以二进制的方式存储的而是以字符的方式。所以每个域的数据类型都是字符型的。
因为文件中给出的域有多条所以用关键字“multiple”，这样就可以直接在模板中使用翻转按钮跳到下一处域（译者的话：这里如果不能理解的话可以参考winhex下的"FAT Directory Entry"模板）
template "dbf field"
// Sample template by Paul Mullen,
description "32 byte definition for each data field"
appliesto file
requires 10 00
multiple
begin
char "Field Name (zero terminated)"
read-only hex 1 "(zero terminator)"
char "Field Type"
int32 "offset from start of record"
byte "Field length (bytes)"
byte "Decimal places"
read-only hex 2 "(Reserved)"
byte "Work area ID"
read-only hex 10 "(Reserved)"
byte "Used in production index"
end
以下是数据库文件的域的描述：
Type Length Dec Name
N 12 3 Area
C 25 State Name
C 2 State FIPS
C 7 Region
C 2 Abbreviation
N 10 Pop 1990
N 10 Pop 1996
数据库中的域记录的开头是一个单字节。如果为“*”则说明此条记录无效。
相应的模板文如下：
template "dbf sample data record"
// Sample template by Paul Mullen
description "applies to states.dbf"
appliesto file
multiple
begin
char "*=deleted"
char "Area"
char "State Name"
char "FIPS"
char "Region"
char "Abbreviation"
char "Pop 1990"
char "Pop 1996"
end
现在你可以试着使用参照winhex下的一些模板编写属于自己的模板文件了。
作者：Paul Mullen 翻译：ozone
-----------------------------------------------------------------------------------
英文原文如下：
-----------------------------------------------------------------------------------
Tutorial on Templates
By Paul Mullen,
Winhex has a powerful but often overlooked way of viewing many different data file formats, the template.
A template describes the structure of each record in a binary data file, so enabling you to see and edit the actual values within each record. You can use a pre-defined template or very simply create your own each time you need to examine a data file.
To illustrate the use of templates, I will look at data in the popular “dbf”, or “xbase”, format, which originated with Ashton-Tate’s dBase program and has since been adopted by many applications. I have provided a sample file called states.dbf containing information about the 50 States of the USA.
A dbf file contains three portions:
Header
Field Descriptions
Data Records
The Header is 32 bytes long, unused fields at end being zero filled.
BYTES DESCRIPTION
00 Version (see below)
01-03 Last update, format YYMMDD
04-07 Number of records in file (32-bit number)
08-09 Length of header (16-bit number)
10-11 Number of bytes in record (16-bit number)
12-13 Reserved, fill with 0x00
14 Incomplete transaction flag (dbase IV)
Begin Transaction sets it to 0x01
End Transaction or RollBack reset it to 0x00
15 Encryption flag, encrypted 0x01 else 0x00
16-27 dBaseIV multi-user environment use
28 Production index exists - 0x01 else 0x00
dBaseIV language driver ID
30-31 Reserved, fill with 0x00
Version: usually 03 if there is no memo field, 0x83 with memo
FoxPro with memo - 0xF5
dBaseIV with memo - 0x8B
dBaseIV with SQL Table - 0x8E
To start creating a template, open the data file in Winhex, position the cursor at the start of a record, and then select the Template Manager from the Tools menu (shortcut, use Alt-F12). It is usually easier to start with an existing template and modify it, rather than create a new template from scratch. You can start use the dbf header.txt and dbf Fields.txt templates as they stand and then build your own data template based on dbf records.txt.
A template file always starts with the word template followed by a title, then there will be the keyword description followed by a longer description – both title and description will be shown by template manager. You can also add comments – everything on a line after // will be ignored.
template "dbf header"
// Sample template by Paul Mullen
description "First 32 bytes of a dBase/xBase .dbf file"
Next we can define how the template is to be used: a good idea to guard against user errors. For now let’s just use
appliesto file
requires 30 "00 00"
The first of these tells us to apply the template to a file, rather than a disk structure. The second is a check for validity of the file format, and just checks that the header ends with two zero bytes.
Now the file structure – which will begin with begin, and end with end!
Each line in between will consist of a type and a description. Depending on your preferred programming language, you can use alternative terms to describe each type of field. Common types (with alternatives) are:
hex
uint8 (byte)
int8 - signed byte size integer
int (int16) - 16 bit signed integer
uint (uint16, word) - 16 bit unsigned integer
int32 (long) - 32 bit unsigned integer
uint32 (dword) - 32 bit unsigned integer
int64 (longlong) - 64 bit signed integer
float (single) - 32 bit (single precision) floating point
real - 48 bit floating point
double - 64 bit (double precision) floating point
longdouble (extended) -128bit floating point
char (string) - ASCII text
char16 (string16) - Unicode
So our dBase header is going to look like this:
begin
hex “Version”
byte 3 “Last update, format YYMMDD”
uint32 “Number of records in file”
uint16 “Length of header”
uint16 “Data Record length”
hex 2 “Reserved, fill with 0”
byte “Incomplete transaction”
byte “Encryption flag”
hex 12 “dBaseIV multi-user”
byte “Production index exists”
byte “dBaseIV language”
hex 2 “always 0x00”
end
As a final touch, let’s mark the two reserved fields with the keyword read-only. This causes those line to appear greyed out, so they can’t be edited, and also forms convenient visual dividers in the record.
Ok, so when you look at the start of the states.dbf file, you should see that it was Version 3, last updated on 6/11/96 (11/6/96 for our European readers), contains 51 data records, which follow 257 bytes of header information, and each data record is 69 bytes long.
The rest of those 257 bytes of header consist of a number of field descriptions, each 32 bytes long, terminated by a single 0 byte. Arithmetic tells us that there must be seven fields in the file (32 + 7*32 + 1 = 257).
Each field in the data record is defined by a 32 byte entry as follows:
BYTES DESCRIPTION
0-10 Field Name ASCII padded with 0x00
11 Field Type Identifier (see below)
12-15 Offset of field in record
16 Field length in bytes
17 Field decimal places
18-19 Reserved
20 dBaseIV work area ID
21-30 Reserved
31 Field is part of production index - 0x01 else 0x00
xbase fields types:
Code Description
C Character
D Date, format YYMMDD
F Floating Point
G General - FoxPro addition
L Logical, T:t,F:f,Y:y,N:n,?-not initialized
M Memo (stored as 10 digits representing the dbt block number)
N Numeric
P Picture - FoxPro addition
A peculiarity of dBase files is that numbers (type N) are not stored in binary form but in characters (like Cobol, if there are any Cobol programmers still around). So every field will be of type char.
So this gives us the definition of dbf fields.txt. Since there will be more than one field description, we add the keyword multiple. This will add a new field to the data editing window, showing the current record number, and previous and next record buttons.
template "dbf field"
// Sample template by Paul Mullen
description "32 byte definition for each data field"
appliesto file
requires 10 00
multiple
begin
char "Field Name (zero terminated)"
read-only hex 1 "(zero terminator)"
char "Field Type"
int32 "offset from start of record"
byte "Field length (bytes)"
byte "Decimal places"
read-only hex 2 "(Reserved)"
byte "Work area ID"
read-only hex 10 "(Reserved)"
byte "Used in production index"
end
From browsing the field descriptions we see the following fields:
Type Length Dec Name
N 12 3 Area
C 25 State Name
C 2 State FIPS
C 7 Region
C 2 Abbreviation
N 10 Pop 1990
N 10 Pop 1996
In addition every dbase record starts with a single character “deleted” marker – space if the record is valid, * if deleted.
So we get the following template
template "dbf sample data record"
// Sample template by Paul Mullen
description "applies to states.dbf"
appliesto file
multiple
begin
char "*=deleted"
char "Area"
char "State Name"
char "FIPS"
char "Region"
char "Abbreviation"
char "Pop 1990"
char "Pop 1996"
end
Finally, you may recall that when we inspected the header, it showed 51 records. Yet there are only 50 states. The additional “record” is not really a record at all buta dBase “end of file marker”, consisting of the single byte 0x1A.This value was used by the old CP/M operating system (and DEC operating systems before it) to mark the end of text files and was carried over into early versions of MsDos.
Now you should be ready to start tackling some more advanced templates: look at the other sample templates and just experiment!
[ 本帖最后由 甜橙 于 2007-10-14 11:16 编辑 ] （38： （38： （38： （38： （38： （38： （38： 不明白.........?
看看
不懂的就要学习嘛. 看看不懂的就要学习嘛.
不错，这个软件太专业。来个教程吧 （49： （49： 什么意思没看明白啊，太多点饿 高人啊，看不明白，要慢慢消化才行! 还看不懂，
过一段时间再看哈