SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 21 | May | 2002 ]

<< Previous Message << >> Next Message >>


Date: Tue, 21 May 2002 22:27:29 PST7
From: "Benedict G. Archer" <bgarcher@gte.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: which newsgroups?

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:

>
> at 08:50 PM, "Benedict G. Archer" said:
>
> >Adding (port, IO, IRQ) to the com.sys line made it work, but I don't see
> >how to specify an IRQ for an SIO2k port. The SIO2k docs seem to say that
> >you can't which would complicate using SIO2k with this kind of modem.
>
> According to Ray, SIO2K should always be able to detect the IRQ. If it
> can't and COM.SYS works, Ray may consider this a SIO2K defect. Before
> e-mailing Ray, read up on logger.exe and use it to find out what's really
> happening. If needed the port can be specfied in sio2k.cfg. In your
> case, you might need to update the entry for $UART,3 (line 165 in
> sample.cfg) although I'd expect SIO2K to find this on its own via the PCI
> configuration block scan.
>
> Steven

As I read it, an sio2k.cfg file can only specify an address, not an IRQ. Somewhere
in the SIO2k docs I read something to the effect that it should never be necessary to
specify an IRQ, and no means are provided as it is automatic. I had tried to specify
the IO address using the syntax suggested in install.txt, LegacyIsa(IO1,IO2, etc), but
this didn't work. If I remember correctly, the modem would initialize and dial, but
hung the system when disconnection. I know, the modem isn't an isa card, but this
seemed to be the syntax for specifying an IO. I started preparing an SIO2k.cfg file,
but when I saw that there was no way to specify an IRQ, I abandoned that and tried
standard com.sys. Since it worked, and since the author strongly discourages using
SIO2k.cfg, I stopped there. If you think I should experiment further to investigate
a possible bug, I will.

Ben

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 21 | May | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.