Re: [sleuthkit-users] FLS on Windows Errors

[Joseph R. M. <jr....@gm...>]

Thanks for the idea.  I was able to figure it out.  I commented the @echo
off line at the top of the script, and realized that my FLS command-line
appeared to have upper-ASCII characters instead of hyphens when it was
presented in the command-prompt window.  I had pasted the FLS command into
the script from a web site and even though they appeared as hyphens, they
certainly were not interpreted as such.  It looked like:

fls ûm C: ûr \\.\C:

So I deleted those characters and replaced them with hyphens, and all seems
better now.  Thanks for your help even though it turned out to be such a
basic issue.


On Thu, Apr 22, 2010 at 5:04 PM, Theodore Pham <te...@gm...> wrote:

> Rename our .cmd file with a .txt extension and attach it to your
> reply.  I'm curious if something in your script is causing it.
>
> On Thu, Apr 22, 2010 at 9:53 AM, Joseph R. Murray <jr....@gm...>
> wrote:
> > Brian & Theodore - Thanks for the ideas.  For more detail, here are the
> > statements to declare the variables:
> >
> > SET LOGDIR="..\Logs"
> > SET TOOLDIR=%~d0%~p0Tools
> >
> > I have tried these lines in the batch file and had the same result:
> > fls –m C: –r \\.\C:
> > fls –m C: –r 7-ntfs-undel.dd
> >
> > I have also tried specifying an image file but that hasn't worked either
> > (same error).  Perhaps it is good to note that I am using a .cmd file and
> > not a .bat file, although I have tried both with the same result.  I have
> > UAC enabled but I am running the command-prompt as an administrator
> before
> > executing the script, and FLS works by itself (most of the time) without
> the
> > script involved.
> >
> > Does anyone have any ideas regarding this?
> > Brian, if there is anything you'd like me to test please let me know.
> >
> >
>