Thread: [sleuthkit-developers] [ sleuthkit-Bugs-2950687 ] Windows binaries not working.
Brought to you by:
carrier
Menu
▾
▴
sleuthkit-developers
|
From: SourceForge.net <no...@so...> - 2010-02-12 16:38:54
|
Bugs item #2950687, was opened at 2010-02-12 11:38 Message generated for change (Tracker Item Submitted) 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: Nobody/Anonymous (nobody) 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 ]] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2950687&group_id=55685 |
|
From: SourceForge.net <no...@so...> - 2010-03-23 01:58:42
|
Bugs item #2950687, was opened at 2010-02-12 11:38 Message generated for change (Settings changed) 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 ]] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2950687&group_id=55685 |
|
From: Al M. <alp...@gm...> - 2010-04-08 18:49:01
|
[ 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 |
|
From: Brian C. <ca...@sl...> - 2010-04-09 13:52:53
|
Can you download depends.exe from: http://dependencywalker.com/ Run it and open one of the TSK exe files (File -> Open). At the bottom, it should list a bunch of dll files and some may be red (or some other error-looking symbol). Can you report which ones are showing that? thanks, brian On Apr 8, 2010, at 2:48 PM, Al MailingList wrote: > [ 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 > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > sleuthkit-developers mailing list > sle...@li... > https://lists.sourceforge.net/lists/listinfo/sleuthkit-developers |
|
From: Al M. <alp...@gm...> - 2010-04-13 19:34:22
|
Sorry it took a while. Ran it, Got something along the lines of: Side bye side configuration information for fls.exe contains errors. Apllication has failed to start... Side bye side configuration information for Libewf.dll contains errors. Application has failed to start... At least one delay - load dependency was not found At least one module has a unresolved import due to a missing export function in a delay-load dependent module Msjava.dll error opening file the system cannot find the file specified (2) And Msjava.dll had a little error symbol next to it and was red. I will rebuild the box I ran this on soon, so let me know if you want any more information. Cheers, Al On Fri, Apr 9, 2010 at 2:52 PM, Brian Carrier <ca...@sl...> wrote: > Can you download depends.exe from: > > http://dependencywalker.com/ > > Run it and open one of the TSK exe files (File -> Open). At the bottom, it should list a bunch of dll files and some may be red (or some other error-looking symbol). Can you report which ones are showing that? > > thanks, > brian > > > > On Apr 8, 2010, at 2:48 PM, Al MailingList wrote: > >> [ 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 >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> sleuthkit-developers mailing list >> sle...@li... >> https://lists.sourceforge.net/lists/listinfo/sleuthkit-developers > > |
|
From: Brian C. <ca...@sl...> - 2010-04-16 14:15:20
|
On Apr 13, 2010, at 3:34 PM, Al MailingList wrote: > Sorry it took a while. > > Ran it, > > Got something along the lines of: > > Side bye side configuration information for fls.exe contains errors. > Apllication has failed to start... > Side bye side configuration information for Libewf.dll contains > errors. Application has failed to start... > > At least one delay - load dependency was not found > At least one module has a unresolved import due to a missing export > function in a delay-load dependent module > > Msjava.dll error opening file the system cannot find the file specified (2) > > And Msjava.dll had a little error symbol next to it and was red. > Strange. I don't have Msjava.dll listed as a dependency when I run depends.exe on my system. If I sort the modules by name in the bottom of the window and copy them out, I get the below list. Can you do a similar thing and maybe we can find out what is different. To be clear, you are using the executables from the sleuthkit.org website and you didn't compile these manually, right? thanks, brian ACTIVEDS.DLL ADSLDPC.DLL ADVAPI32.DLL ADVPACK.DLL APPHELP.DLL ATL.DLL AUTHZ.DLL BROWSEUI.DLL CABINET.DLL CDFVIEW.DLL CERTCLI.DLL CFGMGR32.DLL CLUSAPI.DLL COMCTL32.DLL COMDLG32.DLL CREDUI.DLL CRYPT32.DLL CRYPTUI.DLL CSCDLL.DLL DBGHELP.DLL DEVMGR.DLL DHCPCSVC.DLL DNSAPI.DLL DOT3API.DLL DOT3DLG.DLL DUSER.DLL EAPOLQEC.DLL EAPPCFG.DLL EAPPPRXY.DLL EFSADU.DLL ESENT.DLL FLS.EXE GDI32.DLL GDIPLUS.DLL HLINK.DLL HNETCFG.DLL IEFRAME.DLL IERTUTIL.DLL IESHIMS.DLL IEUI.DLL IMAGEHLP.DLL IMGUTIL.DLL IMM32.DLL INETCOMM.DLL IPHLPAPI.DLL KERNEL32.DLL LIBEWF.DLL LINKINFO.DLL LZ32.DLL MFC42U.DLL MLANG.DLL MOBSYNC.DLL MPR.DLL MPRAPI.DLL MPRUI.DLL MSASN1.DLL MSFEEDS.DLL MSGINA.DLL MSHTML.DLL MSI.DLL MSIMG32.DLL MSLS31.DLL MSOERT2.DLL MSRATING.DLL MSSIGN32.DLL MSVCP60.DLL MSVCR90.DLL MSVCRT.DLL MSWSOCK.DLL NETAPI32.DLL NETCFGX.DLL NETMAN.DLL NETPLWIZ.DLL NETRAP.DLL NETSHELL.DLL NETUI0.DLL NETUI1.DLL NETUI2.DLL NORMALIZ.DLL NTDLL.DLL NTDSAPI.DLL NTLANMAN.DLL OCCACHE.DLL ODBC32.DLL OLE32.DLL OLEACC.DLL OLEAUT32.DLL OLEDLG.DLL OLEPRO32.DLL ONEX.DLL POWRPROF.DLL PRINTUI.DLL PSAPI.DLL QUERY.DLL QUTIL.DLL RASAPI32.DLL RASDLG.DLL RASMAN.DLL REGAPI.DLL RPCRT4.DLL RTUTILS.DLL SAMLIB.DLL SCECLI.DLL SECUR32.DLL SETUPAPI.DLL SHDOCVW.DLL SHELL32.DLL SHLWAPI.DLL SHSVCS.DLL TAPI32.DLL URLMON.DLL USER32.DLL USERENV.DLL USP10.DLL UTILDLL.DLL UXTHEME.DLL VERSION.DLL W32TOPL.DLL WER.DLL WINHTTP.DLL WININET.DLL WINMM.DLL WINSCARD.DLL WINSPOOL.DRV WINSTA.DLL WINTRUST.DLL WLDAP32.DLL WMI.DLL WS2_32.DLL WS2HELP.DLL WSOCK32.DLL WTSAPI32.DLL WZCDLG.DLL WZCSAPI.DLL WZCSVC.DLL XMLLITE.DLL ZLIB1.DLL |
|
From: Al M. <alp...@gm...> - 2010-04-21 21:50:34
|
On Fri, Apr 16, 2010 at 3:15 PM, Brian Carrier <ca...@sl...> wrote: > On Apr 13, 2010, at 3:34 PM, Al MailingList wrote: > >> Sorry it took a while. >> >> Ran it, >> >> Got something along the lines of: >> >> Side bye side configuration information for fls.exe contains errors. >> Apllication has failed to start... >> Side bye side configuration information for Libewf.dll contains >> errors. Application has failed to start... >> >> At least one delay - load dependency was not found >> At least one module has a unresolved import due to a missing export >> function in a delay-load dependent module >> >> Msjava.dll error opening file the system cannot find the file specified (2) >> >> And Msjava.dll had a little error symbol next to it and was red. >> > > Strange. I don't have Msjava.dll listed as a dependency when I run depends.exe on my system. If I sort the modules by name in the bottom of the window and copy them out, I get the below list. Can you do a similar thing and maybe we can find out what is different. To be clear, you are using the executables from the sleuthkit.org website and you didn't compile these manually, right? > > thanks, > brian > > > > ACTIVEDS.DLL > ADSLDPC.DLL ... > XMLLITE.DLL > ZLIB1.DLL > > Gah. Sorry about this Brian, but the machine has been rebuilt by another team and is back in service I think :( I was using the executables, not building from source. I grabbed the latest - 3.1.1 from the web site. When I had the issue mentioned with those, I went back to 3.0.1 which worked fine. It does seem very odd that you don't have the same dependencies..... Maybe someone else will see a similar issue and report it? Apologies. Al |
|
From: SourceForge.net <no...@so...> - 2010-09-10 16:07:06
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-10-28 02:46:39
|
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: Closed >Resolution: Fixed 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-10-27 21:46 Message: The redist dlls installer seemed to help. ---------------------------------------------------------------------- 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X