HP3000-L Archives

August 2005, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James B. Byrne" <[log in to unmask]>
Reply To:
James B. Byrne
Date:
Tue, 30 Aug 2005 15:04:18 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
Just a note for those that expressed an interest in how this trial
(in many senses of the word) was proceeding.

I have successfully loaded MPE/iX 7.0 onto an IBM DGHS18Y SCSI SE
17/18GB drive although MPE/iX has truncated the volume to 4.7GB.
This drive uses a native 80pin connector and I am using an adapter
of unknown manufacture to convert it to a 50pin SCSI-2.  This item
together with the adapter was purchased on eBay for $39.00 USD plus
$11.00 S/H to Canada.  However, it did require a low level format
before MPE/iX would recognize it.

I performed the necessary LLF from the Advansys SCSI-2 50pin
adapter (c. 1999) that I have in the domain member server that I
use as a personal workstation. The format took about 1.5 hours to
complete.

I have also successfully added a used ST318417N as a private
volume.  The disc required a LLF as well before MPE/iX or Windows
would recognize it.  However, the LLF for the Seagate drive only
required about 30 minutes to complete vice 90 minutes for the IBM
UltraStar. A different ST318417N that was purchased new did not
require a LLF for MPE/iX to recognize it. I infer that both the IBM
and the used ST drive had been installed in systems that had a
sector topography that varied from that expected by the HP3000.

I have configured all discs ldevs with a device ID of ST318416N as
it seems from inspection of IODFAULT.PUB.SYS that the MPE driver
and device classes and sub-classes are all the same for SCSI SE
drives regardless of size or manufacturer.  It further seems
probable that the device ID probably has little real meaning as it
appears that MPE diagnostics get their device information directly
from the drive itself.

After some experimentation with seldom used (by me) MPE commands
regarding volume management I eventually got these drives mounted
via some variant of the following:

volutil: NEWSET HAL_BKUP MEMBER1 2

I am presently installing the FOS and SUBSYS tapes and things seem
to be going swimmingly.  I will report on further developments.

Regards,
Jim

--
     *** e-mail is not a secure channel ***
mailto:byrnejb.<token>@harte-lyne.ca
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
<token> = hal                 Canada L8E 3C3

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2