Hi,

I think this is really a very valuable product.
However I found two issues with it:

1.)
When executing a batch file the first time it asks if I
want to allow it ("An unknown script file..."). After
presing the "Allow" button the script is executed. But it
is not executed in the original directory! Instead the
batch file runs in the windows system directory.

2.)
After performing the daily check over night and removing
some spyware products, the tool asked for permission to
reboot the system. After pressing OK it crashed. Is guess
this is related to the fact, ther have been two user
logins on the XP system at this time.

Regards,

Martin

#1 is a serious bug and is known to Microsoft and being worked on.
#2 I'm not sure what to say about--you may be right about the cause--when
you say "crash"--does that mean a reboot? Was there a blue screen? Any
information in the system error log for the time of that occurrence?
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Martin Fuchs" <(E-Mail Removed)> wrote in message
news:227e01c50e8a$2779b310$(E-Mail Removed)...
> Hi,
>
> I think this is really a very valuable product.
> However I found two issues with it:
>
> 1.)
> When executing a batch file the first time it asks if I
> want to allow it ("An unknown script file..."). After
> presing the "Allow" button the script is executed. But it
> is not executed in the original directory! Instead the
> batch file runs in the windows system directory.
>
> 2.)
> After performing the daily check over night and removing
> some spyware products, the tool asked for permission to
> reboot the system. After pressing OK it crashed. Is guess
> this is related to the fact, ther have been two user
> logins on the XP system at this time.
>
> Regards,
>
> Martin

Hello,

>#1 is a serious bug and is known to Microsoft and being
worked on.

OK, I found it in your list of know bugs.

>#2 I'm not sure what to say about--you may be right about
the cause--when
>you say "crash"--does that mean a reboot? Was there a
blue screen? Any
>information in the system error log for the time of that

No, it was only a simple "GPF error" (General Protction
Fault) - an access to some illegal memory address. After
that the Antispam program terminated, nothing more.
Sorry - I can't provide you more information, I couldn't
find an entry about this in the system log.

Regards,

Martin

#1) Known
#2) Are you submitting the crash report to Microsoft so we can analyze?


-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
<(E-Mail Removed)> wrote in message
news:266b01c50edd$7b518af0$(E-Mail Removed)...
> Hello,
>
>>#1 is a serious bug and is known to Microsoft and being
> worked on.
>
> OK, I found it in your list of know bugs.
>
>>#2 I'm not sure what to say about--you may be right about
> the cause--when
>>you say "crash"--does that mean a reboot? Was there a
> blue screen? Any
>>information in the system error log for the time of that
>
> No, it was only a simple "GPF error" (General Protction
> Fault) - an access to some illegal memory address. After
> that the Antispam program terminated, nothing more.
> Sorry - I can't provide you more information, I couldn't
> find an entry about this in the system log.
>
> Regards,
>
> Martin