Actually, internally MPE/V used a VOLUME NUMBER (usually VOLUME 1 and
LDEV 1 were the same).  Remember having to know the DRT of the device
on a reload?  So if LDEV 2 was assigned a VOLUME NUMBER of 1 it could
be used for booting and all kinds of OS stuff.  I'm sure not
everything would work, but it worked fine in the Internals Class I
took.

Also, a few years ago I learned something that I have not seen
reported latly:

NETCONTROL and NSCONTROL do not work in the SYSSTART file unless you
add a ;OVERRIDE parameter to them,  such as:

NETCONTROL START;NET=LAN1;OVERRIDE
NSCONTROL START;OVERRIDE

I have never seen these parameters documented, but they work great.

Rgds
Mel Rees
[log in to unmask]

>Nope, I don't think so. While ldev 1 was not initialized and added
>automatically during a RELOAD on MPE/V like is done on MPE/XL, there
>was quite a bit of code in the OS that "assumed" a structure was on
>ldev 1. It would actually reference ldev 1 by default, paying no
>attention whatsoever to the actual ldev number in the DST, CST, or
>label table. The OS just knew it HAD to be there. I recall a time or
>two where it wasn't and it caused major problems. I can't remember
>off-hand how the file or structure managed to get on a different drive
>than ldev 1.
>
>Regards,
>
>
>--
>        --Pete Crosby  ([log in to unmask]  a.k.a. [log in to unmask])
>
>          I loved MPE/V. It was so much more cut-and-dried than MPE/XL.
>