[sleuthkit-developers] [ sleuthkit-Bugs-2950687 ] Windows binaries not working.

[Al M. <alp...@gm...>]

[ sleuthkit-Bugs-2950687 ] Windows binaries       not working.
> Message: 1
> Date: Tue, 23 Mar 2010 01:58:42 +0000
> From: "SourceForge.net" <no...@so...>
> Subject: [sleuthkit-developers] [ sleuthkit-Bugs-2950687 ] Windows
>        binaries        not working.
> To: no...@so...
> Message-ID: <E1N...@sf...>
> Content-Type: text/plain; charset="UTF-8"
>

<snip>

> sleuth-win32-3.1.0.zip:  On some machines in our relatively homogeneous
> computer lab, attempting to run TSK tools yields the following error
> message:  "The system cannot execute the specified program"   My limited
> research seems to indicate that an incorrect version of a system DLL could
> be the culprit (e.g., older kernel32.dll) but I haven't been able to pin
> down a difference between working and non-working machines, even with
> Dependency Walker.

Just letting you know I had the same issue on a Windows XP SP2
machine. Let me know if you want more info, apologies if things are
under control.

And also, not sure if anyone has seen this or can reproduce it....

Once I got things working on the above machine (XP SP2, using TSK
3.0.1 instead which worked), I was doing some timeline creation (fls
-r -m ... ). Everything seemed to be working OK, and then I started up
a second fls, again with -r and -m but on only a subdirectory (I got
impatient and figured I didn't really need the whole fs).

This produced a crash (windows error report). I tried it again and on
different sub directories, but it seemed to keep crashing. When I just
ran one at a time over the whole drive, no problem. This was on a
machine I can't really mess about with too much, and I actually don't
have a good dev setup right now. Is it even possible this is affecting
things?? If so, and it's not a wacky coincidence or a more subtle
issue, can someone try and reproduce it? i.e.

fls -r -m C: \\.\C:

and while that is still going:

fls -r -m C: \\.\C: <some sub dir>

where C: is an NTFS drive.

Hope I'm not on crazy pills.

Thanks for the great tools.

Al