New Fischerle Versions (64 and 32 Bit)
Moderators: hgm, Harvey Williamson, bob
Forum rules
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
- RolandoFurioso
- Posts: 55
- Joined: Sat Feb 22, 2014 6:29 pm
- Location: Frankfurt
New Fischerle Versions (64 and 32 Bit)
Hi all,
I have just released a follow-up version of my chess engine: Fischerle_0_9_50. It is available for download at http://www.stuckardt.de/index.php/schac ... herle.html
The main new features are:
- the king plays a more active role in late middlegame / early endgame;
- most instances of some important types of draw (viz., particular positions of type king vs. rook pawn or king vs. rook pawn and wrong-colored bishop) are now properly recognized;
- configuration file config.ini enables the user to alter some supplementary settings (such as the font and font sizes to be employed for displaying chess pieces in Fischerle's proprietary GUI).
Moreover, a distinction is now drawn between a 64 bit and a 32 bit version. While the code base is identical, there is just one difference: in the 32 bit version, more hash table entries are assigned since their memory footprints in 32 bit environments turned out to be slightly smaller than in 64 bit environments.
I have as well added a 32 bit version to the Fischerle_0_9_30b distribution. If you'd like to continue using this older version: it is as well available at http://www.stuckardt.de/index.php/schac ... herle.html
Have fun!
Roland
I have just released a follow-up version of my chess engine: Fischerle_0_9_50. It is available for download at http://www.stuckardt.de/index.php/schac ... herle.html
The main new features are:
- the king plays a more active role in late middlegame / early endgame;
- most instances of some important types of draw (viz., particular positions of type king vs. rook pawn or king vs. rook pawn and wrong-colored bishop) are now properly recognized;
- configuration file config.ini enables the user to alter some supplementary settings (such as the font and font sizes to be employed for displaying chess pieces in Fischerle's proprietary GUI).
Moreover, a distinction is now drawn between a 64 bit and a 32 bit version. While the code base is identical, there is just one difference: in the 32 bit version, more hash table entries are assigned since their memory footprints in 32 bit environments turned out to be slightly smaller than in 64 bit environments.
I have as well added a 32 bit version to the Fischerle_0_9_30b distribution. If you'd like to continue using this older version: it is as well available at http://www.stuckardt.de/index.php/schac ... herle.html
Have fun!
Roland
Re: New Fischerle Versions (64 and 32 Bit)
Thank you for the update, Roland.
Re: New Fischerle Versions (64 and 32 Bit)
Thank you, Roland.
I may be hopeless but I would like to ask how does the bat file know which java environment to use when I have both 32-bit and 64-bit java environment installed and my operating system is 64-bit.
I may be hopeless but I would like to ask how does the bat file know which java environment to use when I have both 32-bit and 64-bit java environment installed and my operating system is 64-bit.
Gabor Szots
CCRL testing group
CCRL testing group
- Sylwy
- Posts: 3358
- Joined: Fri Apr 21, 2006 2:19 pm
- Location: IASI (Romania) - the historical capital of MOLDOVA
Re: Nice !
THANK YOU !
Silvian
R
Below is the previous Fischerle performance in my JAVA GRAND FINAL 2014:

Silvian
Below is the previous Fischerle performance in my JAVA GRAND FINAL 2014:

- Sylwy
- Posts: 3358
- Joined: Fri Apr 21, 2006 2:19 pm
- Location: IASI (Romania) - the historical capital of MOLDOVA
Re: The final response ! -:)
SzG wrote:Thank you, Roland.
I may be hopeless but I would like to ask how does the bat file know which java environment to use when I have both 32-bit and 64-bit java environment installed and my operating system is 64-bit.
Hi Gabor !
In short:
1.-Java bytecode (and source code) is platform independent, assuming you use platform independent libraries. 32 vs. 64 bit shouldn't matter.
2.-Data serialized on a 32bit platform must be read in on the 64bit platform with no issues at all.
Still alive (
Silvian

Re: The final response ! -:)
Hi Silvian,Sylwy wrote:SzG wrote:Thank you, Roland.
I may be hopeless but I would like to ask how does the bat file know which java environment to use when I have both 32-bit and 64-bit java environment installed and my operating system is 64-bit.
Hi Gabor !
In short:
1.-Java bytecode (and source code) is platform independent, assuming you use platform independent libraries. 32 vs. 64 bit shouldn't matter.
2.-Data serialized on a 32bit platform must be read in on the 64bit platform with no issues at all.
Still alive () the Java teacher
SilvianR
As far as I understood Roland's statements, even that totally equivalent code produces different hash sizes, therefore maybe different strength.
However, what I don't understand at all is that both batch files begin with 'java', which I interpret as a program called 'java' is invoked and this program uses the jar file as an input. If that 'java' program is different when 32-bit and when 64-bit OS is used, maybe the strength of the engine will also be different.
On my 64-bit machine I have Program Files and Program Files(x86), under both of them there is a java directory. In your opinion which of the two will be invoked when the system starts the execution of the bat file with that 'java' instruction?
Gábor
Gabor Szots
CCRL testing group
CCRL testing group
- Sylwy
- Posts: 3358
- Joined: Fri Apr 21, 2006 2:19 pm
- Location: IASI (Romania) - the historical capital of MOLDOVA
Re: The final response ! -:)
Delete the Java 32-bit environment from your machine ! That's my advice.SzG wrote:Hi Silvian,Sylwy wrote:SzG wrote:Thank you, Roland.
I may be hopeless but I would like to ask how does the bat file know which java environment to use when I have both 32-bit and 64-bit java environment installed and my operating system is 64-bit.
Hi Gabor !
In short:
1.-Java bytecode (and source code) is platform independent, assuming you use platform independent libraries. 32 vs. 64 bit shouldn't matter.
2.-Data serialized on a 32bit platform must be read in on the 64bit platform with no issues at all.
Still alive () the Java teacher
SilvianR
As far as I understood Roland's statements, even that totally equivalent code produces different hash sizes, therefore maybe different strength.
However, what I don't understand at all is that both batch files begin with 'java', which I interpret as a program called 'java' is invoked and this program uses the jar file as an input. If that 'java' program is different when 32-bit and when 64-bit OS is used, maybe the strength of the engine will also be different.
On my 64-bit machine I have Program Files and Program Files(x86), under both of them there is a java directory. In your opinion which of the two will be invoked when the system starts the execution of the bat file with that 'java' instruction?
Gábor
On Java 64-bit you can test both the 32 & 64-bit Fischerle executables.
Java libraries aren't 32 or 64 bit, they are in Java ByteCode. So they can be executed on any JVM 64 or 32 the exact same way.
Silvian
- RolandoFurioso
- Posts: 55
- Joined: Sat Feb 22, 2014 6:29 pm
- Location: Frankfurt
Re: The final response ! -:)
Hi Gabor,
which Java version will be employed depends upon the setting of some environment variables of your operating system. Generally speaking, there is a variable called $PATH or so that specifies a list of directories and thus determines the order in which they are searched for a program with name java. The first one that is found will then be employed to run Fischerle.
It is, however, possible to override the outcome of this default search procedure by simply specifying the complete path of the java version. That is: edit the .bat files and specify the complete paths of the Java versions to be used, depending upon the location of your jres, this might look as follows:
C:\Program Files\Java\jre7\bin\java -Xms1400m -Xmx1400m -XX:+UseParallelGC -jar "dist\Fischerle.jar" uci
... and likewise for the 32 bit version:
C:\Program Files (x86)\Java\jre7\bin\java -Xms1400m -Xmx1400m -XX:+UseParallelGC -jar "dist\Fischerle.jar" uci
It might be necessary to include the paths into quotes ("..." or so) since they contain blanks.
If you'd like to employ the .exe starters instead, you'd have to recompile them from the changed .bat files.
All the best
Roland
which Java version will be employed depends upon the setting of some environment variables of your operating system. Generally speaking, there is a variable called $PATH or so that specifies a list of directories and thus determines the order in which they are searched for a program with name java. The first one that is found will then be employed to run Fischerle.
It is, however, possible to override the outcome of this default search procedure by simply specifying the complete path of the java version. That is: edit the .bat files and specify the complete paths of the Java versions to be used, depending upon the location of your jres, this might look as follows:
C:\Program Files\Java\jre7\bin\java -Xms1400m -Xmx1400m -XX:+UseParallelGC -jar "dist\Fischerle.jar" uci
... and likewise for the 32 bit version:
C:\Program Files (x86)\Java\jre7\bin\java -Xms1400m -Xmx1400m -XX:+UseParallelGC -jar "dist\Fischerle.jar" uci
It might be necessary to include the paths into quotes ("..." or so) since they contain blanks.
If you'd like to employ the .exe starters instead, you'd have to recompile them from the changed .bat files.
All the best
Roland
Re: The final response ! -:)
Thank you very much, Roland.RolandoFurioso wrote:Hi Gabor,
which Java version will be employed depends upon the setting of some environment variables of your operating system. Generally speaking, there is a variable called $PATH or so that specifies a list of directories and thus determines the order in which they are searched for a program with name java. The first one that is found will then be employed to run Fischerle.
It is, however, possible to override the outcome of this default search procedure by simply specifying the complete path of the java version. That is: edit the .bat files and specify the complete paths of the Java versions to be used, depending upon the location of your jres, this might look as follows:
C:\Program Files\Java\jre7\bin\java -Xms1400m -Xmx1400m -XX:+UseParallelGC -jar "dist\Fischerle.jar" uci
... and likewise for the 32 bit version:
C:\Program Files (x86)\Java\jre7\bin\java -Xms1400m -Xmx1400m -XX:+UseParallelGC -jar "dist\Fischerle.jar" uci
It might be necessary to include the paths into quotes ("..." or so) since they contain blanks.
If you'd like to employ the .exe starters instead, you'd have to recompile them from the changed .bat files.
All the best
Roland
Gabor Szots
CCRL testing group
CCRL testing group

