Very bad bug

[=?iso-8859-1?Q?Per_=D8stergaard?=]

When a script is executed for the first time, a
allow/block message appears. This could be ok, but two
bugs are present in this:
1. If you press allow, the script is executed in a new
command window (my default is cscript) so you loose the
output.
2. This first-time execution is asynchroneous to the
process calling the script. E.g. if you run the script
from a command (bat/cmd) file, the next lines in the
command file will be executed right away without waiting
for the script. This could cause very serious problems
for many users.

Best regards
Per

 

[Guest]

I noticed that too and its even worse then that. When I
open a script for edit using PrimalScript "Edit with
PrimalScript" the allow/block prompt comes up, I click
allow and instead of opening in PrimalScript the script
runs!! Very bad.. I tried to disable Script Blocking
under Application Agents and that worked for a while, but
now it's doing it again and the Agent is still disabled!

Bob

 

[=?iso-8859-1?Q?Per_=D8stergaard?=]

Could someone from the MS team please comment on this