O
Oliver Wright
This is a bug within the spyware program (unless someone
can come up with a solution).
Very simple installation batchfile (works on everything
from win95 up..) Copies from current location (cd-
rom/memory stick etc. to specific director on c:\). (It
doesn't need to be complicated.) Unfortunately get's
intercepted as an unrecognised script.
Trouble is, if intercepted by Spyware Beta, the context
of the script changes from the current drive (d:, e:
etc...) to c:\windows..... and this happens before the
script is actually run so I've no way of knowing what's
happening.
So Spyware needs to restore the current context of the
batch file BEFORE continuing if the user selects Allow.
Worse still, should the user have previously pressed
allow, future incarnations of the script fail to run
since the context still gets switched, but this time
silently.....
(Altenatively, does anyone have a simple solution to
finding the location from which a batch file is
running??)
can come up with a solution).
Very simple installation batchfile (works on everything
from win95 up..) Copies from current location (cd-
rom/memory stick etc. to specific director on c:\). (It
doesn't need to be complicated.) Unfortunately get's
intercepted as an unrecognised script.
Trouble is, if intercepted by Spyware Beta, the context
of the script changes from the current drive (d:, e:
etc...) to c:\windows..... and this happens before the
script is actually run so I've no way of knowing what's
happening.
So Spyware needs to restore the current context of the
batch file BEFORE continuing if the user selects Allow.
Worse still, should the user have previously pressed
allow, future incarnations of the script fail to run
since the context still gets switched, but this time
silently.....
(Altenatively, does anyone have a simple solution to
finding the location from which a batch file is
running??)