Brian O'Reilly

Thanks for raising this again - appreciate this was raised some time ago on the Google groups but it is something we still intend to look at further in the...

This is a known issue. The maximum bytes message occurs when you have a signature where none of the constituent byte sequences are defined relative to BOF or EOF (i.e....

The “no profile” mode should indeed help with this scenario. There are examples in the DROID help as a minumum, you need to specify the folder location and a full...

Hi AnanthNagarajanInfosys, Firstly, apologies - I didn't mean to mark this as closed this when I commented earlier - but I realised I clicked the wrong button! Yes, unfortunately you...

Great to know this solution worked for you - I've found this approach useful on other occasions in the past, though I agree that the presentation of the aliased path...

I wouldn't agree with making it "False" - extension mismatches would normally be the exception so we would want to highlight such cases in outputs and filtering even where there...

I'm seeing the fmt/59 identification when run with the default maximum bytes to scan setting (65536). And fmt/61 when this is set to -1. Same behaviour in earlier version 6.1.5...

To note for completeness - with the command line DROID, the identification is fmt/59 if run with just a binary signature, and fmt/61 if you add a container signature (-Nc...

Ross, With reference to the proxy issue,have you configured the proxy settings element in your Maven settings.xml file (in the conf subdirectory of the Maven install location)? Regards, Brian

Please see https://github.com/digital-preservation/droid/issues/67 - in particular my 6 January 2016 comment. DROID's OLE2 identifier engine uses Apache POIFS - it calls the POIFSFileSystem constructor to obtain a reader. This sometimes...