Recent changes to bugs

IrCOMM2K v2.0.0-beta3 does not honour min-turn-around time

Anonymous — Tue, 19 Sep 2006 12:32:49 -0000

From my observations it seems that IrCOMM2K
v2.0.0-beta3 is always using a minimum turn around time
of zero, resulting in transmission errors (peer might
miss the start of a packet and therefore ignore it,
causing packet retransmissions), especially for baud
rates of 115200 and 57600 bit/s.

Apparently a linux related patch in irlap.c
(v1.4->v1.5) seems to disable the use of additional
XBOF's to achieve the necessary min-turn-around time.
However for Windows there is no timer or anything in
exchange.

Another thing that makes me wonder is that irlap.c uses
10us as default min-turn-around time instead of 10ms as
specified in the IrLAP standard. Anyway right now the
min turn around is not applied anywhere.

(I hope i didnt miss anything in the code...)

Kerio Personal Firewall vs. IrCOMM2k

Jan Kiszka — Wed, 24 Sep 2003 23:32:02 -0000

Kerio Personal Firewall (tested with version 2.1.5) is
not compatible with IrCOMM2k version 2. As soon as
IrCOMM2k is installed, warning messages of the firewall
are constantly popping up. IrCOMM2k has to manipulate
parts of the networking framework of Windows in order
to take over the IrDA adapters. This manipulation is
obviously unexpected to Kerio and cause the firewall to
fail.

Currently I don't know how I can avoid this
interoperability problem. It seems that the work has to
be done by Kerio. I already submitted a support request
but got no response yet.

Windows XP hangup

Frédéric BERNARD — Thu, 24 Apr 2003 21:14:30 -0000

I posted a message on the Source Forge forum about it.

PsiWin is working.

I use an external IrDA transceiver connected by USB
(IRXpress USB IrDA Adapter).

I have installed IrCOMM2k ("irdainst.exe -i" command),
the virtual COM port ("ircomm2k.inf"), but not the
infrared device, as my IRXpress driver was installed and
properly working.

I also desactivated the automatic start of the infrared
monitor service.

It works ...

I have some problem when connected to Internet, via an
USB ADSL modem. The PC hangs, the only way out is
hard reset.

I had to add an hardware profile to desactivate some
drivers when connected to Internet (IRXpress USB IrDA
Adapter in USB controlers, IRXpress USB Infrared
Adapter in Infrared devices, and the virtual COM port in
ports)

I did not try alpha7 version ...

Thank you for your work.

Regards,

Frédéric BERNARD
fred.pa.bernard@infonie.fr
92400 COURBEVOIE
FRANCE

No IR Device Can Be Connected

Jan Kiszka — Fri, 07 Mar 2003 00:47:28 -0000

After reboot no IR device can be connected.
Applications which worked normally with previous
versions are now reporting troubles.

An already identified bug in ircomm2k.sys causes this
behavior. A corrected version of the alpha6 release
will come up soon. Until then a temporary workaround is
to disable and re-enable the virtual COM port in the
device manager after each reboot.

IrCOMM2k adds boot delay to Windows XP

Jan Kiszka — Sun, 16 Feb 2003 12:44:11 -0000

When IrCOMM2k is installed on Windows XP, the system takes about 30 s longer to boot.

This delay is caused by the MS-IrDA Forward adapter waiting for a connection with the IrDA2k protocol
driver. This bug should get fixed for the next release.

Psion Connection Breakdown

Jan Kiszka — Wed, 12 Feb 2003 22:49:12 -0000

While transfering large files the connection between
IrCOMM2k and Psion devices can break down occasionally.
Afterwards the Psion may not be able to reconnect again
(or even hang).

Difficulties in Connecting Psion PDAs

Jan Kiszka — Wed, 12 Feb 2003 22:44:52 -0000

The connection establishment between Psion PDAs and PCs
running the synchronization software Psiwin can fail.
Before Psiwin has been started the Windows displays a
tray icon indicating that the Psion is in range,
probably even the "connection established" symbol is shown.

The cause is that starting Psiwin switches to
IrCOMM2k's infrared protocol implementation cutting the
IR link between Windows and the Psion. The Psion fails
to drop this link completely and to allow a new link
with IrCOMM2k.

This bug may appear in conjunction with other IR
devices based on the EPOC operating system, too.

Multiprocessor Systems Freeze

Jan Kiszka — Wed, 12 Feb 2003 22:32:22 -0000

Windows freezes on multiprocessor system when trying to
use IrCOMM2k 2.0.0-alpha with various applications
(known: VieSie 1.94, Siemens XTND).

There are probably still some synchronization bugs in
the current version. It will be difficult to track down
this bug because no testing equipment (dual processor
system) is available at the moment.