Sounds good, I've disabled the JWS. Thanks for investigating further as well.
Thanks for the link. Interesting -- this only seems to happen when the JavaWebStart launch method is used. Not sure why, offhand. We'll investigate. For the time being, you may want to disable JWS via the WebScriptWizard. This will enforce the plugin launch method.
Hmm, I'm super confused. Here is the link to my launch page: http://research.millisecond.com/lbens/Batch.web
Are you able to access my actual script if you have my username (lbens)?
What you describe certainly isn't consistent with a launch technology issue. As I said, *no* script would run without the Inquisit engine having been installed to the system via one of the available venues (JavaWebStart, NPAPI plugin, ClickOnce, ActiveX).
What goes exactly goes on, I have no way to tell without access to your files and launch page.
You think this is the issue, even keeping in mind that the batch plays through entirely (with no problem) when we click the link at the bottom of the page where it says "try to mozilla plugin version? Once we click this the first time, and the plugin downloads, we are good to go from there...
I just don't think the undergrads will be as persistent if they encounter any problem at all.
Without the plugin, Inquisit would not be able to run the 1st script at all. I.e., the plugin must already have been installed. The behavior you describe rather points to an issue with your <batch> elements.
When I tested on both my PC and Mac, I used Mozlilla (current version). I believe that's what others used as well.
I just had one of our IT guys test it, and he had the same issue.
What happens is that without downloading the plugin, Inquisit will take the user through my first script in the batch, but then the window will close when the batch tries to transition to the second script.
Hm, weird. Which browser(s)?
No JavaScript blockers or the like...
Do you use any JavaScript blockers or the like?