After not playing on KGS for a while I had the bad surprise to encounter this issue when coming back (on win 7 x64)
I solved it by installing Java 6u31 (apparently the latest that still works) without uninstalling Java 7. Then I just dowloaded the CGoban jar file and made a batch file to start it with version 6u31.
That way I can keep an unmodified latest version of Java 7 for everything else and have CGoban working without having to pull off my own hair in frustration trying some of the clever hacks proposed here
Codexus wrote:After not playing on KGS for a while I had the bad surprise to encounter this issue when coming back (on win 7 x64)
I solved it by installing Java 6u31 (apparently the latest that still works) without uninstalling Java 7. Then I just dowloaded the CGoban jar file and made a batch file to start it with version 6u31.
That way I can keep an unmodified latest version of Java 7 for everything else and have CGoban working without having to pull off my own hair in frustration trying some of the clever hacks proposed here
And you would retain the automatic updating features of java webstart.
I just tried your suggestion but it doesn't work for me. The Java 6 logo is displayed but CGoban itself is still started with Java 7. As I understand it, java webstart is supposed to choose the correct version of Java to run based on the content of jnlp file and defaults to the latest. There might be a way to modify the jnlp for that but then there are code signing problems if I do that.
I was able to fix my missing stone-click sounds with the java-extension-mixer-hack.. Thanks for that.
What's really weird, is that the KGS "error" sound (if I try to click before the mis-click timer) still soudns find, just the stone click sounds are missing.
Testaudio produced no sound for me.. here is the output.
C:\kgs>java -jar testaudio.zip
Played audio file at volume 0.85125035
C:\kgs>java -version
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
davesf wrote:
What's really weird, is that the KGS "error" sound (if I try to click before the mis-click timer) still soudns find, just the stone click sounds are missing.
yes, wms said he used different ways to play a sound in Java as they were coded at different times and some functions were not available in earlier versions.
Now I haven't seen the code but it would seem to me that for a quick fix, just a ugly copy/paste of the code for a sound that works to replace one that doesn't should solve this problem in no time... Better code can be written later if needed.
If this server is such a nuisance, why not just shut it down? Or hand control in all respects (including programming) to someone who cares.
But I'm going on vacation on Friday (to Congress then to a family event); I don't want to fix before then, because if there is a problem with my fix I won't be able to change anything until I return. So I'll try to get a fix in sometime after August 20...it's a long way off, but that's when I'll be back around.
It's well past August 20th now and stone sounds are still broken. No updates have been offered and the only solutions seem to be made for people with programming savvy.
dfunkt wrote:If this server is such a nuisance, why not just shut it down? Or hand control in all respects (including programming) to someone who cares.
I have been in this exact situation. My free applet had problems after a Java upgrade and it's really annoying to have to go back and fix something that broke itself for no good reason when you have other priorities at the moment. And that kind of angry comment demanding an immediate fix did not help me get in the mood to work on something I give away for free again.
The admins have been told that the switch to use the old audio engine is only for Java 1.6.0_30 to 1.6.0_37. It is not available in Java 1.7, and Java older than 1.6.0_30.
lovelove wrote:What is wms doin? Java keep bothers me to update, but I can't cuz stone sound will be gone again.
No idea. The last thing I heard was this (Jul the 31st):
wms wrote:I give up. I'll fix the *!@*$!@#*$ stone sounds.
But I'm going on vacation on Friday (to Congress then to a family event); I don't want to fix before then, because if there is a problem with my fix I won't be able to change anything until I return. So I'll try to get a fix in sometime after August 20...it's a long way off, but that's when I'll be back around.
Codexus wrote:After not playing on KGS for a while I had the bad surprise to encounter this issue when coming back (on win 7 x64)
I solved it by installing Java 6u31 (apparently the latest that still works) without uninstalling Java 7. Then I just dowloaded the CGoban jar file and made a batch file to start it with version 6u31.
That way I can keep an unmodified latest version of Java 7 for everything else and have CGoban working without having to pull off my own hair in frustration trying some of the clever hacks proposed here
For everybody still reading this thread, I just used Codexus fix and it still works.
Codexus wrote:After not playing on KGS for a while I had the bad surprise to encounter this issue when coming back (on win 7 x64)
I solved it by installing Java 6u31 (apparently the latest that still works) without uninstalling Java 7. Then I just dowloaded the CGoban jar file and made a batch file to start it with version 6u31.
That way I can keep an unmodified latest version of Java 7 for everything else and have CGoban working without having to pull off my own hair in frustration trying some of the clever hacks proposed here
For everybody still reading this thread, I just used Codexus fix and it still works.
Why is it the only choice? I have to agree with you that it's a bit... unprofessional to leave a bug like this hanging for so long, but the fix mentioned above is available to anyone, right? Or is it only available to windows users?