VAX panic - buried models?

From: John Allain <John.Allain(a)donnelley.infousa.com> True. And it identifies the basic hardware and CPU. Keep in mind the basic "kits" carry no license or other machine locked stuff. The license is applied during or after the install. Even then I've built and installed systems on my MVII and then carried the media to the MV2000 as both bootable and complete (even licensed if that is within the written license terms). That was how we cloned VMS sustems at DEC as it was faster than using TK50 tapes. I've put the VMS 7.2kit (cdrom) on everythingt from MVII and VS2000 through 3100m76 and would expect it to load and run on most any other VAX as well. The biggest problem of installing on older hardware is the minimum system (ram and disk) has grown during the years and early version coulld fit on 30mb disk and 1mb ram that has grown to over 150mb disk and 4mb ram. Though it is possible to shoehorn the latest version is to less than the specified disk and ram it is a exercise fort the experienced and will produce a system of limited utility. Well since all VAX are by definition matching hardware there is little issue. However there are exceptions like the RTVAX which is not totally cpu compatable VAX and differs in the translate tables, it never ran VMS. The VMS7.2 Hobbiest version is available there. Note HOBBIEST version does not mean stripped or limited. It means it's packaged with many hobbiest desireable packages besides VMS itself. VMSbuild is a standard utility and is used often to configure custom installs once you have a configureation you want to standardize on. Anotehr useful VMS utility for small systems is VMStailor which allows trimming off or adding in libraries, fonts and other peices to tailor a system. Allison