[HECnet] Boot VAX from Alpha host Infoserver?

[Kari Uusim ki]

Indeed, the memory is limited, but it doesn't much affect the Infoserver software. It's not a resource hog like modern software.

Kari




Steve Davidson wrote:
Max memory supported on the original MicroVAX 3100 M10 version was 4MB.   I know, because I was one of the DEC internal field-test sites.   Great little box!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Kari Uusim  ki
Sent: Wednesday, November 25, 2009 16:16
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Boot VAX from Alpha host Infoserver?
Fred,
I really appreciate your efforts trying to get the (host based) Infoserver software to serve you, but anyway I suggest you build your own Infoserver (like the original one).
The instructions are simple.
The needed HW consist of a MicroVAX 3100 (model 10 or 20, not the newer ones), one or two suitable SCSI disk drives (narrow) and a SCSI CD-ROM drive (also narrow).
The needed software is available on OpenVMS Freeware 8, disc 1. There's a Zip file where the needed images are. You just have to burn two CD's, the Infoserver software CD and the Disc Function CD.
When you have the HW assembled and burnt the CD's you just boot from the Infoserver software CD like:
>>> B/R5:D0000000 <cd drive>
Then the MicroVAX will boot the Infoserver software from the CD and then you will be able to install the software on the disc drive.
When you are finished halt the MicroVAX and boot from the disc drive using the same syntax. Voil  , you have created your own Infoserver.
Then you can create a partition on the disc sufficiently big to have space for the OpenVMS VAX CD contents. Do remember to enable MOP. When it's ready, create a service for the partition and mount your OpenVMS VAX on your Alpha (or any VMS node). Start the ESS client and find the service from your Infoserver. Connect and bind the service with the option /write. Mount the DADx: device on your Alpha and then perform and image backup from the CD to the Infoserver partition.
Now you should be able to boot from the Infoserver and install VAX/VMS.
I hope I didn't forget anything as I wrote this out from memory.
Cheers,
Kari
Fred wrote:
On Wed, 25 Nov 2009, gerry77 at mail.com wrote:

request that the host-based thing is not able to understand, so the ISL sits
there until a timeout is reached and an error is sent to the poor user. :-\
You may be on to something here.   I only say this because while sitting in front of Wireshark (ethernet sniffer) I see various LAST protocols come by, and when I look they are from the VAX.

If I look in LASTCP, I see the VAX as a client - BUT in the Infoserver software itself, there is no connection to the service that I set up. It's as almost as the request never makes it to the Alpha -or- the software on the Alpha doesn't understand the request (as you say) and ignores it.

It would be nice to be able to sniff the initial phases of the dialog
between different architecture systems and an InfoServer, just to check if
For grins if you'd like I can send you some traces off-list.

A final silly question: do you have actually seen any VAX installing VMS
from a host-based InfoServer? I have missed this simple "detail"! :-)
I have not.   In fact before about a week ago I did not know the host-based Infoserver software existed and was sitting, waiting on my Alpha!

Right now my current course of action is to set up OpenVMS on SIMH, set that node up as a cluster, and satellite boot the real VAX so I can get access to the disks (cdrom with 7.3 on it).   I installed OpenVMS into the SIM last night, and will hopefully get the networking working tonight.

P.S.: Excuse my English: it's not my native language and sometimes I'm very
dubious about the understandability of my sentences. :-P
No problem whatsoever - I can understand you just fine.

Cheers,

Fred

--- All parts should go together without forcing.   You must remember that the parts you are reassembling were disassembled by you.   Therefore, if you can't get them together again, there must be a reason.   By all means, do not use a hammer.
              -- IBM maintenance manual, 1925


.

.