Your VASL shortcut is behaving correctly.
The VASL shortcut loads a 'compiled' version of VASL, which is a .jar
file, not a .mod file. It's preset to run under the specific VASSAL
version it was created in - it won't use a later VASSAL version if
one happens to exist on your box. You can't load this .jar file from
VASSAL.
To run VASL by loading the module after starting VASSAL, you need to
have the latest VASL.mod file, which you must d/l separately from
www.vasl.org/download.htm (click the link 'VASL module file'). Create
a dir in your VASSAL dir that ID's the VASL version number (such
as 'VASL52'). Extract the VASL.mod file from the d/l'd VASL.zip &
place it in this new dir. Now you can nav to & load VASL.mod from
VASSAL.
VASL.mod v5.0b2 is one of several betas of v5 & is of purely
historical interest - best to delete that modfile. The current
version of VASL.mod is v5.2, which requires VASSAL v2.5.2. The
upcoming version of VASL will be v5.3, which will require VASSAL
v2.6.3.
hth
--- In [email protected], "Tom & Sandy Sharp"
<[EMAIL PROTECTED]> wrote:
>
> Brent,
> Well I'm getting closer. I am able to launch VASSAL2.6.3 but
unable to
> locate VASL5.2 If I launch Java Web Start. I found VASL5.0b.2 or
something
> like that. If I launch VASL 5.2 from my desktop directly it doesn't
find the
> latest version of VASSAL. I it finds VASSAL 2.5.2. Go figure.
>
> Tom
YAHOO! GROUPS LINKS
- Visit your group "vassalengine" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
