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

[SourceForge.net <no...@so...>]

Bugs item #2950687, was opened at 2010-02-12 11:38
Message generated for change (Comment added) made by carrier
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2950687&group_id=55685

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brian Carrier (carrier)
Assigned to: Brian Carrier (carrier)
Summary: Windows binaries not working. 

Initial Comment:
>From Gregg Gunsch:


Per the instruction on the bug tracker page, I'm sending this to the
sleuthkit-users list first.  Does anybody else see this problem or know of
a simple solution?


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.

The files were extracted from the .zip archive and placed into a directory
in "C:\Program Files", preserving the hierarchy found in the archive.  The
path was added to the environment variable, and the commands are being
found (e.g., "which istat" locates it).  They just aren't successfully
being run.  I even tried copying the DLLs that came with TSK into the
system32 folder, but no help.  We are running WinXP Pro, SP2 and SP3. 
Some SP2 machines run TSK just fine, as do the SP3 versions (and yes, I'm
in the process of updating them all).  I've also hashed the TSK files on a
working system and compared to those on a non-working machine - they are
identical.

Is there a way to produce a more portable collection of executables that
are less target-system dependent?  Is there something I should be doing
with the manifest so that the dependencies are satisfied? Should I be
compiling the source myself instead of using the build in the .zip file?
It's been years since I've done development, and a lot seems to have
changed, so there may be some simple steps that I'm just overlooking right
now.

Thanks for your assistance,

[[ other offline e-mails exist.  Other versions of visual studio are on the machine ]]

----------------------------------------------------------------------

>Comment By: Brian Carrier (carrier)
Date: 2010-09-10 11:07

Message:
Dan Jerger reported that installing the VS 2008 redist dlls helped:

http://www.microsoft.com/downloads/details.aspx?FamilyID=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en

It's still not clear why this is needed though because these dlls are
included with TSK...  But, they are not officially installed. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2950687&group_id=55685