V E C T O R - C O N N E C T I O N ================================= - BUGS - 'What's up, doc?' -- Bugs Bunny. Known Bugs and Problems: ======================== ------------------------------------------------------------------------ There is a lot of confusion on the PCB and in the manual about the numbering scheme of the ports. I prefer (and I will use, if not other marked) the Commodore counting as used in the OpenDevice call (or in the 'Unit' Parameters of all Communication software). So the ports are called 0, 1, 2 and 3. The count begins with '0'. However, on the PCB, the counting starts with '1', so they're called '1', '2', '3', '4'. Yes, this is confusing. In fact, it was so confusing that I couldn't find a bug for quite a while because I misunderstood a bug report. =:-( I will in all documentation files *always* start counting with '0'. (I'm a computer science major, not an business major :-) ). ------------------------------------------------------------------------ On *all* PCB revisions up to and including 2.7, on port '2' (this one is labeled '3' on the PCB, but it is '2' in the OpenDevice call), the signal lines for 'DSR' and 'CD' are swapped. The device supplied in this software release knows about this and fixes this problem with software. If you get a PCB of release 2.8 or above, you can *not* use this software release. Look out for a newer release in the support boxes (See below). ------------------------------------------------------------------------ In some very rare (1:100) cases, the device can misjudge the clock speed of a board and take a 'turbo' (having an 7.2328 MHz crystal) for an 'normal' (having an 3.6864 MHz crystal) board. This will give you baud rate mismatches. You can solve this problem with closing all device units and removing the device with 'avail flush'. This bug is well known and will be removed in a future release. Please do not report it. ------------------------------------------------------------------------ Due to their nature, transfer rates of 76800 and 115200 bps are supported only on boards which have an 7.2328 MHz crystal installed. However, there is no warranty for the reliability and stability of these transfer rates as the serial chips are overclocked beyond their normal operating ranges when using these baud rates. ------------------------------------------------------------------------ Unlike other serial devices, the vectorser.device rejects all serial requests that are bigger than the set 'Receive Buffer'. These requests are rejected with 'Error 4', that is 'BuffError' from devices/serial.h. If your program returns requests immediately with 'Error 4', just try a bigger buffer setting in the VectorSer prefs program. ------------------------------------------------------------------------ The well known GiftWare Program 'Term' by Olaf Barthel ignores the 'BufferSize' setting in the serial panel in versions up to 3.4. You must set the BufferSize in the 'VectorSer' program if e.g. the xprzymodem.library gives you the 'Error 4' messages. This bug is known and confirmed by Olaf and it will be fixed in later releases. ------------------------------------------------------------------------ There may be a problem with some 3rd Party Zorro II and III boards (e.g. the Fastlane Z3 SCSI II Hostadapter). Most of these problems can be cured by cutting the PCB line to Pin 66 (DTACK) on the Vector Connection I/O board. ------------------------------------------------------------------------ Known Compatibility risks: ========================== There is no warranty if you: - use Programs written in 'GFA Basic'. - use the 'Multiterm BTX program'. This software was not written according to the Commodore Amiga programming guidelines. - use the Merlin Graphics board without the Hardware fixes from ProDev This hardware was not designed according to the Commodore Amiga Bus design specifications. If you have a GVP Harddisk controller, please use the latest available software release for this board. New Bugs (not mentioned in the section above): ============================================== So you found a bug? Fine. Report it to us! If you don't report it, we can't fix it. Please use the form below: --------------------------- cut --------------------------- 1) Your computer: Computer (e.g. Amiga 3000): _____________________________ OS-Version (e.g. 37.175): _____________________________ CPU installed (e.g. 68030): _____________________________ Board Revision (e.g. 6.2): _____________________________ Other Boards installed: _____________________________ _____________________________ _____________________________ _____________________________ _____________________________ 2) The board: Type (e.g. Vector Connection): _____________________________ Software Revision (e.g. 2.0): _____________________________ Board Revision (e.g. 2.7): _____________________________ 3) Your address: Name: _____________________________ Street: _____________________________ Address: _____________________________ Country: _____________________________ Telephone: _____________________________ Fax: _____________________________ EMail (UseNet Notation please): _____________@_______________ 3) Your software: Software which showed problems: _____________________________ Version: _____________________________ 4) Your problem (Please state it in German or English. Feel free to include Enforcer Hits, Logs from your software, GIF or IFF pictures of problems etc): --------------------------- cut --------------------------- Please fill out this form and FAX it to the following phone number: +49 (Germany) 221 / 369065 (HK Computer Cologne) Please include a line 'ATTENTION: Mr. Scholz' in the Fax. You can also send it via regular Mail to HK Computer Vector Connection Support Hoeniger Weg 220 D-50969 Koeln Germany Support BBS =========== There are two support BBSes, where you can find the latest releases of the Vector Connection Software. QUASAR BBS: +49-221-721633 HK SUPPORT BBS: +49-221-369024 Both are in Germany. AmiNet ====== Beginning with V 2.1 I will start to upload the software distribution to the AmiNet ftp-servers. Please see the 'README.AMINET' File.