This section describes how to test the MCS-l controller, the installation of the device driver, and the tape drive and cable connections.
2.5.1 Testing the Device Driver Installation
500521 H
To determine if the device driver is being loaded correctly, reboot the system and watch the display. When the MCS-l device driver loads, the system displays an identifying message. The driver then looks for the MCS-l, and, if found, runs some diagnostic tests on it to determine its operational status. It is not necessary to have a tape drive online or even connected to the MCS-l for the driver to be initialized properly. Following these diagnostics, the device driver will report whether or not it installed itself.
If everything went OK, the following message will appear:
Found 512 Kbytes of 16-bit memory, testing - passed USing interrupt 15, I/O address 380
If errors were detected, the device driver will display a brief error message identifying the cause of the problem. The device driver will not be loaded and will you will not be able to use any of
2-5
Chapter 2: MCS-1 Installation
2.5.2
2-6
the tape programs. The following paragraphs list some of the more common error messages, their causes, and corrective action you can take.
1. Nine track controller not found at specified base address Driver not installed
CAUSE #1 -The base I/O address given on the device driver command line differs from the address actually set by the MCS-1 switches.
FIX #1-Either change the device driver command line in your CONFIG.SYS file, or change the address switch settings on the MCS-1. In either case, the two must agree if the device driver is to communicate with the controller.
CAUSE #2 - The MCS-1 board is defective or not properly seated in the motherboard connectors.
FIX #2 -Reset or replace the MCS-1 board.
2. I/O conflict at selected address Driver not installed
CAUSE - The base I/O address set by jumpers on the MCS-1 is also being used by another device in the computer.
FIX - Since no two devices in a PC can share the same base I/O addresses, the address used by one of the devices must be changed. If the MCS-1 address is changed, the corresponding device driver line in your CONFIG.SYS file must also be changed. Refer to Section 2.2 for details.
3. Interrupt failure. Already in use?
Driver not installed.
CAUSE - The interrupt channel use by the MCS-1 is being used by another device in the computer, or is not working correctly.
FIX - Change the interrupt channel either of either the MCS-1 or the other device which is using the same interrupt. If the MCS-1 interrupt channel needs to be changed, the appropriate line in the device driver line in your CON-FIG.SYS file must also be changed. Refer to Section 2.2 for details.
Using MCSl DIAG.EXE
MCS1DIAG.EXE is used to test both the MCS-1 controller and the tape drive. For this part of the test procedure, the tape drive does not need to be connected.
NOTE
Online help is available by choosing H from the main menu.
1. Go to the subdirectory in which the application programs reside and type:
mcsldiag
2. If the device driver was correctly installed, an opening screen like the one shown in Figure 2-2 should appear. If so, skip ahead to Section to test the tape drive.
3. If the device driver was not correctly installed, a screen like the one shown in Figure 2-3 will appear instead, and the tape subsystem cannot be used. In this
500521 H
2.5.3
500521 H
Testing the Installation
ttcS1D iag u4. 22 Copyright eCl 1998-1'132 by ~lstar Corporation
Controllers.lDriuers
Installed: eFl Fast tape read-wri te checkout
#1 at 3881'15 PASSED (Ll Long tape read-write test (Cl Controller card test only
CTl Test controller to tape driue connection (Sl Se lect dr iuer to test
(Hl Help Using Controller 1 (Ql Quit
Enter cho ice )
~~tries
~ite Head This pass:
This test:
Figure 2-2 MCS1 DIAG Main Screen (driver correctly installed)
case, the MCS-1 can still be tested (if it is installed) to verify that it is working.
In order to test the MCS-l at this point, the following information is required:
a The base I/O address, set by the four switches at the lower left comer of the MCS-1 (default setting is 380H);
b. The interrupt channel number (default is 15).
If either one of these settings has been changed, use the current settings. If the system has just been unpacked and the settings have not been changed, use the factory defaults.
4. Choosing C tests the MCS-1. At the end of the test, the following message will appear on the top line if the test was successful:
Controller test PASSED
Correcting MCS-l Controller Problems
Some problems can be traced to the MCS-l, and MCSIDIAG will report any MCS-l problems it finds. If you experience any difficulties, try the following:
1. Verify the MCS-1 board is properly installed.
a. Remove the MCS-l and clean the connector contacts at the bottom of the board with a pencil eraser so that they are bright.
b. Place the MCS-l on a flat surface and press down on all chips which are in sockets to ensure that they are well seated.
c. Reinstall the MCS-l in the computer, taking care that it seats fully in the expansion slot connector.
2-7
Chapter 2: MCS-1 Installation
2.5.4
t1CS1Diag v4.ZZ Copyright (e) 19'39-1992 by Qualstar Corporation roblem: MCS Deuice Driuer (MCSTAPE.S~S) Not Loaded Controllers/Drivers
Installed:
None The tape deuice driuer is not loaded.
Th is is because:
a) ~ou hauen"t run the installation prograJI (or instal led the deuice driuer yourselr);
b) The deuice driver was instal led but was not configured correctly;
c) There is a problCJI with the controller card;
d) The controller card is not installed.
IF the controller card IS installed" you can run
SOllIe tests on it which don"t need the deuice driuer.
11---Jie'tries Do you want to run these tests now (~A1)?
Write Read This pass:
This test:
Figure 2-3 MCS1 DIAG Main Screen (driver not correctly installed)
2. Verify the MCS-I base I/O address does not conflict with another device. See Section 2.2 (page 2-1) for more information. If the test fails for any reason, MCSIDIAG will try to provide an explanation.
a. If the message indicates there may not be a controller at the given address, double-check the base I/O address to see if the address actually set on the MCS-l switches is the same one entered in MCSIDIAG. If it is not, run MCS IDIAG again and enter the correct address.
b. For other remedies, tum to Section 2.5.3 (page 2-7).