Version 2.1.1 Problems
The following list describes the known problems with Fixation 2.1.1:
- Copy and paste does not work in the console when running the Carbon version
of Fixation under OS X.
- Setting the background color to a color other than white may not work properly
in the text window.
- The Server prompt option is not currently implemented for the FICS.
- The last character of italicized colored text may get partially or wholly truncated
when the next line of text is displayed in the text window.
- Changing the server variables in the Preferences does not take effect
until the next logon.
- Changing the server prompt on the FICS will disable colored text until
you re-logon to the FICS with the new prompt.
- Setting the ptime variable on the FICS will cause unpredictable results.
As noted in the help file, interfaces such as Fixation will have problems.
- The separator line for the command entry field in the Engine communications
window may not displayed properly.
- When you run Fixation 2.x for the first time and you have Fixation 1.3 or
earlier installed, the preferences conversion will fail. However, a default
2.x preferences will be created. If you want to convert your 1.x preferences,
install 1.41 or
1.4 before running Fixation 2.x.
Version 2.1.1 Limitations
- Move validation is performed by the chess server. You can enable Fixation's
move validation logic by pressing Command-Z. However, Fixation's move
validation is currently incomplete and not fully tested; it may cause Fixation to crash.
- On the FICS, using the "bsetup" command shows an empty game board but is missing
the King piece in the column of pieces. As a workaround, you can enter "wk@e1" to
place a white King at e1.
- The "Save Game" command will not save the full list of moves if you observe a
game in progress.
- The "Save PGN" command is only implemented for the ICC.
- The Seek Graph and chess engines are not
supported for chess.net.
- The Seek Graph window layout cannot be changed.
-
Apple Game Sprockets is not supported. If you have a non-standard input device
that requires Game Sprockets in order to work properly, you may have problems
making moves.
- The Seek window is only supported for the ICC, FICS and USCL servers. The
Appearance extension must also be installed and enabled.
- Sounds are not user configurable, only whether they are played or not.
- The Accuclock protocol for chess.net is not supported. If you play games on chess.net,
your time will not be compensated for network lag.
- The ICC Free Trial is not supported in the Carbon version. If you want to
use a free trial account, you will need to use the Classic version of Fixation.
Reporting New Problems
Before reporting a problem, please check the following places to see if someone has
already reported the problem:
- the list above.
- select "Bugs & Suggestions" from the Info menu.
- messages in the
Fixation discussion group. You will need to be a member of the group before you can
read the messages.
When reporting a problem, please provide the following information:
- The full version number of Fixation (e.g. 2.1.1) you are having the problem
with. Note that for any problems reported for versions earlier than the currently
released version, my standard response will be to upgrade to the current
version first and check if the problem still occurs. For example, if you report
a problem with 2.0.4, I'm going to ask that you first upgrade to 2.1.1.
If you are not using the latest available version (i.e. 2.1.1), explain why.
- The type of Macintosh you are using (e.g. Power Mac 7300, G3, G4).
- The version of MacOS (8.x/9.x/X) or System 7.x you are running. If you are
using Classic mode of OS X, please note that as well.
- The version of Open Transport installed. You can find out what version you have by
selecting "TCP/IP Status" from the Info menu.
- The chess server(s) you are using when the problem occurs. Fixation does
some things differently depending on which chess server you are using. This is
especially important if you want me to try and reproduce the problem.
- A description of the problem. When describing the problem, please provide
me with as much information as you can. The more information that you can
provide, the better chance it gives me of reproducing the problem. If I can
reproduce the problem, there is a much greater chance of the problem
being fixed sooner rather than later (or not at all). Also state whether
you can reproduce the problem repeatedly.
You can summarize the above information if you wish in one line.
e.g. Env: Fixation 2.1.1, ICC, Mac OS 9.1, PM 7300
If Fixation quits unexpectedly and the Finder reports it as such, the perfect
assistance to me for reporting the problem is to install
MacsBug
and do a "stdlog" when MacsBug is invoked. Then email me (not to the group) the
log file. MacsBug is however, a programmer's tool and thus requires some
programming experience to make any sense out of using it (heck, even us
programmers have trouble using it sometimes!). Like I said, that would be
perfect for helping me but I don't expect most people to go that route. Crashes
under Mac OS X (not Classic mode) will be easier for obtaining the crash
information without the need for MacsBug.
NOTE: I cannot fix any problems for version 1.41 or earlier.
Please send your problem reports to the Fixation discussion group.
Revised: November 14, 2004