>
>Ok, to do this you'd need two pieces:
>
>1: A device driver to provide the simulated serial ports. To do this you'd
>need to get the DDK (device driver kit) from Microsoft and spend quite a
>bit of time figuring it out. Non-trivial to say the least. This driver
>could possibly directly access the real COM port, but you'd probably be
>better off having it work with:
>
>2: An application (or NT service) that reads the data from the real COM
>port and hands it off to the device driver (via a private API) to be sent
>to fake COM ports and vice versa.

Hmm.. I seem doomed.

I don't even know anyone who can write windows device drivers.

The original theory was that the application I designed this for, would put
in a lower layer that would handle this, but it's not happening.

--
Dave's Engineering Page: http://www.dvanhorn.org
Where's dave? http://www.findu.com/cgi-bin/find.cgi?kc6ete-9

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.