12-12-2010, 02:05 AM
I think in the Custom Path it would be better if users choose the actual jar file itself instead of just the jar path. This way the file doesn't have to be named jpcsp.jar. This is useful for those of us who download the source code directly through svn and build the jar file ourselves. In Netbeans, the name of the jar file is whatever name we use for the Netbeans project folder.
Oh, another switch that can be added in the Basic page is -Xverify:none which causes the JVM to skip the Java bytecode verification routine when loading classes. This speeds up the Jpcsp loading at the beginning a bit especially on slow machines, and probably also helps when combined with the -XX:+CMSClassUnloadingEnabled advanced switch so that when unloaded classes are loaded again, the JVM doesn't spend CPU time verifying it.
Oh, another switch that can be added in the Basic page is -Xverify:none which causes the JVM to skip the Java bytecode verification routine when loading classes. This speeds up the Jpcsp loading at the beginning a bit especially on slow machines, and probably also helps when combined with the -XX:+CMSClassUnloadingEnabled advanced switch so that when unloaded classes are loaded again, the JVM doesn't spend CPU time verifying it.