<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/tcp2com/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/tcp2com/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/tcp2com/bugs/</id><updated>2006-10-02T07:20:44Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>tcp2com breaks when com port disabled/re-enabled</title><link href="https://sourceforge.net/p/tcp2com/bugs/1/" rel="alternate"/><published>2006-10-02T07:20:44Z</published><updated>2006-10-02T07:20:44Z</updated><author><name>Ahti Legonkov</name><uri>https://sourceforge.net/u/leg0/</uri></author><id>https://sourceforge.netfd04b0adfe7f39998451e8567195d325c15d9456</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When installing tcp2com for a virtual COM port, there&lt;br /&gt;
is a problem when this COM port is removed and&lt;br /&gt;
recreated - the global hCom handle is invalidated after&lt;br /&gt;
the COM port si removed and it stays invalid after the&lt;br /&gt;
COM port is recreated. As a result of this no data is&lt;br /&gt;
transfered from COM to tcp.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>