si2013 wrote:
This question follows on from my last question, which can be found here.
When I use libesedbtool to export/rip the Windows.edb file, sometimes I end up with SystemIndex_0A.2 and other times, I end up with SystemIndex_0A.7
Just to confirm - I am using the exact same Windows.edb file each time I run the software. Is there any reason that the file might end in 2 or 7? It's not the end of the world, the file still holds the same information in, but it's just a bit annoying because for my University project, i'm writing a script search the SystemIndex_0A.7 file and sometimes it spits out a 0A.2 file, so my script breaks because it was expecting a 0A.7 file.
I know I can add an if statement and fix the script, but I was curious about why this happens.
Thanks in advance. I hope this question is reasonably clear.
It's the table index number is appended to prevent tables with duplicate names overwriting each other.
You probably better off not relying on the number suffix but actually check which SystemIndex_0A.* files were created. Note that there are Python bindings in the making that should make scripting libesedb easier.
You're also better off asking that question on the project site or via mail. It's a coincidence I was reading this forum.
↧