[HECnet] Bringing up a MicroVAX 3100-80

[Supratim Sanyal]

On 3/30/20 6:14 PM, G. wrote:

> On Mon, 30 Mar 2020 17:51:21 -0400, Supratim Sanyal wrote:
>
>> What is the recommended way to recover from "FILNOTCNTG" error?
> Boot the system in some other way (cluster satellite, CD-ROM, etc.) and
> check that SYSBOOT.EXE is contiguous:
>
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried 
to boot dka400, didn't work. The internet is flush with discussions 
about "special format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks, 
etc.

My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid 
disk image"). So basically I have to research and find a way to burn a 
CD-ROM in the necessary format that will boot the MicroVAX into DCL so 
that I can repair the CONTIGUOUS issue on DKA100.

I am sure lots of people here have done this - any tips welcome while I 
am trolling the internet.

KA47-A V1.2-343-V4.0
08-00-2B-2D-FF-39
24MB

?? 001   9        NI  0172
?? 100  10      SCSI  0034

 >>>

 >>> sh dev

   VMS/VMB      ADDR      DEVTYPE    NUMBYTES     RM/FX WP    
DEVNAM      REV
   -------      ----      -------    --------     ----- --    
------      ---
   ESA0         08-00-2B-2D-FF-39
                A/0/0
                A/0/1
                A/0/2
                A/0/3
                A/0/4
                A/0/5
                A/0/6
                A/0/7
   DKA100       A/1/0     DISK         1.05GB FX            RZ26L       440C
   DKA200       A/2/0     DISK         2.10GB FX            RZ28        442C
   DKA400       A/4/0     RODISK      ......       RM WP    RRD42       4.5d
  ..HostID..    A/6       INITR




> $ DIR/FULL DKA100:[VMS$COMMON.SYSEXE]SYSBOOT.EXE;0
>
> The "File Attributes" line must show "Contiguous" and hopefully "MoveFile
> disabled" too. If not, COPY/CONTIGUOUS it to a newer version of the same in
> the same directory and try the boot again.
>
> The other possibility is that the volume is damaged or does not contain a
> valid VMS file structure. In this case the FILNOTCNTG error is just an
> indication that VMB.EXE (in ROM) got very confused by your disk's contents.
>
> HTH, :)
> G.
>
-- 
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet