AW: iGOView 2.0 beta testing
Detection is not done according to the file extension.
The file extension in DAT file is for the case that the original file extension is lost or wrong - it will be recovered from the rest of the data in the line.
iGOView consist from a couple of parsers. First one will will decrypt and parse the data according to the first number in the line (00544553 in the case of all Fxx files). This block of data contains the creation date of the file and some data for decrypting the rest of the file. There was also some text in older versions of the file (in recent files stays just "Development version")
After that second parser will get the rest according to the last number in the line (07067619 for FBL files). In this block of data is the text where we get the name of the producer, release version etc.
Some files have more then one such block ("all in one" files where FBL file also contains truck info, junction views etc.)
All the data from 2nd parser is sent to some of the text parsers which will search for known strings (producer, country name etc.)
POI files have all the data in first block (just like old FBL files for
igo 8.0).
Some files are not crypted at all (like DEM files).
In case of FSP files, first parser will get the data according to the settings for FBL files (because the magic number is the same and FBL line comes first in DAT file), and the second parser will get the rest according to the setting from FSP line because the 2nd magic number will be found in that line.
It is a flaw, but I started to write the parsers step by step, without knowing what comes next. It got me to such parsers structure.
Better structure would be a DAT file with conditional branching (tree structure). That would reflect better the parser structure, but it would be a bit complicated to describe and set in a textual file (like this DAT file).
As for the error you get, I need to investigate that a little bit as I can't reproduce this bug.
Can you give me some more details: OS version, file system where the FSP files are, admin on limited user on the system etc?
- - - Aktualisiert - - -
One more question - can it be that you have some FSP files that are not released in forums, with some other magic number for second block of data?
That would also cause an error message, but I believe it would cause some "Reading behind the end of stream" error message or something similar.