🚀 go-pugleaf

What is it you are trying to do? Virtual COM ports would normally be OS 
drivers and not components.



"Thom A." <thoma@gmx.at> wrote in message 
news:4594aa0b$1@newsgroups.borland.com...
> Does anyone have an example on how to create a virtual serial COM port?
>
> I know there are shareware components for that, but they are extremely 
> expensive... :-(
>
>
> Thomas 

>>Does anyone have an example on how to create a virtual serial COM port?
>>
>>I know there are shareware components for that, but they are extremely 
>>expensive... :-(


> What is it you are trying to do? Virtual COM ports would normally be OS 
> drivers and not components.


Almost. My software would work like a driver. It would give a 
configurable number of programs the option to access a device by opening 
the respective number of virtual ports. It would handle incoming 
requests from the other programs and either forward them to the device, 
or respond itself.

Thom

Are the programs accessing the comport existing programs or are you writing 
them yourself?
Is access to the comports needed by several programs at the same time?

I have in the past used a null modem cable between two comports and then 
used the 1st port for an existing application using that comport and had my 
program listening on the 2nd comport and relaying the tx/rx data to/from a 
device connected to via TCP/IP.
However you would normally only allow a single connection to the 1st 
comport.

John




"Thom A." <thoma@gmx.at> wrote in message 
news:459ac9e9$1@newsgroups.borland.com...
>>>Does anyone have an example on how to create a virtual serial COM port?
>>>
>>>I know there are shareware components for that, but they are extremely 
>>>expensive... :-(
>
>
>> What is it you are trying to do? Virtual COM ports would normally be OS 
>> drivers and not components.
>
>
> Almost. My software would work like a driver. It would give a configurable 
> number of programs the option to access a device by opening the respective 
> number of virtual ports. It would handle incoming requests from the other 
> programs and either forward them to the device, or respond itself.
>
> Thom 

Hi John,


thank you very much for your suggestions, but workarounds are no 
options. I cannot force anyone to buy extra hardware, so that he/she can 
use my software!

Actually, there are douzens of programs that usually use a not very 
intelligent driver to use with the same device at the same time via 
serial connection. My program is much more sophisticated, and shall 
replace the driver. For this reason, it must provide the well-known 
interfaces, including (virtual) RS232 ports.


Thom

No worries Thom, then I could only suggest looking at the WINDDK and 
building your own driver to which your program then provides an interface to 
have some control or paying the money to get something that has already been 
done by a third party.

John


"Thom A." <thoma@gmx.at> wrote in message 
news:459ada35$1@newsgroups.borland.com...
> Hi John,
>
>
> thank you very much for your suggestions, but workarounds are no options. 
> I cannot force anyone to buy extra hardware, so that he/she can use my 
> software!
>
> Actually, there are douzens of programs that usually use a not very 
> intelligent driver to use with the same device at the same time via serial 
> connection. My program is much more sophisticated, and shall replace the 
> driver. For this reason, it must provide the well-known interfaces, 
> including (virtual) RS232 ports.
>
>
> Thom 

> No worries Thom, then I could only suggest looking at the WINDDK and 
> building your own driver to which your program


I don't want to build a driver, but a program that replaces the original 
driver. The program already exists. It's a normal EXE.

The question remains unresolved: How can my program create a virtual 
serial (RS232 / COM) port?

Thom