--- In [email protected], Keith Todd <[EMAIL PROTECTED]> wrote:
>
> You certainly use those directins by using common
> sense but not literally. My webstart console does not
> follow that menu path anymore. I think it changed
> with latest JRE.
>
> Keith
>
I had the problem too. With my java version (5), I had to do something
a little different than what was posted earlier. Assuming you are
running windows XP, doubleclick on the "java" icon in your control
panel (i.e. "start/control panel"). This should start up the Java
Control Panel. You should see a block near the bottom that says
"Temporary Internet Files." Click on the "Delete Files" button. There
are three checkboxes you may select. The only one I needed to select
was the middle one: Downloaded Applications. Make sure that one is
selected. Click Ok.
This will wipe all java webstart applications. Go back to the vassal
home page and try again.
If you aren't running windows XP or the above does not match your
setup or you don't want to wipe every webstart application, you can
try something else. Search your computer for "javaws" or "javaws.exe".
On my computer, there are a bunch of copies, but the primary appears
to be in the system32 directory. If you run this program, it should
open a java webstart console, and you should see a list of all
webstart applications you have installed. If you don't see anything,
try "view" on the menu and selecting all or applications. You can then
select vassal-related applications. Then select "application" and
"remove." This should wipe out the old stuff, and then you should be
able to go back to the vassal page and try again.
and now for some java-ese not of interest to the typical player:
I am a java designer/programmer by profession, so I spent some time
trying to get to the bottom of this problem. I have worked with
webstart before, but unfortunately I don't know enough of how things
are configured to get more information other than the obviou. It seems
odd to me that the downloading of the new vassal.jar seems to be
dependent on the existence (or not) of older versions -- UNLESS Rodney
is using some sort of jar-differences program when vassal.jar is
downloaded. With a differencing mechanism, it would be trying to only
downloaded the parts that changed, and that could explain why
downloading a new version over an old one might fail. If this scenario
is true, I would suggest that Rodney not use jar-differencing and
instead have users download a complete fresh copy of vassal.jar.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
