Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bloom-picayune.mit.edu!mintaka!think.com!sdd.hp.com!uakari.primate.wisc.edu!dali.cs.montana.edu!ogicse!ucsd!mvb.saic.com!eafbvax!eafbtems!martin From: martin%boot.decnet@edwards-tems.af.mil Newsgroups: comp.sys.dec Subject: Re: VMS upgrade path question Message-ID: <1991Jun17.094735.78%boot.decnet@edwards-tems.af.mil> Date: 17 Jun 91 16:47:34 GMT References: <962@hadron.COM> <1991Jun13.225429.1537@gp.co.nz> <1991Jun14.112726.76@%boot.decnet@edwards-tems.af.mil> <1991Jun15.133712.1542@gp.co.nz> Followup-To: comp.sys.dec Organization: T&E Mission Simulator - Edwards AFB, CA Lines: 19 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 ! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -