Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.vms > #58574 > unrolled thread

Alpha V8.4-2 distribution

Started byDavid Froble <davef@tsoft-inc.com>
First post2016-06-18 23:51 -0400
Last post2016-06-22 07:18 -0700
Articles 20 on this page of 43 — 12 participants

Back to article view | Back to comp.os.vms

Contents

  Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-18 23:51 -0400
    Re: Alpha V8.4-2 distribution Steven Schweda <sms.antinode@gmail.com> - 2016-06-18 21:17 -0700
      Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-19 01:31 -0400
        Re: Alpha V8.4-2 distribution helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2016-06-19 08:00 +0000
          Re: Alpha V8.4-2 distribution moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-06-19 13:14 +0000
            Re: Alpha V8.4-2 distribution Hans Vlems <hvlems@freenet.de> - 2016-06-19 08:49 -0700
              Re: Alpha V8.4-2 distribution moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-06-20 01:43 +0000
                Re: Alpha V8.4-2 distribution Paul Sture <nospam@sture.ch> - 2016-06-20 04:57 +0200
                  Re: Alpha V8.4-2 distribution Steven Schweda <sms.antinode@gmail.com> - 2016-06-19 21:15 -0700
                  Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-20 01:02 -0400
                    Re: Alpha V8.4-2 distribution Steven Schweda <sms.antinode@gmail.com> - 2016-06-19 23:51 -0700
                      Re: Alpha V8.4-2 distribution Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2016-06-20 19:25 +0000
                        Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-20 19:07 -0400
                          Re: Alpha V8.4-2 distribution Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> - 2016-06-21 12:57 +0000
                Re: Alpha V8.4-2 distribution lawrencedo99@gmail.com - 2016-06-26 20:22 -0700
    Alpha V8.4-2 distribution Hans Vlems <hvlems@freenet.de> - 2016-06-18 23:35 -0700
    Re: Alpha V8.4-2 distribution helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2016-06-19 07:58 +0000
    Re: Alpha V8.4-2 distribution Jan-Erik Soderholm <jan-erik.soderholm@telia.com> - 2016-06-19 11:09 +0200
      Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-19 22:39 -0400
        Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-20 01:04 -0400
        Re: Alpha V8.4-2 distribution Jan-Erik Soderholm <jan-erik.soderholm@telia.com> - 2016-06-20 09:29 +0200
          Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-20 12:17 -0400
            Re: Alpha V8.4-2 distribution Jan-Erik Soderholm <jan-erik.soderholm@telia.com> - 2016-06-20 21:00 +0200
              Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-20 19:10 -0400
            Re: Alpha V8.4-2 distribution Steven Schweda <sms.antinode@gmail.com> - 2016-06-20 13:54 -0700
              Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-20 19:13 -0400
                Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-21 22:12 -0400
                  Re: Alpha V8.4-2 distribution Steven Schweda <sms.antinode@gmail.com> - 2016-06-21 19:47 -0700
                    Re: Alpha V8.4-2 distribution Hans Vlems <hvlems@freenet.de> - 2016-06-22 11:00 -0700
                  Re: Alpha V8.4-2 distribution Jan-Erik Soderholm <jan-erik.soderholm@telia.com> - 2016-06-22 11:11 +0200
                    Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-22 16:08 -0400
                      Re: Alpha V8.4-2 distribution Jan-Erik Soderholm <jan-erik.soderholm@telia.com> - 2016-06-23 01:21 +0200
                        Re: Alpha V8.4-2 distribution Stephen Hoffman <seaohveh@hoffmanlabs.invalid> - 2016-06-23 08:32 -0400
                  RE: Alpha DVD (was: Re: Alpha V8.4-2 distribution) Stephen Hoffman <seaohveh@hoffmanlabs.invalid> - 2016-06-22 09:11 -0400
                    Re: Alpha DVD Eberhard Heuser <eberhard.heuser@chemie.uni-konstanz.de> - 2016-06-22 16:56 +0200
                      Re: Alpha DVD Stephen Hoffman <seaohveh@hoffmanlabs.invalid> - 2016-06-22 11:52 -0400
                    Re: Alpha DVD David Froble <davef@tsoft-inc.com> - 2016-06-22 16:09 -0400
            Re: Alpha V8.4-2 distribution Hans Vlems <hvlems@freenet.de> - 2016-06-20 14:47 -0700
    Re: Alpha V8.4-2 distribution dgordonatvsi@gmail.com - 2016-06-21 10:26 -0700
      Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-21 14:48 -0400
        Re: Alpha V8.4-2 distribution Steven Schweda <sms.antinode@gmail.com> - 2016-06-21 14:11 -0700
          Re: Alpha V8.4-2 distribution David Froble <davef@tsoft-inc.com> - 2016-06-21 18:42 -0400
            Re: Alpha V8.4-2 distribution Steven Schweda <sms.antinode@gmail.com> - 2016-06-22 07:18 -0700

Page 1 of 3  [1] 2 3  Next page →

#58574 — Alpha V8.4-2 distribution

FromDavid Froble <davef@tsoft-inc.com>
Date2016-06-18 23:51 -0400
SubjectAlpha V8.4-2 distribution
Message-ID<nk54r8$r72$1@dont-email.me>
It's Saturday night, or I'd ask VSI.  So it's your lucky day to consider my 
question.

Got the Alpha 8.4-2 evaluation kit.  Unzipped it on my Alpha, got an iso image, 
which I was able to mount using LD.  The kit will work as an upgrade to V8.3, or 
later, but will not (according to the release notes) install on an empty disk. 
No problem, made an image copy of my 8.3 system disk.

Now, it's been a LONGGGG time since I did any installations / upgrades, and I'm 
not sure what can be done.  What I remember is you boot off the distribution 
media and use the menu to install or upgrade.  Can't boot off an LD container, 
since it needs VMS up before LD works.  Chicken and egg issues ....

What I think I need to do is backup /image the LD container onto a spare disk. 
Can't use the optical drive.  The local crumudgen got a good laugh when I told 
him I was trying to read a DVD and finally realized the Alpha had a CD drive. 
Gonna attempt to fix that next week.  Don't think the distribution will fit on a CD.

Anyway, yeah, I'll get around to it, my question.  Can I upgrade VMS while 
running on a system disk, or do I need to have distribution media I can boot from?

[toc] | [next] | [standalone]

#58577

FromSteven Schweda <sms.antinode@gmail.com>
Date2016-06-18 21:17 -0700
Message-ID<7c3bfbd2-2213-4994-aef6-2a005058c90c@googlegroups.com>
In reply to#58574
> [...] What I remember [...]

   How does that compare with what's in the Upgrade and
Installation Manual?

> Don't think the distribution will fit on a CD.

   If you disclosed the size of the disc image, then an
informed opinion might be easier to obtain.

[toc] | [prev] | [next] | [standalone]

#58583

FromDavid Froble <davef@tsoft-inc.com>
Date2016-06-19 01:31 -0400
Message-ID<nk5an8$7qh$1@dont-email.me>
In reply to#58577
Steven Schweda wrote:
>> [...] What I remember [...]
> 
>    How does that compare with what's in the Upgrade and
> Installation Manual?

Only as a last resort RTFM ...

:-)

>> Don't think the distribution will fit on a CD.
> 
>    If you disclosed the size of the disc image, then an
> informed opinion might be easier to obtain.

It won't fit.  The TCP/IP is separate.  But, I took out the CD drive anyway.  I 
got plenty of 36 GB disks.  Easiest to just put the distribution, bootable, on one.

The VMS stuff is just over about a GB, un-zipped.

ALPHAX842.IMG;1            2000000/2000000  [1,1]       (RWED,RWED,RE,)
ALPHAX842.ZIPEXE;1         1151413/1151416  [1,1]       (RWED,RWED,RE,)
PAK.TXT;1                        5/8        [1,1]       (RWED,RWED,RE,)
V84_IG.PDF;1                 14616/14616    [1,1]       (RWED,RWED,RE,)
V84_IG.ZIP;1                 11931/11936    [1,1]       (RWED,RWED,RE,)
VSI-AXPVMS-TCPIP-V0507-13ECO5-1.PCSI$COMPRESSED;1
                             109029/109040   [1,1]       (RWED,RWED,RE,)
VSI-AXPVMS-TCPIP-V0507-13ECO5-1.PCSI$COMPRESSED_VNC;1
                                  2/16       [1,1]       (RWED,RWED,RE,)
VSI-AXPVMS-TCPIP-V0507-13ECO5.ZIPEXE;1
                              94921/94928    [1,1]       (RWED,RWED,RE,)

Don't know why they made the IG a PDF, I don't have that capability on my VMS 
systems.  Guess I'll move it to weendoze to read it.

I also don't have a clue why there is 272 directories, SYS0, SYS1, SYS??, and so 
on.  Haven't looked yet to see if any have files.

[toc] | [prev] | [next] | [standalone]

#58592

Fromhelbig@asclothestro.multivax.de (Phillip Helbig (undress to reply))
Date2016-06-19 08:00 +0000
Message-ID<nk5je4$2j53$3@news.kjsl.com>
In reply to#58583
In article <nk5an8$7qh$1@dont-email.me>, David Froble
<davef@tsoft-inc.com> writes: 

> I also don't have a clue why there is 272 directories, SYS0, SYS1,
> SYS??, and so on.  Haven't looked yet to see if any have files. 

272?  Really?  There should be 0 through FF.  The idea is that you can 
boot from any root for the upgrade.

[toc] | [prev] | [next] | [standalone]

#58602

Frommoroney@world.std.spaamtrap.com (Michael Moroney)
Date2016-06-19 13:14 +0000
Message-ID<nk65s3$n7i$1@pcls7.std.com>
In reply to#58592
helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) writes:

>In article <nk5an8$7qh$1@dont-email.me>, David Froble
><davef@tsoft-inc.com> writes: 

>> I also don't have a clue why there is 272 directories, SYS0, SYS1,
>> SYS??, and so on.  Haven't looked yet to see if any have files. 

>272?  Really?  There should be 0 through FF.  The idea is that you can 
>boot from any root for the upgrade.

What's amusing is I noticed a long time ago that one of the 0-FF roots is 
actually missing.

They're all clones of each other ($ SET FILE/ENTER) so the upgrade will
happen no matter which root is your default (unless it's the missing one).

[toc] | [prev] | [next] | [standalone]

#58610

FromHans Vlems <hvlems@freenet.de>
Date2016-06-19 08:49 -0700
Message-ID<142565cc-8fa5-4df0-8ee4-5923925e1413@googlegroups.com>
In reply to#58602
Which one,[SYS0E.]?

[toc] | [prev] | [next] | [standalone]

#58632

Frommoroney@world.std.spaamtrap.com (Michael Moroney)
Date2016-06-20 01:43 +0000
Message-ID<nk7hnn$rtn$1@pcls7.std.com>
In reply to#58610
Hans Vlems <hvlems@freenet.de> writes:

>Which one,[SYS0E.]?

If I remember, it was [SYSD.]  I don't have an upgrade disk to check at 
the moment, I'll check tomorrow if nobody else beats me to it.

I believe that in CI VAX days root F was reserved for upgrades, E for 
standalone backup. I don't know if D or anything else was reserved perhaps
making this deliberate.

[toc] | [prev] | [next] | [standalone]

#58638

FromPaul Sture <nospam@sture.ch>
Date2016-06-20 04:57 +0200
Message-ID<8m2k3d-9gh.ln1@news.chingola.ch>
In reply to#58632
On 2016-06-20, Michael Moroney <moroney@world.std.spaamtrap.com> wrote:
> Hans Vlems <hvlems@freenet.de> writes:
>
>>Which one,[SYS0E.]?
>
> If I remember, it was [SYSD.]  I don't have an upgrade disk to check at 
> the moment, I'll check tomorrow if nobody else beats me to it.

On the ALPHA084.ISO image I received as part of the Hobbyist kit in May-2015:

$ dir SYS%

Directory DUC0:<000000>

SYS0.DIR;1          SYS1.DIR;1          SYS2.DIR;1          SYS3.DIR;1         
SYS4.DIR;1          SYS5.DIR;1          SYS6.DIR;1          SYS7.DIR;1         
SYS8.DIR;1          SYS9.DIR;1          SYSA.DIR;1          SYSB.DIR;1         
SYSC.DIR;1          SYSE.DIR;1          SYSF.DIR;1          

Total of 15 files.

SYSD it is.

> I believe that in CI VAX days root F was reserved for upgrades, E for
> standalone backup. I don't know if D or anything else was reserved
> perhaps making this deliberate.

Correct.  I'd speculate that D was 'reserved for use by Digital' rather
than being an omission.

From VAX/VMS V7.3 STABACKIT.COM

$ !  P1 - Target device
$ !  P2 - Target directory, defaults to <SYS0.SYSEXE>.  If target
$ !       device is SYS$SYSDEVICE:, the directory is forced to
$ !       <SYSE.SYSEXE> and the <SYSE> directory will be given
$ !       a SYSCOMMON root which points to common system files
$ !       (i.e. points to SYS$TOPSYS for normal systems and to
$ !       existing SYSCOMMON for shared system disks).  Forced to
$ !       <SYS0.SYSEXE> for small media.
$ !  P3 - Source device and directory, defaults to SYS$SYSROOT:<SYSEXE>
$ !  P4 - Application kit type, one of [BACKUP, BAD] (Forced to
$ !       BACKUP for V5.0)   !*bad*
$ !  P5 - If run from VMSKITBLD, do not INITIALIZE tape or large disk.
$ !       This parameter is unsupported, for internal use only.

I don't recall using P4=BAD at any stage.

-- 
There are two hard things in computer science, and they are cache invalidation,
naming, and off-by-one errors.

[toc] | [prev] | [next] | [standalone]

#58643

FromSteven Schweda <sms.antinode@gmail.com>
Date2016-06-19 21:15 -0700
Message-ID<aaa26430-8ec6-4997-a6cb-c2f164a0771e@googlegroups.com>
In reply to#58638
> [...] I'd speculate that D was 'reserved for use by
> Digital' [...]

   In the old days (which continue in the local antique
collection), [SYSD] is where I put the MicroVAX Diagnostic
Monitor files.  It's easy to remember, and I don't remember
ever seeing it used for anything else.

[toc] | [prev] | [next] | [standalone]

#58644

FromDavid Froble <davef@tsoft-inc.com>
Date2016-06-20 01:02 -0400
Message-ID<nk7tdu$u9c$1@dont-email.me>
In reply to#58638
Paul Sture wrote:
> On 2016-06-20, Michael Moroney <moroney@world.std.spaamtrap.com> wrote:
>> Hans Vlems <hvlems@freenet.de> writes:
>>
>>> Which one,[SYS0E.]?
>> If I remember, it was [SYSD.]  I don't have an upgrade disk to check at 
>> the moment, I'll check tomorrow if nobody else beats me to it.
> 
> On the ALPHA084.ISO image I received as part of the Hobbyist kit in May-2015:
> 
> $ dir SYS%
> 
> Directory DUC0:<000000>
> 
> SYS0.DIR;1          SYS1.DIR;1          SYS2.DIR;1          SYS3.DIR;1         
> SYS4.DIR;1          SYS5.DIR;1          SYS6.DIR;1          SYS7.DIR;1         
> SYS8.DIR;1          SYS9.DIR;1          SYSA.DIR;1          SYSB.DIR;1         
> SYSC.DIR;1          SYSE.DIR;1          SYSF.DIR;1          
> 
> Total of 15 files.
> 
> SYSD it is.
> 
>> I believe that in CI VAX days root F was reserved for upgrades, E for
>> standalone backup. I don't know if D or anything else was reserved
>> perhaps making this deliberate.
> 
> Correct.  I'd speculate that D was 'reserved for use by Digital' rather
> than being an omission.
> 
> From VAX/VMS V7.3 STABACKIT.COM
> 
> $ !  P1 - Target device
> $ !  P2 - Target directory, defaults to <SYS0.SYSEXE>.  If target
> $ !       device is SYS$SYSDEVICE:, the directory is forced to
> $ !       <SYSE.SYSEXE> and the <SYSE> directory will be given
> $ !       a SYSCOMMON root which points to common system files
> $ !       (i.e. points to SYS$TOPSYS for normal systems and to
> $ !       existing SYSCOMMON for shared system disks).  Forced to
> $ !       <SYS0.SYSEXE> for small media.
> $ !  P3 - Source device and directory, defaults to SYS$SYSROOT:<SYSEXE>
> $ !  P4 - Application kit type, one of [BACKUP, BAD] (Forced to
> $ !       BACKUP for V5.0)   !*bad*
> $ !  P5 - If run from VMSKITBLD, do not INITIALIZE tape or large disk.
> $ !       This parameter is unsupported, for internal use only.
> 
> I don't recall using P4=BAD at any stage.
> 

The following is something I wasn't quite ready for ....

Directory LDA1:[000,000]

000000.DIR;1        AVAIL_MAN_BASE.DIR;1
DECNET_PHASE_IV_ALPHA0842.DIR;1         DWMOTIF_SUPPORT_ALPHA0842.DIR;1
KITS.DIR;1          SYS0.DIR;1          SYS1.DIR;1          SYS10.DIR;1
SYS11.DIR;1         SYS12.DIR;1         SYS13.DIR;1         SYS14.DIR;1
SYS15.DIR;1         SYS16.DIR;1         SYS17.DIR;1         SYS18.DIR;1
SYS19.DIR;1         SYS1A.DIR;1         SYS1B.DIR;1         SYS1C.DIR;1
SYS1D.DIR;1         SYS1E.DIR;1         SYS1F.DIR;1         SYS2.DIR;1
SYS20.DIR;1         SYS21.DIR;1         SYS22.DIR;1         SYS23.DIR;1
SYS24.DIR;1         SYS25.DIR;1         SYS26.DIR;1         SYS27.DIR;1
SYS28.DIR;1         SYS29.DIR;1         SYS2A.DIR;1         SYS2B.DIR;1
SYS2C.DIR;1         SYS2D.DIR;1         SYS2E.DIR;1         SYS2F.DIR;1
SYS3.DIR;1          SYS30.DIR;1         SYS31.DIR;1         SYS32.DIR;1
SYS33.DIR;1         SYS34.DIR;1         SYS35.DIR;1         SYS36.DIR;1
SYS37.DIR;1         SYS38.DIR;1         SYS39.DIR;1         SYS3A.DIR;1
SYS3B.DIR;1         SYS3C.DIR;1         SYS3D.DIR;1         SYS3E.DIR;1
SYS3F.DIR;1         SYS4.DIR;1          SYS40.DIR;1         SYS41.DIR;1
SYS42.DIR;1         SYS43.DIR;1         SYS44.DIR;1         SYS45.DIR;1
SYS46.DIR;1         SYS47.DIR;1         SYS48.DIR;1         SYS49.DIR;1
SYS4A.DIR;1         SYS4B.DIR;1         SYS4C.DIR;1         SYS4D.DIR;1
SYS4E.DIR;1         SYS4F.DIR;1         SYS5.DIR;1          SYS50.DIR;1
SYS51.DIR;1         SYS52.DIR;1         SYS53.DIR;1         SYS54.DIR;1
SYS55.DIR;1         SYS56.DIR;1         SYS57.DIR;1         SYS58.DIR;1
SYS59.DIR;1         SYS5A.DIR;1         SYS5B.DIR;1         SYS5C.DIR;1
SYS5D.DIR;1         SYS5E.DIR;1         SYS5F.DIR;1         SYS6.DIR;1
SYS60.DIR;1         SYS61.DIR;1         SYS62.DIR;1         SYS63.DIR;1
SYS64.DIR;1         SYS65.DIR;1         SYS66.DIR;1         SYS67.DIR;1
SYS68.DIR;1         SYS69.DIR;1         SYS6A.DIR;1         SYS6B.DIR;1
SYS6C.DIR;1         SYS6D.DIR;1         SYS6E.DIR;1         SYS6F.DIR;1
SYS7.DIR;1          SYS70.DIR;1         SYS71.DIR;1         SYS72.DIR;1
SYS73.DIR;1         SYS74.DIR;1         SYS75.DIR;1         SYS76.DIR;1
SYS77.DIR;1         SYS78.DIR;1         SYS79.DIR;1         SYS7A.DIR;1
SYS7B.DIR;1         SYS7C.DIR;1         SYS7D.DIR;1         SYS7E.DIR;1
SYS7F.DIR;1         SYS8.DIR;1          SYS80.DIR;1         SYS81.DIR;1
SYS82.DIR;1         SYS83.DIR;1         SYS84.DIR;1         SYS85.DIR;1
SYS86.DIR;1         SYS87.DIR;1         SYS88.DIR;1         SYS89.DIR;1
SYS8A.DIR;1         SYS8B.DIR;1         SYS8C.DIR;1         SYS8D.DIR;1
SYS8E.DIR;1         SYS8F.DIR;1         SYS9.DIR;1          SYS90.DIR;1
SYS91.DIR;1         SYS92.DIR;1         SYS93.DIR;1         SYS94.DIR;1
SYS95.DIR;1         SYS96.DIR;1         SYS97.DIR;1         SYS98.DIR;1
SYS99.DIR;1         SYS9A.DIR;1         SYS9B.DIR;1         SYS9C.DIR;1
SYS9D.DIR;1         SYS9E.DIR;1         SYS9F.DIR;1         SYSA.DIR;1
SYSA0.DIR;1         SYSA1.DIR;1         SYSA2.DIR;1         SYSA3.DIR;1
SYSA4.DIR;1         SYSA5.DIR;1         SYSA6.DIR;1         SYSA7.DIR;1
SYSA8.DIR;1         SYSA9.DIR;1         SYSAA.DIR;1         SYSAB.DIR;1
SYSAC.DIR;1         SYSAD.DIR;1         SYSAE.DIR;1         SYSAF.DIR;1
SYSB.DIR;1          SYSB0.DIR;1         SYSB1.DIR;1         SYSB2.DIR;1
SYSB3.DIR;1         SYSB4.DIR;1         SYSB5.DIR;1         SYSB6.DIR;1
SYSB7.DIR;1         SYSB8.DIR;1         SYSB9.DIR;1         SYSBA.DIR;1
SYSBB.DIR;1         SYSBC.DIR;1         SYSBD.DIR;1         SYSBE.DIR;1
SYSBF.DIR;1         SYSC.DIR;1          SYSC0.DIR;1         SYSC1.DIR;1
SYSC2.DIR;1         SYSC3.DIR;1         SYSC4.DIR;1         SYSC5.DIR;1
SYSC6.DIR;1         SYSC7.DIR;1         SYSC8.DIR;1         SYSC9.DIR;1
SYSCA.DIR;1         SYSCB.DIR;1         SYSCC.DIR;1         SYSCD.DIR;1
SYSCE.DIR;1         SYSCF.DIR;1         SYSD0.DIR;1         SYSD1.DIR;1
SYSD2.DIR;1         SYSD3.DIR;1         SYSD4.DIR;1         SYSD5.DIR;1
SYSD6.DIR;1         SYSD7.DIR;1         SYSD8.DIR;1         SYSD9.DIR;1
SYSDA.DIR;1         SYSDB.DIR;1         SYSDC.DIR;1         SYSDD.DIR;1
SYSDE.DIR;1         SYSDF.DIR;1         SYSE.DIR;1          SYSE0.DIR;1
SYSE1.DIR;1         SYSE2.DIR;1         SYSE3.DIR;1         SYSE4.DIR;1
SYSE5.DIR;1         SYSE6.DIR;1         SYSE7.DIR;1         SYSE8.DIR;1
SYSE9.DIR;1         SYSEA.DIR;1         SYSEB.DIR;1         SYSEC.DIR;1
SYSED.DIR;1         SYSEE.DIR;1         SYSEF.DIR;1         SYSF.DIR;1
SYSF0.DIR;1         SYSF1.DIR;1         SYSF2.DIR;1         SYSF3.DIR;1
SYSF4.DIR;1         SYSF5.DIR;1         SYSF6.DIR;1         SYSF7.DIR;1
SYSF8.DIR;1         SYSF9.DIR;1         SYSFA.DIR;1         SYSFB.DIR;1
SYSFC.DIR;1         SYSFD.DIR;1         SYSFE.DIR;1         SYSFF.DIR;1
VMS$COMMON.DIR;1

Total of 261 files.

[toc] | [prev] | [next] | [standalone]

#58649

FromSteven Schweda <sms.antinode@gmail.com>
Date2016-06-19 23:51 -0700
Message-ID<edab74a0-0b03-4f67-92e5-dece943bb6ca@googlegroups.com>
In reply to#58644
> The following is something I wasn't quite ready for ....

  Where's the surprise?  How does this stuff differ from any
other Alpha VMS installation CD (other than the VMS version
numbers)?

> Directory LDA1:[000,000]

   Why waste the effort on the comma?

   I tend to specify /EXCLUDE = SYS*.* when using DIRECTORY
on these things, so that I can get more useful stuff onto a
screen.

   On my spare/experimental XP1000, which also has a Tru64
disk, the default boot flags specify "a" (for Tru64), so
SYSA, at least, has been useful for me.  (The VMS system
disks on that system have a SYSA which is linked to SYS0, so
that I can leave the flags at "a" for VMS, too.)

[toc] | [prev] | [next] | [standalone]

#58681

FromSimon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
Date2016-06-20 19:25 +0000
Message-ID<nk9fv6$5cr$3@dont-email.me>
In reply to#58649
On 2016-06-20, Steven Schweda <sms.antinode@gmail.com> wrote:
>> The following is something I wasn't quite ready for ....
>
>   Where's the surprise?  How does this stuff differ from any
> other Alpha VMS installation CD (other than the VMS version
> numbers)?
>
>> Directory LDA1:[000,000]
>
>    Why waste the effort on the comma?
>

Maybe David misses his RSTS/E days ? :-)

Simon.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world

[toc] | [prev] | [next] | [standalone]

#58687

FromDavid Froble <davef@tsoft-inc.com>
Date2016-06-20 19:07 -0400
Message-ID<nk9t03$smq$1@dont-email.me>
In reply to#58681
Simon Clubley wrote:
> On 2016-06-20, Steven Schweda <sms.antinode@gmail.com> wrote:
>>> The following is something I wasn't quite ready for ....
>>   Where's the surprise?  How does this stuff differ from any
>> other Alpha VMS installation CD (other than the VMS version
>> numbers)?

Really, does recent distribution have all those directories?

>>> Directory LDA1:[000,000]
>>    Why waste the effort on the comma?
>>
> 
> Maybe David misses his RSTS/E days ? :-)
> 
> Simon.
> 

Well, if you were to pay attention to details ....

AS800> syh
OpenVMS V8.4-2  on node AS800   20-JUN-2016 19:01:29.55   Uptime  0 00:38:02

AS800> dir lda1:[0,0]

Directory LDA1:[0,0]

000000.DIR;1        AVAIL_MAN_BASE.DIR;1                    BACKUP.SYS;1
BADBLK.SYS;1        BADLOG.SYS;1        BITMAP.SYS;1

You will note that in the original post, there is no "$" or even "AS800>" prompt 
in front of ">>> Directory LDA1:[000,000]", so, it was the output of the 
directory command that used the comma.  I may have wasted the comma, but it 
wasn't what was commented upon.

RSTS/E was fun.  No, I don't miss TKB ....

[toc] | [prev] | [next] | [standalone]

#58702

FromSimon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
Date2016-06-21 12:57 +0000
Message-ID<nkbdk5$uvo$1@dont-email.me>
In reply to#58687
On 2016-06-20, David Froble <davef@tsoft-inc.com> wrote:
>
> Well, if you were to pay attention to details ....
>

Oh I was, because I know the only time you get that style output for
[000000] is when you use a comma in the directory specification for
the dir command. :-)

> AS800> syh
> OpenVMS V8.4-2  on node AS800   20-JUN-2016 19:01:29.55   Uptime  0 00:38:02
>
> AS800> dir lda1:[0,0]
>
> Directory LDA1:[0,0]
>
> 000000.DIR;1        AVAIL_MAN_BASE.DIR;1                    BACKUP.SYS;1
> BADBLK.SYS;1        BADLOG.SYS;1        BITMAP.SYS;1
>
> You will note that in the original post, there is no "$" or even "AS800>" prompt 
> in front of ">>> Directory LDA1:[000,000]", so, it was the output of the 
> directory command that used the comma.  I may have wasted the comma, but it 
> wasn't what was commented upon.
>
> RSTS/E was fun.  No, I don't miss TKB ....

You mean you don't miss the wonders of overlays ?

Don't worry, I don't miss faffing around with them either. :-)

Simon.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world

[toc] | [prev] | [next] | [standalone]

#58962

Fromlawrencedo99@gmail.com
Date2016-06-26 20:22 -0700
Message-ID<2cc01e66-deb1-4bc4-8c95-ecf74156a156@googlegroups.com>
In reply to#58632
On Monday, June 20, 2016 at 1:44:02 PM UTC+12, Michael Moroney wrote:
> I don't know if D or anything else was reserved perhaps
> making this deliberate.

D = 13?

[toc] | [prev] | [next] | [standalone]

#58585

FromHans Vlems <hvlems@freenet.de>
Date2016-06-18 23:35 -0700
Message-ID<8c1d0a0f-f56f-44b9-8b76-e6621992b937@googlegroups.com>
In reply to#58574
I upgraded a DS20E some time ago. I put the iso file on an rx2600, connected it to an LD device. Next, copy the bootloader to mom$system. The rx2600 eas already configured for LAD and InfoServer services.
The DS20E was booted via a gigabit ethernet controller and after selecting the appropriate service the upgrade went without a hitch. It took less than 15 minutes.
If you've got ECO13 installed of the latest tcp/ip kit and have installed the telnet patch then you'd better deinstall that telnet patch. 
I didn't and uncovered a PCSI bug..
Hans

[toc] | [prev] | [next] | [standalone]

#58591

Fromhelbig@asclothestro.multivax.de (Phillip Helbig (undress to reply))
Date2016-06-19 07:58 +0000
Message-ID<nk5jbu$2j53$2@news.kjsl.com>
In reply to#58574
In article <nk54r8$r72$1@dont-email.me>, David Froble
<davef@tsoft-inc.comwrites: 

> Got the Alpha 8.4-2 evaluation kit.  Unzipped it on my Alpha, got an iso
> image, which I was able to mount using LD.  The kit will work as an
> upgrade to V8.3, or later, but will not (according to the release notes)
> install on an empty disk. No problem, made an image copy of my 8.3
> system disk. 
> 
> Now, it's been a LONGGGG time since I did any installations / upgrades,
> and I'm not sure what can be done.  What I remember is you boot off the
> distribution media and use the menu to install or upgrade.  Can't boot
> off an LD container, since it needs VMS up before LD works.  Chicken and
> egg issues .... 
> 
> What I think I need to do is backup /image the LD container onto a spare
> disk. 

A while back, I installed 8.4 from the hobbyist distribution.  
Downloaded the image, mounted a disk /FOREIGN, copied the image to it, 
then booted off of this.

Note: COPY, not BACKUP.

[toc] | [prev] | [next] | [standalone]

#58593

FromJan-Erik Soderholm <jan-erik.soderholm@telia.com>
Date2016-06-19 11:09 +0200
Message-ID<nk5ng1$c87$1@news.albasani.net>
In reply to#58574
Den 2016-06-19 kl. 05:51, skrev David Froble:
> It's Saturday night, or I'd ask VSI.  So it's your lucky day to consider my
> question.
>
> Got the Alpha 8.4-2 evaluation kit.  Unzipped it on my Alpha, got an iso
> image, which I was able to mount using LD.  The kit will work as an upgrade
> to V8.3, or later, but will not (according to the release notes) install on
> an empty disk. No problem, made an image copy of my 8.3 system disk.
>
> Now, it's been a LONGGGG time since I did any installations / upgrades, and
> I'm not sure what can be done.  What I remember is you boot off the
> distribution media and use the menu to install or upgrade.  Can't boot off
> an LD container, since it needs VMS up before LD works.  Chicken and egg
> issues ....
>
> What I think I need to do is backup /image the LD container onto a spare
> disk. Can't use the optical drive.  The local crumudgen got a good laugh
> when I told him I was trying to read a DVD and finally realized the Alpha
> had a CD drive. Gonna attempt to fix that next week.  Don't think the
> distribution will fit on a CD.

The original download did not fit on a CD since there was a large file
stored in the ISO as two copies by mistake. I took that away and re-built
the ISO and my ISO did then fit on a CD.

VSI also release an updated ISO shortly after this error was reported,
and it is now "589.5 MB" according to the download page.

Do you still have the origanal ISO? That was around 1 GB, I think...
If so, just fetch the latest copy from VSI.


Anyway...

If you have a spare disk you can copy the ISO to that one and boot from
it. Philip described that in another post.

And you should be able to either INSTALL or UPGRADE using this dist,
either from a spare disk or from a CD.


Regards, Jan-Erik.




>
> Anyway, yeah, I'll get around to it, my question.  Can I upgrade VMS while
> running on a system disk, or do I need to have distribution media I can
> boot from?

[toc] | [prev] | [next] | [standalone]

#58634

FromDavid Froble <davef@tsoft-inc.com>
Date2016-06-19 22:39 -0400
Message-ID<nk7l19$c72$1@dont-email.me>
In reply to#58593
Jan-Erik Soderholm wrote:
> Den 2016-06-19 kl. 05:51, skrev David Froble:
>> It's Saturday night, or I'd ask VSI.  So it's your lucky day to 
>> consider my
>> question.
>>
>> Got the Alpha 8.4-2 evaluation kit.  Unzipped it on my Alpha, got an iso
>> image, which I was able to mount using LD.  The kit will work as an 
>> upgrade
>> to V8.3, or later, but will not (according to the release notes) 
>> install on
>> an empty disk. No problem, made an image copy of my 8.3 system disk.
>>
>> Now, it's been a LONGGGG time since I did any installations / 
>> upgrades, and
>> I'm not sure what can be done.  What I remember is you boot off the
>> distribution media and use the menu to install or upgrade.  Can't boot 
>> off
>> an LD container, since it needs VMS up before LD works.  Chicken and egg
>> issues ....
>>
>> What I think I need to do is backup /image the LD container onto a spare
>> disk. Can't use the optical drive.  The local crumudgen got a good laugh
>> when I told him I was trying to read a DVD and finally realized the Alpha
>> had a CD drive. Gonna attempt to fix that next week.  Don't think the
>> distribution will fit on a CD.
> 
> The original download did not fit on a CD since there was a large file
> stored in the ISO as two copies by mistake. I took that away and re-built
> the ISO and my ISO did then fit on a CD.
> 
> VSI also release an updated ISO shortly after this error was reported,
> and it is now "589.5 MB" according to the download page.
> 
> Do you still have the origanal ISO? That was around 1 GB, I think...
> If so, just fetch the latest copy from VSI.

I just got this from VSI on Friday.

> Anyway...
> 
> If you have a spare disk you can copy the ISO to that one and boot from
> it. Philip described that in another post.
> 
> And you should be able to either INSTALL or UPGRADE using this dist,
> either from a spare disk or from a CD.

Well, I don't know what you CAN do, but the info from VSI is that you cannot 
install, only upgrade V8.4 or later.  PAK is good only until September.

> Regards, Jan-Erik.
> 
> 
> 
> 
>>
>> Anyway, yeah, I'll get around to it, my question.  Can I upgrade VMS 
>> while
>> running on a system disk, or do I need to have distribution media I can
>> boot from?
>

[toc] | [prev] | [next] | [standalone]

#58645

FromDavid Froble <davef@tsoft-inc.com>
Date2016-06-20 01:04 -0400
Message-ID<nk7tgs$u9c$2@dont-email.me>
In reply to#58634
David Froble wrote:

> Well, I don't know what you CAN do, but the info from VSI is that you 
> cannot install, only upgrade V8.4 or later.  PAK is good only until 
> September.

Should read "upgrade V8.3 or later"

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | comp.os.vms

csiph-web