Re: Problem with path variables in a cmd shell, Windows IR script

On Tue, 9 May 2006 15:59 +0200, l1st3r@gmx.net wrote:

> Hi
>
> I am trying to create a windows first response IR script for Windows 2000
> Pro using binaries that do not touch the file system, but am having problems
> making the environment variables stick.
[snip]
> set path:d:\IR\...; etc...
[snip]

> PROBLEM
>
> It does not matter whether I run this from CD or from the writable USB
> stick, as user or as Administrator (runas /user:Administrator
> e:\cmdenv.bat), the environment variables appear to be set OK (tested with
> "set".) But when I run the ir batch script on a second test system, filemon
> shows that the program DLLs are still taken from the system32 directory.
> There is no searching for DLLs in the CDROM / USB stick, the environment
> variables appear to have been ignored. It does not look like a permissions
> problem.
>
> Does anyone know how to force the DLL paths within a batch script / cmd
> shell?

   One thing: the syntax should be

      set path=d:\IR\...;
              ^
   not

      set path:d:\IR\...;
              ^


   [Perhaps the colon works, but it sure doesn't look like it.  Under XP, 
I get an error of "Environment variable path:d:\IR\ not defined."]

   -BPB

University of Michigan AntiVirus Team Leader
University of Michigan Data Recovery Team Leader
PGP 2.6.2 key fingerprint:  0D A5 98 3C 91 DA E0 DD  9C 6D FA 8F 4D 34 95 ED