Hi Dennis, should it be named Schooner 2.033 or SchoonerII 0.33 now?
(I see it is a complete rewrite and named Schooner II by yourself in 'Features' at your homepage)
Hi Dennis, should it be named Schooner 2.033 or SchoonerII 0.33 now?
(I see it is a complete rewrite and named Schooner II by yourself in 'Features' at your homepage)
Gabor Szots wrote: ↑Tue Oct 30, 2018 9:35 am
Thanks Denis. Could you please include the necessary dll files in the package?
Hello Gabor,
Could you list the dll files that your system reports are required?
The engine tested fine in Windows 7.
In Windows 10, "libwinpthread-1.dll" was reported to be missing. I can include this in the zip package if it is the only one missing. Maybe some other programmers might have some suggestions on how to compile POSIX without having to use to this dll.
The engine would not load from the Linux Fedora archive manager I have installed. However, I am not a regular Linux user and I do not know why it would not load.
Hi Dennis, should it be named Schooner 2.033 or SchoonerII 0.33 now?
(I see it is a complete rewrite and named Schooner II by yourself in 'Features' at your homepage)
Hello Guenther,
I am not sure what you mean. The names issued were:
The Schooner II is supposed to be an artistic Roman Numerals two (and not eleven), but with todays different non-serif fonts I suppose this is becoming confusing.
Since this was a complete re-write, I almost changed the name of the engine to something different. However, about 70% of the content of the engine still come from the previous version. The main difference is in the method of compilation using gcc, and in the simplification of the evaluator.
Gabor Szots wrote: ↑Tue Oct 30, 2018 9:35 am
Thanks Denis. Could you please include the necessary dll files in the package?
Hello Gabor,
Could you list the dll files that your system reports are required?
The engine tested fine in Windows 7.
In Windows 10, "libwinpthread-1.dll" was reported to be missing. I can include this in the zip package if it is the only one missing.
I think that is the only one missing although I cannot be sure because after the error message pops up and I click on OK,the engine exits. Usually, if an engine needs several dll's it displays all of them before exiting.
Gabor Szots wrote: ↑Tue Oct 30, 2018 9:35 am
Thanks Denis. Could you please include the necessary dll files in the package?
Hello Gabor,
Could you list the dll files that your system reports are required?
The engine tested fine in Windows 7.
In Windows 10, "libwinpthread-1.dll" was reported to be missing. I can include this in the zip package if it is the only one missing.
I think that is the only one missing although I cannot be sure because after the error message pops up and I click on OK,the engine exits. Usually, if an engine needs several dll's it displays all of them before exiting.
"libwinpthread-1.dll" now included in the zip file.