i do something really trivial !
Before reinstalling, i completly delete the roaming\vassal\ directory.
Now it seems to work !
Merci Joel
Thus spake Lorenzo26:
i do something really trivial !
Before reinstalling, i completly delete the roaming\vassal\ directory.
Now it seems to work !
Hmm, I’m unsure why that would help, but I’m glad your problem is
solved.
–
J.
Joel,
my problem is back !
After a windows update this morning.
And this time after desinstalling vassal, deleting all vassal files in temp, roaming vassal, it works only one time after reinstalling.
I’m desesperate.
Laurent.
seems really to be a windows 8 compatibility problem.
With a right-clic on the program, i can solve this problem, asking W8 to run vassal as an XP program.
Seems to work for now…
Thus spake Lorenzo26:
seems really to be a windows 8 compatibility problem.
With a right-clic on the program, i can solve this problem, asking W8 to
run vassal as an XP program.
Seems to work for now…
We haven’t heard from anybody else having this problem on Windows 8.
Is anyone out there using Windows 8 without issue?
–
J.
We just had the a similar problem with a new laptop that had a Windows 8 (32bit) installed. Vassal would only open and operate normally if you put it in “Windows XP (SP3)” compatibility mode and start it as administrator.
Relevant settings that got vassal to load modules and operate them properly: on the desktop link rclick->properties, switch to compatibility tab, check use compatibility and choose “Windows XP (SP3)”, check the “start as administrator” option, press apply or ok.
(windows was a German brand, I translated on the fly, actual options might be named differently)
Cheers
Thus spake Dabrion:
We just had the a similar problem with a new laptop that had a Windows 8
(32bit) installed. Vassal would only open and operate normally if you
put it in “Windows XP (SP3)” compatibility mode and start it as
administrator.Relevant settings that got vassal to load modules and operate them
properly: on the desktop link rclick->properties, switch to
compatibility tab, check use compatibility and choose “Windows XP
(SP3)”, check the “start as administrator” option, press apply or ok.
(windows was a German brand, I translated on the fly, actual options
might be named differently)
Plese delete VASSAL’s errorLog, try running VASSAL without this
compatibility mode, and then post the new contents of the errorLog here.
I’d like to see what exactly is happening. You can find the errorLog
in C:\Users<username>\AppData\Roaming\VASSAL.
–
J.
Will do when I see my friend and his laptop again soon. I would not worry too much as this is likely a Win8 <-> lwjgl issue that will auto-resolve soon™ (several java apps that use lwjgl have this problem, Minecraft frex, I presume you use it as well?)
Thus spake Dabrion:
Will do when I see my friend and his laptop again soon. I would not
worry too much as this is likely a Win8 ↔ lwjgl issue that will
auto-resolve soon™ (several java apps that use lwjgl have this
problem, Minecraft frex, I presume you use it as well?)
No, we’re not using lwjgl.
–
J.