It's actually even simpler than that.
On MPE, you should be able to connect any size SE SCSI or Fast SCSI disk drive
using any name you see in IODFAULT.PUB.SYS for such a disk drive, for example
ST34573. The main thing is to make sure the DM (device manager or driver) that
gets used is SCSI_DISC_DM. This also applied to CD-ROM.
You can connect any size Differential FW SCSI disk drive using any name in the
IODAULT.PUB.SYS for such a device, for example ST19171WD. The main thing is to
make sure the DM (device manager or driver) that gets used is
SCSI_DISK_AND_ARRAY_DM.
Continuing on, you can connect any SE SCSI DDS-1, DDS-2 or DDS-3 tape device
using any name in the IODAULT.PUB.SYS for such a device, for example HPC1502A.
The main thing is to make sure the DM (device manager or driver) that gets
used is SCSI_TAPE_DM.
Finally, you can connect any Differential FW SCSI DLT4000, DLT7000 and DLT8000
tape device using any name in the IODAULT.PUB.SYS for such a device, for exa
mple DLT4000. The main thing is to make sure the DM (device manager or driver)
that gets used is SCSI_TAPE2_DM.
The only other SCSI related drivers (DM or device manager,) are the SCSI pass
trough driver, MO_SCSI_PTHRU_DM and the SCSI printer driver, SCSI_PRINTER_DM.
The former is used for MO devices and also by Hiback to manage and use DDS and
DLT library and the latter is used for the HP 5000/F100 printer.
SCSI is SCSI. It is a well-know, well-understood standard which makes it very
easy to integrate and use all sorts of similar devices. Right now, MPE is
fairly behind the times WRT SCSI as it does not support Ultra SCSI, Ultra2 SCSI
and Ultra160 SCSI. Also, MPE only supports a few SCSI devices, such as disk,
arrays, DDS, DLT and a printer. It does not support scanner, autoloaders (on
its own, Hicomp had to write the driver), or other SCSI devices.
So 6 drivers in all.
SCSI_DISC_DM for SE SCSI and FAST SCSI disk drives of any size.
SCSI_DISK_AND_ARRAY_DM for Differential F/W SCSI disk drives and arrays of any
size.
SCSI_TAPE_DM for SE DDS devices of any format.
SCSI_TAPE2_DM for Differential F/W DLT devices of any format.
MO_SCSI_PTHRU_DM for MO and other controllers or robots.
SCSI_PRINTER_DM for the HP 5000/F100 printer.
Kind regards,
Denys. . .
Denys Beauchemin
HICOMP
(800) 323-8863 (281) 288-7438 Fax: (281) 355-6879
denys at hicomp.com www.hicomp.com
-----Original Message-----
From: Wirt Atmar [SMTP:[log in to unmask]]
Sent: Thursday, July 06, 2000 12:04 PM
To: [log in to unmask]
Subject: Re: Seagate vs HP firmware on ST34573
Paul writes:
> Thanks for all the replies. My 918LX uses the pedestrian single ended
> SCSI interface for its one and only disk currently installed. My
> space woes were somewhat abated through some aggressive inspection of
> what is actually stored on our disk;
Just to add my comments regarding "SCSI is SCSI" to those that have gone
before, I too had a 918DX that had only one 1.6 GB internal disc drive and
was running very short of space. Because I had a little extra time this last
weekend, I decided to see if I couldn't do something about that shortage of
space.
I remembered that about three or four years ago I had bought a single-ended
SCSI disc drive from APS for one of our Macintoshes. The single-ended SCSI
disc drive was marketed wholly for Macs, and indeed, for a bit of time I did
have the disc drive mounted on a Mac, but as things worked out, I thought
that I needed it more for a new project and tried to mount in on our 917 as a
private volume.
Everything went swimmingly three years ago. I installed it as an HP7935
look-alike, and everything seemed to work just fine. However, as things
worked out, the project I intended to use this disc drive for never got off
of the ground and the disc just spinned for a year, unused, before I decided
to demount it and put in a closet.
That was two years ago. A week ago, I took the disc out of the closet -- but
by now, my failing memory being what it is -- I couldn't remember for the
life of me what size the disc was or who made it. All I knew for sure was
that it was single-ended.
Because there were absolutely no markings on the APS case, other than the APS
logo, I took the disc drive apart to see what the heck it was, but that
proved equally fruitless. All I was able to discover was that fact that the
disc was made by Quantum, but there was no indication anywhere on the
physical drive as to what the size it was, or even its model number.
More discouragingly, Quantum isn't listed anywhere in the IODFAULT.PUB.SYS
listings.
I then spoke to Rene Woc of Adager, as I often do when I'm stumped as to what
to do next, and Rene had a particularly good idea. Take the 918 down and
connect the disc to an unused SCSI address, and then, when bringing up the
machine, run ODE's MAPPER and see if it could identify the disc. If it could
ID the disc, then go ahead and bring the machine up. The worst that could
happen is that I'd crash the machine, but then what are backups for?
Lo and behold, MAPPER identified the disc as a Quantum Fireball TM_3200S
drive, and after looking in the archives at the Quantum web site, I deduced
that it was a 3.2GB drive. I now had the complete specificiations of the
drive (I'm still fairly impressed with the idea of the web).
Based on this information, I brought the 918DX up, with the disc drive being
partially recognized (it was "mounted" but otherwise inaccessible). After
doing some VOLUTIL magic, I was able to scratch it, reformat it, and mount it
as a second member of the MPE system volume:
------------------------ Volume Information ------------------------
Ldev Type Index Volume Set Name Volume Name
1 Master 1 MPEXL_SYSTEM_VOLUME_SET MEMBER1
2 Member 2 MPEXL_SYSTEM_VOLUME_SET MEMBER2
3 Unmounted 0
4 Unmounted 0
11 Unmounted 0
My primary concern at this point was: what driver do I use to assign to the
new LDEV 2, especially given that there were no Quantum drives listed in
IODFAULT? In the absence of any other information, I just left the driver as
the one that had been pre-configured by someone at HP for LDEV 2:
------------------------- IO Configuration -------------------------
Highest Ldev: 311
Ldev Path Device Type Device ID Device Mgr Class
Name
1 56/52.6.0 Disk HPC2247M1 SCSI_DISC_DM
2 56/52.5.0 Disk HPC2247M1 SCSI_DISC_DM
3 56/52.4.0 Disk HPC2247M1 SCSI_DISC_DM
4 56/52.3.0 Disk HPC2247M1 SCSI_DISC_DM
I was most impressed that doing this not only worked, but that the Device ID
now seems to be a relic of the past. As it turns out, neither of the two disc
drives on this machine are what they say they are, and SYSINFO reports this
fact:
Device Adapter(56/52.5) --- PSEUDO
Device(56/52.5.0) [ ldev 2 HPC2247M1 DISK]
***DEV CONFIG MISMATCH, ACTUAL ID = HPFIREBALL_TM3200S***
Device Adapter(56/52.6) --- PSEUDO
Device(56/52.6.0) [ ldev 1 HPC2247M1 DISK]
***DEV CONFIG MISMATCH, ACTUAL ID = ST34572N***
(noticing of course, that the Quantum Fireball label has now been changed to
HPFIREBALL :-).
All in all, I'm fairly impressed. The disc was now mounted and properly
recognized as it size -- and all of the new files (customer databases) were
placed on this new empty disc, in preference to alternating back and forth,
the way that disc fills had been done on the Classics.
Somebody has clearly done their homework, and is to be congratulated.
Wirt Atmar
|
