This article is from the Programming VCOMM FAQ, by email@example.com (Taed Nelson) with numerous contributions by others.
[Contributed by Taed Nelson (firstname.lastname@example.org).]
It is reasonable for a VCOMM port driver to have no logical configuration
resources at all. This can occur since the port driver may communicate with
another driver, such as a network driver, to virtualize that as a COM port.
The port driver would then have no resources of its own.
But this leads to a problem. The documentation states (in the VCOMM Device
Initialization section), "[VCOMM] assigns a PortName to the device in its
hardware key, if its devnode contains system resources." Thus, without
resources, we don't get a port name, such as COM5. And without a port name,
we have discovered, we are not recognized by Dial-Up Networking or UNIMODEM.
These are all required functionalities for any port driver.
The only solution at this point is to edit the Registry and add PortName and
FriendlyName entries by hand. It is possible to hard-code the PortName and
FriendlyName (but not Description) in the port.inf file so that no
hand-editing is required. The place to do the editing is