Re: VS3100M76 question

Bart.Zorn_at_xs4all.nl
Date: 05/18/05


Date: 18 May 2005 01:16:16 -0700


The only 3100M76 that I know has space for three internal SCSI disks,
no floppy and no CDROM. It has two SCSI busses, one for the internal
disks and one for external devices. If you do not connect any external
devices, it will not complain about a missing terminator on the
external bus.

For the initial installation of VMS I would follow JF's advice, except
that the crimping of an extra connector can be omitted if you
temporarily remove one of the fixed disks.

Be aware that some of the older disks do get pretty hot when they have
to run for a prolonged time with the cover removed. The cover provide
for a better guided airflow around the disks.

HTH,

Bart Zorn

JF Mezei wrote:
> The Eighth Doctor wrote:
> > Next question, what are the methods for installing an internal
CDROM drive?
>
> I have a 3100 model 30. What I did was to crimp a SCSI connector on
the
> SCSI ribbon cable. Used the power for the diskette drive. Deposited
the
> CDrom drive on top of the topless unit, and was able to install VMS
on
> it. Not a permanent installation, but it worked.
>
> the other way is to use anothet vms system as boot node, and boot the
> 3100 via ethernet into a cluster and then backup the B saveset to the
> 3100's drive.
>
> you then need to look at the sysgen parameters stored on the 3100
system
> (from the B saveset) and take note of the startup file.
>
> Copy the 3100's sysgen parameters stored in the 3100's system
specific
> directory on the boot node to the hard drive of the 3100. And then
apply
> the startup file you jotted down from the B save set config. You also
> need to copy the cluster password file. Also make sure the 3100 has a
> different allocation class from the other node
>
> You can then boot the 3100. It will boot as a member of the cluster
and
> thus have access to the other node's drives, and will execute the VMS
> installation continuation. When it asks for the device name, just
enter
> the fully qualified (eg: $x$yyyy: ) device name of the cd drive on
the
> other node and then the VMS install will continue.



Relevant Pages

  • Re: New XP Installation on new hard drive - will not read from CD
    ... >>Assuming your system is set to boot from the CD-ROM ... >>To Repair a Windows XP Installation using Recovery ... drive and both CD drives are ...
    (microsoft.public.windowsxp.basics)
  • Re: XP Home and XP Pro on two separate drives
    ... , while the CD and DVD drives are on the other ... slave and boot from my old XP configuration (with the old drive as ... :> In the case of SATA HDs, the default HD boot order is just ... :> During installation of WinXP, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: moving from FC 5 to FC 8
    ... New computer now has 3 hard drives in the following configuration. ... sdb - new 500 GB drive with Windows Vista ... Used the BIOS to alter the boot sequence to: ... So I'm pretty sure that the Kubuntu installation left the MBR on sdb intact from the Windows installation and upgraded the GRUB installation on sda from the FC 5 installation. ...
    (Fedora)
  • Re: Boot problems with RAID
    ... The drives would definitely have been different now as I had booted to, and performed some actions on, just one of the 750s. ... Maybe I was daft to leave the drives hooked up and reboot to the old XP install but what would have happened to cause my problem? ... I don't know what to make of the fact that the array looks ok from the system ROM or that the Recovery Console's map command appears to see it correctly, but the error message about disk hardware configuration problems tells us its trying to boot from the wrong disk or from a disk that is not on the system, the boot.ini file points to an invalid location. ... See if you can boot the installation with a boot floppy. ...
    (microsoft.public.windowsxp.general)
  • Re: Boot problems with RAID
    ... did boot up OK. ... I wanted to avoid having to un-RAID the drives as the rebuild takes an age ... drives hooked up and reboot to the old XP install but what would have ... See if you can boot the installation ...
    (microsoft.public.windowsxp.general)