serial driver

Hi all!

I’m writing virtual serial port driver. Originally the project was started as

WDM driver and it is almost done under Win2k. But Win98 uses different

communications driver architecture so no applications see port devices created

by WDM driver under Win98. So now I’m writing separate port driver vxd for 9x.

And my questions are:

  • Am I right in starting writing port driver vxd, or may be there is some other

way to make WDM driver work under Win98 (I dont have to support Win95). If

there IS a way to avoid writing port driver vxd, it would be great :))

  • When I install new ports (under Win98), my port driver vxd gets loaded and

called appropriatly when port is used by Win32 applications (that use MS Comm

ActiveX or applications that talk directly to communication API). BUT. If DOS

applications uses this port, my port driver NEVER GETS CALLED. It doesnt even

get loaded. I checked out that standard serial port driver (serial.vxd) doesnt

get loaded neither (when port in use by DOS app). What should I do to make my

port driver work with DOS apps too?

  • What is vcd.vxd? 95DDK says almost nothing about it. (I add registry entry

Contention = *vcd.vxd)

Thanks in advance,

Vladimir


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Your best bet for Win9x is to write a VCOMM port driver. vcd.vxd does a
number of things: It handles contention for serial port drivers between
virtual machines and sets up the virtualization of serial ports for DOS
virtual machines. A non-serial port VCOMM port driver will not be accessible
by a DOS VM because vcd.vxd does not setup virtualization for them. You will
need a something like TurboCom ViP from Pacific CommWare,
http://www.pacificommware.com, to do the virtualization for you. You could
also write your own custom vcd to do your virtualization, but that would
require digging into the internals of vcd.

Jim

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@chat.ru
Sent: Tuesday, August 21, 2001 5:36 AM
To: NT Developers Interest List
Subject: [ntdev] serial driver

Hi all!

I’m writing virtual serial port driver. Originally the project was started
as

WDM driver and it is almost done under Win2k. But Win98 uses different

communications driver architecture so no applications see port devices
created

by WDM driver under Win98. So now I’m writing separate port driver vxd for
9x.

And my questions are:

  • Am I right in starting writing port driver vxd, or may be there is some
    other

way to make WDM driver work under Win98 (I dont have to support Win95). If

there IS a way to avoid writing port driver vxd, it would be great :))

  • When I install new ports (under Win98), my port driver vxd gets loaded and

called appropriatly when port is used by Win32 applications (that use MS
Comm

ActiveX or applications that talk directly to communication API). BUT. If
DOS

applications uses this port, my port driver NEVER GETS CALLED. It doesnt
even

get loaded. I checked out that standard serial port driver (serial.vxd)
doesnt

get loaded neither (when port in use by DOS app). What should I do to make
my

port driver work with DOS apps too?

  • What is vcd.vxd? 95DDK says almost nothing about it. (I add registry entry

Contention = *vcd.vxd)

Thanks in advance,

Vladimir


You are currently subscribed to ntdev as: xxxxx@youngendeavors.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com