Chindi
Known Bugs
- Transfer resuming does not work.
FIXED (2002-05-15)
- When connected to the server through localhost, transfers will not work.
- The server now prints stacktraces on every transfer that fails; this is not a bug,
the error is handled correctly. This has been added to debug server-to-client transfers
that fail with no apparent reason. If you get an unexplained server-to-client transfer error
please capture and send the stacktrace to us via the comment submissions form.
- The Windows XP start menu flickers when the server or client is running.
This is possibly not a bug in Chindi, but a conflict between the Java API repaint code
and Windows XP.
- You cannot use filenames containing spaces.
FIXED (2002-02-06)
- On some linux systems the server will not find the address
of the local host. Make sure /etc/hosts points to your IP.
- If you change the CODEC the next user who logs in will still use the old one.
The second connection will get the new CODEC. The problem has been identified and ignored.
- The horizontal scrollbar in the file panel acts somewhat randomly when the window is small.
- If the connection is closed forcibly transfer jobs will remain in the queue and cannot
be deleted.
- The scribbleboard generated an ArrayIndexOutOfBoundsException. This is probably due to a
bug in HypersonicSQL not being capable of handling ORDER BY expressions. The problem has been
circumvented by not ordering the scribbleboard. One-liners should still be in order if the
database doesn't do anything funny.
- Transfer jobs may be incorrectly placed in Win98 (not on XP or X-Windows).
- An exception is cast upon disconnect from the server. Bug has been located.
FIXED (2002-02-07)
- 'list [noslashdirectory]' will work on Windows and render the ".."-button inoperable.
FIXED (2002-02-06)
Planned Changes
- Enable server option that controls which ports are used for transfer connections.
Useful if you want to set up port forwarding on a IP-MASQ server.
To use this feature, edit the server.transferport.min/max values to the range of
transfer ports you want to use. 3-4 ports is probably sufficient, since the ports
are only used for (max) the number of seconds specified by server.transferSocketTimeout setting.
If your server is behind a masquerading router, you also need to set the server.transferip
setting to the ip of your router.
DONE (2002-02-06)
- Support for proxys and firewalls.
- Confirm box on "Remove".
- Plug-in type CODECs