Why so slow?-Cornucopiae
In AutoHotkey, there are no native hash/checksum commands. So, you have three options: 1) Use a command line executable, 2) a DLL, or 3) use a function library that somebody has developed. SFV Ninja uses number one and three. However, I've found that the function library, while very fast and accurate, has a tendency to crash randomly and I don't know why. So, I changed SFV Ninja to only use that function when absolutely necessary where before it was using it for smaller files because of its speed.
Any hints as to what the issue is (or what you thought it is)?-f0dder
So, back to the explanation of SFV Ninja using a command line executable for most of the grunt work. SFV Ninja creates a temp folder and extracts the necessary files it needs into it. During operation, it then calls the command line exe and dumps the output to a temp file named as the current ISO timestamp. I thought this would be enough granularity (to the second) until stefanobrunesci's reported issue made me think that two concurrently running scans could attempt to create temp files with the same name and write to them at the same time. This, perhaps, was what was causing stefanobrunesci's issue. So, to solve it, the change I made was to have each running instance of SFV Ninja work out of its own unique temp folder. The files it extracts total around half a meg so I'm not worried about multiple temp folders, etc.
Recent Posts
-Renegade (September 16, 2012, 10:02 AM)
