if your hardware already has 'COM1:', then it will start at 'COM2:'), but that's easily overridden, so verify in the registry.įor examples of the driver implementations see the following locations on your PC (this assumes you've got Platform Builder - I think any version since about 3. Typically it will start at the first available port (i.e. After the mapping your application can open COM2, but it will actually use COM9. For example, they have created COM9 port but your application supports only this case you can use Advanced Virtual COM Port to map COM9 to COM1 (or COM2.COM4). How that driver will work depends on the hardware.ĪS to what the port name will be, that's up to the host driver's registry settings. Some serial to USB adapters or expansion cards do not allow users to change the serial port number they create. If it doesn't, then you need to write a host device driver to allow the USB system to communicate with this particular device. it has an FTDI or Prolific chipset in it)? If so, just install the right CE driver and you're set.

What kind of device is it? Does it act as a serial device already (e.g. Now if it's a CE 5.0 device and if it's a USB Host port then we get down to the USB device type and the OS drivers. If it's the port that you hoos the device to the PC through, then it's a client port and is not going to be able to accept a peripheral. USB has two 'modes' - Host and CLient - and they are different both physically and in software. Second, you have to verify what the 'USB port' is. Windows Mobile != Windows CE 5.0, so first you need to verify what your hardware is actually running.

Windows check usb virtual port numer