I have spent several days now turning this problem around.
(Over 100 views but no replies to my post on bleepingcomputer.)
It seems that the gpx xml files may be tough to search with photorec.
But what about gdb?
I have looked at the hex info with several readers and seems likely that a photorec.sig file could be added for gdb files.
The info seems to be in the first line, 0 offset...
And I don't know how to work fidentify.
I have created various text file versions of a photorec.sig file and placed them in the testdisk folder.
gdb 0 0x4D735263660002
gdb 0 0x4D 0x73 0x52 0x63 0x66 0x00 0x02
gdb 0 0x4D73526366
gdb 0 0x4D 0x73 0x52 0x63 0x66
gdb 0 "MsRcf"
etc
I also tried to introduce a test, using similar approach with hex info from pdf files.
I even tried punching in the example signature from the instruction page
http://www.cgsecurity.org/wiki/Add_your ... o_PhotoRec
I have been clicking the fidentify_win file, and it seems to open a command window, scan the files in the folder, generate a text file, and vanish.
The text file at first gave me an ms-dos error, which was resolved by searching and finding a fix regarding environment variables.
But, I have not generated any response so far regarding the various .sig text files that I have tried.
Obviously I am missing a lot here.
Is it something really really basic?
Do I have to run fidentify from a command prompt?
I am not getting any result, no "unknown" or "?gdb" or goodtogo...nothing.
thanks
FileAlyzer:
4D 73 52 63 66 00 02 00 00 00 44 6D 00 1B 00 00 00 41 67 02 73 71 61 00 46 65 62 20 20 39 20 32 30 30 39 00 31 31 3A 33 31 3A 33 30 00 4D 61 70 53 6F 75 72 63 65 00 70 00 00 00 57 20 30 31 31 4C 64 73 00 00 00 00 00 00 00 00 00 00 FF