Hello again,

	I'm still stuck at the miniroot stage and can't get a root up. I
write the miniroot to TK50 and after booting with the BOOT TK50 I arrive
at the prompt where I edlabel. After configuring ra81 I reboot and here's
where I get confused. When I call up 'copy' it appears to write the
miniroot if I use mt(0,1) as source and ra(0,1,1) as target. I wish to use
DUA1: as the NetBSD drive and partition 'b' to hold the miniroot which I
believe translated to ra(0,1,1). If I try mt(0,0) as suggested the tape
goes off into never-never land and never completes whatever operation it
appears to be doing during the 'reading...' stage. using mt(0,1) returns
the correct 'completion' message and requests a reboot. On the next reboot
from the Boot tape I try everything I can think of to bring up a miniroot
from tape or from ra(0,1,1) without anything but a 'can't find directory'
message.

Additionally, as an experiment I wrote the boot file to DUA1: via the DCL
command copy/contig TK50-file1-12G DUA1: after remounting my DUA1: drive
as a foreign disk. I could then boot immediately using b/3 DUA1: and
attempt to get miniroot up but still no luck.

I'm working with the MINIROOT and BOOT images from ftp.bitcon.no and I
need to know the ACTUAL sequence of events to bring up the miniroot for
this image. I'm getting mixed signals in what I should type and what
should work between the FAQ, the cues within the boot loader, suggestions
from the list, and the available literature on NetBSD, the Vax port, and
tech-Install. Can anyone drop me a line with a less ambiguous response
they know to work with 12G, a 630 uVAX, and TK50 tape drive. I will try to
furnish you with any and all further info you may need to narrow the
instructions to bring up the miniroot to one set that is definitive. I
still can't tell if I've got a problem here or I'm just a little dense and
have missed something.

Thanks for those who responded previously.

regards,

Dan

PS - Since I have the miniroot and root images on DUB0: is there an easier
way to install using VMS 5.2_2? I could easily punch the boot onto the
drive but after that the operations would require that partition level
accesses be possible via VMS, no? Any clarification would help.