Closed arisjr closed 2 years ago
I ran a quick test here using an absolute path and it worked fine. Looking at the code (belq), I saw that it checks if the model file exists in the given path. If it is not there, only then it tries to add the "base" path as a suffix.
File dieDat = new File(diePath.trim()); // Here diePath is the one that came from the configuration file
if (!dieDat.exists()) // If not found
dieDat = new File(new File(Configuration.getInstance().appRoot), diePath.trim()); // then add the "base" path
Can you double check if the absolute path you used is correct (and accessible to IPED's process)?
By the way, I used 3.18.12 here too, but on Windows 10, although it doesn't seem to be an OS specific issue.
I'm also not able to reproduce this with Ubuntu-20.04, openjdk-1.8.0_292 and iped-3.18.12. I tried to execute from iped-3.18.12 root folder and from an unrelated folder, setting ledDie = /media/DRIVE_F/LED/V1.27.00/die/rfdie.dat
@arisjr if you think this isn't a permission issue like @tc-wleite said and can provide a detailed step by step to reproduce this, please reopen.
Sorry, guys, I was out on vacation... Just saw now, the path was wrong indeed. The correct path was /mnt/led/pedo/die/rfdie.dat.
Thanks and regards, Aristeu
Dear developers,
I've set ledDie=/mnt/led/die/rfdie.dat, an absolute path, and IPED interpret as relative path, turning ledDie path into /root/IPED/iped/mnt/led/die/rfdie.dat.
I'm using IPED 3.18.12 on linux Ubuntu 20.04. Follows the run log with the error.
Changing the flag to the default value, using relative path to the embedded ledDie, works.
Regards, Aristeu