John
Wed Apr 27 09:13:42 CDT 2005
The goal is to allow "many" commercial existing programs that were designed
to work with a HAM radio connected to a local com port be able to
communicate to a HAM radio on a different computer via TCP/IP etc. The idea
is not to have do anything to whatever software a HAM operator now has, just
extend the way it connects to include a Virtual com port so the radio can be
located somewhere else (down stairs, Ham shack, across town, etc).
So the existing programs would just select the new virtual com port instead
of their current local com port and everything else happens magically for
them.
John
"Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
news:C8FCE2BB-8A08-4B66-81EA-743992C29B1A@microsoft.com...
> Well I'm not sure that *any* driver (especially virtual com port) is a
best
> and fastest way to do this.
> if you have sources of that s/w, try to make it working over a normal
> network client/server design, or maybe even a web service (ha ha ha !)
>
> --PA
>
> "John Long" wrote:
> > I've setup a reading room at the house HaHaHa
> > No hurry on this so I am trying to make it as much "fun" as possible.
> >
> > I am looking at developing a virtual com port to extend the front end
> > interfaces of exciting (old fashion) Amateur Radio Software. Yes HAM
gear
> > talks to the computer using 1200 / 9600 baud com ports. Since the
hardware
> > if fixed I am looking at extending the usefulness by use of virtual
drivers
> > so a program on one Computer and talk to a HAM device connected to the
com
> > port of a different computer. This way the existing HAM software and
the
> > existing HAM radios do not need to be modified.
> >
> > After I complete the virtual com port project I get to do it all over
again
> > with sound cards. HaHaHa
> >
> > If you can suggest any ways of jump-starting the project, please feel
free
> > to suggest them.
> >
> >
> > Thanks,
> > John
> >
> >
> >
> >
> > "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
> > news:362F88F3-D93A-401E-A402-9D3DE0CB1E31@microsoft.com...
> > > Hi,
> > > First of all you need to determine which type your driver belongs to.
> > > Is it going to be a virtual NDIS miniport, or NDIS IM or something
else.
> > > Or you can do all in usermode.
> > > If you still need a driver, read DDK starter how-tos.
> > > With DDK, Visual Studio is just an optional text editor. DDK has it's
own
> > > compiler,
> > > and you *must* use that.
> > >
> > > Good luck
> > > --PA
> > >
> > > "John Long" wrote:
> > > > Thanks for the replys.
> > > >
> > > > I'm one ot those types that likes to get everything lined up and
then
> > jump
> > > > in over my head ;-) .....
> > > >
> > > > Besides, this will keep me of the streets for the next 6
months......
> > > >
> > > >
> > > > John
> > > >
> > > >
> > > >
> > > > "John Long" <john@thelongs.us> wrote in message
> > > > news:%23XKh0vmSFHA.3236@tk2msftngp13.phx.gbl...
> > > > > I am new to the DDK.
> > > > > I am going to develope a simple virtual device driver for a Ham
Radio
> > > > > progect.
> > > > >
> > > > > What tools do I need?
> > > > > I have Visual Studio Pro 2003 & I just received the DDK from
> > Microsoft.
> > > > >
> > > > > I noticed that I should be developing in C++.
> > > > > So do I need VS Pro 6.0 for C++ or can I use the Standard VS
C++
> > 6.0,
> > > > any
> > > > > older versiond of VS C++, or any way to use the C++ complier in
the VS
> > Pro
> > > > > .NET versions?
> > > > >
> > > > > I read where some people do development in a good IDE and do unit
> > testing
> > > > > there and then do the final compiling and testing with VS Pro C++
6.0.
> > So
> > > > I
> > > > > don't go out and purchase the wrong thing I am oppen to
sugestions.
> > > > >
> > > > > Since I may be selling the final product, I wish to stay legal.
> > > > >
> > > > >
> > > > >
> > > > > Thanks for any help.
> > > > >
> > > > > John Long
> > > > > Salt Lake City, Utah USA
> > > > > john@thelongs.us
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >