Impact technologies Version Française Version Française  Versión española Versión española  Versione italiana Versione italiana  Contact
Home / Support / Multiports / FAQ






Technical Support
Téléphone :
(33) 1 64 86 29 21
e-mail : support@itechno.com

Afer Sales Services
Phone:
(33) 1 64 86 29 23
e-mail: sav@itechno.com
FAQ
The Fitwin serial ports are opened correctly, but there is no communication with the peripheral devices.

The problem mainly occurs with ISA cards (FitwinPRO, FitPass) and in most cases, it is due to the interrupt used, which is not suitable either because it is in conflict with another peripheral device or it is not managed correctly by the system (particularly interrupt 9).
My application cannot access (or see) the serial ports beyond COM10.

You must use a specific syntax: \\.\COM10
On Windows 95 (or Windows 98) systems, my application cannot open the FitwinISA ports.

This is a known bug (in version 2.5); it has been corrected from version 2.6
I have just installed a Fitclip card via CFPC on Twin Server 2.2a, but the channels declared from the second module do not function.

It is a module used by CFPC (CFPORT-XP) that is at fault. This problem is corrected in Twin Server 2.2b. Otherwise, you must apply the update patch diskette for Twin Server 2.2a
My FitCom card, which works correctly in a small Pentium server on OS/2, is not recognized on a faster system (Pentium II or III).

Obtain a driver that is more recent (from 1.8.0) and FitCom will be correctly initialized on high-speed systems.
I have connected Axel Iris Platine terminals on FitClip on a Twin Server system, but the display quickly becomes anarchistic! (hexadecimal).

This problem is corrected by downgrading the Axterm screen controller version (1.3a or less) or disabling the automatic TCP/IP protocol option (if this option is available) in the terminal SETUP menu.
After installing a FitwinPCI4 card on a NT system, the event log indicates that the FitwinPCI driver could not be started.

There are two possible reasons for this problem: on some systems, the OS plug and play installed option in the setup menu prevents the driver from starting. Consequently, you need only disable this option (Windows NT4 is not Plug and Play). On systems including more than one PCI bus, use version 1.3 or later (you must remove the current driver via the Add/Remove Program utility prior to installing the new version.
Printing is extremely slow on printers connected to terminals on Twin Server. How can I speed it up ?

This problem occurs in some cases with the printing double flow mode. The only known way of obtaining a decent printing speed is to break the double flow string, by using controllers (screen or multi-channel card) that do not support this feature (contact us for card controller versions that do not manage the double flow).
When I switch off my modem or terminal connected to Fitwin, Windows freezes.

This problem was identified on certain series of our cards, particularly those involving UARTS 16C554 revision BC. The problem is due to poor break management and is corrected from Fitwin driver version 2.6.
On Linux systems, the kernel relinking process is not completed (error message on serial.c).

FitwinPCI has two distinct drivers for Linux. For Linux distributions of kernel version 2.0.x, you must use the fitwinPCI driver version 1.0. For more recent Linux distributions (Kernel 2.2.x), you must use version 1.2
On Windows 95 (or Windows 98), the serial ports are displayed as unknown peripheral devices in the peripheral manager.

This problem is due to the fact that the serial ports are incorrectly listed on some systems. The problem is corrected from driver version 1.2.3