[Info-vax] InfoServer 150

[Bill Gunshannon]

On 1/27/19 10:46 PM, Bob Wilson wrote:
> 
>>
>> They won't mount on a real VAX running VMS, why would I expect
>> them to mount on SIMH?  I am loading ImgBurn.  That will be
>> the 7th total and 3rd Windows application.  You will pardon me
>> if I don't feel confident that this is going to solve the
>> problem.
>>
>> bill
> 
> Bill,
> 
> Can you get the .img/.iso file(s) onto a Alpha or IA64 VMS system that has LD running on it? Sorry, I don't recall what version of VMS started to include SYS$LDDRIVER and associated stuff (I don't think that it ever made it to VAX VMS). If LD is present on your system you need to run the startup procedure SYS$STARTUP:LD$STARTUP.COM.

Once again, all I have are VS3100's and my Infoserver 150.

> 
> In any case, you should be able to LD CONNECT the .img/.iso files, and MOUNT them. If the .img/.iso contains a ODS-2/5 or ISO-9660 volume then VMS ought to be able to MOUNT the LD device created by LD CONNECT.
> 
> This will at least allow you determine if the .img/.iso is a VMS ODS or ISO-9660 structure, and if it is to look at what's in it. If it's not a VMS ODS or ISO-9660 (i.e. MOUNT/OVER=ID fails) you can do some forensics with MOUNT/FOREIGN and DUMP.

It's "Files-11 On-Disk Structure (ODS-2); VAX/VMS or OpenVMS file
system; volume label is 'IS_V35      '"

I don't need VMS to look at the raw contents.  I have looked at
them enough to determine VOLUME NAME and other things like the
fact the the two supposedly boot images both contain the string
"is not a system disk" at the head of the data they contain.
Do not know what that is supposed to mean.

bill