V
Vinay6663
Guest
Hi,
I have developed a Windows Virtual COM Port driver based on UMDF 2.15. I am able to open the COM port via some of the well known terminals like Putty, Hyperterminal, Tera-Term, CoolTerm, RealTerm and XCTU. But if I try to open the terminal through some of the terminals like SerialMon and YAT I will get the following error.
The given port name does not start with COM/com or does not resolve to a valid serial port.
Parameter name: portName
I have also checked in Windows Registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ROOT\PORTS that whether the the Virtual COM port is registered properly or not. Under Device parameters I could able to see a key PortName with COM port number.
My questions are,
1) If other terminals are able to open the port then what is the problem with these terminals?
2) Is the port name key is case sensitive? The error I am getting in these terminals has 'portName' whereas the key registered on the windows registry has 'PortName' with p as upper case. Could it be a problem? I changed some code in driver after creating symbolic link to change the key name to lower case p. But It did not work.
3) Since it is a Virtual Port those terminals are not able to open it?? Do they support only physical port??
Please help me to solve this issue.
Continue reading...
I have developed a Windows Virtual COM Port driver based on UMDF 2.15. I am able to open the COM port via some of the well known terminals like Putty, Hyperterminal, Tera-Term, CoolTerm, RealTerm and XCTU. But if I try to open the terminal through some of the terminals like SerialMon and YAT I will get the following error.
The given port name does not start with COM/com or does not resolve to a valid serial port.
Parameter name: portName
I have also checked in Windows Registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ROOT\PORTS that whether the the Virtual COM port is registered properly or not. Under Device parameters I could able to see a key PortName with COM port number.
My questions are,
1) If other terminals are able to open the port then what is the problem with these terminals?
2) Is the port name key is case sensitive? The error I am getting in these terminals has 'portName' whereas the key registered on the windows registry has 'PortName' with p as upper case. Could it be a problem? I changed some code in driver after creating symbolic link to change the key name to lower case p. But It did not work.
3) Since it is a Virtual Port those terminals are not able to open it?? Do they support only physical port??
Please help me to solve this issue.
Continue reading...