[Info-vax] InfoServer 150

[johnwallace4 at yahoo.co.uk]

On Sunday, 27 January 2019 23:49:37 UTC, Bill Gunshannon  wrote:
> I am getting real close to giving up on this.
> 
> I just decided to take a look at the contents of the
> images provided in Freeware 8.0 Infoserver.
> 
> 3 of them are MSDOS floppy images.
> 4 of them have the statement "IS_KEY_DISK" in the beginning of the
> img.
> 
> And that leaves two.
> 
> VTX Software V2.1
> InfoServer/VMS
> ag-pjjhh-be.img
> 
> InfoServer/VMS V3.5
> ag-r7lfa-bs.img
> 
> Both of these have statements in the beginning of the image as well.
> 
> VXT021          is not a system disk
> 
> IS_V35          is not a system disk
> 
> Is it just me or wold this mean none of them are bootable.  And, if
> that is the case, how does one do an initial load of an Infoserver?
> 
> There are other anomalies.  Like the readme says VTX Software V2.1
> but the disklabel is VXT021.  Is there no one here who ever created
> an Infoserver 150 from scratch?  Did they always come from DEC with
> all the software loaded and could only be reloaded by a Service Tech
> from DEC?  Are there no Service Techs here to answer this question?
> 
> bill

Wow, somebody finally noticed that VTX and VXT aren't the same.

The reference to VTX is a presumably a persistent trypo in the
freeware readme in question (and apparently elsewhere too, see 
below). 

There was a DEC product called VTX,but it's of little relevance 
in this discussion. Mind you, this discussion... no, let's not 
go there.

Potentially relevant discussion, with tryping error in product 
name:
http://www.vcfed.org/forum/showthread.php?23342-DEC-VTX-2000-and-vtx2000-sys

Relevant VXT and Infoserver documents, product name correct, 
might include:
https://terminals-wiki.org/wiki/index.php/DEC_VXT2000

https://archive.org/details/h42_DEC_VXT_2000_Windowing_Terminal_User_Information

http://www.bitsavers.org/pdf/dec/ethernet/infoserver/AA-PJXJC-TE_InfoServer_System_Operations_Guide_Oct94.pdf

and various related.

Anyway, if it's not working for you, you're probably
holding it wrong, or it's got a virus, or something along
those lines. Have you tried switching it off and on again?