Can't run any versions past 3.6.16

Technical Support & Bugs
21

This one also failed

22

Next one: https://vassalengine.org/~uckelman/VASSAL-7b6ba53e.exe

(I suspect this one will work. The bad commit is probably fa9a7cbd. Once weā€™ve confirmed that, Iā€™ll stare at it a bit to see if I can spot whatā€™s wrong, and then Iā€™ll have a fix for you to test.)

23

Yes, this one did work. Might not get to your next one for an hour or so

24

Next one: https://vassalengine.org/~uckelman/VASSAL-revert.exe

This one is produced by launch4j 3.50 with commit fa9a7cbd reverted. I suspect it will work. The next step after this one is to figure out whatā€™s wrong with that commit. I donā€™t quite see it yet.

25

Yes, this one worked

1 Like
26

Try running the original VASSAL.exe from 3.6.17 with the command line option --l4j-debug-all, so like this:

VASSAL.exe --l4j-debug-all

That should produce a file named launch4j.log. Please post the contents of that file.

27

I didnā€™t find the log file anywhere, I looked in the user profile path and the vassal directory.

28

I expect the log would be written in the directory from which youā€™re launching VASSAL.exe. Can you run it from your user directory? Say, as C:\Program Files\VASSAL-3.6.17\VASSAL.exe --l4j-debug-all?

29

Hereā€™s where I found one:
C:\Users\XXXXXX\AppData\Local\VirtualStore\Program Files\VASSAL-3.6.17
But it is a zero byte file.

30

Does the timestamp for that file match when you ran VASSAL.exe?

31

Yes, it matched 17:55 EST

32

Letā€™s see if we can figure out how far it gets before crashing.

Try this one: https://vassalengine.org/~uckelman/VASSAL-1.exe

(This one might work. If it works, that means it got at least up to the bail-out point I inserted.)

33

Actually it didnā€™t get through. I also tried it with the log switch and it didnā€™t create one.

34

Just to make sure, I ran VASSAL-7b6ba53e.exe again with the log switch and it did create one, so I know it can work :slight_smile:

35

Thank you for checking thatā€”I was about to ask. This means VASSAL-1.exe is failing sooner than I thought it would.

Next one: https://vassalengine.org/~uckelman/VASSAL-2.exe

36

No run on that one and no log

37

How about this one? https://vassalengine.org/~uckelman/VASSAL-3.exe

38

Same result, no run and no log

39

Itā€™s obnoxious that it doesnā€™t flush the log on each writeā€¦ Thatā€™s something youā€™d really like to have when youā€™re doing debug logging.

Iā€™ll stare at this more tomorrow. Thanks for testing.

1 Like
40

Iā€™ve hit a wall. In order to debug further, I need to be able to recompile head.c in Launch4j, but Launch4j doesnā€™t provide any instructions for doing that correctly. (Iā€™ve spent about four hours now trying.)

Iā€™m going to file a bug report with Launch4j, but it could be a long time (or never) before it gets acted on. I might switch us back to Launch4j 3.14, which doesnā€™t have this problem. In the meantime, you can use a VASSAL.exe from 3.6.16 as your launcher instead.