🚀 go-pugleaf

In <1991Jun17.094735.78%boot.decnet@edwards-tems.af.mil> martin%boot.decnet@edwards-tems.af.mil writes:

>In article <1991Jun15.133712.1542@gp.co.nz>, gpwrmdh@gp.co.nz writes:
>> 
>> No, you don't remember correcly. V5.0 was a full VMS tape - "point nought" 
>> releases always will be. During V4.x, the "point even number" (i.e, 4.0, 
>> 4.2, 4.4, 4.6) were full VMS tapes. V4.7 definitely was not. The strategy 
>> has changed for V5.x, with generally only the "dash releases" not being 
>> full releases - I think V5.1 may be an exception to this. Certainly V5.0, 
>> 5.2, 5.3, and 5.4 have been full releases.
>> 

>Agreed that .0 releases are ordinarily full VMS releases but 5.0 was not a full
>VMS tape because there was no working standalone backup for 5.0 or 5.1. 
>Standalone backup was fixed with the release of 5.2, which was a full tape.

>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
>Gary S. Martin                !  (805)277-4509  DSN 527-4509
>6510th Test Wing/TSWS         !  Martin@Edwards-TEMS.af.mil
>Edwards AFB, CA 93523-5000    ! 
>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
My VMS V.50 came complete with Standalone Backup on the TK50.  I just checked
it out to make sure.  I know that I used it to install V5.0 from scratch on
a test disk when V5.0 first came out.

I seem to recall the release notes for early VMS V5.x systems cautioning not
to generate new Standalone Backup's with STABACKIT.COM due to some problems,
but the distribution itself does have a Standalone Backup on it, making it
a complete distribution capable of being installed from scratch on a new
disk.

			Harry Herman
			herman@corpane