[ggo-discussion] Re: gGo crashes machine?

On Sun, Mar 02, 2003 at 11:38:52AM -0500, Jeffrey Nowakowski wrote:
> 
> I think I got around the crashing problem by removing a KVM switch (it
> lets you run two computers with the same keyboard, monitor, and
> mouse).

Ah ok, I guess Java cannot handle that properly. No idea, I don't use such
stuff myself. It should not be a problem related to gGo but related to Java
in general, so I'm pretty sure this is not my business.


> However, now I have problems playing against Gnu Go.  When I try to
> resume a saved .sgf game, it won't let me make any moves as black.
> I've included the .sgf file and some output from .ggo.log.

Owww... there you found some nasty thing. :)
When you resume a GNU Go game, gGo will take the boardsize from the setup
dialog, not from the SGF file. The log suggests your setup dialog size was
19. The SGF is loaded properly, but when gGo later translates a click into a
GTP coordinate, it used 19 as size, producing invalid coordinates. When I
changed the size to 9 in the setup dialog and then resumed the game it
worked.
Nevertheless, this behaviour is not good, the client should overwrite the
dialog boardsize with the real boardsize read from the SGF file. Will fix
that for the next release, thanks for this hint. :)


> One last thing.  The log indicates it is using Java 1.3, even though I
> have 1.4 installed.  I used Java Web Start to download gGo, so I would
> think it would use 1.4, no?

Depends on how you configured Webstart. See File-Settings (or whatever thats
called in the english version) of the webstart application manager. There
you can add a list of JRE's, I *think* webstart will use the top entry.

To confuse things even more, when you install 1.3 via webstart (some older
webstart apps still demand Java 1.3, so webstart will automatically install
1.3 even if 1.4 is present, but this is the fault of the application
authors), a registry entry gets overwritten. gGo (non-webstart version) uses
this registry entry to determine the path to the Java installation to find
the javaw.exe binary.
*Maybe* webstart will not use the top entry of its configuration but the JRE
this registry entry points to. I am not sure about this.

However, if you deinstall Java 1.3 and still have 1.4 present, the registry
entry is not fixed by the 1.3 deinstaller. Sun fumbled here, and this
registry usage is generally a mess.

Generally I made the experience having more than one JRE/SDK's installed on
Windows is a bad idea, and once you deinstall one or want to setup not the
latest installed one as default, you need to manually edit the registry.
Whom to blame? Microsoft for inventing a <censored> like registry, and Sun
for using it. Me? No! :) The gGo webstart configuration says, use 1.3 or
above, whatever is available (I cannot set it to 1.4 because that would
exclude Mac OS X users).


 Peter

Other related posts: