Virtual Serial Port ActiveX Control - Frequently Asked Questions

1. My problem is the following: I'm sending 10000 bytes down the line and remote port receives just 8000.

   You must enable "Hardware Flow Control" option for both ports. To get more information about this problem please reffer to MSDN page (pay attention to "p" parameter). The other way to solve the problem is enabling baudrate emulation to decrease the speed.

2. I have registration key and OEM version of Virtual Serial Port ActiveX, what should I do next?
   You can register your VSP AX by using quiet registration (for OEM License users only) or simply launch any application, which uses VSP AX and enter your registration information there.
    
3. I have created COM10, however I cannot open it using my own application. What am I doing wrong?

   In order to open port COM10 and above, you must use the full system path to it, i.e. \\.\COM10 and so on.

4. How can I dynamically create virtual serial ports in C#? When I try to do it, I always get the error: "An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in mscorlib.dll
   Additional information: Catastrophic failure"

   To correctly create virtual serial ports you must follow these steps :

   1. Create a new instance: m_vsPort = new VSPortLib.VSPortClass();
   2. Initializate it by calling BeginInit()
   3. Add our control using AddRange()
   4. End initialization: EndInit()
   5. And now you can use ActiveX methods provided by our application

   For instance:

   AxVSPortLib.AxVSPort axVSPort3 = new AxVSPortLib.AxVSPort();
   ((System.ComponentModel.ISupportInitialize)(axVSPort3)).BeginInit();
   this.Controls.AddRange (new System.Windows.Forms.Control[] {axVSPort3}); 
   ((System.ComponentModel.ISupportInitialize)(axVSPort2)).EndInit(); 
   axVSPort3.CreatePort ("COM6"); 
   axVSPort3.Delete();
   

5. When I tried console example under Microsoft .net 2005 (project conversion is automatically done by .net 2005) in Debug configuration, I got some errors reported on .net output log when exiting: "First exception chance... Access violation". These errors didn't occur under Microsoft .net 2003...
   
   Our testers have reproduced the issue and have worked out a solution: applications using ActiveX Control must be built for 32-bit targets under Microsoft .net 2005.
   
   1. Open the 'Properties' page for your project.
   2. Select the 'Build' tab (alternatively it can be 'Compile' tab).
   3. In the 'General' section, click the 'Platform Target' dropdown list down arrow.
   4. Select 'x86'.
   5. Close the 'Properties' page.
   6. Rebuild the application.
    
6. I have found a bug in your component/program, how may I report about it?

   You may report it by sending email to support@eltima.com