A way to split a com port into 2 or more virtual com ports (using virtual drivers). I realize that may be difficult, however, it would be extremely helpful in some cases. There currently are just not many options out there that accomplish this.
The batch files would be a nice addition, however, I'm not aware of any way to control com0com with the windows cmd prompt as it uses its own proprietary console interface that doesnt accept windows cmd line arguments as far as I know. hub4com is an extention to com0com that hooks many virtual pairs together in different ways uses windows cmdline interface though, but its kind of useless without com0com.
I will have to try uninstalling com0com again and documenting what I had to do better in order to give you a solid step by step way of getting it to work on windows 10. I've had some experience with windows 64bit and test signing that allowed me to get these drivers to work, in a nutshell heres what I had to do:
Use windows driver development tool kit to test sign the 64bit com0com driver.
Set computer into test mode (makes an annoying watermark appear).
Install com0com (the usual errors will occur and it will fail to load).
Manually uninstall any drivers com0com tryied to install during program installation.
Replace driver files located in program files folder with the new test signed ones.
I then ran the com0com GUI and added a virtual comport pair and everything seemed to work right.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can sign com0com and the installer.
I would make this available to donors to Realterm, and the original writer. (Donations pay for the signing key -thanks all you Donors)
Easy if it is an nsis installer, or you want to make an nsis installer script for it, I can run and sign it all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Com0Com is what you want:
https://sourceforge.net/projects/com0com/
note that for Realterm to talk to the port, you need to make the numbered vcps, not the named ones.
Thanks for your help! That works well ( - a lot of tinkering to get it to work with windows 10)
Could you whip up an html page I can add to site explaining what you had to do?
Alternatively document it here.
I was wondering if there should be some batch files for com0com in with the Realterm examples to help set it up. Is this a good idea?
The batch files would be a nice addition, however, I'm not aware of any way to control com0com with the windows cmd prompt as it uses its own proprietary console interface that doesnt accept windows cmd line arguments as far as I know. hub4com is an extention to com0com that hooks many virtual pairs together in different ways uses windows cmdline interface though, but its kind of useless without com0com.
I will have to try uninstalling com0com again and documenting what I had to do better in order to give you a solid step by step way of getting it to work on windows 10. I've had some experience with windows 64bit and test signing that allowed me to get these drivers to work, in a nutshell heres what I had to do:
Use windows driver development tool kit to test sign the 64bit com0com driver.
Set computer into test mode (makes an annoying watermark appear).
Install com0com (the usual errors will occur and it will fail to load).
Manually uninstall any drivers com0com tryied to install during program installation.
Replace driver files located in program files folder with the new test signed ones.
I then ran the com0com GUI and added a virtual comport pair and everything seemed to work right.
I can sign com0com and the installer.
I would make this available to donors to Realterm, and the original writer. (Donations pay for the signing key -thanks all you Donors)
Easy if it is an nsis installer, or you want to make an nsis installer script for it, I can run and sign it all.