Mark0's Forum
General => Generic Talk => Topic started by: kdaube on January 11, 2015, 05:28:09 PM
-
Hello friends,
I have quite a large file (60 MB) without a proper extension which I want to analyse what it is. Hence uploading to the online-function is not an option (have tried...).
However, the rules for the local installation are not found, although everything is in the same directory:
(http://www.daube.ch/zz_tests/tridnet1.png)
(http://www.daube.ch/zz_tests/tridnet2.png)
Even this known format is not handled at all.
What may be wrong with my setup?
-
Hi!
The .TRD package is used by the command line tool, TrID.
TrIDNet instead use the definitions in XML format.
You'll find the link for the compressed RAR archive with them in the download section near the end of TrIDNet's page: http://mark0.net/soft-tridnet-e.html
Just unpack them in the same H:\Utilities\TrIDNet and you should be OK!
-
Thank You Mark0
It's a little bit confusing to have the ZIP file also there - I prefer ZIP over RAR...
And it turns out that reading the definitions is not that intuitive as expected:
- Klicking on Browse allows me to set the directory where to find the defs
(H:\Utilities\TrIDNet\triDDefs_xml) - After Open i see the complete list of files in this directory
- In the first run I need to select all files in this list and then hit Open
- In next runs I can select the top file {sa}proj.trid.xml and then Open
It turned out that my file is an "IntallShield archive". It has a Z extension, but obviously is not a standard Z archive file (could not be opened by 7-Zip).
Thanks for the help - i could extract relevant information from that huge file now thanks to knowing what it is (using Usinversal Extractor).
-
If the definitions are in the same folder as the TrIDNet.exe file, it's not needed to tell TrIDNet where to find them.
You can just open the file to analyze, and then TrIDNet will read all the definitions (if it hadn't already), and then analyze the file you selected.
-
Yes, Mark0,
I knew that, but also have read somewhere that the defs could also be in a subdirectory - which seems not to be the case.
Have now moved up - and all is OK.
Thank You for Your help
Klaus Daube