Page 1 of 1

Vassal will not start

PostPosted: January 12th, 2013, 11:14 am
by Proxiehunter
Model - Acer Aspire 1
Operating System Windows 7 Ultimate 32-bit SP1
CPU Intel Atom N270 @ 1.60GHz Diamondville 45nm Technology
Memory 1.00 GB Single-Channel DDR2 @ 266MHz (4-4-4-12)
Video Card Generic PnP Monitor (1024x600@60Hz)
Mobile Intel 945 Express Chipset Family
Mobile Intel 945 Express Chipset Family
Vassal version 3.2.2
Java version Java 7 update 10

When I attempt to start Vassal nothing happens except the program sucking up 50,000K or more of memory. Nothing opens, no error message is produced. It does not seem to have produced an error log.

Re: Vassal will not start

PostPosted: January 12th, 2013, 6:21 pm
by Proxiehunter
Update: Discovered that if I let it run long enough (which seems to be over an hour) it will suck down nearly 100,000 k of memory, appear on my task bar, and be non-functional in any way.

Re: Vassal will not start

PostPosted: January 13th, 2013, 1:18 pm
by uckelman
Thus spake Proxiehunter:
> Model - Acer Aspire 1
> Operating System Windows 7 Ultimate 32-bit SP1
> CPU Intel Atom N270 @ 1.60GHz Diamondville 45nm Technology
> Memory 1.00 GB Single-Channel DDR2 @ 266MHz (4-4-4-12)
> Video Card Generic PnP Monitor (1024x600@60Hz)
> Mobile Intel 945 Express Chipset Family
> Mobile Intel 945 Express Chipset Family
> Vassal version 3.2.2
> Java version Java 7 update 10
>
> When I attempt to start Vassal nothing happens except the program
> sucking up 50,000K or more of memory. Nothing opens, no error message is
> produced. It does not seem to have produced an error log.

Check whether you have both Java 6 and Java 7 installed at once. If so,
uninstal one of them. This is the most common cause of the symptoms
you're reporting.

--
J.

Re: Vassal will not start

PostPosted: January 13th, 2013, 11:35 pm
by Proxiehunter
uckelman wrote:Thus spake Proxiehunter:
> Model - Acer Aspire 1
> Operating System Windows 7 Ultimate 32-bit SP1
> CPU Intel Atom N270 @ 1.60GHz Diamondville 45nm Technology
> Memory 1.00 GB Single-Channel DDR2 @ 266MHz (4-4-4-12)
> Video Card Generic PnP Monitor (1024x600@60Hz)
> Mobile Intel 945 Express Chipset Family
> Mobile Intel 945 Express Chipset Family
> Vassal version 3.2.2
> Java version Java 7 update 10
>
> When I attempt to start Vassal nothing happens except the program
> sucking up 50,000K or more of memory. Nothing opens, no error message is
> produced. It does not seem to have produced an error log.

Check whether you have both Java 6 and Java 7 installed at once. If so,
uninstal one of them. This is the most common cause of the symptoms
you're reporting.

--
J.



Unless java is installed separately on different user profiles and this can cause interference this isn't the issue. I just deleted every trace of Java I could find (with the aid of a program called Java Ra) and did a clean install; incidentally moving to Java 7 update 11 in the process. I'm still getting this behavior.

There was an issue with me having multiple java installs that I discovered early after posting this thread, however fixing that via less drastic methods than the clean install I tried today also failed to clear up the problem.

Edit: Looks like I can no longer edit the original post so here are my computers most up to date specs:

Model - Acer Aspire 1
Operating System Windows 7 Ultimate 32-bit SP1
CPU Intel Atom N270 @ 1.60GHz Diamondville 45nm Technology
Memory 1.00 GB Single-Channel DDR2 @ 266MHz (4-4-4-12)
Video Card Generic PnP Monitor (1024x600@60Hz)
Mobile Intel 945 Express Chipset Family
Mobile Intel 945 Express Chipset Family
Vassal version 3.2.2
Java version Java 7 update 11

Re: Vassal will not start

PostPosted: January 24th, 2013, 3:35 am
by .mp
I just solved my own Vassal won't start problem. Same symptoms as this thread so I'm posting here instead of starting yet another won't start thread. In my case, it appears java.com fed me the 32 bit version; however, I use Win 7 64 bit. I uninstalled all previous versions of java using the windows console & then manually removed some jetsam left behind while attempting to fix the problem. Many reboots and a clean java install later, Vassal now runs.

Good luck,