DeviceIoctl Vs SerialComm API

NTDEV
1

Hi,

I have installed WDM based Virtual Serial Port Driver using CCPORT.SYS
support in Win 98 SE.

CreateFile(), CloseHandle() type of calls are working. DeviceIoControl()
calls are also working. But If I use SerialComm APIs like SetCommTimeout(),
the return value is 0, and the extended error is 6 (Invalid Handle).
Conttrol is not reaching my driver. At the same time if I issue DeviceIoctl
with code as IOCTL_SERIAL_SET_TIMEOUT, it is working and I am getting the
control.

Please help me.

Thanks
San Wind

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

2

Hello,

CreateFile(), CloseHandle() type of calls are working. DeviceIoControl()
calls are also working. But If I use SerialComm APIs like SetCommTimeout(),
the return value is 0, and the extended error is 6 (Invalid Handle).

what is your code in user mode? Maybe some things wrong and you use
not the right handle.

I have used for all my test’s the very old MTTTY demo application from MS
without problems.

When one device control works than all call must works.

elli

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

3

My guess is that the registry is not setup exactly right. I suggest using regmon to watch the registry accesses. Use it with a “standard” serial port then with your “Virtual” serial port.

Larry

-----Original Message-----
From: Mathias Ellinger [mailto:xxxxx@Ellisoft.de]
Sent: Wednesday, October 10, 2001 11:05 AM
To: NT Developers Interest List
Subject: [ntdev] Re: DeviceIoctl Vs SerialComm API

Hello,

CreateFile(), CloseHandle() type of calls are working. DeviceIoControl()
calls are also working. But If I use SerialComm APIs like SetCommTimeout(),
the return value is 0, and the extended error is 6 (Invalid Handle).

what is your code in user mode? Maybe some things wrong and you use
not the right handle.

I have used for all my test’s the very old MTTTY demo application from MS
without problems.

When one device control works than all call must works.

elli

You are currently subscribed to ntdev as: xxxxx@diebold.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

4

San Wind,
In Windows 98/ME the SerialCommAPI’s directly map
to VCOMM function and they route the control to the
*.vxd (Serial.vxd). Hence control doesnot come to the
WDM based driver. But surprisingly the control will
come to the read,write,open,close,deviceiocontrol
calls to the wirtual WDM driver.

Cheers,
Jay

— San Wind wrote:
> Hi,
>
> I have installed WDM based Virtual Serial Port
> Driver using CCPORT.SYS
> support in Win 98 SE.
>
> CreateFile(), CloseHandle() type of calls are
> working. DeviceIoControl()
> calls are also working. But If I use SerialComm APIs
> like SetCommTimeout(),
> the return value is 0, and the extended error is 6
> (Invalid Handle).
> Conttrol is not reaching my driver. At the same time
> if I issue DeviceIoctl
> with code as IOCTL_SERIAL_SET_TIMEOUT, it is working
> and I am getting the
> control.
>
> Please help me.
>
> Thanks
> San Wind
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.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