Windows scripting of filepro startup files

Fairlight fairlite at fairlite.com
Wed Sep 16 17:22:24 PDT 2009


On Wed, Sep 16, 2009 at 06:43:12PM -0400, Kenneth Brody, the prominent pundit,
witicized:
> Fairlight wrote:
> > On Wed, Sep 16, 2009 at 06:06:24PM -0400, Kenneth Brody, the prominent pundit,
> > witicized:
> >> Perhaps Server 2008 is even pickier than Vista?
> >>
> >> As I said, nothing in Vista, aside from a web browser, gives so much as a 
> >> peep when I start a batch file.
> > 
> > I've personally seen warnings/verifications in XP about batch file
> > security.  In every case, the batch file being started was on a network
> > share, rather than on a local drive.  The network shares are considered a
> > non-trusted domain.
> > 
> > Might that be the case here?
> 
> If I place the batch file on a network share, double-clicking its icon gives 
> me a warning on Vista:
> 
>     The publisher could not be verified.  Are you sure you want to run
>     this software?

That's the one in XP as well.

> The same batch file on a local drive, started using the exact same method, 
> runs without incident.

Yup.  Same in XP.

> Note, however, that even a .exe file gives the same warning when it's on a 
> network drive, so if this is his problem, replacing a .bat with something 
> else probably won't help.

Not necessarily.  A local copy of Perl calling a script on a network share
as an argument for the interpreter should work without warning, if the perl
were genuinely local.

But as you said, we don't know if that's the case for the OP.

mark->
-- 
Audio panton, cogito singularis,


More information about the Filepro-list mailing list