Re: HXDRIVER VAX installation issues in OVMS 7.3

From: Barry Treahy, Jr. (Treahy_at_MMaz.com)
Date: 06/25/04 

Date: Thu, 24 Jun 2004 22:43:00 -0700

Bruce Stafford wrote:

>"Barry Treahy, Jr." <Treahy@MMaz.com> wrote in message news:<40DAE607.1070505@MMaz.com>...
>
>
>>Bruce Stafford wrote:
>>
>>
>>>I have a MicroVAX 3500 with a DRQ3B Q-Bus interface card installed.
>>>Had trouble getting older VAX disks and am using SCSI-1 disks and
>>>CDROM devices via a third party Q-Bus to SCSI-1 Interface module.
>>>Disks and CDROM work fine, however have had trouble loading the
>>>HXDRIVER v1.4 from CDROM. Note that SCSI interface card uses vector
>>>300, so DRQ3B card is set for 310. Have license already installed.
>>>Documentation claims that driver will work with v5.5 and up VMS. Does
>>>anyone have experience with VMS v7.3 with this HXDRIVER v1.4?
>>>
>>>Install goes fine, but does not create the HXDRIVER.exe. The
>>>HX$LOAD.COM file can be run manually and should start a SYSGEN
>>>operation and reload the HXDRIVER.EXE from SYS$LOADABLE_IMAGES
>>>directory and connect to ports, then exit. Even though there is a
>>>VMSINSTAL.HISTORY file that states the driver installation is a
>>>success, the HXDRIVER.EXE cannot be located on the disk, so therefore
>>>the HX$LOAD.COM file does not produce a loadable image. Any helpful
>>>information you can provide will be greatly appreciated.
>>>
>>>
>>>
>>>
>>>
>>My first guess is that if this drive is linked at installation time, the
>>link is failing otherwise the driver would be there, or would be
>>provided as an image on the kit. Look through the DCL procedures and
>>find out where HX comes from, your answers are there...
>>
>>Barry
>>
>>
>
>Barry:
>
>Thanks for your reply. As luck would have it, I tried installing the
>HXDRIVER on another OVMS v6.2 disk (actually on another system) and
>was able to get the driver to load. I then copied the file to TK50
>tape and then copied it to the target system with OVMS v7.3. Was then
>able to load and test the driver successfully. The system messages
>during the install were vastly different than install efforts on OVMS
>v7.3, which indicates it has been tested up to this OS version but
>probably not past it to later versions. I could write a book on how
>much trouble I had to get to today's success, but instead, I would
>appreciate some pointers on how to debug/trace the install steps using
>DCL procedures. The HX014.A file is the kit for this driver. Could not
>open this file to see what was going on during the install (not human
>readable). Is there a method to debug during the install?
>
>
>
That is a VMS saveset file which is commonly labeled .A, .B, .C, etc for
VMSINSTAL kits. Use BACKUP to list the contents, for example:

BACKUP HX014.A/SAVE/LIST

and you'll find, among other files, a file named KITINSTAL.COM which is
actually called by VMSINSTAL after the .A saveset is expanded for that
product. The KITINSTAL is what drives the product specific installation
and it is there that you would have found the VMS version test, or the
link statements...

Barry 

-- 
Barry Treahy, Jr                       E-mail: Treahy@MMaz.com
Midwest Microwave                          Phone: 480/314-1320
Vice President & CIO                         FAX: 480/661-7028

Relevant Pages