Internal bug continues

(1) I have apparently correctly updated my JAVA Runtime…when checking my C: drive directory today’s install is there…so I seem to have done this correctly and SHUT DOWN and restarted since then…

(2) It looks like I have also correctly updated VASSAL today to 3.2.17

(3) and i have apparently update the VASL module to 6.4.1 today and relabeled or created new files for the updated program

My issue is that when I go to “start new game” in VASL 6.4.1 and load a Bounding Fire Productions map “BFPC” which I re-downloaded to the new 6.4.1 file… I get “internal error”… from VASSAL…

I am no expert…but have given you the pertinent info as best I can…I would be happy to allow a tech of yours at VASSAL to have access to my machine at a distance to see what problem might be…

Thus spake ptebennett:

(1) I have apparently correctly updated my JAVA Runtime…when checking
my C: drive directory today’s install is there…so I seem to have done
this correctly and SHUT DOWN and restarted since then…

(2) It looks like I have also correctly updated VASSAL today to 3.2.17

(3) and i have apparently update the VASL module to 6.4.1 today and
relabeled or created new files for the updated program

My issue is that when I go to “start new game” in VASL 6.4.1 and load a
Bounding Fire Productions map “BFPC” which I re-downloaded to the new
6.4.1 file… I get “internal error”… from VASSAL…

I am no expert…but have given you the pertinent info as best I
can…I would be happy to allow a tech of yours at VASSAL to have
access to my machine at a distance to see what problem might be…

Please post the contents of the errorLog when you have this “internal
error”.

Instructions for how to find the errorLog are here:

vassalengine.org/wiki/Error_Logs


J.