WIN-OS/2 can't see my Gold Card Modem
Dr Geoff Hogan
an FAQ, just please tell me where to find it!
I have OS/2 Warp Connect on my ThinkPad (755CX). I recently changed to
a Psion Dacom Gold Card PCMCIA modem, which works fine with the native
OS/2 programmes. However it is supplied with software to allow it to be
set to be used in different countries (rcognise dial tones, etc). This
is supplied as Windows software. I installed the Win 3.1 version under
WIN-OS/2 where it runs, but cannot see the modem (just tells me that COM
2, that it is using, is unavailable).
I have gone throught the DOS/WIN-OS/2 session settings, especially the
COM ones, and can't find anything to fix it. Any suggestions?
Many thanks,
Geoff Hogan
Rich Walsh
If COM_DIRECT_ACCESS->ON and the other obvious settings don't work
in either windowed or full-screen sessions, you might try this
wild-assed-guess: comment-out com.sys and vcom.sys in config.sys
so that OS/2 doesn't even know your com ports exist. Then reboot
and try again. I have no idea whether this will work, but it
should only take a few minutes to find out. (If the app "knows"
that com2 is at port 2f8, then it may; if it has to query the
system for this, then it certainly won't.)
Another thought: if these modem parameters are handled as AT
commands _and_ they're suitably documented, you might try feeding
them to your modem by entering them as an init string in your
dialer or terminal program. You could probably even do this
from a command line, i.e.
"copy con com2:", then "AT[parms]"enter, then Ctrl-Z
== == almost usable email address: rlwalshATpacket.net == ==
___________________________________________________________________
| - DragText v3.1 -
Rich Walsh | A Distinctly Different Desktop Enhancement
Ft Myers, FL | New! Pickup & Drop for text, and more...
| http://www.usacomputers.net/personal/rlwalsh/
___________________________________________________________________
Tony Wright
Rich Walsh wrote:
> On Tue, 12 Oct 1999 14:28:57, Dr Geoff Hogan <g.h...@physics.ox.ac.uk> wrote:
>
> > Please excuse me if this kind of question has already been answered in
> > an FAQ, just please tell me where to find it!
> >
> > I have OS/2 Warp Connect on my ThinkPad (755CX). I recently changed to
> > a Psion Dacom Gold Card PCMCIA modem, which works fine with the native
> > OS/2 programmes. However it is supplied with software to allow it to be
> > set to be used in different countries (rcognise dial tones, etc). This
> > is supplied as Windows software. I installed the Win 3.1 version under
> From: rlw...@packet.net (Rich Walsh)
> Newsgroups: comp.os.os2.misc
> Subject: Re: WIN-OS/2 can't see my Gold Card Modem
> Date: 15 Oct 1999 09:20:27 GMT
> Organization: http://extra.newsguy.com
> Lines: 42
> Message-ID: <zzdHjdPQunhi-pn2-JcHd3YgxXx4K@localhost>
> References: <380345A9...@physics.ox.ac.uk>
> NNTP-Posting-Host: ftm046.usacomputers.net
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 8bit
> X-Newsreader: ProNews/2 Version 1.50á1
> Path: news3.prserv.net!newsfeed.us.ibm.net!ibm.net!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.berkeley.edu!su-news-hub1.bbnplanet.com!news.gtei.net!pln-w!spln!extra.newsguy.com!newsp.newsguy.com!enews4
> Xref: news3.prserv.net comp.os.os2.misc:209238
>
> On Tue, 12 Oct 1999 14:28:57, Dr Geoff Hogan <g.h...@physics.ox.ac.uk> wrote:
>
> > Please excuse me if this kind of question has already been answered in
> > an FAQ, just please tell me where to find it!
> >
> > I have OS/2 Warp Connect on my ThinkPad (755CX). I recently changed to
> > a Psion Dacom Gold Card PCMCIA modem, which works fine with the native
> > OS/2 programmes. However it is supplied with software to allow it to be
> > set to be used in different countries (rcognise dial tones, etc). This
> > is supplied as Windows software. I installed the Win 3.1 version under
> > WIN-OS/2 where it runs, but cannot see the modem (just tells me that COM
> > 2, that it is using, is unavailable).
> >
> > I have gone throught the DOS/WIN-OS/2 session settings, especially the
> > COM ones, and can't find anything to fix it. Any suggestions?
>
> If COM_DIRECT_ACCESS->ON and the other obvious settings don't work
> in either windowed or full-screen sessions, you might try this
> wild-assed-guess: comment-out com.sys and vcom.sys in config.sys
> so that OS/2 doesn't even know your com ports exist. Then reboot
> and try again. I have no idea whether this will work, but it
> should only take a few minutes to find out.
Fair comment (and stranger things have been known to work<g>) but as OS/2 prevents DOS from directly manipulating/accessing hardware directly without going via a virtualised device driver (ie vcom.sys which also in most
cases requires com.sys) how is removing the VDD supposed to help?
COM_DIRECT_ACCESS allows the dos/winos2 application to directly access the ports via VCOM.SYS (but then has disadvantage of not using buffers in com.sys which may loose bits).
COM_HOLD ensures that port is kept open for as long as the dos/winos2 session is open and prevents com.sys from closing the port when it thinks it's idle (after default timout).
COM_SELECT ensures only a specific port is used (the others being hidden).
It's not readily apparent as to whether original poster tried these individually and/or in various combinations?
Apologies if I missed any previous pertinent info/suggestions earlier in thread but does
> If COM_DIRECT_ACCESS->ON and the other obvious settings don't work
>
also include:
1. Whether this is application specific or generic (eg does winterm produce same error) and thus potentially also point to PCMCIA, card & socket services? (eg VPCMCIA.SYS) Perhaps the actual specific "application"
requires/assumes Point Enabler software instead of CS/SS and may require a /IG0=124 or similar parameter to "fudge" it using the latter?
2. Checking the com.sys and vcom.sys dates/sizes? in case the version/level is relevant to the problem? (IE trying versions from both later and earlier FP's may be relevant).
3. Include specifically trying parameters for drivers (including ignoring unexpected interrupts)? EG: com.sys (2,02f8,3,I)
4. replacing with SIO drivers and if required the parameters in 2. above?
Not forgetting the obvious to ensure that TP755 system bios is at latest level of course....<g>...(v1.44 possibly?)
> (If the app "knows"
> that com2 is at port 2f8, then it may; if it has to query the
> system for this, then it certainly won't.)
If set explicitly as parameter to COM.SYS then it certainly should, but as you recommended remming it out I can't see how it has any choice but to try and query system?Unless there is a specific Point Enabler(DACOM
monolithic interface) for OS/2 perhaps?
--
Rgds Tony W Email: hors...@ibm.net
"humanum est errare: To err is human
.... and to fail is to be a Project Manager...
...but to foul things up completely needs a computer!"