Closed GoogleCodeExporter closed 9 years ago
After I install Java 6, I still observe:
c:\Program Files (x86)\Raptor>Raptor.exe
c:\Program Files (x86)\Raptor>[info] Module Name: c:\Program Files (x86)\Raptor\
Raptor.exe
[info] Module INI: c:\Program Files (x86)\Raptor\Raptor.ini
[info] Module Dir: c:\Program Files (x86)\Raptor\
[info] INI Dir: c:\Program Files (x86)\Raptor\
[info] Found VM: C:\Program Files\Java\jre7\bin\server\jvm.dll
[info] Expanding Classpath: updater.jar
[info] Generated Classpath: c:\Program Files (x86)\Raptor\updater.jar
[info] VM Args:
[info] vmarg.0=-Djava.class.path=c:\Program Files (x86)\Raptor\updater.jar
[info] Main Class: raptor/updater/UpdateManager
[info] Registering natives for Native class
[warn] Could not find Native class
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at raptor.updater.UpdateManager.invokeMain(Unknown Source)
at raptor.updater.UpdateManager.main(Unknown Source)
Caused by: java.lang.NullPointerException
at raptor.Raptor.shutdownWithoutExit(Unknown Source)
at raptor.Raptor.shutdown(Unknown Source)
at raptor.Raptor.shutdown(Unknown Source)
at raptor.Raptor.main(Unknown Source)
... 6 more
Original comment by DandyD...@gmail.com
on 7 Jul 2013 at 2:06
I have the same problem.
Raptor doesn't even start anymore.
I have tried everything on windows 7 and on windows 8.
Please help because I really liked the program.
I think the problem started when the fics server where down and only the backup
servers worked.
Regards Jonathan
Original comment by cremersj...@gmail.com
on 9 Oct 2013 at 2:01
Based on that stack trace, it looks like maybe the problem has something to do
with the UpdateManager. Is there a way to launch Raptor with the UpdateManager
disabled? Maybe that would bypass the problem?
Original comment by cr...@vieregg.net
on 26 Nov 2013 at 7:01
That's a great idea. I have reinstalled Raptor (this time, the 64-bit version)
and manually downloaded Raptor.jar to C:\Program Files\Raptor\Raptor.jar. I'll
try again tonight (from source code) since the following fails:
c:\Program Files\Raptor>java -jar Raptor.jar
Exception in thread "main" java.lang.NullPointerException
at raptor.Raptor.shutdownWithoutExit(Unknown Source)
at raptor.Raptor.shutdown(Unknown Source)
at raptor.Raptor.shutdown(Unknown Source)
at raptor.Raptor.main(Unknown Source)
Original comment by DandyD...@gmail.com
on 26 Nov 2013 at 8:09
An Eclipse build from source (swtEnv=Windows32 in build.xml) succeeds and
connects to FICS using my preferences!
FYI, a "Windows64" build (which should work on my 64-bit OS) fails. I'll see
if I can figure this out:
run:
[java] Exception in thread "main" java.lang.NullPointerException
[java] at raptor.Raptor.main(Raptor.java:222)
[java] Java Result: 1
Original comment by DandyD...@gmail.com
on 29 Nov 2013 at 12:46
In order to run 32-bit Raptor on my 64-bit Windows machine, I had to update my
Java preferences to define a 32-bit JRE via the following steps:
1. Run > "javaws -viewer"
2. Java > View > Find (or Add)
3. Find (or Add) an installed 32-bit JRE (can be a Java 7 JRE) from the
C:\Program Files (x86)\Java directory.
I'm still curious and trying to figure out why 64-bit Raptor doesn't work on my
machine, but I can confirm that 32-bit Raptor with a 32-bit JRE running on a
64-bit Windows OS works (including the Updater working).
Original comment by DandyD...@gmail.com
on 29 Nov 2013 at 1:52
Thanks for the workaround. I'm up and running with 32-bit Raptor now.
Before installing 32-bit Raptor, I tried to use the uninstaller for the 64-bit
Raptor and got an error, for which I created Issue 736. I'm not sure whether
these two issues might be related.
Original comment by cr...@vieregg.net
on 29 Nov 2013 at 7:42
Original comment by evil...@gmail.com
on 7 Nov 2014 at 9:02
I would recommend classifying this issue as an open low-priority Java 7 64-bit
compatibility defect, for which there is a workaround (use the 32-bit version
and require the user to figure out how to install 32-bit Java).
Original comment by DandyD...@gmail.com
on 8 Nov 2014 at 7:13
Original issue reported on code.google.com by
DandyD...@gmail.com
on 7 Jul 2013 at 2:01