While there is not yet a configure option to compile fileview, it can be easily compiled after running the configure script by switching to the fileview directory and typing 'make'.
The utility itself can be used by executing the mulefileview executable and giving an aMule binary file as argument.
An example:
$ ./mulefileview ~/.aMule/Temp/001.part.met
Decoding file: /home/johkra/.aMule/Temp/001.part.met
Version : PARTFILE_VERSION (0xe0)
LastChanged : 1215680812 (Thu Jul 10 09:06:52 2008 UTC)
FileHash : 834604C8ED9FEB337454B4E75F77CE9F
Parts : 0
HashSet :
TagCount : 18
{ 0x01 FT_FILENAME, 2 TAGTYPE_STRING, "LinkCreator0.7.[contentdb.emule-project.net].zip" }
{ 0x02 FT_FILESIZE, 3 TAGTYPE_UINT32, 128718 (126 kB) }
{ 0x08 FT_TRANSFERRED, 3 TAGTYPE_UINT32, 0 (0 bytes) }
...You can use this tool to view part.met files as demonstrated or to open the known.met file and view all finished downloads by aMule.
Furthermore he also added a new macro for the configure script, which will allow for a nice formatting of messages and more importantly display all warning messages at the end of the configure output, so no warning will be overlooked in the future.
Lastly I want to point to an discussion in the forum: Mac port - different approach
2 comments:
While there is not yet a configure option to compile fileview, it can be easily compiled after running the configure script by switching to the fileview directory and typing 'make'.
This is intentional as mulefileview is intended primarily as a developer tool. Though this behaviour might be changed later, if a complete user interface is built, and at least all the files aMule uses are covered (currently known2_64.met is missing).
Post a Comment