Johan van der Knijff
Johan van der Knijff
Re-opening as JHOVE still reports this error for some PDFs with security-related features. Examples: - [e-book_79.pdf](https://wiki.opf-labs.org/download/attachments/101613571/e-book_79.pdf) ([jhove output](https://github.com/KBNLresearch/pdf-characterisation/blob/main/output/jhove-pdfhul-impact/pdf-hul-109/e-book_79-jhove.xml)) - [inkonf_1500.pdf](https://wiki.opf-labs.org/download/attachments/101613571/inkonf_1500.pdf) ([jhove output](https://github.com/KBNLresearch/pdf-characterisation/blob/main/output/jhove-pdfhul-impact/pdf-hul-109/inkonf_1500-jhove.xml)) Additional check with VeraPDF confirms both files contain...
What IsoBuster version are you using? I came across some unexplained 1005 errors (which usually indicate the user manually interrupted the imaging, which obviously isn't the case here) while working...
Come to think of it, I *think* the problem we had at the time was caused by the presence of multiple configured drives, which somehow caused the load/unload/reject driver tools...
Other thing that crossed my mind - I think I actually solved our slow response issue of the Nimbie drivers at the time by disabling any unused optical drives (including...
@darcyruppert Good to hear the Nimbie drivers are now working properly. As for Isobuster: I would try running the most recent 4.x version (I think this was 4.7, not entirely...
@darcyruppert 4.9 should be fine. Let me know if you keep getting this issue and I'll try to think of something!
For future reference, I just added a section on disabling unused optical drives to the Iromlab setup documentation: And also a reference to this in the User Guide's Troubleshooting section:
@CyberGonzo Thanks for the heads-up and the offer! I just sent you a quick email with an outline of our plans with Iromlab, and how IsoBuster fits into this.
After updating local .pypirc file (see [here](https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#create-an-account)) + [these changes](https://github.com/openpreserve/jpylyzer/commit/a05a9858dfba3dea218ab4008f06f6d72eb891ea) PyPi packaging + upload works when running package-pypi.sh directly. But apparently these changes break running the Docker file, which now...
@boxerab Thanks for the update. I have literally no idea what made the valgrind errors disappear (changes to the jpylyzer code or perhaps the Python interpreter?), but good to see...