Connecting Exabyte Products to Operating Systems

HOOKUP

COMPENDIUM OF INFORMATION TO CONNECT EXABYTE

PRODUCTS TO VARIOUS OPERATING SYSTEMS

REVISION R 7/20/94

AUTHOR - GARY SECHRIST

HOOKUP

COMPENDIUM OF INFORMATION TO CONNECT EXABYTE

PRODUCTS TO VARIOUS OPERATING SYSTEMS

REVISION R 7/20/94

AUTHOR - GARY SECHRIST

REVISION CONTROL SHEET

Revision H * Section 3.2.2 page 6, corrected block size for 4200/4200C.

* Section 3.2.2 page 6, added note regarding block size for

4200/4200C on Sun systems.

* Section 8.4.5 page 20, Added note regarding support of BRU

command on SGI systems..

* Added Section 8.4.4.1 and .2 to add more instruction for SGI /usr/sysgen/master.d file.

* Added Section 8.4.6.1 and .2 to add more instruction for SGI /dev/MAKEDEV file.

* Section 8.4.6.2 added Reversed order for devices to start with lowest density and added note that user may configure in any order.

* Section 8.4.4.2 Simplified entry for each drive.

Revision J * Section 3.3 modified 2501 to minimum code level of 21 and

jumper to 512.

Revision K * Added instructions for NEXT Cube System.

Revision L * Added Bootable device information for HP9000

* Added Windows NT information

Revision M * Added SCOUnix drive installation.

Revision N * Added procedure for SGI Revision 5.1.1.2 and higher

Revision O * Corrected SunOS ST_CONF.C

* Corrected SGI /var/sysgen/master.d/scsi name

* Reworked SGI

Revision P * Corrected 2501 entry for SunOS

* Added more info to IBM RS6000 data, Section 7.

Revision Q * Added EEimage info for booting to IBM RS6000 on page 18.

* Added support differences for HP 700 verus 800 series.

Revision R * Corrected Entry for EXB-2501 on Sun 4.1.2 and added format

command.

CONTENTS

SUBJECT PAGE

1. OVERVIEW OF PAPER ............................................ 5

2. Product Notes ................................................ 5

3. SUN ....................................................... 5

3.1 SUN Solaris 2.1/2.2 ...................................... 5

3.2 Sun Solaris OS ........................................... 6

3.2.1 Sun Solaris 2.1/2.2 ................................. 6

3.2.2 Solaris 2.3 ......................................... 6

3.2.2.1 Global Tape-config-list property

for Solaris 2.3: ................................. 6

3.2.2.2 TID Specific Tape Devices for Solaris 2.3 ........ 8

3.2.2.3 DUMP PARAMETERS for Solaris 2.3 .................. 9

3.2.2.4 SUN Solaris 2.3 Tape Drive Code Levels ........... 10

3.2.3 Solaris 2.4 ......................................... 10

3.3 SUNOS .................................................... 10

3.3.1 SUNOS 4.1.2 ......................................... 10

3.3.2 SUNOS 4.2 ........................................... 10

3.3.3 ST_CONF.C on SUNOS Systems Configuration Sheet ....... 11

3.3.4 TAR Commands for Sun OS .............................. 13

4. HP ....................................................... 15

4.1 HP 1000 System ........................................... 15

4.2 HP 9000 System ........................................... 15

5. SCO UNIX 3.2 version 4.2 .................................... 15

6. DEC ......................................................... 18

6.1 DEC VAX 4000 Running VMS 5.5-2 ........................... 18

6.2 DEC VAX 4000/VLC ......................................... 18

7. IBM ......................................................... 18

7.1 RS6000 ................................................... 18

7.1.1 RS6000 AIX Revision Levels ............................ 18

7.1.2 Firmware versions Tested ............................. 18

7.1.3 Quick Installation .................................... 19

7.1.4 Smit Setup ............................................ 19

7.1.5 Density Values ........................................ 20

7.1.6 Booting From Exabyte TApe Drive ....................... 20

7.1.6.1 EXB-8200 .......................................... 20

7.1.6.2 EXB-8505/8205 ..................................... 20

7.1.6.3 General Boot Information .......................... 20

7.3 IBM support of EXB-120/60/10/10e ......................... 20

8. SGI ......................................................... 21

8.1 Configuration Procedure for SGI OS IRIX 4.0.5/ 5.1/ 5.2 ... 21

8.2 Applicable SGI Systems ................................... 21

8.3 Option to Modifying Drivers .............................. 21

8.4 Adding Exabyte Tape Products to IRIX ......................21

8.4.1 The Important Files .................................. 21

8.4.2 Define By TID ........................................ 21

8.4.3 Symbolic Link ........................................ 21

8.4.4 Adding Exabyte 8MM Tape Drives to

/usr/sysgen/master.d/tpsc ............................ 21

CONTENTS

SUBJECT PAGE

8.4.4.1 Adding Exabyte Tape Drives to

/usr/sysgen/master.d/tpsc .......................... 21

8.4.4.2 Master.d Modification .............................. 23

8.4.5 Adding Exabyte 4MM Tape Drives to

/usr/sysgen/master.d/tpsc ............................. 24

8.4.6 Additions to /dev/MAKEDEV ............................. 24

8.4.6.1 Select the /dev/MAKEDEV File ....................... 25

8.4.6.2 /dev/MAKEDEV File Modification ..................... 25

8.4.7 Contents of /dev/rt and /dev/rmt ...................... 29

8.4.8 Testing SGI Device Additions .......................... 29

8.5 Adding Exabyte Tape Products to IRIX 5.2 ................... 30

8.5.1 TAR Command ............................................ 30

8.5.2 Modifying Files ........................................ 30

9. NEXT Cube System ............................................ 33

9.1 Exabyte Code ............................................. 33

9.2 SCSI ID .................................................. 33

9.3 Host Test for Device ..................................... 33

9.4 Procedure ................................................ 33

9.5 Using Monitor to Set Density ............................. 34

9.6 Test Ran ................................................. 34

10. SCO UNIX ................................................... 34

11. SUNSOFT .................................................... 34

12. LEGATO SYSTEMS ............................................. 34

13. CHEYENNE .................................................... 34

14. PC SYSTEMS .................................................. 35

14.1 Novell .................................................. 35

14.2 Cheyenne ................................................ 35

14.3 Novastor ................................................ 35

14.4 Systron ................................................. 35

14.5 Microsoft ................................................ 35

14.6 Corel ................................................... 35

14.7 Microsoft Windows NT ..................................... 36

14.7.1 Test Configuration ..................................... 36

14.7.2 Installing Drives into Operating Sys. .................. 36

14.7.3 Backup Operation ....................................... 36

14.7.4 Restore Operation ...................................... 37

15. Macintosh Products ......................................... 37

15.1 Novastor ................................................ 37

15.2 Optima .................................................. 37

15.3 Surf City ............................................... 37

EXABYTE HOOKUP INFORMATION

REVISION L - 3/31/94

1. OVERVIEW OF PAPER

This document is a compendium of Exabyte information gathered from many sources. It is meant as a resource tool to answer the many questions asked regarding Exabyte products on various systems. Our thanks to all those who have contributed.

2. Product Notes

EXB-8200 Code Configuration

The EXB-8200's operating firmware is located on two proms. The Control Code is located on the MX card, the second from the last card as seen from the front of the unit. The Servo prom is located on the Servo Card which is the large mother board across the bottom of the unit. On very earily units, the prom can not be seen and access is by removing the lower cover and removing the Servo Card. In later versions, the prom was

EXB-8500/8505/8205 Code configuration

EXB-2501

Starting with rev 21, J5/5&6 jumpered will set block size default to 512 bytes. Jumper out default is 1024 bytes. This jumper is mandatory for all

Sun 4C or 4M systems. It will result in data overruns otherwise.

Rev has J1 pins 1 and 4 jumpered for non-compression and out for compression. Previous revisions used these pins for SCSI-1, SCSI-2 selection. So take care when upgrading code !

EXB-4200C Rev 139 and higher supports selection of compression mode in the Mode Select command non-paged format using the Density byte.

3. Sun

There are two major classes of Sun systems, Sun4 and Sun4c. SUN4 are older systems (4/110, 4/260, & 4/470) which are VME based. Contact Exabyte for information regarding these systems. SUN4C are the newer UNIX products such as 4/670 4/690, SLC, IPC, IPX, and all the SPARCstations. The information below is regarding this class of products.

3.1 SUN Solaris 2.1/2.2

Solaris 2.1/2.2 supports the EXB- 8200, EXB- 8500 and the EXB- 8505. Solaris 2.1/2.2 does not have a means to add products that can be recognized by the systems. Therefore, to use an EXB- 8500C, install eeimage 8CE- 0189 which will allow the EXB- 8500C to report itself as an EXB- 8505 in the product field of the inquiry command response. This would be done for example when using the EXB- 8500C in any EXB- 10/i/e and EXB- 60 /120 products. 8CE-0189 is an generic version of the Sun eeimage and has the following features:

Super Hot Button - Immediate unload without rewinding.

8200 style space command response.

Does not Queue commands but returns Busy instead.

The 8205 can also be used with eeimage 8VE- 0168 but there is no ability to turn compression off in write mode. The 8205 will automatically enable or disable compression in the read mode depending on whether the data is compressed or not. It is possible using Exabyte's CTS Monitor program to turn compression to always off using the option menu.

3.2 Sun Solaris OS

The newer Sun Operating system did not have a means of adding devices until

release 2.3. Special EEimages are required to add devices prior to 2.3.

3.2.1 Sun Solaris 2.1/2.2

PRODUCT MXCODE SVCODE

EXB- 8200 2618 MINIMUM C034 MINIMUM

EE IMAGE

EXB- 8500 85E- 0155 Standard EEimage

EXB- 8500C 8CE- 0189 Reports ID = 8500, compression on

EXB- 8205 8VE- 0168 Reports ID = 8200, compression on

EXB- 8505 8SE-0219 Reports ID = 8500, compression on.

PROM

4200 N/A Can not be ran on this level of code

4200C N/A Can not be ran on this level of code

2501 N/A Can not be ran on this level of code

3.2.2 Solaris 2.3

Solaris 2.3 has an ASCII Look Up Table /kernel/drv/st.conf wherein devices are assigned by TID or globally. The device information is defined in TID =4 for 8200, 8500 and 8505. To add other Exabyte devices, or to use them at a different tid, enter the specific device as follows:

3.2.2.1 Global Tape-config-list property for Solaris 2.3:

To make a global entry, enter your choice of one of the following product listings starting at the first line of the file. A Boot-R should be used after making entries.

The product configuration is part of the 'data' of the second line ie:

1,0x35,1024,0x0039,4,0x14,0x90,0x15,0x8c,3;

| | | | | | | | | |__ Default to Density #(0-3)

| | | | | | | | | ___8500 w/compression

| | | | | | | | ___ 8500 wo/compression

| | | | | | |___ 8200 w compression

| | | | | |___ 8200 wo/compression

| | | | |___ number of densities

| | | |___ Flag

| | |___ Block size

| |___ Product Group (34 = 4mm, 35 = 8mm)

|___ # of product groups

****************************************************************************

/* Entry for the Exabyte EXB-8500c 8mm tape drive*/

tape-config-list =

"EXABYTE EXB8500C", "Exabyte 8MM /w compression", "EXB8500C-data";

EXB8500C-data = 1,0x35,1024,0x0039,4,0x14,0x90,0x15,0x8c,3;

The 3 highlighted in the 'data' field will default to the fourth density selection (0-3) or the 0x8c, 8500 mode with compression. User can select the default by changing the 3 to which ever is desired.

****************************************************************************

/* Entry for the Exabyte EXB-8505 8mm tape drive*/

tape-config-list =

"EXABYTE EXB8505", "Exabyte 8MM hh /w compression", "EXB8505-data";

EXB8505-data = 1,0x35,1024,0x0039,4,0x14,0x90,0x15,0x8c,3;

****************************************************************************

/* Entry for the Exabyte EXB-8205 8mm tape drive*/

tape-config-list =

"EXABYTE EXB8205", "Exabyte 8MM hh /w compression", "EXB8205-data";

EXB8205-data = 1,0x35,1024,0x0039,2,0x14,0x90,1;

The 1 highlighted in the 'data' field will default to the second density selection (0-3) or the 0x90, 8200 mode with compression. User can select the default by changing the 1 to which ever is desired.

***************************************************************************

/* Entry for the Exabyte EXB-4200 4mm DAT tape drive*/

tape-conf-list =

"EXABYTE EXB-4200", "Exabyte 4 mm DAT", "EXB4200data";

EXB4200data = 1,0x34,1024,0x0039,1,0,0;

***************************************************************************

/* Entry for the Exabyte EXB-4200C 4mm DAT tape drive with compression*/

tape-conf-list =

"EXABYTE EXB-4200C", "Exabyte 4 mm DAT with comp", "EXB4200C-data";

EXB4200C-data = 1,0x34,1024,0x0039,2,0x63,0x43,1;

The 1 highlighted in the 'data' field will default to the second density selection (0-3) or the 0x43, 4200 mode with compression. User can select the default by changing the 1 to which ever is desired.

NOTE!!

In the case were Sun and SGI are interconnected and data is interchanged, the 1024 in the above 4mm entries should be 512. The entry must be 1024 in order to run the Sun Unix archival command 'dd'. The normal Tar command, etc will accept either.

3.2.2.2 TID Specific Tape Devices for Solaris 2.3

To make the tape drive TID specific instead of global, enter in the tape-conf-list any of the following and use Boot-R to reconfigure:

****************************************************************************/tt>

Example is for TID = 4

/* Entry for Exabyte EXB-8500c */

name="st" class="scsi"

target=4 lun=0;

tape-config-list =

"EXABYTE EXB8500C", "Exabyte 8mm w/compression", "EXA8500C-data";

EXB8500C-data = 1,0x35,1024,0x0039,4,0x14,0x90,0x15,0x8c,3;

****************************************************************************/tt>

/* Entry for Exabyte EXB-8505*/

name="st" class="scsi"

target=4 lun=0;

tape-config-list =

"EXABYTE EXB8505", "Exabyte 8MM hh /w compression", "EXB8505-data";

EXB8505-data = 1,0x35,1024,0x0039,4,0x14,0x90,0x15,0x8c,3;

****************************************************************************/tt>

/*Entry for Exabyte EXB-8205*/

name="st" class="scsi"

target=4 lun=0;

tape-config-list =

"EXABYTE EXB8205", "Exabyte 8MM hh /w compression", "EXB8205-data";

EXB8205-data = 1,0x35,1024,0x0039,2,0x14,0x90,1;

****************************************************************************

/*Entry for Exabyte EXB-4200*/

name="st" class="scsi"

target=4 lun=0;

tape-config-list =

"EXABYTE EXB-4200", "Exabyte 4 mm", "EXB4200-data";

EXB4200-data = 1,0x34,512,0x0039,1,0,0;

****************************************************************************

/*Entry for Exabyte EXB-4200c*/

name="st" class="scsi"

target=4 lun=0;

tape-config-list =

"EXABYTE EXB-4200C", "Exabyte 4 mm", "EXB4200C-data";

EXB4200C-data = 1,0x34,512,0x0039,2,0x63,0x43,1;

Definition: ____ ___ ______ _ ____ ____

| | | | | | |__Default density

| | | | | |

| | | | | |--second density code

| | | | |--first density code

| | | |--How many densities supported

| | |--Flag

| |--Block size

|-- Product group (34=4mm,35=8mm)

3.2.2.3 DUMP PARAMETERS for Solaris 2.3

The dump parameters would be:

ufsdump 0fdbsf /dev/rmt/0l 64 54000 13000

||_ l = low density no compression(8200)

| m = low density/compression (8205)

| h = high density no compression (8500)

| c = high density/compression

| 0 = Default

|-- This is not a target ID but indicates which of several drives to use, similar to the use of n in the tar command for SUNOS. See 3.3.4

for more detail.

Note 1

To use the Exabyte tape drive at an TID of other than 4, simply define the desired TID in the above expression after target = . Only one target can be defined per expression. It would be best to use the global expression if more than one drive is to be used.

Note 2

Care must be taken in selecting TID for Exabyte products especially for IPX as OS will attempt to spin disk on addresses 0, 1 and 3 during a boot operation. That command to a tape drive is the same as the Load Tape command. The boot software is not very intelligent and will continue to issue that command regardless of the check condition returned.

3.2.2.4 SUN Solaris 2.3 Tape Drive Code Levels

While Sun

PRODUCT MXCODE SVCODE

EXB- 8200 2618 MINIMUM C034 MINIMUM

EE IMAGE FECODE

EXB- 8500 85E- 0155 85C- 05E0 or later

EXB- 8500C 8CE- 0210 8CC- 05B0 or later

EXB- 8205 8VE- 0167 8SC- 05B0 or later

EXB- 8505 8SE- 0212 8SC- 05B0 or later

PROM

4200 No restriction, but recommend 148 or higher

4200C 149 Minimum (Mode select for compression)

2501 21 or higher, Must jumper for 512 block size

3.2.3 Solaris 2.4

When released Solaris will include support for the EXB- 2501 as standard in the st.com file in addition to the normal SUN Exabyte products.

3.3 SUNOS

Below SUNOS 4.1.2 Contact Exabyte for instructions.

3.3.1 SUNOS 4.1.2

Supports 8200 and 8500. To add other devices, see attached st_conf.c Configuration Sheet.

3.3.2 SUNOS 4.2

Supports 8200, 8500 and 8505. To add other devices see attached st_conf.c Configuration Sheet.

3.3.3 ST_CONF.C on SUNOS Systems Configuration Sheet

The st_conf.c file is used on SUN4C (4/70, 4/90, SLC, IPC, IPX and all SPARCstations). It is used for all SunOS levels 4.0.5 through 4.2.

NOTE!

At the users discretion, the following Kernel entries can have the order of density and compression in either highest to lowest density/compression or as shown with lowest to highest density/compression. See paragraph 3.3.4 TAR Commands for Sun OS for effect. Many users prefer to have the 00 in the TAR command default to the highest density rather than the lowest and as the SunOS does not have the default as part of the device data, it must be done by order of entry. To enact that preference, simple reverse the order in the density/compression line, ie:

{ 0X8C, 0X15, 0X90, 0X14 }, /* Density/compression selection H to L)

An 0x0c = not used.

Kernel Entry:

/* Exabyte 8mm 5 Gb w/compression cartridge (Full- high)*/

{

"Exabyte EXB- 8500c 8mm Helical Scan", 16, "EXABYTE EXB8500C"

ST_TYPE_EXB8500, 1024,

(ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE),

5000, 5000,

{ 0X14, 0X90, 0X15, 0X8C }, /* Density/compression selection L to H)

{ 0, 0 ,0 ,0 }

}

/* Exabyte 8mm 5GB no compression cartridge */

{

"Exabyte EXB- 8500 8mm Helical 2 Scan", 16, "EXABYTE EXB- 8500",

ST_TYPE_EXB8500, 1024,

(ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE),

5000, 5000,

{ 0X14, 0X15, 0X0C, 0X0C }, /* Density selection L to H)

{ 0, 0, 0, 0 }

}

/* Exabyte 8mm 5GB w/compression cartridge (Half- High) */

{

"Exabyte EXB- 8505 8mm Half- High" 16, "EXABYTE EXB- 8505",

ST_TYPE_EXB8500, 1024,

(ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE),

5000, 5000,

{ 0X14, 0X90, 0X15, 0X8C }, /* Density/compression selection L to H)

{ 0, 0, 0, 0 }

}

/* Exabyte 8mm 2.5GB 8mm H/H w/compression cartridge (Half- High)*/

{

"Exabyte EXB- 8205 8mm Half- high" 16, "EXABYTE EXB- 8205",

ST_TYPE_EXABYTE, 1024,

(ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE),

5000, 5000,

{ 0X14, 0X90, 0X0C, 0X0C }, /* compression selection off, on)

{ 0, 0, 0, 0 }

}

/* Exabyte 8mm 2.5GB 8mm )*/

{

"Exabyte EXB- 8200 8mm Half- high" 16, "EXABYTE EXB- 8200",

ST_TYPE_EXABYTE, 1024,

(ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE),

5000, 5000,

{ 0X14, 0X00, 0X0C, 0X0C }, /*SINGLE DENSITY DEVICE*/

{ 0, 0, 0, 0 }

}

/* Exabyte 4MM 4GB w/compression cartridge */

{

"Exabyte EXB- 4200C 4MM Helical Scan", 16, "EXABYTE EXB4200C",

ST_TYPE_DEFAULT, 512,

(ST_VARIABLE|ST_BSF|ST_BSR),

5000, 5000,

{0X63, 0X43, 0X0c, 0X0c }

{ 0, 0, 0, 0 }

}

ST_CONF.C on SUNOS Systems Configuration Sheet (Con't)

/* Exabyte 4MM 4GB cartridge */

{

"Exabyte EXB- 4200 4MM Helical Scan", 16, "EXABYTE EXB- 4200",

ST_TYPE_DEFAULT, 512,

(ST_VARIABLE|ST_BSF|ST_BSR),

5000, 5000,

{ 0, 0X0C, 0X0C, 0X0C }

{ 0, 0, 0, 0 }

}

/* Exabyte QIC-121 DC2000 cartridge tape drive*/

{

"Exabyte 2501C", 16, "EXABYTE EXB-2501",

ST_TYPE_DEFAULT, 1024,

(ST_QIC | ST_BSR | ST_BSF ),

400, 400,

{ 0, 0X0C, 0X0C, 0X0C }, /* No density code to enable compression*/

{ 0, 0, 0, 0 }

}

For the Exabyte EXB-2501 and EXB-2501C, if jumper J9 pins 5&6 are jumpered for 512 byte blocks, line 2 should be changed to :

ST_TYPE_DEFAULT, 512,

Formatting: The command to format the EXB-2501 is: mt -f /dev/rst0 erase

3.3.4 TAR Commands for Sun OS

The TAR command is as follows:

tar - cvf /dev/nrstXX file name

where XX to be replaced with one of the following:

1st Drive 2nd Drive EXB-2501 EXB-2501C

0 1 Default Default

The EXB-2501C compression can only be disabled by the jumper on the rear

of the unit.

1st Drive 2nd Drive EXB-4200C EXB-4200

0 1 Compression off Default (NO COMPRESSION)

8 9 Compression on N/A

16 17 N/A N/A

24 25 N/A N/A

EXB- 8200 EXB- 8500

0 1 N/A 8200 Mode w/o compression

8 9 N/A 8500 Mode w/o compression

16 17 N/A N/A

24 25 N/A N/A

EXB- 8205 EXB- 8500C/EXB- 8505

0 1 Compress off 8200 Mode w/o compression

8 9 Compress on 8500 Mode w/o compression

16 17 N/A

24 25 N/A

4200C NOTE:

Starting with released code V139, there are new density codes to enable or disable compression for the EXB- 4200C. This was implemented for UNIX customers that can not access the compression page. It is similar to what we did in the 8MM products. However, the implementation is not the same. Compression on is 43h and compression off is 63h in the density byte. A 00h, 13h and 7fh are no ops. The issuing of a 43h or 63h at other than LBOT will not cause a check condition and will not alter the state of compression. During a Read operation, Decompression is always on(!) regardless of the state of the DCE bit which is determined by either the density byte or the DCE bit during the Mode Select. Therefore, if a Mode Select is issued with a Density code of 43h and a non- compression tape is inserted, (or vise- versa) the tape will be read correctly but a Mode Sense's DCE bit will be as set in the Mode Select and not altered by the state of the tape when read!!!!!!

The DCE bit is meaningless in a Read mode. A drive set to non- compression (63h) at LBOT followed by a Mode Select changing the density code to 00h or 13h at LBOT will write in non- compression mode. The 00h or 13h will not change to compression mode.

Regardless of being in compression mode or not, the Mode Sense Density byte will always report 13h.

4. HP

4.1 Model 1000 Either Ultrix or UNIX system requires

special software to operate.

4.2 9000 system

4.2.1 SERIES 700

The Series 700 allows the user to add products. Therefore all Exabyte products can be added. The EXB-8505 is included in the standard HPUnix 9.03.

needs specific Eeimage. When booting, hit escape so that system will look for devices. It escape now to stop bootable selection 9.03.

4.2.2 Series 800

The Series 800 operating system HPUnix 9.03 is similar to Sun's Solarus 2.2 in that the user can not add addition device types to the system. The only Exabyte products that can be used are the EXB-8505 with standard EEimage and the EXB-8500C with EEimage 8CE-0189.

********

8500, 8500c works standard. looks for specific EEimage.

USe SAM doesn't recognize 8500 or 8500C did 8505. File is Directory /user/sam/lib/C

file is pd_devinfo.tx Modifiable string looks like 700? Sam works when EEimage changed. Could not add 8200 or 8205. 4200C?

NOTE!

Exabyte 8 MM products are not currently bootable devices for the HP 9000.

This has to do with the Read Block size during a boot operation, the HP needs 256 kbyte block size and the maximum size allowed in the 8 MM is 240 Kbyte.

As of 3/31/94 the understanding is that a special EEimage may be available soon to correct this.

5 SCO UNIX 3.2 version 4.2

5.1 Configuration

Drive Mode Code Inquiry Controller

4200C 43 140B RB150 AHA 1740A

4200 63 141A RB100 AHA 1740A

NOTE!!!!!!!!!!

With INQ = EXB- 4200 or EXB-4200C, SCO tar command HANGS.

8200 14 262Y/C034 EXB- 8200 AHA 1740A

2501 Not supported

The AHA 1740A use in Standard or Enhanced Mode

The AHA 1744 (Differential Controller) use in Enhanced Mode

Tar Command - tar cvf /dev/rStp *

NOTE!!!!!

SCOunix commands are case sensitive. S is not the same as s.

NOTE!!!!!

The next release from SCO due in 6/94 should contain support for the EXB-4200 and 4200C as named and should also have support for 2501.

5.2 Procedure for installing an Exabyte Tape Drive

1. Attach the tape device to be used with the system powered down. Power up the tape drive and boot up the system. As menus are presented, the following choices should be selected.

1. Choice 1: From the # prompt, type: mkdev tape <rtn>

2. Choice 4: Install a SCSI Tape Drive <rtn>

3. Choice 2: Install SCSI Exabyte Tape Drive <rtn> (for 8mm devices)

or -

Choice 4: Install a SCSI DAT Drive <rtn> (for 4mm devices)

4. Message: Updating system configuration.

5. Message: Systems files have successfully updated.

6. Message: The SCSI (Exabyte/DAT) Tape Drive must be configured before use.

7. Message: Do you wish to configure the SCSI Tape Drive now? (y/n)

Action: Select y

8. Message: Enter the prefix of the SCSI host adapter that supports this device or press <return> for the default:

Action: Enter: eiad (for Adaptec 1740, enhanced mode)

or -

Enter: <rtn> (for default of ad, Adaptec 1740 standard mode)

9. Message: Enter h for a list of host adapters or enter q to quit.

Which eiad SCSI host adapter supports this device?

Action: Select 0 <rtn> for first adapter, 1 <rtn for second.

10. Message: What is the Target ID for this device?

Select 0 through 7 or h for help, or q to quit.

Action: Select 2.

11. Message: What is the LUN of this device? Press <RETURN> to use the

default: 0

Select 0 through 7 or h for help, or q to quit.

Action: Select <rtn>.

12. Message: .Host

.Adapter...Adapter

.Type..Device..Number.ID..LUN

.eiad..Stp.. 0.. 2.. 0

13. Message: Update SCSI configuration? (y/n)

Action: Select y

14. Link command set is given at this point.

15. Message: Enter new string, 'rm' to remove string, or enter q to leave

current string as is.

Action: Select q.

16. Message: Tape Drive Configuration Program

Action: Select q.

17. Message: You must create a new kernel to effect the driver change you

specified.

Do you wish to create a new kernel now? (y/n)

Action: Select y

18. Message: Do you want this kernel to boot by default? (y/n)

Action: Select y

19. The system will create the kernel automatically and a long message will be displayed, ending with ... You have successfully re-linked a new kernel.

You may at this point enter the tar command, tar cvf /dev/rStp0 * <rtn>

6. DEC

6.1 DEC VAX 4000 Running VMS 5.5-2

If there is no disk drive on the SCSI bus with an EXB-8500, use 85E-0091. This will disable Synchronous Data Transfer and rid the error message of 'larger number of characters than system allows, looking for 38 or less characters........'.

8500 8500C 8505 8205

EEimage 85E-0091 8CE-0175 8SE-0195 8VE-0163

6.2 DEC VAX 4000/VLC Running VMS 5.5-2

An 8505 was tested with 2 hard disk attached (if no hard disk, 85E-0195 may be required). FE code 8SC-05B0 or higher should be used.

6.3 DEC Alpha running Windows NT

The Windows NT program supports all Exabyte 8 and 4 MM products. Testing on this device indicated no problems or modification required to the FE or EE codes. See 14.7 Windows NT.

7. IBM

IBM has a unique configuration of Exabyte products that include the 8200, 8500 and 8505 for the RS6000, AS/400, & PS/2 . The standard version of these products will not work with the IBM software for these products. However, Exabyte products will operate under AIX 3.2.3 or higher using the generic tape driver.

7.1 RS6000

DISCLAIMER: THESE RS6000 TECH NOTES ARE BASED UPON THE FUNCTIONALITY

THAT IBM BUILT INTO THE GENERIC TAPE DRIVER IN AIX RELEASE 3.2 FOR THE

RS6000. REMEMBER THAT THIS IS A GENERIC TAPE DRIVER, NOT A 8MM

DRIVER. IF A CUSTOMER WANTS A 8MM DRIVER, THEY MUST BUY AN IBM

8200 OR AN IBM 8505. THE IBM DRIVER IS SPECIFICALLY FOR 8MM DEVICES.

SOME SYSTEM FUNCTIONS MAY ONLY WORK WITH THE IBM 8MM DEVICES

(SYSTEM LEVEL DIAGNOSTICS), NO EFFORT WILL BE MADE TO DIAGNOSE WHY

THESE DO NOT WORK ON GENERIC DEVICES WITHOUT DIRECTION OF EXABYTE

UPPER MANAGEMENT.

7.1.1 RS6000 AIX REVISION LEVELS

AIX release 3.2 supports generic 8200 and 8500 drives.

AIX release 3.2.3 adds support for the EXB-8505.

To use an EXB-8500C install Eeimage 8CE-0189 and proceed as if it were an EXB-8505.

7.1.2 Firmware Versions Tested:

8200c 2618 / 2687 MX codes.

8500 85C- 06L0/ 85E- 01180

8500C 8CC-06MO/8CE-0201

8505 85C-06M0/8SE-0180

8205 85C-06M0/8VE-0155

IBM Con't

7.1.3 QUICK INSTALLATION:

Set the SCSI target on the tape drive appropriately via switch or jumpers. Shut down the RS6000 properly, and power it down. Connect the new tape drive to the RS6000. Power up the external drives first and then the RS6000.

After booting, the RS6000 should see the new tape drive. Configure it as an ost "other SCSI tape" type device, and as /dev/rmt0, or /dev/rmt1.

Next enter the directory SMIT Devices/Tape/Show or Change Configuration Options. Change the block size and density codes as needed (see following information for entry). The drive should now work.

Many Exabyte tape drive products offer several densities and selection of compression via the density byte of the Mode Select command. It is neceesary to have a means to select these options from the host. On the IBM RS6000, SMIT provides density settings 1 and 2, which can be configured to represent any of the desired density and compression settings.

7.1.4 SMIT SETUP

In SMIT, at the ADD A TAPE DRIVE screen menu select the following entrees:

Heading Entry

- Tape Drive Type ost (other SCSI Tape)

- Tape Drive Interface scsi

- Description Other SCSI Tae Driv

- Parent Adapter scsi0

- CONNECTION address 20

- BLOCK size (0=varible length) (**1024/512/0 - see below)

- Use DEVICE BUFFERS during writes yes

- Use extended filemarks yes

- DENSITY setting #1

- DENSITY setting #2

- Set delay after a failingcommand [45]

- Set maximum delay for read/write command [144]

Setting the connection address: it is in the form of ab, where a is the SCSI TARGET (also called SCSI ID or ADDRESS), and b is the LUN (Logical Unit Number, which will usuaaly be 0).

**Setting the block size: For 8MM, use either 0 or 1024. For 4MM, use 512. In order to interchange tapes between Sun Unix and RS6000 on 8 MM

products, the block size must be set to 0 (variable).

Density settings #1 sets the density value for special files /dev/rmt*, /dev/rmt*.1, /dev/rmt*.2, /dev/rmt*.3. Wherein the * = connection address.

Density setting #2 sets the density value for special files /dev/rmt*.4, /dev/rmt*.5, /dev/rmt*.6, /dev/rmt*.7.

7.1.5 DENSITY VALUES

MODE/DENSITY HEX DECIMAL CODE#

CTS DEFAULT 0X00 0

EXB-820X (LO-DEN) 0X14 20

EXB-850X (HI-DEN) 0X15 21

NO CHANGE 0X7F 127

EXB-850X W/COMPRESSION 0X8C 140

EXB-820X W/COMPRESSION 0X90 144

EXB-4200 WO/COMPRESSION 0X63 99

EXB-4200 W/COMPRESSION 0X43 67

7.1.6 BOOTING FROM EXABYTE TAPE DRIVE

7.1.6.1 EXB-8200

For EXB-8200, the MXcode must be revision 2618 or higher, and the MXcard switches must be 2-3-4-5-8 on.

7.1.6.2 EXB-8505/8205

With an internally attached EXB-8205/8505 tape drive, the host may fail to detect its presents during booting. Under some conditions, this can occur to external drives as well. Therefore, an EEimage has been created

with a predictive Ready code that will correct the situation.

* 8VE-0203 for the generic EXB-8205

* 8SE-0293 for the generic EXB-8505

7.1.6.3 General Boot Information

Use SMIT to change the block size to 512.

AIX must be preloaded.

If the bootlist does not contain the logical TMTX device address, use bootlist -m service RMTX command to add/change service boot devices. Just add the device to the boot list.

WARNING:

Remember that users who have a mixture of 8200 and 8500

drives must be careful to label tapes correctly. 8500

backup tapes when loaded on a 8200 drive will show up as

blank tape (ASC/ASCQ 3002). "DON'T OVERWRITE A 5

GIGABYTE BACKUP TAPE!!"

7.2 IBM support of EXB-120/60/10/10e

IBM has announced ADSTAR Distributed Storage Manager (ADSM) for all IBM AIX, DOS, OS/2 systems. It also operates with Macintosh, SunOS, Novell Netware, Microsoft Windows, HP-Unix, Dec Ultrix and SCO Unix.

8.SGI

8.1 Configuration Procedure for SGI OS IRIX 4.0.5/ 5.1/ 5.2

This section provides instructions on adding standard Exabyte 8 MM AND 4 MM compression tape drives to SGI systems.

8.2 Applicable SGI Systems

The Exabyte EXB-8200 and EXB-8500 are supported on the SGI Indigo system in

IRIX version 4.0.5 and 5.2 and on the Challenge and Indy systems in IRIX version 5.1.or 5.2 The following will describe what is required to add a standard EXB-8500c, EXB-8505, EXB-8205, EXB-4200 and EXB-4200C. It is understood that Indigo will move to IRIX 5.1 by March, 1994. Crimson should also work but I have no data.

8.3 Option to Modifying Drivers

Users may use the following special Exabyte firmware and not modify the drivers

but compression of data files will be unavailable. The following images provide deviations from the normal 8 MM product in that the units default to non-compression data recording and Variable Length Block mode. All of the following codes will report as EXB-8500s in the Inquiry Command response.

PRODUCT FECODE EEIMAGE

EXB-8500C 8CC-05B0 OR HIGHER 8CE-0176

EXB-8505 8SC-05B0 OR HIGHER 8SE-0213

8.4 Adding Exabyte Tape Products to IRIX 4.0.5/5.1/

8.4.1 The important files are:

In IRIX 4.0.5/5.1, it is /usr/sysgen/master.d/tpsc which contain data for the device drivers including the SCSI tape drivers that are of interest here.

/dev/MAKEDEV - a script that when executed, makes the device drivers ( actually the 'device special files') according to information detected by the OS and the information found in the device files in "/usr/sysgen/master.d"

/dev/rmt/tps...., /dev/mt/tps.... - the device driver files that are created by MAKEDEV to provide access to the tape drive ( there is no difference between the two sets of files - in IRIX 5.1, /dev/mt is a link to /dev/rmt)

8.4.2 Define By TID

The SGI IRIX is similar to the SUN Solaris in that it defines the devices by SCSI controller and TID as follows:

tps1d4nrnsv.8505(x)

| || | | | |- Either a 5 or a 0c indicates compression

| || | | |---- Drive emulation

| || | |------ Variable blocking enabled

| || |-------- No byte swapping

| ||---------- No rewind on close

| |----------- SCSI TID number (4 or 5)

|------------- SCSI controller ID number as detected by OS

It is recommended that variable length data mode be used as it will significantly increase the efficiency of transfer.

8.4.3 Symbolic Link

Assuming that the user will consistently use one device and one driver, a symbolic link to it should be made from /dev/tape ie.

# mv /dev/tape /dev/tape.orig

# ln -s /dev/rmt/tps1d4nsv.xxxxx /dev/tape

Where xxxxx =device ie., 8505, or 8500c

With this accomplished any access to the tape will be by the appropriate driver.

The MAKEDEV script creates a link to *an* appropriate driver, but it may not be the one required, hence the above contortion.

8.4.4 Adding Exabyte 8MM Tape Drives to /usr/sysgen/master.d/tpsc

To modify the above mentioned files "/usr/sysgen/master.d/tpsc" and "/dev/MAKEDEV":

8.4.4.1. Select File

1. Login as root (super user)

2. cd /usr/sysgen/master.d

3. cp tpsc.orig (Create a back-up copy of the file 'tpsc')

4. vi tpsc (Edit the file 'tpsc' to add the following entries after the EXB-8500 entry)

5. Add the desired product as shown in 8.4.4.2.

6. Save changes

SGI Con't

8.4.4.2. Master.d File Modification

Add the appropriate device from the following:

*****************************************************************************

{EXABYTE8205, TP8MM, 7,8, "EXABYTE", "EXB-8205", 6, "\40\4\16\0\200\7",

{OX14, 0X90, 0, 0}

MTCAN_SEEK,

80, 4*60, 25*60, 5*60, 1024, 128*1024},

******************************************************************************

Add this entry before the line that contains the string 'Device:*EXB-8200*'

{ EXABYTE8500, TP8MM, 7, 8, "EXABYTE", "EXB8500C", 6, "\40\4\16\0\200\7"

{0X14, 0X90, 0X15, 0x8c},

MTCAN_SEEK,

80, 4*60, 25*60, 5*60, 1024, 128*1024},

#If using an 8500C that has an Inquiry command response of EXB-8500C, then

the first line should read:

{ EXABYTE8500, TP8MM, 7, 9, "EXABYTE", "EXB-8500C", 6, "\40\4\16\0\200\7" ******************************************************************************

Add this entry before the line that contains the string 'Device:*EXB-8200*'

{ EXABYTE8505, TP8MM, 7, 8, "EXABYTE", "EXB-8505", 6, "\40\4\16\0\200\7"

{0X14, 0X90, 0X15, 0x8c},

MTCAN_SEEK,

80, 4*60, 25*60, 5*60, 1024, 128*1024},

SGI/SUN NOTE!

If the SGI system is connected to a Sun processor, 128K blocks exceed the Sun limits and should be reduced to 64k by changing the last line as follows for any of the above strings:

80, 4*60, 25*60, 5*60, 1024, 64*1024},

The sequence that makes up the 2nd line of each stanza ("{0x14, 0x90, 0x15,

0x8c}," for the 8500C and 8505) is significant for the default settings as set forth below.

0X8C = 8500 compatible recording mode w/compression

0x15 = 8500 compatible recording mode without compression

0x90 = 8200 compatible recording mode w/compression

0x14 = 8200 compatible recording mode without compression

SGI con't

8.4.5 Adding Exabyte 4 MM Tape Drives to /usr/sysgen/master.d/tpsc

{DATTAPE, TPDAT, 7,8, "EXABYTE", "EXB-4200", 0, 0, {0, 0, 0, 0},

MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY,

40, 4*60, 5*60, 128*512},

*****************************************************************************

{DATTAPE, TPDAT, 7,8, "EXABYTE", "EXB4200C", 0, 0, {0X63, 0X43, 0, 0},

MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY,

40, 4*60, 5*60, 128*512},

4 MM NOTE!!

The Exabyte 4200C/4200 must have firmware revision 149/148 or higher to support the BRU command..

8.4.6 Additions to /dev/MAKEDEV

Once the following entries have been made, reboot the system, allow the autoconfig at restart, and then run the MAKEDEV script ( MAKEDEV tps) to make the tape drivers.

Note!

Make sure to make backups of the modified kernel described below. If a system disks crashes, the unmodified kernel that would be loaded from a CD will of course not have the modified version and your tape drive will be unaccessible as the system will think it is a QIC device. So, if you want a full tape to be restorable in the miniroot, *with the miniroot kernel*, and the drive type is unknown (system assumes a QIC device with 512 byte blocks), you will want to write the backup file with the modified kernels with 512 byte blocks and be the first file on the tape.

8.4.6.1. Select the /dev/MAKEDEV File

The ' are not a part of the data entry.

1. Enter 'cd /dev'

2. Enter 'cp MAKEDEV MAKEDEV.orig' to create a back-up copy of the file MAKEDEV'.

3. Enter 'vi MAKEDEV' to edit the file 'MAKEDEV' to add any of the following entries in paragraph 8.4.6.2. Make entry ahead of the

EXB-8200 entry.

4. Write the entry and save the file.

5. Configure the Kernel by entering /etc/autoconfig

6. REBOOT the system and login as 'root'

7. Enter 'cd /dev'

8. Enter 'MAKEDEV tps' to execute the 'MAKEDEV' script with 'tps' as

the command line argument. This will create the new devices in the '/dev/mt' directory.

14. The tape drive can now be accessed using the device files under

"/dev/mt" directory.

DEVICE ORDER NOTE!

The user may elect the density and compression sequence of their choice, ie.

0 could represent the 8500C mode rather than the 8200 mode if one desired.

However make sure that both the /dev/MAKEDEV and the /usr/sysgen/master.d/tpsc

are configured in the same order!

8.4.6.2 /dev/MAKEDEV File Modifications

8.4.6.2.1. EXB8500C

*Device:*EXB8500C*) \

set v nrv nsv nrnsv ; \

for add in 4 5 6 7 ; do\

mdev='expr $$minor + $$add'; \

mknod $${prf}$$1 c $$maj $$mdev; \

shift; \

done; \

for dens in 0 8 16 24; do \

case $$dens { \

0) kden=8200;; \

8) kden=8200c;; \

16) kden=8500;; \

24) kden=8500c;; \

}; \

set "" nr ns nrns v nrv nsv nrnsv ;\

for add in 0 1 2 3 4 5 6 7 ; do \

mdev='expr $$minor + $$add + $$dens';\

mknod $${prf}$$1.$$kden c $$maj $$mdev;\

shift;\

done; \

done ;; \

SGI con't

8.4.6.2.2. EXB-8505

*Device:*EXB-8505*) \

set v nrv nsv nrnsv ; \

for add in 4 5 6 7 ; do\

mdev='expr $$minor + $$add'; \

mknod $${prf}$$1 c $$maj $$mdev; \

shift; \

done; \

for dens in 0 8 16 24; do \

case $$dens { \

0) kden=8200;; \

8) kden=8200c;; \

16) kden=8500;; \

24) kden=8500c;; \

}; \

set "" nr ns nrns v nrv nsv nrnsv ;\

for add in 0 1 2 3 4 5 6 7 ; do \

mdev='expr $$minor + $$add + $$dens';\

mknod $${prf}$$1.$$kden c $$maj $$mdev;\

shift;\

done; \

done ;; \

SGI con't

8.4.6.2.3 EXB-8205

*Device:*EXB-8205*) \

set v nrv nsv nrnsv ; \

for add in 4 5 6 7 ; do\

mdev='expr $$minor + $$add'; \

mknod $${prf}$$1 c $$maj $$mdev; \

shift; \

done; \

for dens in 0 8 ; do \

case $$dens { \

0) kden=8200;; \

8) kden=8200C;; \

}; \

set "" nr ns nrns v nrv nsv nrnsv ;\

for add in 0 1 2 3 4 5 6 7 ; do \

mdev='expr $$minor + $$add + $$dens';\

mknod $${prf}$$1.$$kden c $$maj $$mdev;\

shift;\

done; \

done ;; \

SGI con't

8.4.6.2.4. EXB-4200

*Device:*EXB-4200*) \

set v nrv nsv nrnsv ; \

for add in 4 5 6 7 ; do\

mdev='expr $$minor + $$add'; \

mknod $${prf}$$1 c $$maj $$mdev; \

shift; \

done; \

for dens in 0 ; do \

case $$dens { \

0) kden=4200;; \

}; \

set "" nr ns nrns v nrv nsv nrnsv ;\

for add in 0 1 2 3 4 5 6 7 ; do \

mdev='expr $$minor + $$add + $$dens';\

mknod $${prf}$$1.$$kden c $$maj $$mdev;\

shift;\

done; \

done ;; \

SGI con't

8.4.6.2.5. EXB-4200C

*Device:*EXB-4200c*) \

set v nrv nsv nrnsv ; \

for add in 4 5 6 7 ; do\

mdev='expr $$minor + $$add'; \

mknod $${prf}$$1 c $$maj $$mdev; \

shift; \

done; \

for dens in 0 8 ; do \

case $$dens { \

0) kden=4200;; \

8) kden=4200c;; \

}; \

set "" nr ns nrns v nrv nsv nrnsv ;\

for add in 0 1 2 3 4 5 6 7 ; do \

mdev='expr $$minor + $$add + $$dens';\

mknod $${prf}$$1.$$kden c $$maj $$mdev;\

shift;\

done; \

done ;; \

8.4.7 Contents of /dev/rt and /dev/rmt

It should end up with an 'ls' of the /dev/mt and /dev/rmt that looks something like:

mt% ls tps1d4

tps1d4 tps1d4nrns tps1d4nrv tpeid4nsv

tps1d4.4200 tps1d4nrns.4200 tps1d4nrv.4200 tps1d4nsv.4200

tps1d4.4200c tps1d4nrns.4200c tps1d4nrv.4200c tps1d4nsv.4200c

tps1d4.8200 tps1d4nrns.8200 tps1d4nrv.8200 tps1d4nsv.8200

tps1d4.8200c tps1d4nrns.8200c tps1d4nrv.8200c tps1d4nsv.8200c

tps1d4.8500 tps1d4nrns.8500 tps1d4nrv.8500 tps1d4nsv.8500

tps1d4.8500c tps1d4nrns.8500c tps1d4nrv.8500c tps1d4nsv.8500c

tps1d4nr tps1d4nrnsv tps1d4ns tps1d4v

tps1d4n.4200 tps1d4nrnsv.4200 tps1d4ns.4200 tps1d4v.4200

tps1d4n.4200c tps1d4nrnsv.4200c tps1d4ns.4200c tps1d4v.4200c

tps1d4n.8200 tps1d4nrnsv.8200 tps1d4ns.8200 tps1d4v.8200

tps1d4n.8200c tps1d4nrnsv.8200c tps1d4ns.8200c tps1d4v.8200c

tps1d4n.8500 tps1d4nrnsv.8500 tps1d4ns.8500 tps1d4v.8500

tps1d4n.8500c tps1d4nrnsv.8500c tps1d4ns.8500c tps1d4v.8500c

8.4.8 Testing SGI Device Additions

Test drivers with bru, tar (such as FSF/gnu tar), dump, etc and verify that the drivers are working correctly.

8.5 Adding Exabyte Tape Products to IRIX 5.2

In IRIX 5.2, it is /var/sysgen/master.d/scsi which contain data for the device drivers including the SCSI tape drivers that are of interest here. .

/dev/rmt/tps...., /dev/mt/tps.... - the device driver files that are created by MAKEDEV to provide access to the tape drive.

Starting with SGI code version 5.2, both the /var/sysgen/master.d/scsi and the /dev/MAKEDEV files will have to be modified as shown below for EXB-8500C, EXB-8505 and EXB-8205.

Selecting compression is now separate from the device density of the command. It still will create the density bytes 14, 15, 8c and 90, only now compression is defined differently in the TAR command.

8.5.1 Tar Command

tps0d1nrnsc.8500

| |U U | ----

| || | | |

| || | | |____ Density

| || | |_____ Compression on.

| || |______ Variable Block Enabled

| ||_________ No Rewind on Close

| |__________ SCSI TID number

|____________ SCSI Controller ID number.

NOTE!!!!

As SGI defines the density and compression in the TAR command with terms such as 8500 rather than in 00 or 08 hex numbers as done by Sun, the sequence of the listing in dev/makedev is not of any consequence as long as it is in agreement with the /var/sysgen/master.d/scsi.

8.5.2 Modifying Files

Select the /dev/MAKEDEV File

1. Enter>cd /dev

2. Enter>cp MAKEDEV MAKEDEV.orig

3. Enter>vi MAKEDEV (To edit the file MAKEDEV to add any of the following

entries:

4.Enter>

****************************EXB8500C***************************************

*Device:*EXB8500C*) \

set v nrv nsv nrnsv

for add in 4 5 6 7 ; do \

mdev='expr $$minor + $$add';\

mknod $${prf}$$1 c $$maj $$mdev; \

shift; \

done; \

for dens in 0 8 ; do \

case $$dens { \

0) kden=8500;; \

8) kden=8200;; \

}; \

set "" nr ns nrns v nrv nsv nrnsv ;\

for add in 0 1 2 3 4 5 6 7 ; do \

mdev='expr $$minor = $$add =$$dens'; \

mknod $${prf}$$1.$$kden c $$maj $$mdev; \

mdev='expr 16 + $$minor + $$add $$dens'; \ How does this define 16 and 24

mknod $${prf}$$1c/$$kden c $$maj $$mdev; \

shift; \

done; \

done ;; \

**************************EXB-8505 ****************************************

To make an EXB-8505 a device, simply change the first line of the EXB-8500C to:

*Device:*EXB-8505*) \

**************************EXB-8205****************************************

*Device:*EXB-8205*)

set v nrv nsv nrnsv : \

for add in 4 5 6 7 ; \

mdev='expr $$minor + $$add'; \

mknod $${prf}$$1 c $$maj $$mdev

shift; \

done; \

for dens in 0 ; do \

case $$dens { \

0) kden=8200;; \

}; \

set "" nr ns nrns v nrv nsv nrnsv

for add in 0 1 2 3 4 5 6 7 ; do \

mdev+'expr 16 + $$minor + $$add + $$dens'; \

mknod $${prf}$$1c/$$kden c $$maj $$mdev; \

shift; \

done; \

done ;; \

*************************************************************************

5. Save file

8.5.3. var/sysgen/master.d/scsi Modification

Adding any of the following product to the master.d.tpsc will define the acceptable SCSI commands for the device and sets the Exabyte density codes.

This differs from previous SGI releases in that the density is defined as default to 8500 mode rather than 8200 mode and the compression modes are the last modes defined.

*************************************************************************

For the EXB-8500C:

{ EXABYTE8500C, TP8MM, 7. 8. "EXABYTE", "EXB8500C", 6, "\40\4\16\0\200\7",

{0X15, 0X14, 0X8C, 0X90},

MTCAN_SEEK,

80, 4*60, 25*60, 5*60, 1024, 128*1024},

*************************************************************************

For the EXB-8505:

{ EXABYTE8505, TP8MM, 7. 8. "EXABYTE", "EXB-8505", 6, "\40\4\16\0\200\7",

{0X15, 0X14, 0X8C, 0X90},

MTCAN_SEEK,

80, 4*60, 25*60, 5*60, 1024, 128*1024},

***************************************************************************

For the EXB-8205:

{ EXABYTE8205, TP8MM, 7. 8. "EXABYTE", "EXB-8205", 6, "\40\4\16\0\200\7",

{ 0X14, 0X90, 0, 0 },

MTCAN_SEEK,

80, 4*60, 25*60, 5*60, 1024, 128*1024},

***************************************************************************

7. Save changes

8. Configure the Kernel by entering /etc/autoconfig

9. Rebuild the kernel and reboot using "1boot -y -u unix".

Respond with "YES" to the request for verification of reconfiguration.

10. The /dev/MAKEDEV file should now have:

For 8500C and 8505:

tps0d1c.8500

tps0d1nsc.8500

tps0d1nrnsc.8500

The same files with .8200 extensions.

9. NEXT CUBE SYSTEM

To use an Exabyte 8 MM tape drive on a NEXT Cube System running 2.1, with "ROM monitor version 2.55, do the following:

9.1 EXABYTE CODE

Standard Exabyte FE and EEimage is used. However, the option page should be altered to lock in compression mode as the system issues a Mode Select command that will change density to non-compressed (14h) format. By locking the configuration with the Option page, the Mode Select command is overridden.

9.2 SCSI ADDRESS

Set drive SCSI-ID to 5.

9.3 HOST TEST FOR DEVICE

The NEXT system will, at power up, scan the SCSI bus with inquiry commands to determine which devices are connected. As the Exabyte 8 MM drives require several seconds before they will respond to such commands, the drive will not be recognized. To resolve this issue, the user may power up the Exabyte drive prior to powering up the host. If external termination is used, jumper the Exabyte drive to provide terminator power as without it (the host is off) supplied, the drive will not go ready. As an alternative, internal termination on the Exabyte drive can be used.

9.4 PROCEDURE

When the Exabyte drive is READY, Turn on the NEXT system.

In the NEXT PROM monitor (the Next> prompt), the user can turn on options for booting such as 'SCSI test' and 'Verbose mode'. If these are turned on, then during booting, the following inquiry information will be displayed:

product/eeimage/target address/SCSI port

For example using an EXB-8205, the following is reported:

EXB-8205 8VQANXR0 target 5 as st0 on sc0

At the prompt on dev/rx*, do a list command ls -1. /dev/rxt0 should show up as a character device with major# 34 and minor# 2. /dev/nrxt0 (the no-rewind device) should have the same major but the minor# of 3. If they don't exist, they will have to be made. Use the /dev/MAKEDEV script as in "cd /dev: MAKEDEV rxt0", or use the following mknod command:

cd /dev

mknod rxt0 c 34 2

The rxt devices must be used instead of the rst because the rxt have special support for Exabyte drives.

When using other than an EXB-8200, the option page in the drive, needs to be altered to write in other than 8200 mode. The Next system must issue a 14 density code as without making this modification compression will not be enabled. This requires either the Exabyte monitor program or a code load tape with the option page modified.

9.5 USING MONITOR TO SET DENSITY

1. Select Firmware from menu.

2. Select Option Settings from menu.

3. The current Option page will be retrieved from the drive.

4. change "Lock density to power up value" from n to y.

5. Press RETURN

6. Press <CTRL> <RETURN> to save and exit.

A code load tape can be made now of the new setting for other drives.

It may be possible to alter the Next kernel and get it to issue density codes and so toggle write compression via software. If so, /usr/include/nextdev/stvar.h, scsireg.h are probably where it can be done. If someone figures it out, let me know!.

9.6 TESTS RAN

The following tests where ran without error:

cd /usr/lib: tar cvf /dev/rxt0 .

dd of=/dev/rxt0 if=/sdmach ibs=32767 obs32767

mt status (which defaults to /dev/rxt0 and returned "Exabyte SCSI tape drive, residual=0, and a bunch of sense data).

10. SCO Unix

32v4.2 supports the EXB-8200 and 8500 only.

The next release should support all tape drives except the 8205.

11. Sunsoft

Interactive Unix (a SCO clone) 4.0 supports all Exabyte tape drives except the 2501.

12. Legato Systems

Networker v3.3 supports the 8200, 8500, 8500c, and the 8505. The next release will also support the 4200, 4200c and the 2501.

13. Cheyenne

ARCserve/Open v1.1 supports the 8200, 8500 and the 8505. See notes under PC based products.

14. PC Based Products

NOTE!!!!

If an Adaptec 1500 or 1700 series controller is used with an EXB-8500 with Fcode at 05E0 or higher, or with any other of the following drives with Fcode of 05B0 or higher the following special EEimage is required. This is especially true of the 1540B and the 1740B controller. As an alternative Adaptec has a correct to their code available.

PRODUCT EEIMAGE

EXB-8500 85E-0118

EXB-8500c 8CE-0201

EXB-8205 8VE-0155

EXB-8505 8SE-0180

14.1 Novell

Netware 3.11 supports the 8200 and 8500 only.

Netware 4.0 supports the 8200, 8500 and 8505.

Netware (next revision) will support 8200, 8500, 8500C, 8505, 8205, 4200, 4200C, and 2501.

14.2 Cheyenne

Arcserve V4.0 will support all 8mm and 2501. Arcserve V4.02 will also support the 4200 and 4200C. Also supports the EXB-10i and 10e. This software is tricky. If you have problems with it, contact Judy Enderly of Exabyte at (303) 442-4333. She knows it very well.

Arcsolo V2.11 supports the following products 8200, 8500, 8205, 8505, 4200, and the 4200C but does not support the 2501. To use an 8500C, use EEimage 8CE-0189.

Again contact Judy if problems arise.

14.3 Novastor

Novaback v4.00A supports all current Exabyte products on single systems. If system seems to run slow with Adaptec controller make sure the ASPI4DOS.sys is of latest version.

Novanet v4.00 supports all current Exabyte tape drives on LAN.

14.4 Sytron

Sytos Plus v1.42 support the 8200 only!. Plans are to add support for the 8500C, 8505, 8205, 4200, 4200C and the 2501 in the next release.

14.5 Microsoft

Windows NT v3.1 will support all current Exabyte tape drives except the 2501. This will put a damper on some of the above packages.

14.6 Corel

Corel SCSI v1.14 supports the EXB-8200 but only with the following proms, MX = 2640, SV = C034. Switches 1 and 4 on the MX card must be on. V1.2 supports 8200, 8500, 8505, 4200, 4200c, and the 2501.

14.7 Microsoft Windows NT

14.7.1 TEST CONFIGURATION

A DEC Alpha 150 computer was used with an Adaptec 1742 SCSI controller. On the SCSI bus was one disk drive, two CDs, a HP 35480 4 mm tape drive, an Exabyte EXB-4200C 4 mm tape drive, and an Exabyte EXB-8505 8mm tape drive.

Software was Windows NT version 3.1.

14.7.2 INSTALLING DRIVES INTO OPERATING SYSTEM

Windows NT has support for all Exabyte 8 and 4 MM products. To install a specific drive:

Make sure that the device you will be adding will power up with the host or be already powered up as the host will pole the SCSI port for devices. There is sufficient time for all Exabyte drives to wake-up prior to poling if powered-up with the host.

There are no SCSI Address requirements for operation but would suggest that any disk drives have the lower SCSI addresses and tape drives be in the mid range. Numbering does not have to be sequential.

The user must select WINDOWS NT SETUP from the Main Menu.

Select OPTIONS from the SETUP menu.

Select ADD/REMOVE TAPE DEVICES from the OPTIONS menu.

Select ADD and a menu titled SELECT TAPE FROM FOLLOWING LIST will appear in an on screen window.

To add any EXB-8500 product including the EXB-8500, EXB-8500C, or the EXB-8505. Select EXABYTE 8500 SERIES from the menu.

To add any EXB-8200 product including the EXB-8200 or the EXB-8205 select EXABYTE 8200 SERIES from the menu of supported products.

To add any Exabyte 4 MM product, including the EXB-4200 and the EXB-4200C select EXABYTE 4 MM SERIES from the list of supported products.

The operating system will issue a Inquiry command to determine the specific type of drive that is to be supported and will automatically add that device.

14.7.3 BACK-UP OPERATION

Click the mouse back to MAIN MENU and from the ADMINISTRATION TOOLS menu select BACKUP.

Click on the FILE heading at the top of the screen and a selection of tape options will appear including BACK-UP, ERASE, RESTORE and HARDWARE.

Select HARDWARE and a list of devices that are on the system will appear. Make a choice and exit.

Click the mouse on DISK icon and a window with the disk names will appear.

Select the Disk to be backed-up and a window with all the files of that disk will be listed.

Mark the files to be backed-up and click on the BACKUP heading at the top of the screen.

A window will appear for entering the name for the tape. If no tape name is entered, the tape will be labeled TAPE for <date>.

A window will appear that will show the operation being performed, the directory number, the amount of data transferred and the time elapsed in the data transfer.

14.7.4 RESTORE OPERATION

From the Administration Menu select BACK-UP.

A window will appear indicating the tape name in the device selected. To change devices, select the File heading at the top of the screen and from that menu select Hardware. A list of hardware available on that system will be displayed with the currently selected device highlighted. Select the desired device and exit.

The system will return to the tape device window and will indicate the new tape name in the left box. The right-hand box will provide a line of information regarding the tape. Click on this line and the device will read the directory and display the file names stored on the tape in the right-hand box.

Mark the files to be restored and press the RESTORE heading at the top of the screen. Failure to select files to be restored will cause a message at this point stating, FILES NOT SELECTED.

A window will appear that will show the operation being performed, the directory number, the amount of data transferred and the time elapsed in the data transfer.

If the data indicates 0 bytes of data transferred, no transfer took place even if the log indicates Successful Completion!!!!!!!!!!!!!

Start again, you or my instructions messed up.

15. Macintosh Products

15.1 Novastor

NovaMAC v2.25 supports all Exabyte products.

15.2 Optima Tech

DeskTape v1.6 is a special application for video/graphics. A great package. Will run digital video in real time on Mac screen. Runs best with EXB-8500C but will work with EXB-8500. Optima uses a special version that has a soft bus reset which is a hardware modification. Software will work on standard unit. Need 8CE-0171 which returns OTCA in inquiry field. They will provide the EEimage with software.

15.3 Surf City

Surfguard v2.24 will run all Exabyte tape drives except for 2501. The name is groovy but it is a good package.