Windows scripting of filepro startup files

[Kenneth Brody]

Richard Kreiss wrote:
[...]
> Task is running on the server - server 2008.

And it's on a local drive?  That eliminates the "network drive is an 
untrusted source" aspect.

> The batch file will run without a complaint from the command line

Okay.

> but not as
> a shortcut on the desktop.  Always get the warning of an unsigned program.

Perhaps Server 2008 is even pickier than Vista?

> I created a new batch file with just fp's set requirements.  No executable.
> Got the same warning.

I would expect that the contents of the .bat file are irrelevent, and it's 
based solely on the .bat extension.

> I am going to assume that filePro's executables have been Microsoft signed
> as the run without causing a problem or have they?

No, they have not.  Note that, on Vista at least, executables on network 
shares give the same "unsigned" message as .bat files.

> Have you looked at the Windows powershell program.  It looks like they are
> developing something akin to a korn shell with a strong scripting language.

No, I have not.  Will it create .exe files which don't get complaints from 
Vista and Server 2008?

> I may try this next.  There has got to be some way to set fp's environment
> and run a program without having  windows complain about not having the
> proper signature.

If you don't mind having them set globally, then use the control panel to 
set them at startup.  How to do this on Server 2008 is left as an exercise 
to the reader.

-- 
Kenneth Brody