Comments on: Serial Port ActiveX Control 3.0 – a Representative of New Generation Tools to Fully Manage Serial Ports http://blog.eltima.com/2007/07/serial-port-activex-control-30-%e2%80%93-a-representative-of-new-generation-tools-to-fully-manage-serial-ports.html We provide you with newly updates, announcements and useful tips on software Thu, 19 Nov 2009 10:03:35 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: alex.taylor http://blog.eltima.com/2007/07/serial-port-activex-control-30-%e2%80%93-a-representative-of-new-generation-tools-to-fully-manage-serial-ports.html/comment-page-1#comment-8445 alex.taylor Mon, 27 Apr 2009 08:39:15 +0000 http://blog.eltima.com/2007/07/serial-port-activex-control-30-%e2%80%93-a-representative-of-new-generation-tools-to-fully-manage-serial-ports.html#comment-8445 @ Victor - Please, be informed that most commonly COM ports on the standard personal computers do not have an output buffer. That is why OutBufferSize property always returns 0 (zero). This was confirmed by multiple tests and results from other users. @ Victor -
Please, be informed that most commonly COM ports on the standard personal computers do not have an output buffer. That is why OutBufferSize property always returns 0 (zero). This was confirmed by multiple tests and results from other users.

]]> By: Victor http://blog.eltima.com/2007/07/serial-port-activex-control-30-%e2%80%93-a-representative-of-new-generation-tools-to-fully-manage-serial-ports.html/comment-page-1#comment-8443 Victor Sun, 26 Apr 2009 20:32:51 +0000 http://blog.eltima.com/2007/07/serial-port-activex-control-30-%e2%80%93-a-representative-of-new-generation-tools-to-fully-manage-serial-ports.html#comment-8443 I just tried to read the OutBuffSize property after opening the port. It always returns 0. I tried to set it (to 1024) and it still returned zero. I thought this was fixed on 3.0.0.143. Thanks, Victor I just tried to read the OutBuffSize property after opening the port. It always returns 0. I tried to set it (to 1024) and it still returned zero. I thought this was fixed on 3.0.0.143.

Thanks, Victor

]]>