FIBS Board backgammon forum
FIBS Client software => Other Fibsclients => Topic started by: burper on May 09, 2004, 09:07:46 PM
I still have some issues from time to time, but it's better than pre-alpha 1.
If you want to try it again, get it from http://prdownloads.sourceforge.net/fibscom...on.zip?download (http://prdownloads.sourceforge.net/fibscompanion/fibscompanion.zip?download)
known problem: upbound invite for a resumed match causes an exception
Sorry, Burper, but I get the following error messages:
C:\App_Originale\Spiele\Backgammon\FibsCompanion>java -jar -Djava.security.manag
er -Djava.security.policy=security.policy fibscompanion.jar
Exception occurred during event dispatching:
java.lang.NoClassDefFoundError: javax/swing/JSpinner
at net.sf.fibscompanion.FibsCompanion.<init>(FibsCompanion.java:237)
at net.sf.fibscompanion.FibsCompanion.getInstance(FibsCompanion.java:89)
at net.sf.fibscompanion.FibsCompanion.createAndShowGUI(FibsCompanion.jav
a:271)
at net.sf.fibscompanion.FibsCompanion.access$000(FibsCompanion.java:37)
at net.sf.fibscompanion.FibsCompanion$1.run(FibsCompanion.java:78)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
I use Windows XP, have downloaded the zip, extracted, startet JavaFIBS and executed the fc.bat. Have I made something wrong?
Looks like you are not using java 1.4+
So I put code in to check for that. You should have received a popup informing you of the above. :( I will fix that. In the mean time, upgrade.
I've noticed a couple other bogus assumptions I've made regarding what FIBS might send me and will be providing an alpha3 that fixes that stuff sometime this week I think. A couple symptoms to look for: a bogus RepBot query on user '6' and missing the login line on startup of the client connection. I also think this is causing the bogus RepBot timeout messages.