Acquiring temporary control of COM1 or COM2

NTDEV
1

I have a serious problem. I’ve developed a specialized serial
communication driver that among other things implements the
none-bit-protocol and multidrop protocol. Under Windows NT 4.0 I added
the following lines to the registry to prevent the Microsoft serial
driver from reserving COM2. If I did not add those lines the Microsoft
driver loaded and prevented my driver from acquiring the interrupt.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
erial2\DisablePort = 1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
erial2\DosDevices = “COM2”
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
erial2\Interrupt = 0x3
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
erial2\PortAddress = 0x2F8
?When I add the above entries to Windows 2000, the PNP system comes up
and says it detects COM2 and asks for disk with driver. Is there anyway
around this problem?

On another issues, is there a way to request that the serial driver lend
me the serial port under Windows 2000 or Windows NT4.0?

Thanks for your reply,

Regards,

Berto

WCSC(Willies Computer Software Co)
Web: http://www.wcscnet.com Email: xxxxx@wcscnet.com
Tel: (281)360-4232 Fax: (281)360-3231

2

Berto,
I’m writing something similar to yours driver, using DMA on serial COM2. The
thing is that you have build intermediate driver and I think that you have
to communicate with serial driver to do things what you need. (if you
haven’t already work this thing out). My driver won’t work anywhere but on
mine computer so I don’t need serial ao I disconnect it.
I’m wondering as you have done this how did you fill IoConnectInterrupt
routine? I had problems with bus relative level, so I have put there
DISPATCH_LEVEL and it worked fine although the serial driver was loaded.
Did you work this way?

Regards,
Neno

----- Original Message -----
From: “Berto”
To: “NT Developers Interest List”
Sent: 2000. travanj 09 05:15
Subject: [ntdev] Acquiring temporary control of COM1 or COM2

> I have a serious problem. I’ve developed a specialized serial
> communication driver that among other things implements the
> none-bit-protocol and multidrop protocol. Under Windows NT 4.0 I added
> the following lines to the registry to prevent the Microsoft serial
> driver from reserving COM2. If I did not add those lines the Microsoft
> driver loaded and prevented my driver from acquiring the interrupt.
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
> erial2\DisablePort = 1
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
> erial2\DosDevices = “COM2”
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
> erial2\Interrupt = 0x3
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters\S
> erial2\PortAddress = 0x2F8
> When I add the above entries to Windows 2000, the PNP system comes up
> and says it detects COM2 and asks for disk with driver. Is there anyway
> around this problem?
>
> On another issues, is there a way to request that the serial driver lend
> me the serial port under Windows 2000 or Windows NT4.0?
>
> Thanks for your reply,
>
> Regards,
>
> Berto
>
>
> —
> WCSC(Willies Computer Software Co)
> Web: http://www.wcscnet.com Email: xxxxx@wcscnet.com
> Tel: (281)360-4232 Fax: (281)360-3231
>
>
> —
> You are currently subscribed to ntdev as: boris.prekupec@vz.tel.hr
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>