Insert an intermediate driver on the top of the serial port driver.

All,

In WinCE, you can install an intermediate driver on the top of the NDIS
miniport driver. Can we do the similar thing for serial port driver?

Paul
Thu Nov 01 09:22:36 PDT 2007

No, not exactly. You can imagine a driver, though, that would create a
virtual serial port, COM7, say, and open, inside that driver, COM1 and do
something with it. What are you trying to achieve (as opposed to how)?

Paul T.

"Angie" <kimojolin@yahoo.com> wrote in message
news:OXk5ebCHIHA.3980@TK2MSFTNGP03.phx.gbl...
> All,
>
> In WinCE, you can install an intermediate driver on the top of the NDIS
> miniport driver. Can we do the similar thing for serial port driver?
>
>

Angie
Thu Nov 01 11:04:17 PDT 2007

What I tried to do is to intercept the data from a physical serial port, for
instance COM1. If I install a virtual COM driver, I cannot monitor or
intercept the data comming from a COM device. Isn't it true?

"Paul G. Tobey [eMVP]" wrote in message news:e5ES1MKHIHA.4112@TK2MSFTNGP05.phx.gbl...
> No, not exactly. You can imagine a driver, though, that would create a
> virtual serial port, COM7, say, and open, inside that driver, COM1 and do
> something with it. What are you trying to achieve (as opposed to how)?
>
> Paul T.
>
> "Angie" <kimojolin@yahoo.com> wrote in message
> news:OXk5ebCHIHA.3980@TK2MSFTNGP03.phx.gbl...
>> All,
>>
>> In WinCE, you can install an intermediate driver on the top of the
>> NDIS miniport driver. Can we do the similar thing for serial port driver?
>>
>>
>
>

Paul
Thu Nov 01 11:19:00 PDT 2007

You could replace the driver for some particular port with your own, set up
the driver for real hardware to actually manage some other port name (port
names have *nothing* to do with actual base address or anything else; COM1
does not imply a particular base address, for example). So, after changing
the registry, you are COM1 and the real serial port is COM7 and internally
to your driver you open and use COM7 to do the actual I/O.

Paul T.

"Angie" <kimojolin@yahoo.com> wrote in message
news:OoYTfGLHIHA.3600@TK2MSFTNGP06.phx.gbl...
> What I tried to do is to intercept the data from a physical serial port,
> for instance COM1. If I install a virtual COM driver, I cannot monitor or
> intercept the data comming from a COM device. Isn't it true?
>
>
> "Paul G. Tobey [eMVP]" com> wrote in message news:e5ES1MKHIHA.4112@TK2MSFTNGP05.phx.gbl...
>> No, not exactly. You can imagine a driver, though, that would create a
>> virtual serial port, COM7, say, and open, inside that driver, COM1 and do
>> something with it. What are you trying to achieve (as opposed to how)?
>>
>> Paul T.
>>
>> "Angie" <kimojolin@yahoo.com> wrote in message
>> news:OXk5ebCHIHA.3980@TK2MSFTNGP03.phx.gbl...
>>> All,
>>>
>>> In WinCE, you can install an intermediate driver on the top of the
>>> NDIS miniport driver. Can we do the similar thing for serial port
>>> driver?
>>>
>>>
>>
>>
>
>

Angie
Thu Nov 01 14:21:53 PDT 2007

Thanks. I got your idea. As far as I know, a driver for WM 5.0 must be
signed if the driver is loaded when system is booted. However, if I load a
driver from an application, the driver does not need to be signed. Am I
right?

"Paul G. Tobey [eMVP]" wrote in message news:%23OzS4NLHIHA.284@TK2MSFTNGP02.phx.gbl...
> You could replace the driver for some particular port with your own, set
> up the driver for real hardware to actually manage some other port name
> (port names have *nothing* to do with actual base address or anything
> else; COM1 does not imply a particular base address, for example). So,
> after changing the registry, you are COM1 and the real serial port is COM7
> and internally to your driver you open and use COM7 to do the actual I/O.
>
> Paul T.
>
> "Angie" <kimojolin@yahoo.com> wrote in message
> news:OoYTfGLHIHA.3600@TK2MSFTNGP06.phx.gbl...
>> What I tried to do is to intercept the data from a physical serial port,
>> for instance COM1. If I install a virtual COM driver, I cannot monitor or
>> intercept the data comming from a COM device. Isn't it true?
>>
>>
>> "Paul G. Tobey [eMVP]" > DOT com> wrote in message news:e5ES1MKHIHA.4112@TK2MSFTNGP05.phx.gbl...
>>> No, not exactly. You can imagine a driver, though, that would create a
>>> virtual serial port, COM7, say, and open, inside that driver, COM1 and
>>> do something with it. What are you trying to achieve (as opposed to
>>> how)?
>>>
>>> Paul T.
>>>
>>> "Angie" <kimojolin@yahoo.com> wrote in message
>>> news:OXk5ebCHIHA.3980@TK2MSFTNGP03.phx.gbl...
>>>> All,
>>>>
>>>> In WinCE, you can install an intermediate driver on the top of the
>>>> NDIS miniport driver. Can we do the similar thing for serial port
>>>> driver?
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Paul
Thu Nov 01 14:52:20 PDT 2007

I am not a WM expert. That's not the way I would have done it, probably, if
I were them, but who knows. It's pretty easy to fake up a driver really
quick and see what happens.

Paul T.

"Angie" <kimojolin@yahoo.com> wrote in message
news:eZ3R50MHIHA.3768@TK2MSFTNGP06.phx.gbl...
> Thanks. I got your idea. As far as I know, a driver for WM 5.0 must be
> signed if the driver is loaded when system is booted. However, if I load a
> driver from an application, the driver does not need to be signed. Am I
> right?
>
>
>
> "Paul G. Tobey [eMVP]" com> wrote in message news:%23OzS4NLHIHA.284@TK2MSFTNGP02.phx.gbl...
>> You could replace the driver for some particular port with your own, set
>> up the driver for real hardware to actually manage some other port name
>> (port names have *nothing* to do with actual base address or anything
>> else; COM1 does not imply a particular base address, for example). So,
>> after changing the registry, you are COM1 and the real serial port is
>> COM7 and internally to your driver you open and use COM7 to do the actual
>> I/O.
>>
>> Paul T.
>>
>> "Angie" <kimojolin@yahoo.com> wrote in message
>> news:OoYTfGLHIHA.3600@TK2MSFTNGP06.phx.gbl...
>>> What I tried to do is to intercept the data from a physical serial port,
>>> for instance COM1. If I install a virtual COM driver, I cannot monitor
>>> or intercept the data comming from a COM device. Isn't it true?
>>>
>>>
>>> "Paul G. Tobey [eMVP]" >> DOT com> wrote in message news:e5ES1MKHIHA.4112@TK2MSFTNGP05.phx.gbl...
>>>> No, not exactly. You can imagine a driver, though, that would create a
>>>> virtual serial port, COM7, say, and open, inside that driver, COM1 and
>>>> do something with it. What are you trying to achieve (as opposed to
>>>> how)?
>>>>
>>>> Paul T.
>>>>
>>>> "Angie" <kimojolin@yahoo.com> wrote in message
>>>> news:OXk5ebCHIHA.3980@TK2MSFTNGP03.phx.gbl...
>>>>> All,
>>>>>
>>>>> In WinCE, you can install an intermediate driver on the top of the
>>>>> NDIS miniport driver. Can we do the similar thing for serial port
>>>>> driver?
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

PatrickSears
Thu Nov 08 12:29:02 PST 2007

Angie,

Yes, you're right. In fact there's an example of how to do what it sounds
like you're asking at Code Project:

http://www.codeproject.com/useritems/DemoDriver.asp

Even includes instructions on how to sign for WM5.

Hope this helps.
Patrick

"Angie" wrote:

> Thanks. I got your idea. As far as I know, a driver for WM 5.0 must be
> signed if the driver is loaded when system is booted. However, if I load a
> driver from an application, the driver does not need to be signed. Am I
> right?
>
>
>
> "Paul G. Tobey [eMVP]" com> wrote in message news:%23OzS4NLHIHA.284@TK2MSFTNGP02.phx.gbl...
> > You could replace the driver for some particular port with your own, set
> > up the driver for real hardware to actually manage some other port name
> > (port names have *nothing* to do with actual base address or anything
> > else; COM1 does not imply a particular base address, for example). So,
> > after changing the registry, you are COM1 and the real serial port is COM7
> > and internally to your driver you open and use COM7 to do the actual I/O.
> >
> > Paul T.
> >
> > "Angie" <kimojolin@yahoo.com> wrote in message
> > news:OoYTfGLHIHA.3600@TK2MSFTNGP06.phx.gbl...
> >> What I tried to do is to intercept the data from a physical serial port,
> >> for instance COM1. If I install a virtual COM driver, I cannot monitor or
> >> intercept the data comming from a COM device. Isn't it true?
> >>
> >>
> >> "Paul G. Tobey [eMVP]" >> DOT com> wrote in message news:e5ES1MKHIHA.4112@TK2MSFTNGP05.phx.gbl...
> >>> No, not exactly. You can imagine a driver, though, that would create a
> >>> virtual serial port, COM7, say, and open, inside that driver, COM1 and
> >>> do something with it. What are you trying to achieve (as opposed to
> >>> how)?
> >>>
> >>> Paul T.
> >>>
> >>> "Angie" <kimojolin@yahoo.com> wrote in message
> >>> news:OXk5ebCHIHA.3980@TK2MSFTNGP03.phx.gbl...
> >>>> All,
> >>>>
> >>>> In WinCE, you can install an intermediate driver on the top of the
> >>>> NDIS miniport driver. Can we do the similar thing for serial port
> >>>> driver?
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>

Insert an intermediate driver on the top of the serial port driver.

Re: Insert an intermediate driver on the top of the serial port driver. by Paul

Re: Insert an intermediate driver on the top of the serial port driver. by Angie

Re: Insert an intermediate driver on the top of the serial port driver. by Paul

Re: Insert an intermediate driver on the top of the serial port driver. by Angie

Re: Insert an intermediate driver on the top of the serial port driver. by Paul

Re: Insert an intermediate driver on the top of the serial port dr by PatrickSears