Hi Juanma,
Yes, this behavior can be explained. If we have a look at the MapInfo TAB (MITAB) Writer Parameters, under File Version, we will see that this parameter only "Provides a hint of the target version of the output file."
"Note that this option does not affect the overall version number written to the file. That is determined by the specific attribute types, geometry types, or coordinate systems. For example, if the coordinate system is “Krovak S-JTSK”, then the version is promoted to at least 900."
This means that if you set File Version = '300', the system will try to create a MapInfo 3 compatible file, but if this is impossible (for the reasons mentioned above) FME will automatically switch to a higher version.
It looks like the geometry from your shapefile is not compatible with MapInfo 3, so the system generates a TAB file compatible with MapInfo 8. (It might be the geometry, but it could also be one or more of the attributes and/or the projection used...)
HTH,
Egge-Jan
That's totally comprehensive. More clear now, many thanks for the help @egge ! ;)