home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Supreme Volume 6 #1
/
swsii.zip
/
swsii
/
418
/
FAXDOC.ZIP
/
1012601.TXT
< prev
next >
Wrap
Text File
|
1993-05-12
|
7KB
|
137 lines
FYI
(Note: The origin of this information may be internal or external to Novell.
Novell makes every effort within its means to verify this information.
However, the information provided in this document is FOR YOUR INFORMATION
only. Novell makes no explicit or implied claims to the validity of this
information.)
TITLE: Resolving I/O and IRQ Conflicts
DOCUMENT ID#: FYI.P.6054
DATE: 04DEC92
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: FYI.P.6012 and FYI.P.6013
LITE FAX DOC #: 2601
SYMPTOM
NA
ISSUE/PROBLEM
Resolving I/O and IRQ Conflicts
I/O Conflicts
The Ethernet, ARCnet, or other network board will need to use a unique
I/O address. The following table shows some possible conflicts. Column
one shows the range from 200 to 3E0 (hex). Column two shows some
possible conflicting devices. Select an I/O address that best fits your
configuration; however, be aware that this table is generic. If problems
persist, consult the documentation of your specific system. It is also
possible to get a listing of your I/O addresses with a computer utility
program.
┌──────────────┬─────────────────────────────────────┐
│ I/O Address │ Potential Conflicting Devices │
├──────────────┼─────────────────────────────────────┤
│ 200 │ Game controller /Joystick (200-20F) │
├──────────────┼─────────────────────────────────────┤
│ 220 │ Novell Network Keycard │
├──────────────┼─────────────────────────────────────┤
│ 240 │ │
├──────────────┼─────────────────────────────────────┤
│ 260 │ LPT2: (278-27F) │
├──────────────┼─────────────────────────────────────┤
│ 280 │ LCD display on Wyse 2108 PC │
├──────────────┼─────────────────────────────────────┤
│ 2A0 │ │
├──────────────┼─────────────────────────────────────┤
│ 2C0 │ │
├──────────────┼─────────────────────────────────────┤
│ 2E0 │ COM4:, GPIB-Adapter 0 (2E1) │
│ │ COM2:, Data acquisition (300-31F) │
├──────────────┼─────────────────────────────────────┤
│ 300 │ │
├──────────────┼─────────────────────────────────────┤
│ 320 │ XT Hard Disk interface (320-32F) │
├──────────────┼─────────────────────────────────────┤
│ 340 │ │
├──────────────┼─────────────────────────────────────┤
│ 360 │ LPT1: (378-37F) │
├──────────────┼─────────────────────────────────────┤
│ 380 │ SLDC/Sec Bi-Sync interface (380 │
├──────────────┼─────────────────────────────────────┤
│ 3A0 │ Primary Bi-Sync interface (3A0-3A9) │
│ │ Monochrome display (3B0-3BB) │
├──────────────┼─────────────────────────────────────┤
│ 3C0 │ EGA display control (3C0-3CF) │
│ │ CGA display control (3D0-3CF) │
├──────────────┼─────────────────────────────────────┤
│ 3E0 │ COM3: (3E8-3EF) │
│ │ Floppy disk controller (3F0-3F7) │
│ │ COM1: (3F8-3FF) │
└──────────────┴─────────────────────────────────────┘
IRQ Conflicts
A unique interrupt line (IRQ) must be assigned to your network board.
Each manufacturer's network board is unique in the available interrupts
it offers (refer to the network board's manual to determine its interrupt
options). The following table may help in selecting an interrupt option
that is not currently being used in your system. It is also possible to
get a specific reading of your interrupts from a computer utility
program.
┌───────┬────────────┬──────────────────┐
│ IRQ │ XT │ AT (286,386,486) │
├───────┼────────────┼──────────────────┤
│ 0 │ │ TIMER OUTPUT 0 │
├───────┼────────────┼──────────────────┤
│ 1 │ │ KEYBOARD │
├───────┼────────────┼──────────────────┤
│ 2 │ EGA/VGA │ EGA/VGA │
├───────┼────────────┼──────────────────┤
│ 3 │ COM2 │ COM2 │
├───────┼────────────┼──────────────────┤
│ 4 │ COM1 │ COM1 │
├───────┼────────────┼──────────────────┤
│ 5 │ HARD DISK │ LPT2 │
├───────┼────────────┼──────────────────┤
│ 6 │ │ FLOPPY DISK │
├───────┼────────────┼──────────────────┤
│ 7 │ LPT1 │ LPT1 │
├───────┼────────────┼──────────────────┤
│ 8 │ │ REAL TIME CLOCK │
├───────┼────────────┼──────────────────┤
│ 9 │ │ │
├───────┼────────────┼──────────────────┤
│ 10 │ │ │
├───────┼────────────┼──────────────────┤
│ 11 │ │ │
├───────┼────────────┼──────────────────┤
│ 12 │ │ │
├───────┼────────────┼──────────────────┤
│ 13 │ │ COPROCESSOR │
├───────┼────────────┼──────────────────┤
│ 14 │ │ HARD DISK │
├───────┼────────────┼──────────────────┤
│ 15 │ │ │
└───────┴────────────┴──────────────────┘
Note: For best results, you should try using a free interrupt line. If
the chart shows that you are using all possible interrupts, it is
possible that your Ethernet or other network board may use an interrupt
that is already being used. For example: many programs do not address
LPT1 on the interrupt level; hence, if you have no free interrupts, it is
possible to assign two functions to the same interrupt.
SOLUTION
NA