Yes, Stan, you are exactly right...it will support both vCOM to TCP/IP
and vCOM to vCOM without modification to the driver.  Basically I just
need to write the user mode TCP/IP server/listener.

73 de Phil N8VB

On 6/8/05, Stan Schretter <[EMAIL PROTECTED]> wrote:
> Thanks for the feedback.
> 
> Although I get lost in the details of the driver stuff, I think that Phil's
> concept seems like a great extension and generalization of the current
> virtual comm approach. If I read it correctly, it would support VComm<->TCP
> as well as the current VComm<->VComm approach.
> 
> Stan W4MQ
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Philip Covington
> Sent: Wednesday, June 08, 2005 1:30 PM
> To: n4hy
> Cc: Flex Radio
> Subject: Re: [Flexradio] Multiple Virtual Comm Ports
> 
> 
> The Lantronix redirector uses a user mode application (the TCP/IP
> part) that talks to its virtual com port driver via a custom file
> device I/O something like the IRCOMM2k serial to IR driver's IR device
> part.
> We should be able to come up with an equivalent scheme using the vCOM
> driver AS IS.  The user mode application (the TCP/IP part) will just
> open one of the virtual com ports in the pair that vCOM provides.
> 
> So you will have something like this:
> 
> PowerSDR on computer 1
> |
> COM3 <-- first vCOM virtual port on computer 1
> |
> COM4 <-- second vCOM virtual port on computer 1
> |
> TCP/IP user mode app on computer 1
> |
> INTERNET/WAN/LAN/LOCAL
> |
> TCP/IP user mode app on computer 2
> |
> COM4 <-- second vCOM virtual port on computer 2
> |
> COM3 <-- first vCOM virtual port on computer 2
> |
> MixW, HRD, BandMaster, DXLAB Commander, etc..
> 
> All open source of course...
> 
> 73 de Phil N8VB
> 
> 
> On 6/8/05, n4hy <[EMAIL PROTECTED]> wrote:
> > This is a misreading of both GPL and Flex policy.  Flex currently uses
> > proprietary code that
> > it cannot distribute source for.  The EZ USB code for the Ahti/Sami
> > device is handled this way
> > and it is delivered separately from the console.
> >
> > You may certainly install and use this utility in your computer and Flex
> > radio and its policies
> > have nothing to say on the matter.  What must be open source is your
> > code inside the console
> > that talks to it.
> >
> > That said,  I much prefer Phil's code/approach because we can extend it
> > AND we have
> > access to the software and we have an "interested" developer combined
> > with early
> > adopter.
> >
> > Bob
> >
> >
> >
> > Bob Tracy wrote:
> >
> > >Stan,
> > >
> > >Looks like a very interesting utility, unfortunately (after reading the
> > >legal stuff on their website) it is proprietary code and doesn't fit in
> with
> > >the open source philosophy of the SDR-1000.  Wish it were different since
> it
> > >looks like exactly what I need for a current project.
> > >
> > >
> > >73,
> > >
> > >Bob K5KDN
> > >
> > >
> > >
> > >_______________________________________________
> > >FlexRadio mailing list
> > >FlexRadio@flex-radio.biz
> > >http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
> > >
> > >
> > >
> >
> >
> > _______________________________________________
> > FlexRadio mailing list
> > FlexRadio@flex-radio.biz
> > http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
> >
> 
> _______________________________________________
> FlexRadio mailing list
> FlexRadio@flex-radio.biz
> http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
> 
> 
> _______________________________________________
> FlexRadio mailing list
> FlexRadio@flex-radio.biz
> http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
> 


-- 
Philip A Covington, N8VB
vHMI Automation, Inc.
http://www.vhmiautomation.com

Reply via email to