current directory changed

[m.pepper]

AntiSpyware blocked a .bat script I launched with an icon.
I answered "Allow" and the script executed as expected ...
almost. The "Start in:" directory specified in the
properties for the icon that started my batch file was
overridden -- ie, when my script executed, instead of the
current directory being the one specified, it was
windows\system32. The affect was that files looked for
were not found and files created ended up in windows\system32.

AntiSpyware needs to retain (or restore) the current
directory setting after intervening.

 

[Andre Da Costa]

Some information concerning Scripting and Microsoft AntiSpyware:
Scripting:
Unattended uninstall:

MsiExec.exe /X {536F7C74-844B-4683-B0C5-EA39E19A6FE3} /L *vx /Log
c:\msas.log /quiet

Unattended Install:

http://www.overdose.net/docs/msas_silent_remote_install.txt

Scripting and Microsoft AntiSpyware:
http://www.microsoft.com/technet/scriptcenter/resources/articles/antispy.mspx

 

[m.pepper]

I don't really need info on scripting. I should have
simply asked "where should I report bugs to?" Thanks.

 

[Andre Da Costa]

Here, in the newsgroups. The MSAS Team reads all issues you encounter with
MSAS, I read.

--

Andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

I don't really need info on scripting. I should have
simply asked "where should I report bugs to?" Thanks.

 

[Bill Sanderson]

This is the place. This bug was originally reported about January 8th--so
Microsoft is aware of it.

If you continue to use this beta product, I recommend Andre's last link--it
does have useful information about workarounds for beta quirks.

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

I don't really need info on scripting. I should have
simply asked "where should I report bugs to?" Thanks.