"Port already open" problem

[Donald G. Davis]

I've installed Win98SE on an HP Pavilion A656X computer, ASUS
A7V8X-LA (Kelut) motherboard. I have an external serial Diamond Supra 56e
Pro modem on the onboard COM1 socket. I use it in both DOS and Windows.
Here is the problem, which I've never had with my previous ISA modems:

The modem works properly under raw MS-DOS or in a Windows DOS
session, using the Qmodem terminal program.

The modem works properly with a Windows DUN connection if it has not
been used under Qmodem in a DOS session in Windows before starting DUN.

But if Qmodem has been run and exited before I then attempt to
connect in Windows via DUN, the DUN window pops up an Error 630, "modem is
not responding properly." Attempting to run the modem diagnostics under
Control Panel/Modems gives a "port already open" abort.

It appears that something about using the modem in DOS mode leaves
the port in a state that locks out subsequent use in Windows mode. I've
tried issuing the AT&F modem command before exiting Qmodem--the modem
responds OK but this does not help (the problem apparently affects the COM
port in the motherboard, not the modem hardware itself). I have searched
Google for the "port already open" error. The recommendations mostly have
to do with killing the RNAAPP process when using Winmodems. But in my
case, RNAAPP is not running, and I haven't found any advice that seems to
fit this case.

My question: is there some way to re-initialize the port for Windows
use without having to restart Windows? Are there Windows programs for
resetting such hardware?
--
--Donald Davis

[To respond by e-mail, remove "blackhole." from the address.]

 

[Franc Zabkar]

On 17 Nov 2007 06:01:21 GMT, Donald G. Davis
<dgdavis@blackhole.nyx.net> put finger to keyboard and composed:

> I've installed Win98SE on an HP Pavilion A656X computer, ASUS
>A7V8X-LA (Kelut) motherboard. I have an external serial Diamond Supra 56e
>Pro modem on the onboard COM1 socket. I use it in both DOS and Windows.
>Here is the problem, which I've never had with my previous ISA modems:

What's different? Did the ISA modems use a different COM port number?

> The modem works properly under raw MS-DOS or in a Windows DOS
>session, using the Qmodem terminal program.
>
> The modem works properly with a Windows DUN connection if it has not
>been used under Qmodem in a DOS session in Windows before starting DUN.
>
> But if Qmodem has been run and exited before I then attempt to
>connect in Windows via DUN, the DUN window pops up an Error 630, "modem is
>not responding properly." Attempting to run the modem diagnostics under
>Control Panel/Modems gives a "port already open" abort.

Is the DOS window still open when you do this?

I have no idea whether this will work, but maybe you could try the
following before you return to Windows:

echo ATZ > COM1 (or just a plain AT might do)
exit

FWIW, you can take control of a COM port in a DOS window simply by
using the above Echo command.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[MEB]

Try *adding* AT&F^ to either the DUN initialization string or in Qmodem. In
Qmodem this can also be added to the Hang-up line/setting.

If not,,, try adding AT&F^,,ATZ^ - hangup line would look something like
this:
ATH^,,AT&F,,ATZ^
Been awhile since I used Qmodem DOS, so what you want is a hangup, then
pause for 2 seconds, a factory reset, another 2 second pause, then reset to
the first saved modem configuration [generally written when the modem is
first setup unless you've done a AT&W(number)].

Heck, this is all from old memory, though I could probably dig through my
old disks if necessary.. or a search for something like * Diamond Supra
Command Set * might turn up what you need.

--
MEB
http://peoplescounsel.orgfree.com
________


"Donald G. Davis" <dgdavis@blackhole.nyx.net> wrote in message
news:1195279280.931965@irys.nyx.net...
| I've installed Win98SE on an HP Pavilion A656X computer, ASUS
| A7V8X-LA (Kelut) motherboard. I have an external serial Diamond Supra 56e
| Pro modem on the onboard COM1 socket. I use it in both DOS and Windows.
| Here is the problem, which I've never had with my previous ISA modems:
|
| The modem works properly under raw MS-DOS or in a Windows DOS
| session, using the Qmodem terminal program.
|
| The modem works properly with a Windows DUN connection if it has not
| been used under Qmodem in a DOS session in Windows before starting DUN.
|
| But if Qmodem has been run and exited before I then attempt to
| connect in Windows via DUN, the DUN window pops up an Error 630, "modem is
| not responding properly." Attempting to run the modem diagnostics under
| Control Panel/Modems gives a "port already open" abort.
|
| It appears that something about using the modem in DOS mode leaves
| the port in a state that locks out subsequent use in Windows mode. I've
| tried issuing the AT&F modem command before exiting Qmodem--the modem
| responds OK but this does not help (the problem apparently affects the COM
| port in the motherboard, not the modem hardware itself). I have searched
| Google for the "port already open" error. The recommendations mostly have
| to do with killing the RNAAPP process when using Winmodems. But in my
| case, RNAAPP is not running, and I haven't found any advice that seems to
| fit this case.
|
| My question: is there some way to re-initialize the port for Windows
| use without having to restart Windows? Are there Windows programs for
| resetting such hardware?
| --
| --Donald Davis
|
| [To respond by e-mail, remove "blackhole." from the address.]

 

[Donald G. Davis]

>On 17 Nov 2007 06:01:21 GMT, Donald G. Davis
><dgdavis@blackhole.nyx.net> put finger to keyboard and composed:
>> I've installed Win98SE on an HP Pavilion A656X computer, ASUS
>>A7V8X-LA (Kelut) motherboard. I have an external serial Diamond Supra 56e
>>Pro modem on the onboard COM1 socket. I use it in both DOS and Windows.
>>Here is the problem, which I've never had with my previous ISA modems:
>
> What's different? Did the ISA modems use a different COM port number?
>
Those were on COM2. However, this machine has no ISA sockets, and
only one, external, serial socket (though diagnostics show that the
internal hardware includes two COM ports) I assume that this has to be
COM1. The BIOS on this computer is very basic, and has no options for
changing port addressing.

>> The modem works properly under raw MS-DOS or in a Windows DOS
>>session, using the Qmodem terminal program.
>>
>> The modem works properly with a Windows DUN connection if it has not
>>been used under Qmodem in a DOS session in Windows before starting DUN.
>>
>> But if Qmodem has been run and exited before I then attempt to
>>connect in Windows via DUN, the DUN window pops up an Error 630, "modem
>>is not responding properly." Attempting to run the modem diagnostics under
>>Control Panel/Modems gives a "port already open" abort.
>
>Is the DOS window still open when you do this?

Yes I normally leave two DOS sessions running whenever I'm working
in Win98--part of my startup routine, so I can Alt-Tab between Windows and
an open DOS session whenever I want to.

>I have no idea whether this will work, but maybe you could try the
>following before you return to Windows:
>echo ATZ > COM1 (or just a plain AT might do)
>exit
>FWIW, you can take control of a COM port in a DOS window simply by
>using the above Echo command.
>- Franc Zabkar

Thank you for that suggestion. On testing this, I find that simply
exiting that DOS session restores the port functionality in Windows--it is
not necessary to issue the ECHO ATZ > COM1 command first. It's less than
optimal to have to kill the DOS session and restart it, and I'd prefer to
have some way to reset the port directly in Windows, before making a DUN
connection but cycling the affected DOS session is much better than
having to restart Windows altogether.
--
--Donald Davis

[To respond by e-mail, remove "blackhole." from the address.]

 

[Donald G. Davis]

"MEB" <meb@not here@hotmail.com> writes:

> Try *adding* AT&F^ to either the DUN initialization string or in Qmodem. In
>Qmodem this can also be added to the Hang-up line/setting.

> If not,,, try adding AT&F^,,ATZ^ - hangup line would look something like
>this:
>ATH^,,AT&F,,ATZ^
>Been awhile since I used Qmodem DOS, so what you want is a hangup, then
>pause for 2 seconds, a factory reset, another 2 second pause, then reset to
>the first saved modem configuration [generally written when the modem is
>first setup unless you've done a AT&W(number)].

I tried entering that sequence manually the modem responded OK to
each command, but Windows reported that the port remained open until I
exited the DOS session in which Qmodem had used the modem.
--
--Donald Davis

[To respond by e-mail, remove "blackhole." from the address.]

 

[Franc Zabkar]

On 18 Nov 2007 20:13:10 GMT, Donald G. Davis
<dgdavis@blackhole.nyx.net> put finger to keyboard and composed:

>>On 17 Nov 2007 06:01:21 GMT, Donald G. Davis
>><dgdavis@blackhole.nyx.net> put finger to keyboard and composed:
>>> I've installed Win98SE on an HP Pavilion A656X computer, ASUS
>>>A7V8X-LA (Kelut) motherboard. I have an external serial Diamond Supra 56e
>>>Pro modem on the onboard COM1 socket. I use it in both DOS and Windows.
>>>Here is the problem, which I've never had with my previous ISA modems:
>>
>> What's different? Did the ISA modems use a different COM port number?
>>
> Those were on COM2. However, this machine has no ISA sockets, and
>only one, external, serial socket (though diagnostics show that the
>internal hardware includes two COM ports) I assume that this has to be
>COM1. The BIOS on this computer is very basic, and has no options for
>changing port addressing.

FYI, DOS assigns numbers to COM ports in the order in which they are
discovered whereas Windows assigns numbers according the actual I/O
address. In my case DOS detects COM1, COM2, and COM3, but Device
Manager finds COM1, COM2, and COM4. COM3 and COM4 are actually the
same port, at I/O address 2E8-2EF.

I just thought this info may be useful ...

>>> The modem works properly under raw MS-DOS or in a Windows DOS
>>>session, using the Qmodem terminal program.
>>>
>>> The modem works properly with a Windows DUN connection if it has not
>>>been used under Qmodem in a DOS session in Windows before starting DUN.
>>>
>>> But if Qmodem has been run and exited before I then attempt to
>>>connect in Windows via DUN, the DUN window pops up an Error 630, "modem
>>>is not responding properly." Attempting to run the modem diagnostics under
>>>Control Panel/Modems gives a "port already open" abort.
>>
>>Is the DOS window still open when you do this?
>
> Yes I normally leave two DOS sessions running whenever I'm working
>in Win98--part of my startup routine, so I can Alt-Tab between Windows and
>an open DOS session whenever I want to.

Just for fun you may want to try this.

Take control of COM1 in DOS box #1 by executing the following:

echo AT > COM1

Use Debug to write (O)and read (I) the Modem Control Register (3FC)
for COM1 as follows:

debug
-o 3fc 0
-i 3fc
-o 3fc 1
-i 3fc
-o 3fc 2
-i 3fc
-o 3fc 3
-i 3fc
-q

Bits 0 and 1 are the DTR and RTS bits.

After each I/O command, switch to DOS box #2 and use Debug to write
and read the same register. You will notice that whatever you do in
one window will not affect what you see in the other. Watch your
modem's DTR and RTS LEDs while doing this.

There is one curious quirk that is worth mentioning. While the COM
port's I/O address space is protected, there is one register, the
scratchpad register at 3FF, that is not. You can verify this by
writing anything (eg FF, 00, AA or 55) in either DOS box and observing
the changes in the other.

>>I have no idea whether this will work, but maybe you could try the
>>following before you return to Windows:
>>echo ATZ > COM1 (or just a plain AT might do)
>>exit

>>FWIW, you can take control of a COM port in a DOS window simply by
>>using the above Echo command.

>>- Franc Zabkar
>
> Thank you for that suggestion. On testing this, I find that simply
>exiting that DOS session restores the port functionality in Windows ...

Hmm, if you have been in the habit of leaving the DOS window open,
then surely you must have had the same problem with your ISA modems?

BTW, AFAICT, the COM port "belongs" to the DOS window, not to the
application running within it. That's why you need to close the window
before the port can be released.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[MEB]

"Donald G. Davis" <dgdavis@blackhole.nyx.net> wrote in message
news:1195483475.774095@irys.nyx.net...
| "MEB" <meb@not here@hotmail.com> writes:
|
| > Try *adding* AT&F^ to either the DUN initialization string or in Qmodem.
In
| >Qmodem this can also be added to the Hang-up line/setting.
|
| > If not,,, try adding AT&F^,,ATZ^ - hangup line would look something like
| >this:
| >ATH^,,AT&F,,ATZ^
| >Been awhile since I used Qmodem DOS, so what you want is a hangup, then
| >pause for 2 seconds, a factory reset, another 2 second pause, then reset
to
| >the first saved modem configuration [generally written when the modem is
| >first setup unless you've done a AT&W(number)].
|
| I tried entering that sequence manually the modem responded OK to
| each command, but Windows reported that the port remained open until I
| exited the DOS session in which Qmodem had used the modem.
| --
| --Donald Davis
|
| [To respond by e-mail, remove "blackhole." from the address.]

Ah, okay, but you did that in the terminal Window which will NOT release
the modem until the terminal Window is closed. So try modifying the Hangup
string to see if that helps.

Okay, to kill of other potentials:
So what did you choose for your Properties and Advanced Settings in the DOS
Box batch files links {you put them in StartUp right?}?

Do you have Prevent MSDOS based programs from Detecting Windows checked
[works both ways for many Dos programs]?
Do you have everything unchecked in Misc except perhaps Mouse Exclusive and
Fast Pasting?
How about Memory and Screen settings?

And, for reference, is the Com Port the same in DOS as it is in Windows
[Port, address, and IRQ]?

Meanwhile, give me a couple days [wait its the holidays, maybe four or
five] to dig through my old disks and info,,, maybe I can find something
don't you have Qmodem Pro for 95 [no, or he'd be using it]?
Did you happen to check over on the UK Modem site,, they had old data bases
of information for some comm programs at one time..
[Slaps head] Oh yeah, that might help,, what version are you using? 3, 4,
5,,,

--
MEB
http://peoplescounsel.orgfree.com
________

 

[Donald G. Davis]

Franc Zabkar <fzabkar@iinternode.on.net> writes:

Thanks for your additional sugggestions I've been out of town and
delayed in responding. I've saved your posts for future reference.

>>On testing this, I find that simply
>>exiting that DOS session restores the port functionality in Windows ...

>Hmm, if you have been in the habit of leaving the DOS window open,
>then surely you must have had the same problem with your ISA modems?

>BTW, AFAICT, the COM port "belongs" to the DOS window, not to the
>application running within it. That's why you need to close the window
>before the port can be released.

No, I haven't had the problem with any ISA modems. I'm typing
this in Qmodem over one of these ISA modems now--when I exit Qmodem,
leaving the DOS session running, then switch to the Windows desktop and
run the modem diagnostics or make a DUN connection, the port will have
been freed and the modem will work normally in Windows. I've done it
hundreds of times, and it's completely reliable. But on the machine with
the external serial modem, if I do the same things in the DOS session, the
port will be unreleased unless I also close the DOS session. (I normally
use the DOS sessions in full-screen DOS text mode, not in a Windows
graphic emulation of the DOS screen, if that matters.)
--
--Donald Davis

[To respond by e-mail, remove "blackhole." from the address.]

 

[Franc Zabkar]

On 26 Nov 2007 19:29:12 GMT, Donald G. Davis
<dgdavis@blackhole.nyx.net> put finger to keyboard and composed:

>Franc Zabkar <fzabkar@iinternode.on.net> writes:
>
> Thanks for your additional sugggestions I've been out of town and
>delayed in responding. I've saved your posts for future reference.
>
>>>On testing this, I find that simply
>>>exiting that DOS session restores the port functionality in Windows ...
>
>>Hmm, if you have been in the habit of leaving the DOS window open,
>>then surely you must have had the same problem with your ISA modems?
>
>>BTW, AFAICT, the COM port "belongs" to the DOS window, not to the
>>application running within it. That's why you need to close the window
>>before the port can be released.
>
> No, I haven't had the problem with any ISA modems. I'm typing
>this in Qmodem over one of these ISA modems now--when I exit Qmodem,
>leaving the DOS session running, then switch to the Windows desktop and
>run the modem diagnostics or make a DUN connection, the port will have
>been freed and the modem will work normally in Windows. I've done it
>hundreds of times, and it's completely reliable. But on the machine with
>the external serial modem, if I do the same things in the DOS session, the
>port will be unreleased unless I also close the DOS session. (I normally
>use the DOS sessions in full-screen DOS text mode, not in a Windows
>graphic emulation of the DOS screen, if that matters.)

I have a "full hardware" ISA modem on COM2. If I execute the following
in a DOS box, whether full-screen or windowed, and then switch to
another application, I get the message that the port is already open.

C:\WIN98SE>echo ATL3M2H1 > com2
C:\WIN98SE>echo ATH > com2

The above commands turn on the modem's speaker at max volume, take the
modem off-hook, and then hangup. You should hear a dialtone.

Maybe yours is a "winmodem" on a virtual COM port (eg CommWave), and
maybe Windows is providing DOS box support ???

One way to detect real non-PnP COM ports in real DOS mode is via
Debug:

debug
-d 40:0 f
0040:0000 F8 03 F8 02 E8 02 00 00-78 03 78 02 00 00 0F 02
^^^^^ ^^^^^ ^^^^^ ^^^^^ ^^^^^ ^^^^^ ^^^^^
COM1 COM2 COM3 COM4 LPT1 LPT2 LPT3
3F8 2F8 2E8 378 278
-q

Note that Device Manager detects port address 2E8 as COM4, whereas DOS
assigns COM port numbers in sequential order.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[Franc Zabkar]

On 26 Nov 2007 19:29:12 GMT, Donald G. Davis
<dgdavis@blackhole.nyx.net> put finger to keyboard and composed:

>Franc Zabkar <fzabkar@iinternode.on.net> writes:
>
> Thanks for your additional sugggestions I've been out of town and
>delayed in responding. I've saved your posts for future reference.
>
>>>On testing this, I find that simply
>>>exiting that DOS session restores the port functionality in Windows ...
>
>>Hmm, if you have been in the habit of leaving the DOS window open,
>>then surely you must have had the same problem with your ISA modems?
>
>>BTW, AFAICT, the COM port "belongs" to the DOS window, not to the
>>application running within it. That's why you need to close the window
>>before the port can be released.
>
> No, I haven't had the problem with any ISA modems. I'm typing
>this in Qmodem over one of these ISA modems now--when I exit Qmodem,
>leaving the DOS session running, then switch to the Windows desktop and
>run the modem diagnostics or make a DUN connection, the port will have
>been freed and the modem will work normally in Windows.

I've just installed Qmodem v4.6 on my Win98SE box. When I do exactly
as you have done, using my internal ISA modem, I get a "port already
open" error.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[Donald G. Davis]

Franc Zabkar <fzabkar@iinternode.on.net> writes:

>> No, I haven't had the problem with any ISA modems. I'm typing
>>this in Qmodem over one of these ISA modems now--when I exit Qmodem,
>>leaving the DOS session running, then switch to the Windows desktop and
>>run the modem diagnostics or make a DUN connection, the port will have
>>been freed and the modem will work normally in Windows.

>I've just installed Qmodem v4.6 on my Win98SE box. When I do exactly
>as you have done, using my internal ISA modem, I get a "port already
>open" error.

This only gets more and more puzzling. Perhaps the specific modem
design determines whether or not the problem occurs. I wish I knew of
some Windows utility that could force the port to be released even when
the affected DOS session is still running in the background.
--
--Donald Davis

[To respond by e-mail, remove "blackhole." from the address.]

 

[Franc Zabkar]

On 06 Dec 2007 16:19:14 GMT, Donald G. Davis
<dgdavis@blackhole.nyx.net> put finger to keyboard and composed:

>Franc Zabkar <fzabkar@iinternode.on.net> writes:
>
>>> No, I haven't had the problem with any ISA modems. I'm typing
>>>this in Qmodem over one of these ISA modems now--when I exit Qmodem,
>>>leaving the DOS session running, then switch to the Windows desktop and
>>>run the modem diagnostics or make a DUN connection, the port will have
>>>been freed and the modem will work normally in Windows.
>
>>I've just installed Qmodem v4.6 on my Win98SE box. When I do exactly
>>as you have done, using my internal ISA modem, I get a "port already
>>open" error.
>
> This only gets more and more puzzling. Perhaps the specific modem
>design determines whether or not the problem occurs.

What are the ATIn responses in CP -> Modem -> Diagnostics? What are
the part numbers on the modem chips?

This is my favourite modem support site:
http://modemsite.com/56k/trouble.asp

Identifying Your Chipset:
http://modemsite.com/56k/chipset.asp

Who Manufactured My Modem?
http://modemsite.com/56k/whomadeit.asp

>I wish I knew of
>some Windows utility that could force the port to be released even when
>the affected DOS session is still running in the background.

I wonder if in your case the modem's port is owned by some lower level
software module ???

Try running msinfo32.exe and checking the Software Environment ???

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.