<div>When I did the VAX station all I did was burn the iso image normally. The SCSI drive was a Toshiba 4x tray drive with a switch for 512 byte sector support. <br/>
<br/>
Any switch settings on the DEC drive? <br/>
You also should be able to use dd on linux/unix to write the install iso to another scsi disk to see if it boots. <br/>
<br/>
Also--what is the scsi rom error message. <br/>
Is it using the weird DEC scsi cable like the DECstations? <br/>
<br/>
Bill<br/>
<br/>
<font color="#888888"><font color="#888888">Sent from </font><font color="#888888"><a href="mailto:pechter@gmail.com">pechter@gmail.com</a></font></font><br/><br/>-----Original Message-----<br/>From: Supratim Sanyal <supratim@riseup.net><br/>To: hecnet@Update.UU.SE<br/>Sent: Mon, 30 Mar 2020 21:44<br/>Subject: Re: [HECnet] Bringing up a MicroVAX 3100-80<br/><br/></div>On 3/30/20 6:14 PM, G. wrote:
<br/>
<br/>
> On Mon, 30 Mar 2020 17:51:21 -0400, Supratim Sanyal wrote:
<br/>
>
<br/>
>> What is the recommended way to recover from "FILNOTCNTG" error?
<br/>
> Boot the system in some other way (cluster satellite, CD-ROM, etc.) and
<br/>
> check that SYSBOOT.EXE is contiguous:
<br/>
>
<br/>
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried
<br/>
to boot dka400, didn't work. The internet is flush with discussions
<br/>
about "special format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks,
<br/>
etc.
<br/>
<br/>
My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid
<br/>
disk image"). So basically I have to research and find a way to burn a
<br/>
CD-ROM in the necessary format that will boot the MicroVAX into DCL so
<br/>
that I can repair the CONTIGUOUS issue on DKA100.
<br/>
<br/>
I am sure lots of people here have done this - any tips welcome while I
<br/>
am trolling the internet.
<br/>
<br/>
KA47-A V1.2-343-V4.0
<br/>
08-00-2B-2D-FF-39
<br/>
24MB
<br/>
<br/>
?? 001 9 NI 0172
<br/>
?? 100 10 SCSI 0034
<br/>
<br/>
>>>
<br/>
<br/>
>>> sh dev
<br/>
<br/>
VMS/VMB ADDR DEVTYPE NUMBYTES RM/FX WP
<br/>
DEVNAM REV
<br/>
------- ---- ------- -------- ----- --
<br/>
------ ---
<br/>
ESA0 08-00-2B-2D-FF-39
<br/>
A/0/0
<br/>
A/0/1
<br/>
A/0/2
<br/>
A/0/3
<br/>
A/0/4
<br/>
A/0/5
<br/>
A/0/6
<br/>
A/0/7
<br/>
DKA100 A/1/0 DISK 1.05GB FX RZ26L 440C
<br/>
DKA200 A/2/0 DISK 2.10GB FX RZ28 442C
<br/>
DKA400 A/4/0 RODISK ...... RM WP RRD42 4.5d
<br/>
..HostID.. A/6 INITR
<br/>
<br/>
<br/>
<br/>
<br/>
> $ DIR/FULL DKA100:[VMS$COMMON.SYSEXE]SYSBOOT.EXE;0
<br/>
>
<br/>
> The "File Attributes" line must show "Contiguous" and hopefully "MoveFile
<br/>
> disabled" too. If not, COPY/CONTIGUOUS it to a newer version of the same in
<br/>
> the same directory and try the boot again.
<br/>
>
<br/>
> The other possibility is that the volume is damaged or does not contain a
<br/>
> valid VMS file structure. In this case the FILNOTCNTG error is just an
<br/>
> indication that VMB.EXE (in ROM) got very confused by your disk's contents.
<br/>
>
<br/>
> HTH, :)
<br/>
> G.
<br/>
>
<br/>
--
<br/>
Supratim Sanyal, W1XMT
<br/>
<a href="tel:3919151">39.19151</a> N, <a href="tel:7723432">77.23432</a> W
<br/>
QCOCAL::SANYAL via HECnet
<br/>
<br/>