SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Thu, 21 Nov 2002 15:35:47 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: interrupts

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.
=====================================================

> >I'm guessing the PCI bus changed the interrupt on my NIC.
>
> More likely the PCI bus decide the NIC and the WinModem could share and
> IRQ.

That would be my guess, also. And as Steven stated, you might be able to
correct the problem by swapping boards around on your motherboard, until
the NIC gets its own, individual IRQ. I use OS/2's RMVIEW.EXE program to
help me track and store away information on my system IRQ's, IO's,
DMA's, etc.

Attached please find a REXX script that I built a couple of years ago.
It provides a text-based, user interface to RMVIEW.EXE. The script
allows you to use RMVIEW.EXE without having to remember, or look up, its
various commandline parameters. Also, the script redirects the
RMVIEW.EXE screen output to an ASCII file. Optionally, it also sends the
output to the printer, if you like.

You are welcome to use the script. If you want to, please note the
following:

1. Place the script anywhere on your hard drive

2. Create a program object for it. On the "Program Tab" of the "path
and file name" and "Parameters" fields respectively as follows:
?\OS2\PMREXX.EXE
/Q "??\RMVIEW.CMD"

Above, "?" means your boot drive, like "C:\".

"??" means the path to the folder where you placed the RMVIEW.CMD REXX
script. The "/Q" parameter allows you to run PMREXX.EXE in "quiet" mode.
That is, when the script finishes, you do not have to respond to that
annoying message, "The REXX procedure has ended", and also manually
close out the PMREXX window. Above, you need the quotes surrounding
"??\RMVIEW.CMD", but not on the "/Q" portion.

Run the script under PMREXX.EXE, and not as a commandline REXX program.
The text-based instructions look better in PMREXX

When you first run RMVIEW.CMD, it will create 2 subfolders under the
folder into which you placed RMVIEW.CMD. One subfolder will hold any
ASCII text file output from RMVIEW.CMD. The other subfolder holds any
previous text file output (before it creates a new text file, it moves
any existing one over to the other folder).
HCM
________________________________________________________________________________________

Steven Levine wrote:
>
> =====================================================
> 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.
> =====================================================
>
> In <2EE3E396.23422976@concentric.net>, on 11/17/02
> at 11:36 AM, Dave said:
>
> >Does anyone know of a good tutorial or crib sheet on troubleshooting
> >interrupt conflicts? I tried sticking a PCI winmodem in a spare slot on
>
> Not really.
>
> >a Warp4 system, rebooted and Warp won't find my NIC. My temporary
> >solution was to pull the modem out. Having some options makes it easier.
> >I'm guessing the PCI bus changed the interrupt on my NIC.
>
> More likely the PCI bus decide the NIC and the WinModem could share and
> IRQ. With PCI, you can see the IRQ assignments when the BIOS boots.
> You've got two options. Find a version of the NIC driver that supports
> IRQ sharing. I'm assuming your NIC is PCI too. Otherwise, swap the PCI
> cards amoung the available slots until the NIC gets its own IRQ.
>
> Steven
>
> --
> ---------------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4
> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
> ---------------------------------------------------------------------
>
> =====================================================
>
> 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".
>
> =====================================================

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

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".

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

Return to [ 21 | November | 2002 ]

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.