Jim,
I'm going to try changing the shell execution verb from open to runas and see 
if that works. I'm not getting this error on my machine; so, I was hopeful but 
not sure.

Did the setup.exe with the installation wizard  for the changes run OK? Trying 
to figure out if it is both the WE4Java_setup.exe and the InstallWE4Java.exe 
that is having a problem.

From: Jim Grimsby Jr. [mailto:[email protected]]
Sent: Tuesday, February 24, 2009 4:02 PM
To: [email protected]
Subject: RE: WE4Java 0.9.16 released to Script Central

Hi well here is the bad news.  Just ran it on my vista box and guess what!
Setup
Unable to execute file:
C:\Program Files\WE4Java\InstallWE4Java.exe
CreateProcess failed; code 740.
The requested operation requires elevation.
OK
From: Macarty, Jay {PBSG} [mailto:[email protected]]
Sent: Tuesday, February 24, 2009 1:09 PM
To: [email protected]; [email protected]
Cc: [email protected]
Subject: WE4Java 0.9.16 released to Script Central

All,
Version 0.9.16 of WE4Java has been released to script central. The change log 
is shown below. The major highlights are that the script now includes the 
StandardHelpDialog; so, you have the option to turn automatic updates on or off 
from the script manager. A change in the shell calls for the setup.exe will 
hopefully avoid the 740 error from some vista users. Also, the java code has 
been updated to now be able to read popup message boxes in your java 
applications.

One other thing (Jesse and Jamie) to note. The Install WE4Java to a Java 
Environment utility now contains a Validate Install button (alt+v). this checks 
for all the WE4Java files in a given directory and also lets you run a small 
test class. The results of the test class run are put into an edit popup box 
and also copied to the clipboard so you can send the results to me. <smile>

Here is the full change log:

Beta Release 0.9.16 - Tuesday, 2/24/2009

This release contains the following updates:

  * The WE4Java.vbs script has been updated to include the StandardHelp
    logic in order to enable the Help/Controls button in Script Manager.
  * The shell objects used to execute the setup.exe and the install java
    utility have been updated from wscript.shell to shell.application.
    Hopefully, this will avoid the 740 error reported by some vista users.
  * The Install WE4Java to a Java Environment utility has been updated to
    include a new button called Validate Install (alt+v). This option
    will check a java environment to make sure all the required wE4Java files
    are present and will then prompt the user to ask if a small test program
    should be run. If yes is selected, the test java class is executed.
    Whether the test class is successful or not, the console output of the
    test run is placed into a popup edit window and is also automatically
    copied to the clipboard. In this way, a user can paste the results
    into an e-mail to be sent for trouble shooting (e.g. to Jay Macarty).
  * The WE4Java java code now includes the ability to read popup message
    dialogs created by the JOptionPane object. The Swingset2 demo
    contains a sample tab for JOptionPane showing 5 different types
    of dialogs; input, warning, message, component, and confirmation.
    The dialogs also contain a mixture of regular text and html formatted
    messages. Testing thus far, indicates all dialog types can be read.

NOTE: The dialog title bar is not always being spoken correctly. This is being
      researched.



__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 3844 (20090211) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 3844 (20090211) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Reply via email to