i do not agree with @Nathan W thoughts.
!version 300 can give us that it is a MapInfo tab file but it doesnt give us
which program use for creating this tab file...
so when you convert your shp data to tab file in globalmapper it also create
!version 300 but no info about which program is used...
you can find more info here. The following info was taken from Jacques Paris experience...
Structure of Tab File Format
The version seems to be set automatically by MI to the minimum
compatible with the table.
300 basic, most commonly used
400 when Metadata is present (*)
410 for MDB ACCESS files
450 for XLS files
500 for MIG files
(*) an assumption based on the appearance of Metadata functions in MB language version 4
Note: there may be different versions associated with the raster formats; new ones may have been included since the version 3
and that may have some effect on the version number. I do not have
enough examples to verify all the formats recognized by MI in version
6.0: BIL, TIF, BMP, GIF, TGA, JPG, PCX. This list according to the help file does not include GRC that shows up in the "open file"
requester and that may have been abandoned since version 3.
!version 300 required, variable, controlled by MI
!charset WindowsLatin1 required, variable, depending on user's choice
These are MapBasic commands similar to those present in a WOR.
They are executed sequentially and before the next segment (table definition) is read. They cannot thus be applied to the table defined
Variations depending on the nature of the nature. See "Detailed table definitions"
Metadata commands. They can be added to any tab file. They can be retrieved only if an application does it explicitly (as MI with the
interpolator definition of a MIG file; see "Detailed table
The sequence of these 3 blocks must be respected but they may not all
be present. The most frequent case calls only for table definition;
that block can be sometimes followed by metadata (always, in a MIG
file). There are rare examples of tabs with only a command block (see
"Special examples"). Nothing stops us from imagining commands and
table definition, and, why not, metadata, in the same TAB file.
i hope it helps you...