home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
-
-
-
-
-
-
-
- CTS IRQInfo (TM)
-
- User Guide
-
-
-
- Computer Telecommunication Systems, Inc.
- 3847 Foxwood Road, Suite 1000
- Duluth, Georgia 30136-6100 USA
-
- Voice: 1-770-263-8623
- FAX: 1-770-263-0124
- Email: support@comminfo.com
- or 76662,2315 (CompuServe)
- World Wide Web: http://www.comminfo.com
-
-
-
-
-
- Copyright 1994-95 Computer Telecommunication Systems, Inc. All
- Rights Reserved.
-
- No part of this User Guide may be reproduced, transmitted,
- transcribed, stored in a retrieval system, or translated into any
- language (natural or computer), in any form or by any means,
- without the prior written permission of Computer
- Telecommunication Systems, Inc.
-
- Information in this manual is subject to change without notice
- and does not represent a commitment on the part of Computer
- Telecommunication Systems, Inc.
-
- Computer Telecommunication Systems, Inc. may make improvements
- and/or changes in the manual and/or in IRQInfo at any time.
-
- Trademarks and Copyrights
- =========================
- IBM(R) and PS/2(R) are registered trademarks of International
- Business Machines Corporation.
-
- The CTS Serial Port Utilities(TM), IRQInfo(TM), IRQInfo PRO(TM),
- SwapIRQ(TM) and AT Command Test(TM) are trademarks of Computer
- Telecommunication Systems, Inc.
-
- SoundBlaster(TM) is a trademark of Creative Labs, Inc.
-
-
- DISCLAIMER OF WARRANTY
-
- USERS OF THIS SOFTWARE MUST ACCEPT THIS DISCLAIMER OF WARRANTY:
-
- THIS SOFTWARE IS SUPPLIED AS IS. COMPUTER TELECOMMUNICATION
- SYSTEMS DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF
- MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH
- RESPECT TO THE SOFTWARE AND THE ACCOMPANYING WRITTEN MATERIALS.
-
- NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL
- COMPUTER TELECOMMUNICATION SYSTEMS OR ITS SUPPLIERS BE LIABLE FOR
- ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES
- FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF
- BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF THE
- USE OF OR INABILITY TO USE THIS COMPUTER TELECOMMUNICATION
- SYSTEMS PRODUCT, EVEN IF COMPUTER TELECOMMUNICATION SYSTEMS HAS
- BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME
- STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
- CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT
- APPLY TO YOU.
-
-
-
-
-
-
-
-
- Introducing IRQInfo . . . . . . . . . . . . . . . . . . . . . 4
-
- How a Computer Uses IRQs . . . . . . . . . . . . . . . . . . 4
- Common Interrupt Problems . . . . . . . . . . . . . . . 5
-
- Installing IRQInfo . . . . . . . . . . . . . . . . . . . . . 6
-
- Running IRQInfo . . . . . . . . . . . . . . . . . . . . . . . 6
-
- The System Interrupt Table . . . . . . . . . . . . . . . . . 7
- Used in This System . . . . . . . . . . . . . . . . . . 7
- Yes - (device detected) . . . . . . . . . . . . . . 7
- Yes - Com# (Mouse) . . . . . . . . . . . . . . . . 7
- Yes - (?) LPT# . . . . . . . . . . . . . . . . . . 7
- Yes - Unknown . . . . . . . . . . . . . . . . . . . 8
- Driver - (driver name) . . . . . . . . . . . . . . 8
- TSR - (TSR name) . . . . . . . . . . . . . . . . . 8
- Possibly - Enabled but not active . . . . . . . . . 8
- * Nothing Detected . . . . . . . . . . . . . . . . 8
- No - Not Installed . . . . . . . . . . . . . . . . 8
- Available . . . . . . . . . . . . . . . . . . . . . . . 9
- Never . . . . . . . . . . . . . . . . . . . . . . . 9
- No-In Use . . . . . . . . . . . . . . . . . . . . . 9
- ??? . . . . . . . . . . . . . . . . . . . . . . . . 9
- Shared? . . . . . . . . . . . . . . . . . . . . . . 9
- Conflict? . . . . . . . . . . . . . . . . . . . . . 9
- Yes . . . . . . . . . . . . . . . . . . . . . . . . 9
-
- IRQInfo Command Line Options . . . . . . . . . . . . . . . . 9
-
- Tips for Using IRQInfo . . . . . . . . . . . . . . . . . . . 10
-
- Using LPT# IRQs . . . . . . . . . . . . . . . . . . . . . . . 11
-
- Devices Not Detected . . . . . . . . . . . . . . . . . . . . 11
-
- The IRQInfo Order Form . . . . . . . . . . . . . . . . . . . 13
-
-
-
-
- - 4 -
-
- Introducing IRQInfo
- ===================
- IRQInfo is a powerful interrupt identification tool. If you have
- gone through the frustration of using a utility that incorrectly
- identifies or "guesses" at the IRQs used by devices, then you can
- appreciate how important accuracy is in a tool of this type.
- IRQInfo focuses on identifying what IRQs are being used by the
- devices in the computer.
-
- IRQInfo goes through eight separate tests to identify the IRQs
- used on the computer. By using a multiple-test approach, maximum
- accuracy and device coverage is assured. The biggest difference
- between IRQInfo and similar utilities is that IRQInfo never
- assumes anything. When an IRQ is not detected, then you are told
- that it wasn't.
-
- Because of the way IRQInfo works with the computer when it runs,
- it must be run from a true DOS environment with the DOS device
- drivers loaded prior to running IRQInfo. This provides maximum
- accuracy in detecting the system interrupts.
-
-
- How a Computer Uses IRQs
- ========================
- Computer systems use interrupts as signals between the hardware
- and the software. Devices are assigned to use specific interrupt
- lines (similar to "phone lines") when the board is installed. The
- hardware device creates an Interrupt ReQuest (IRQ) by signalling
- on the interrupt line selected by the jumper or switch. The
- software using the device must be set up to watch the same
- interrupt line. When the software "sees the request", it stops
- whatever it is doing (it is "interrupted") and does whatever
- action is required by that particular device.
-
- NOTE: The terms "interrupt" and "IRQ" are generally
- interchangeable - the board uses a particular interrupt line to
- signal an IRQ. These are commonly discussed as "IRQ #", where "#"
- is the number of the interrupt line used.
-
- There are 8 interrupt lines on a IBM PC/XT, and 16 on an ISA or
- EISA computer. Several of these lines are "used" internally in
- the computer and are not available for add-in devices. On a
- PC/XT, only IRQs 2-7 are available for add-in devices. With a
- common configuration of two serial ports (IRQs 3&4), a hard disk
- (IRQ 5), floppy disk (IRQ 6) and line printer (IRQ7), only IRQ 2
- is free (though IRQ 7 can often be used...see the section on
- "Using LPT# IRQs".)
-
- When IBM introduced the ISA (AT computer bus), it expanded the
- number of IRQs available by adding a second "interrupt
- controller". The interrupt controller is a chip that detects when
- an interrupt line has been activated by the hardware, and then
- tells the software to handle, or "service" the interrupt. The
-
-
-
- - 5 -
-
-
-
- software that services the interrupt is called an Interrupt
- Service Routine, or ISR.
-
- Each interrupt controller can handle 8 interrupt lines, so the
- IBM AT and all compatible systems support 16 interrupt lines. Of
- these, only 11 are available on the system bus for use by
- devices. The other 5 (IRQs 0-2, 8 and 13) are used internally by
- the computer system.
-
- Common Interrupt Problems
- -------------------------
- Computer systems use interrupts to operate more efficiently.
- Interrupts allow the processor to keep working while a slow
- device performs an operation. When the slow device has finished
- it's task, then it can tell the processor that the task is
- finished by generating an IRQ.
-
- For example, the disk drive is much slower than the processor.
- When you enter the command to run IRQInfo, the operating system
- tells the disk to find "IRQInfo.EXE". When the disk controller
- locates the file, it signals the operating system ("Here it is!")
- by using the interrupt. The software (the ISR for the disk drive)
- then reads the information from the controller.
-
- This brings up a key point, and the source of many interrupt
- problems on computers: each interrupt line has one (and only one)
- ISR at any one time. For the computer system to work properly,
- the ISR for each interrupt line must match the device using that
- line. ISRs are "device specific"; an ISR for the Com port cannot
- deal with a disk drive and the ISR for the disk drive cannot
- service a sound card. The device will not work if the ISR does
- not support the device. So, when installing a new device in the
- system, you must make sure that: 1) the device is installed on an
- IRQ that isn't already in use; 2) all of the software which uses
- the device is set to use the same IRQ; and 3) no other software
- is going to try and use this interrupt to control a different
- device.
-
- When the computer system BIOS loads, it sets up default ISRs for
- the system, including those needed for the keyboard, disk drives,
- the system clocks, and so on. When you start an application in
- DOS, it may replace one or more of the default ISRs with new
- ones. For example, most DOS communication applications install a
- new ISR for the Com ports. This is why it is very important to
- set the software to use the correct IRQ. If it isn't set
- properly, it will fail since it cannot detect the interrupt
- generated by the modem.
-
- Windows, Win95 and OS/2 install drivers when they start up which
- replace the default ISRs. Some drivers "auto-detect" the IRQs
- used by their devices, and others have to be installed and set up
- properly to work. For example, in Windows, you must set the
- interrupt for the "non-standard" Com ports through the control
- panel (ports, advanced settings).
-
-
-
- - 6 -
-
-
-
- The other common problem is that only one device can use an IRQ
- at any time on most computers (EISA and PS/2 systems support
- interrupt sharing, but most systems, cards and software do not.)
- In general, try to set up your system with one device per IRQ,
- and, if at all possible, use the default IRQs for the devices.
-
-
- Installing IRQInfo
- ==================
- IRQInfo may be the easiest program to use that you've seen in a
- while. IRQInfo is normally placed in a subdirectory on your hard
- disk. The following instructions assume you will put IRQInfo in a
- directory named "IRQINFO"
-
- 1. Create an "IRQInfo" subdirectory on your hard disk using the
- DOS Make Directory (MD) command:
-
- Example: C>MD IRQInfo <Enter>
-
- NOTE: <Enter> means to press the Enter (Return) key.
-
- 2. Change the default directory to the directory you created
- using the DOS Change Directory (CD) command:
-
- Example: C>CD IRQInfo <Enter>
-
- 3. Copy the distribution files to the IRQInfo directory. If the
- distribution files are on a floppy diskette in drive A, you
- would enter:
-
- Example: C:\IRQINFO>COPY A:\*.* <Enter>
-
- If a README.TXT file was copied to the hard drive, then read this
- file for additional information not included in this User Guide.
- IRQInfo is ready to run.
-
- Running IRQInfo
- ===============
- If the computer is currently running Windows, you will need to
- shut down all of the Windows applications and exit to DOS from
- the Program Manager. If the computer is running OS/2 or another
- operating system or environment (including DesqView), then re-
- boot into DOS or run from the reboot to DOS Mode of Windows 95.
-
- When you load DOS, make sure that device drivers are loaded (do
- NOT do a "clean boot"). Because of the wide variety of devices,
- IRQInfo may use the device drivers to identify some IRQs that are
- used by the devices controlled by the drivers. If the computer is
- connected to a network, please log into the network. This
- activates the IRQ used by some network cards.
-
- To run IRQInfo, enter:
-
- IRQInfo <Enter>
-
-
-
- - 7 -
-
-
-
- IRQInfo will start running. After several seconds, IRQInfo will
- alert you that it is ready to test the line printer interrupts.
- Press the "Enter" key to test the printer ports, or press the
- "Esc" key to skip the printer interrupt test. IRQInfo then spends
- a few seconds testing the system, displays the "System Interrupt
- Table", and quits.
-
-
- The System Interrupt Table
- ==========================
- The System Interrupt Table contains 4 columns of information:
-
- 1) the IRQ numbers supported on this computer;
- 2) the "standard" or common use of that particular IRQ;
- 3) how the IRQ is being used in this computer;
- 4) the status of the IRQ.
-
- NOTE: The Sample Table referenced below is not included in this
- version of the User Guide.
-
- The first two columns describe the IRQ number and the typical use
- of each interrupt. If you have an installation choice to make,
- try to use the default or standard configuration. In general,
- we've found that users have fewer problems with their system and
- software if the most common settings are used.
-
- Used in This System
- -------------------
- This column describes exactly how each IRQ is being used in this
- computer. There are a number of different messages that can
- occur:
-
- Yes - (device detected)
- -----------------------
- This interrupt is in use by the device(s) listed in this
- column. In the example table, IRQs 0-9 and 14 are in use
- with the devices listed.
-
- Yes - Com# (Mouse)
- ------------------
- This message indicates that a serial mouse was detected on
- the IRQ and Com port indicated.
-
- Yes - (?) LPT#
- --------------
- It is not possible to always detect the line printer port(s)
- IRQs properly. When IRQInfo cannot detect the actual IRQ
- used, it will display "(?)" beside the LPT# while displaying
- the default IRQ used by the printer. When the actual IRQ is
- detected by IRQInfo, no "(?)" appears.
-
-
-
-
- - 8 -
-
-
- IRQ 7 in the sample table shows that the LPT1 IRQ was
- actually detected, while IRQ 5 shows the IRQ that is
- normally used by LPT2. Also note that IRQ 5 may have a
- conflict, as a SoundBlaster compatible card is also using
- this IRQ.
-
- NOTE: You can ensure that IRQInfo always detects the actual
- printer IRQ by using a printer loopback plug.
-
- Yes - Unknown
- -------------
- This IRQ is enabled and active, but IRQInfo was not able to
- determine what device is using the IRQ. You may be able to
- figure it out by comparing the devices detected by IRQInfo
- with the list of equipment on the computer.
-
- Driver - (driver name)
- ----------------------
- The IRQ is under the control of the driver listed. This
- normally indicates that the driver is controlling a device
- using this IRQ. Do not attempt to use this IRQ for a new
- device. The driver name usually gives a good description of
- the device that is being controlled.
-
- TSR - (TSR name)
- ----------------
- The IRQ is under the control of the Terminate & Stay
- Resident (TSR) software listed. This normally indicates that
- the TSR is controlling a device using this IRQ. Do not
- attempt to use this IRQ for a new device. You should be able
- to identify the device being controlled from the name of the
- TSR.
-
- Possibly - Enabled but not active
- ---------------------------------
- This is an interesting situation. For some reason, this
- interrupt has been enabled, but there is no activity on the
- interrupt line, and no device was detected as using this
- interrupt. Most of the time, this message is caused by the
- BIOS leaving the interrupt enabled after "booting up" the
- computer.
-
- * Nothing Detected
- ------------------
- IRQInfo did not detect any use of this interrupt. This IRQ
- is available for additional devices.
-
- No - Not Installed
- ------------------
- This message will only appear on IRQ 13 when a numeric
- coprocessor is not installed.
-
-
-
- - 9 -
-
-
-
- Available
- ---------
- This column shows the current status of the IRQ. There are
- several different messages that may appear here:
-
- Never
- -----
- These IRQs are used internally in the computer and are not
- available for use by any add-in devices. These IRQs are not
- available on the system bus.
-
- No-In Use
- ---------
- This IRQ is definitely being used by a device in the
- computer.
-
- ???
- ---
- This interrupt was detected as having been activated at one
- time, but no device was detected. See the description above
- for "Possibly - Enabled but not active". This interrupt is
- probably available for use by a new device - but try to use
- the IRQs listed as "Yes" (available) first.
-
- Shared?
- -------
- If multiple devices are detected as using the same IRQ on an
- EISA computer system, then the IRQ may be shared between the
- two devices. Note that the devices and software must be
- properly configured to support IRQ sharing in this manner.
-
- Conflict?
- ---------
- If multiple devices are detected as using the same IRQ on an
- ISA or PC/XT computer system, then an IRQ conflict may
- exist.
-
- Yes
- ---
- The IRQ is not being used, and is available for an add-in
- card.
-
-
- IRQInfo Command Line Options
- ============================
- IRQInfo options are controlled by "command line switches".
- Command line switches are program options that you place on the
- command line. Each option is preceded by a slash character "/".
- These "switches" control the IRQInfo software the way a hardware
- switch controls the options on a board.
-
-
-
- - 10 -
-
-
-
- Program Help - /?
- -----------------
- A short help screen is displayed when you enter the command
- line:
-
- IRQInfo /? <Enter>
-
- Copy IRQInfo Results to a File
- ------------------------------
- IRQInfo will create a "log file" that contains a copy of all
- screen displays. To create the log file IRQINFO.LOG, enter
- the command line:
-
- IRQInfo /L <Enter>
-
- If you wish to add to an existing log file, use the command
- line:
-
- IRQInfo /LA <Enter>
-
- To print a copy of the log file on the system printer, use
- the command line:
-
- IRQInfo /P <Enter>
-
- NOTE: printing a copy of the log file, and then taping the
- report to the inside cover of the computer is an excellent
- way to keep track of what devices are installed.
-
-
- Tips for Using IRQInfo
- ======================
- IRQInfo is a tool to assist with installing new equipment in the
- computer. Think of IRQInfo as a checkpoint in each step of the
- device installation. Run "IRQInfo /P" before starting to create a
- printed record of what is already in the computer and to assist
- in planning how you will proceed.
-
- There are two things to remember when installing a device: 1) one
- of the IRQs supported by the device must be available; and 2) the
- software that uses the board must support the IRQ used.
-
- After the initial IRQInfo printout, examine the report and see if
- the device will just "drop in" to an unused IRQ. If so, follow
- the installation instructions that came with the device and
- continue with the installation. When finished, run "IRQInfo /P"
- once again to create a record of the new setup.
-
- In many cases, you will be required to change an IRQ assignment
- for another device (or possibly remove it) before installing the
- new device. This is a time for careful thought before proceeding.
- Determine what device IRQ(s) need changing. Remember to verify
- that the software that uses the device(s) will support the IRQ
- change. When you are ready to proceed, take it one step at a
-
-
-
- - 11 -
-
-
-
- time. After each change, complete the installation of the device
- changed and make certain it is fully operational. Then run
- "IRQInfo /P" again to check the current system setup. By testing
- and verifying each step, you can save yourself literally hours of
- anguish trying to sort out problems later.
-
-
- Using LPT# IRQs
- ===============
- The IRQs that are "used" by the printer (LPT) port(s) on the
- computer are often available if you are using DOS or Windows
- (This discussion does not apply to OS/2 users - OS/2 uses the
- printer interrupts). With rare exceptions, DOS and Windows do not
- use the printer interrupts for printing - meaning that the IRQs
- allocated for these devices can often be used for another device.
- For example, many sound cards and accompanying software use of
- IRQ 5 and/or IRQ 7 - the same IRQs normally used by LPT2 and
- LPT1. When a card is installed using the same IRQ as one of the
- printer ports, IRQInfo will show this as a possible conflict. As
- long as both devices continue to work for you as expected, you
- may ignore the conflict message.
-
- Devices Not Detected
- ====================
- It is possible that IRQInfo will not detect a device that is
- installed in the computer. If you run into this situation:
-
- 1. Make certain that the DOS device driver (if any) is loaded for
- the device.
-
- 2. If the device is a network card, log into the network to
- activate the card.
-
- 3. Run IRQInfo several times to verify that the device is not
- detected.
-
- 4. If no DOS device driver exists for this card (for example, a
- network card running a Windows For Workgroups Network), you will
- need to obtain IRQInfo PRO to test this system.
-
- If the problem persists, please send the following information to
- us:
-
- 1. A complete description (manufacturer, model number,
- version number and brief description) of the device.
-
- 2. Copies of the following files: CONFIG.SYS, AUTOEXEC.BAT
- from the boot disk, and SYSTEM.INI from the Windows
- directory.
-
- 3. The IRQInfo version number you are running (this is
- displayed when you run IRQInfo.)
-
-
-
- - 12 -
-
-
-
- 4. Please send this information via Email to CTS at internet
- address 76662.2315@compuserve.com or on a diskette to 3847
- Foxwood Road, Suite 1000, Duluth, GA 30136-6100 (USA).
-
- We will attempt to update IRQInfo for any undetected devices that
- are reported.
-
- Association Of Shareware Professionals Member
- =============================================
-
- _______
- ____|__ | (R)
- --| | |-------------------
- | ____|__ | Association of
- | | |_| Shareware
- |__| o | Professionals
- -----| | |---------------------
- |___|___| MEMBER
-
-
- This program is produced by a member of the Association of
- Shareware Professionals (ASP). ASP wants to make sure that the
- shareware principle works for you. If you are unable to resolve a
- shareware-related problem with an ASP member by contacting the
- member directly, ASP may be able to help. The ASP Ombudsman can
- help you resolve a dispute or problem with an ASP member, but
- does not provide technical support for members' products. Please
- write to the ASP Ombudsman at 545 Grover Road, Muskegon, MI
- 49442-9427 USA, FAX 616-788-2765 or send a CompuServe message via
- CompuServe Mail to ASP Ombudsman 70007,3536.
-
-
- The IRQInfo Order Form
-
- Name: ______________________________ Telephone: ____________________
-
- Company: ________________________________ E-mail ID: ____________________
-
- Address: __________________________________________________________________
-
- __________________________________________________________________
-
- QTY Description Price Subtotal
- === =========== ===== ========
- ___ IRQInfo $24 ________
-
- ___ IRQInfo PRO 35 ________
-
- ========
-
- Sub-Total $________
-
- Sales Tax: Georgia residents add 5% $________
-
- Shipping & Handling: $ 4.00
- =========
-
- TOTAL (US dollars, please) $________
-
- PAYMENT METHOD: Check __ Money Order __ EuroCheq __ Discover __
- Visa __ MasterCard __ Am. Express __ Purchase Order ($50 min) __
- ========================================================================
- CREDIT CARD INFORMATION
-
- Name as it appears on the card: _________________________________
-
- Card No. ________ ________ ________ ________ Expires ___/___
-
- Cardholder signature: ___________________________________________
-
- Please send to, FAX, Email or call:
- +--------------------------------------------------------------------+
- | Computer Telecommunication Systems, Inc. |
- | 3847 Foxwood Road, Suite 1000 |
- | Duluth, Georgia 30136-6100 USA |
- +--------------------------------+-----------------------------------+
- | Telephone | Electronic Mail |
- | --------- | --------------- |
- | Orders: 1-800-380-2666 | Internet:sales@comminfo.com |
- | Voice: 1-770-263-8623 | or http://www.comminfo.com |
- | FAX: 1-770-263-0124 | CompuServe: 76662,2315 |
- +--------------------------------+-----------------------------------+
- Federal TaxID: 58-1880693. Prices are subject to change without notice.
-
-
-