Vassal Window Invis & Minimizes by self

Vassal Window is Invisible & Minimizes itself as soon as i open it. And when i click on Icons on the Desktop i have also noticed that some of them can not be accessed therefore VASSAL is “Invisible”, I have tried versions 3.1.18-3.2.2, I’ve also tried Java 6.22 and 7.7.17 both from a blank slate with no avail. And as Ive read on other posts every one wants the error-log so here it is from the last installation Ive tried with VASSAL 3.2.22 and Java 7.7.17.

2013-03-28 19:18:20,799 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-03-28 19:18:20,814 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7
2013-03-28 19:18:20,814 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_17
2013-03-28 19:18:20,814 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.2
2013-03-28 19:18:20,861 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2013-03-28 19:23:12,709 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

This is a 64bit version of windows i am running as well.

Thus spake mccink:

Vassal Window is Invisible & Minimizes itself as soon as i open it. And
when i click on Icons on the Desktop i have also noticed that some of
them can not be accessed therefore VASSAL is “Invisible”, I have tried
versions 3.1.18-3.2.2, I’ve also tried Java 6.22 and 7.7.17 both from a
blank slate with no avail. And as Ive read on other posts every one
wants the error-log so here it is from the last installation Ive tried
with VASSAL 3.2.22 and Java 7.7.17.

2013-03-28 19:18:20,799 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-03-28 19:18:20,814 [0-main] INFO VASSAL.launch.StartUp - OS
Windows 7
2013-03-28 19:18:20,814 [0-main] INFO VASSAL.launch.StartUp - Java
version 1.7.0_17
2013-03-28 19:18:20,814 [0-main] INFO VASSAL.launch.StartUp - VASSAL
version 3.2.2
2013-03-28 19:18:20,861 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManager - Manager
2013-03-28 19:23:12,709 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManagerWindow - Exiting

Do you have another version of VASSAL running at the same time?


J.

No, no other versions running at the sametime, these were clean installs with all other versions uninstalled

Thus spake mccink:

No, no other versions running at the sametime, these were clean installs
with all other versions uninstalled

I don’t recognize the problem you’re having as one I’ve seen before.

When you try to run VASSAL, do you get an entry for it in the task
bar?


J.

Yes its in the Task Bar and on the windows minimize bar as well but when I click on it on the bar below were it has minimized it does nothing and the only way to shut it down is through the task manager

Thus spake mccink:

Yes its in the Task Bar and on the windows minimize bar as well but when
I click on it on the bar below were it has minimized it does nothing and
the only way to shut it down is through the task manager

Can you bring it up by cycling to it with ALT+TAB?


J.

No alt tabing does nothing to bring it up on my screen, I am also able to close it by right clicking on it on the task bar, but just clicking on it it just flashes but does not come up

Thus spake mccink:

No alt tabing does nothing to bring it up on my screen, I am also able
to close it by right clicking on it on the task bar, but just clicking
on it it just flashes but does not come up

Have you ever had VASSAL working on this machine?


J.

Yes, granted its been a while since I last tried it, 4-5 months ago maybe.

Thus spake mccink:

Yes, granted its been a while since I last tried it, 4-5 months ago
maybe.

Try deleting C:\Users<username>\AppData\Roaming\VASSAL, which is where
VASSAL stores its configuration information. Does that help?


J.

That did nothing for it same thing still happing

Thus spake mccink:

That did nothing for it same thing still happing

Can you run VASSAL from the “generic” bundle instead?

downloads.sourceforge.net/vassal … -other.zip

(Unzip. Try running VASSAL.bat.)


J.

That didn’t seem to do any good either

Thus spake mccink:

That didn’t seem to do any good either

I’m out of ideas. This is likely a problem with something in your
installation of Windows, not a problem with VASSAL.


J.