1 INFO-VAX	Wed, 06 Dec 2006	Volume 2006 : Issue 670       Contents:! Re: Alpha sales extended 6 months ! Re: Alpha sales extended 6 months ! Re: Alpha sales extended 6 months ! Re: DECNET during SYSHUTDWN.COM ? , Re: Default sys$manager:sylogin.com question Re: IP over Fiber Channel  Re: IP over Fiber Channel  Re: IP over Fiber Channel  Re: Left in the dust?  Re: recursive copy in VMS  Re: recursive copy in VMS K Re: Seemingly different results with backup of file in and out of procedure  Re: SHOW LOGICAL oddity ! Re: VAX 11/730 SABACKUP questions  Re: VMS  Alpha  Console (VGA)  vmstar for IA64? Re: vmstar for IA64?  F ----------------------------------------------------------------------  % Date: Tue, 05 Dec 2006 19:39:50 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> * Subject: Re: Alpha sales extended 6 monthsJ Message-ID: <paul.sture.nospam-8CDB6B.19395005122006@mac.sture.homeip.net>  A In article <1165334411.655374.34010@16g2000cwy.googlegroups.com>, #  "Ian Miller" <gxys@uk2.net> wrote:   ' > This was hinted at in the VMS roadmap  > G > "Alpha Systems begin their phase down at the end of October 2006 with B > the end of normal ordering for systems. After October, HP cannotI > guarantee that a product will be available, but will accept an order if , > the company has some left over inventory." > 2 > but HP have gone further with the new statement.  H Did anyone else notice that the last set of VMS roadmaps mentioned 2013  instead of the previous 2011?   A One of the links given here when Rich Marcello's resignation was  F reported, was an interview with Rich, where he talked of 5 year plans.  % 2001 - Alpha end of life announcement  2006 - Alpha end of sales / 2011 - Alpha supported at least until this time    --  
 Paul Sture   ------------------------------  $ Date: Tue, 5 Dec 2006 18:43:06 -0500F From: "David Turner, Island Computers US Corp" <dbturner@islandco.com>* Subject: Re: Alpha sales extended 6 months7 Message-ID: <fundh.1173$hD6.898@bignews8.bellsouth.net>   / I guess that's good news for some of you !  :0( 8 We intend to go a lot longer in Alpha sales than that... FYI...   DT    5 "David Mathog" <mathog@caltech.edu> wrote in message  % news:el46o2$t52$1@naig.caltech.edu...  > DaveG wrote:< >> http://www.openvms.org/stories.php?story=06/12/04/4813299 >> > Quote: > ? >   As part of this plan, we ensured we had sufficient material B >   to cover any pre-retirement surge in demand. Although the lastA >   sale date has passed, we are now able to continue sales while 9 >   materials last for orders received by HP on or before B >   April 27, 2007, with scheduled delivery through July 27, 2007. > < > One possible translation:  the hypothetical pre-retirement9 > surge in demand either did not occur, or it was smaller < > than expected, so HP still has hardware in the warehouses.; > Rather than sending it to the junkyard and writing it off - > as a loss they are extending the sale date.  > B > The only upside of this is, I suppose, that if the stuff lingersE > in the HP warehouses long enough David Turner might be able to pick E > up the lot of it for a song.  Then HP can proudly announce the sale ? > (as opposed to the junking) of "all remaining alpha systems".  > 
 > Regards, >  > David Mathog     ------------------------------  % Date: Tue, 05 Dec 2006 19:24:59 -0800 * From: "Tom Linden" <tom@kednos-remove.com>* Subject: Re: Alpha sales extended 6 months) Message-ID: <op.tj4brxoltte90l@hyrrokkin>   E On Tue, 05 Dec 2006 16:32:51 -0800, <david20@alpha2.mdx.ac.uk> wrote:   H > In article <1165333691.027337.120430@j44g2000cwa.googlegroups.com>,  =  - > "DaveG" <david.gudewicz@abbott.com> writes: > >> http://www.openvms.org/stories.php?story=3D06/12/04/4813299 >> >> Interesting.  >> >  > What a mess. > I > Extending the last sale date before the date arrives looks like you ar=  e I > responding to customers. Reinstating sales for 6 months a month after =   =   > sales  > stopped looks ...  > " It likely is just a revenue issue.   > David Webb > Security team leader > CSS  > Middlesex University > 
 >> Dave... >>       -- =  E Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    ------------------------------  * Date: Tue, 5 Dec 2006 21:25:32 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)* Subject: Re: DECNET during SYSHUTDWN.COM ?$ Message-ID: <el4o4c$sb4$2@online.de>  H In article <4572dbe7$1@news.langstoeger.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:    j > In article <b1dd0$4572ba2b$cef8887a$19548@TEKSAVVY.COM>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:F > >I need to run a task during system shutdown under a different user. > > N > >During the execution of SYSHUTDWN.COM, is DECNET (4) garanteed to still be  > >available ? > ; > No. DECnet is shut down before SYSHUTDWN.COM even starts. I > A rest of DECnet remain working, because you should be able to shutdown G > via a CTERM session, but this is probably not enough for you (and not M > even for VMS itself, eg. you can't shutdown VMS from a CTERM DECnet-over-IP 
 > session)  G I'm still coming to terms with the fact that one can log in via TELNET  E and do a shutdown with reboot and the machine comes back up (even if  ? it is not set to reboot automatically at the console prompt).   I Presumably this will work with DECnet as well.  Of course, TCPIP is also  I shut down during the shutdown procedure.  Is there an exception made for  6 the current process?  (SHUTDOWN.COM is quite cryptic.)   ------------------------------  * Date: Tue, 5 Dec 2006 21:30:35 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)5 Subject: Re: Default sys$manager:sylogin.com question $ Message-ID: <el4odr$sb4$3@online.de>  G In article <1165178167.023403.52760@16g2000cwy.googlegroups.com>, "Zack % Kline" <Z_kline@hotmail.com> writes:     > Hello,G > Sorry for asking so beginner of a question here, but it's one which I  > consider somewhat important.H > Whenever I log in to an account, be it over Telnet or at the "console"I > of my machine, there is something in the default sylogin.com that comes G > with a new OpenVMS 7.3 install which causes the terminal screen to be G > cleared, except for the prompt.  I find this very annoying, because I G > don't get a chance to see things like my last interactive login time, H > etc.  While I doubt anyone would actually be able to break my account,E > it's still good to know.  Not to mention if I have mail messages... H > The problem is that I don't know which line, if any, it is that clearsE > the screen.  I know of only one command in DCL thus far that can do  > that:  > $ type/page nl: A > And I've not found that in the sylogin.com.  I'd appreciate any F > enlightenment as to what it is that happens, and if I can stop it or > change it somehow.    H SET TERMINAL/WIDTH ! clear the screen even if you don't change the width   ------------------------------  $ Date: Tue, 5 Dec 2006 13:19:44 -0500 From: "Jilly" <jilly@hp.com>" Subject: Re: IP over Fiber Channel* Message-ID: <4575b849@usenet01.boi.hp.com>  4 "Alan Fay" <alan_fay@symantec.com> wrote in message . news:el24n6$bdt$1$8302bc10@news.demon.co.uk... > B > Are there any plans for OpenVMS to support IP over Fiber Channel > using 2 Gig HBA's ?  > 
 > Alan Fay > NBU Client Team  > Roseville Engineering   K AFAIK there are no plans. There are multiple vendors that sell ethernet to  G fibre bridges that work very well and these are the suggested means of  - moving your TCPIP traffic over to the fibre.     ------------------------------  % Date: Tue, 05 Dec 2006 18:57:25 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>" Subject: Re: IP over Fiber Channel) Message-ID: <el5115$14ja$1@pyrite.mv.net>    Alan Fay wrote:   B > Are there any plans for OpenVMS to support IP over Fiber Channel > using 2 Gig HBA's ?   H  From what little I have followed of it, the original plans for IP over F Fibre Channel (FC) seem to have disappeared from the OpenVMS roadmap, F and the approach that has replaced it is FC over IP.  It appears that E the reverse of the original plan -- and using hardware -- is now the  E target, and it's also apparently potentially available.  HP DRM, for  I instance, has targeted FC over IP for its longer-haul connections.  (eg:   100+ km)  And FC over ATM.  F Within the October 2006 OpenVMS Roadmap, I believe that this protocol B (re)stacking is the "Qualify `FC to IP' bridge" reference that is G lurking within; this appears to be the approach based on Fibre Channel   Tunneling or Storage Tunneling.   E Cisco calls it FCIP, Fibre Channel over IP, and various vendors have  E products here.  One of the folks from DNPG reportedly commented that  1 LightSand can bridge FC and SCS over IP, as well.   
 See RFC 3821.   & RFC 3831 is the reverse, IPv6 over FC.  " http://tools.ietf.org/html/rfc3821" http://tools.ietf.org/html/rfc3831  C There are IP (over FC) bridges around, but apparently rather fewer.   H To me, having a big FC pipe -- while most certainly very nice -- is/was H somewhat less interesting than having a big IP pipe -- a SONET/SDH/OC-3 G pipe, for instance -- that can also run FC and iSCSI and DECnet and...  E It's been my experience that more telecom providers tend to offer IP  > primarily, and Fibre seemingly secondarily.   For instance, a G metropolitan cluster that I was recently dealing with was SONET-based,   and it's (now) wicked fast.   I On a more local LAN, gigabit Ethernet (GbE) and the planned support (and  I again, per the Roadmap) for the 10 GbE AB287A NIC.  That, and apparently  E IP off-load engines; moving various parts of the IP networking stack   into the NIC itself.  I The only immediate down-side I can see to FC-over-IP is if you are PCI-X  C slot constrained, and don't have room for a GbE or 10GbE NIC.  PCI  H Express (PCIe) is also another future option (per the roadmap).  On the I (non-HP and non-OpenVMS) systems I've been working with, the ExpressCard  H and PCEe expansion slots are (also) wicked fast.  Somebody from HP will < have to comment on which HP boxes can and/or will have PCIe.  I But do ping HP more directly for any FC-related official statements they  7 might have here, beyond what is in the OpenVMS Roadmap.    ------------------------------  % Date: Tue, 05 Dec 2006 19:21:38 -0800 * From: "Tom Linden" <tom@kednos-remove.com>" Subject: Re: IP over Fiber Channel) Message-ID: <op.tj4bmcmftte90l@hyrrokkin>   ? On Tue, 05 Dec 2006 10:19:44 -0800, Jilly <jilly@hp.com> wrote:    > 5 > "Alan Fay" <alan_fay@symantec.com> wrote in message 0 > news:el24n6$bdt$1$8302bc10@news.demon.co.uk... >>C >> Are there any plans for OpenVMS to support IP over Fiber Channel  >> using 2 Gig HBA's ? >> >> Alan Fay  >> NBU Client Team >> Roseville Engineering > K > AFAIK there are no plans. There are multiple vendors that sell ethernet    > toH > fibre bridges that work very well and these are the suggested means of. > moving your TCPIP traffic over to the fibre. > K topologically a set of nodes connect thru nic's to a switch is no different K HBA connected a FC switch.  It would have been a neat solution to superpose ? Ip traffic with SAN related traffic, thus overloading the HBA's        --  E Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    ------------------------------  % Date: Tue, 05 Dec 2006 16:22:04 -0500 - From: "John E. Malmberg" <wb8tyw@qsl.network>  Subject: Re: Left in the dust?; Message-ID: <R4WdnZpbe96PfujYnZ2dnUVZ_tOdnZ2d@adelphia.com>    Zack Kline wrote:  <snip>  > > I'm worried mostly about being left behind, as it were.  TheC > descriptions of certain OpenVMS tools requiring the Alpha or IA64 G > processors are discouraging. GNV, for instance, and a number of other 6 > companies which claim to be phasing out VAX support.  K Most of GNV could probably be implemented on VAX.  It would take some work.   ( The main obstacles and work arounds are:  0 1. ODS-2 does not support some of the filenames.  F     The work around for that is to encode the long filenames some how.D     it needs to be a reversible encoding such as Pathworks (Advanced     Server) uses.   > 2. New software is requiring a C99 compiler or support for theA     "long long" type.  The HP C compiler for OpenVMS VAX does not      provide this support.   F     This requires either code changes, or it requires updating GCC for     OpenVMS VAX.  " 3. Old TCP/IP and runtime library.  &     Replacement and supplemental code.   4. Time/money/need.   H > I am unfortunately only able to make real practical use of an emulatedE > system.  That's mainly because of the fact that no real support has B > been implemented in VMS for a screen reader, which is a piece of* > technology I find pretty near essential.  C I do not understand this restriction, as text access to OpenVMS is  F typically through a real terminal, terminal emulator, or X-11 program.  H What ever you use to communicate with the emulated VAX should work with K any OpenVMS system, and most other platforms that support a serial console.   F > I suppose that's possible.  I don't have the resources at present to2 > buy an Alpha, though, or an emulated Alpha even.  F Several OpenVMS systems are available for public access, some of them - have compilers where programming can be done.    http://encompasserve.org   http://deathrow.vistech.net/  $ http://www.testdrive.hp.com/os/#ovms  E Of course this only provides non-privileged access, and there may be  
 quota issues.    >  The setup would be a G > bit cumbersome to maintain, in my view, just because of how seemingly I > complex it'd be.  Windows OSes aren't stable, not really.  And in order I > to get the kind of situation I'm in now with the emulation, I'd need to F > keep a terminal window open pretty near constantly.  The prospect ofD > some hardware failure or other is a little worrysome to me as wellG > simply because I've seen too many computers which I thought were very ' > well-off simply not work as expected.   G OpenVMS telnet connections to encompasserve.org support disconnectable  H terminals.  I can disconnect instead of logging off, and then reconnect H again from the same or another source.  A failure of a system running a B terminal emulator in a telnet session would cause a disconnection.  C The downside of that, is that sometimes it takes some time for the  9 remote system to detect that the session is disconnected.   F I have not checked to see if that facility is enabled on the deathrow ' cluster, or with the testdrive systems.    >  All told, though, I supposeH > that's an idea, if there's absolutely nothing to be done about the VAX
 > problem.  B It is simply a matter of time or money.  There really are not any B obstacles that could not be overcome by someone that is motivated.   -John  wb8tyw@qsl.network Personal Opinion Only    --  < Need a senior system engineer?  I am looking for employment.: http://encompasserve.org/~malmberg/MALMBERG_CS1_RESUME.TXT   ------------------------------   Date: 5 Dec 2006 13:13:06 -0800 $ From: "AEF" <spamsink2001@yahoo.com>" Subject: Re: recursive copy in VMSA Message-ID: <1165353186.856171.45190@80g2000cwy.googlegroups.com>   
 AEF wrote: > JF Mezei wrote:  > > Joseph Huber wrote: J > > > Others have answered the recursive question, one observation though: > > L > > One more observation: To make sure you get all files and all contents of > > filles, also include:  > >   > > /IGNORE=(interlock,nobackup) > > L > > First one allows you to copy files that are currently opened. Second one > F > Be warned that files open for write may be copied in an inconsistent9 > fashion, though such a copy may be better than no copy.  > N > > copies the contents of files marked as "nobackup". Without it, those filesO > > get created in the destination directory with the same size and attributes, $ > > but without any of the contents. > G > Normally only page- and swap-files have this attribute. And since you   < Oops! Also the system dump file is normally marked NOBACKUP.  D > DON'T want to back up their contents, there is usually no need forH > /IGNORE=BACKUP. Other files would have had to have been explicitly setG > with the nobackup attribute, in which case you didn't want their data D > backed up anyway! So I think it would be a rare occasion for which > /IGNORE=BACKUP is needed.  >  > [...]  >  > AEF    AEF    ------------------------------  # Date: Wed, 06 Dec 2006 02:51:47 GMT   From: John Santos <john@egh.com>" Subject: Re: recursive copy in VMS, Message-ID: <7fqdh.26585$kz1.19544@trnddc07>  
 AEF wrote: > JF Mezei wrote:  >  >>AEF wrote: >> >>: >>>Normally only page- and swap-files have this attribute. >> >>M >>Due to the disk space growing at a faster rate than tape drives (in my case I >>anyways),  I have often employed the SET FILE/NOBACKUP for files that I : >>know are copies of stuff than can be obtained elsewhere. >>G >>For instance, when I backup a mac to my vax, all those files are then M >>marked /NOBACKUP so that they don't take up huge amounts of space on a tape E >>(and slow the backup process). Similarly, large patches that can be 4 >>downloadeed from the HP site get marked /NOBACKUP. >  > $ > But you cut too much from my post: > 
 > I wrote: > G > Normally only page- and swap-files have this attribute. And since you D > DON'T want to back up their contents, there is usually no need forH > /IGNORE=BACKUP. Other files would have had to have been explicitly setG > with the nobackup attribute, in which case you didn't want their data D > backed up anyway! So I think it would be a rare occasion for which > /IGNORE=BACKUP is needed.  >  > OK > H > Now, if you've marked these files NOBACKUP because you don't want themF > backed up, why all of a sudden do you want to use /IGNORE=BACKUP? Do! > you want them backed up or not?  > H > One problem with this approach is that when you restore from tape, allH > the NOBACKUP files will be restored, but without their data. They willI > take up space on the disk and you will have to delete them all. This is H > exactly what you want for pagefiles and swapfiles, but is not what youG > want for the files you mark NOBACKUP. Depending on how many and which G > files you mark NOBACKUP, you might be left with quite a mess to clean  > up!  >  > AEF  >     F Once again, a truly modern operating system (RSTS/E) shows the way :-)  G IIRC (and it's been a *very* long time), RSTS/E (in the late V9.x/V10.x L time frame) had *two" "nobackup" bits.  One functioned like the VMS NOBACKUPG flag; the file metadata got backed up (and restored), suitable for swap G files and so forth, and the other bit said "completely ignore this file J on backup", which was suitable for temp files, and in these cases, objects1 and compiler listings, downloadable patches, etc.   F And oh, by the way, it's /IGNORE=NOBACKUP, not /IGNORE=BACKUP, just in, case someone someday cuts and pastes this...   --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Tue, 05 Dec 2006 22:39:15 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> T Subject: Re: Seemingly different results with backup of file in and out of procedureJ Message-ID: <paul.sture.nospam-3E649C.22391505122006@mac.sture.homeip.net>   In article  F <OF08BCF63F.CD2E3DEE-ON8525723B.00647925-8525723B.0064F9C6@metso.com>,  norm.raphael@metso.com wrote:   > I do not get what I see here. H > Executing the backup command from the terminal adds a copy of the file > (expected)K > Then executing the same command as part of the procedure DELETES the copy  > (???)    Found it - see below.    >  > $ dir [copy.out]*.*;*  >  > Directory JAM340:[COPY.OUT]  > C > LOGINMESS.TXT;12           1  12-AUG-1998 12:37:27.98  [CINCOM,CO  > (RWED,RWED,,R) >  > Total of 1 file, 1 block. . > $ backup/nolog JAM351:[NORM]LOGINMESS.TXT;12' > jam340:[copy.out]*.*;*/own=parent/new  > $ dir [copy.out]*.*;*  >  > Directory JAM340:[COPY.OUT]  > C > LOGINMESS.TXT;13           1  12-AUG-1998 12:37:27.98  [CINCOM,CO  > (RWED,RWED,,R)C > LOGINMESS.TXT;12           1  12-AUG-1998 12:37:27.98  [CINCOM,CO  > (RWED,RWED,,R) >  > Total of 2 files, 2 blocks.  > $ @copy_to_in  > $ say="WRITE SYS$OUTPUT" > $ set noon > $ defi/user sys$output nl: > $ defi/user sys$error nl: : > $ delete_/nolog/before="today-8-" jam340:[copy.out]*.*;*!                   ^^^^^^^^^^^^^^^   G This is deleting files older than 8 days. The existing files are dated   12-AUG-1998.  	 > $ say - < >  "Enter your filename (wildcarding is okay, file should be > world-readable)." K > Enter your filename (wildcarding is okay, file should be world-readable). 
 > $ infile="" > > $ read/prompt="File to copy: "/timeout=50 sys$command infile* > File to copy: jam351:[norm]loginmess.txt7 > $ infile=f$search(f$parse(infile,,,,"SYNTAX_ONLY"),1)  > $ if infile .eqs. "" > $ else > $!$ defi/user sys$output nl: > $!$ defi/user sys$error nl: . > $ backup/nolog JAM351:[NORM]LOGINMESS.TXT;121 > jam340:[copy.out]*.*;*/owner=parent/new_version  > $ sev=$severity  > $ if sev .ne. 1 	 > $ endif 	 > $ endif  > $ exit > $ dir [copy.out]*.*;*  >  > Directory JAM340:[COPY.OUT]  > C > LOGINMESS.TXT;12           1  12-AUG-1998 12:37:27.98  [CINCOM,CO  > (RWED,RWED,,R) >  > Total of 1 file, 1 block.  > $    --  
 Paul Sture   ------------------------------  * Date: Tue, 5 Dec 2006 21:19:22 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)  Subject: Re: SHOW LOGICAL oddity$ Message-ID: <el4noq$sb4$1@online.de>  ? In article <3bd93$4572b167$cef8887a$691@TEKSAVVY.COM>, JF Mezei ' <jfmezei.spamnot@teksavvy.com> writes:     >  >$ show log sysuaf/fullE >  >   "SYSUAF" [super] = "SYS$SYSTEM:SYSUAF.DAT" (LNM$PROCESS_TABLE) A >  >   "SYSUAF" [super] = "$DISK1:[VMS$COMMON.SYSEXE]SYSUAF.DAT"   > (LNM$SYSTEM_TABLE) >  >$ deassign/proc sysuaf >  >$ deassign/system sysuaf >  >$ show log sysuaf/full@ >  >   "SYSUAF" [exec] = "$DISK1:[VMS$COMMON.SYSEXE]SYSUAF.DAT"  > (LNM$SYSTEM_TABLE) >  >$  > N > Shouldn't the [exec] definition have been listed along with the [super] one  > in the SYSTEM table ?    You can get this by adding a *:    $ sh log /system/ful sysuaf .    "SYSUAF" [super] = "XXX" (LNM$SYSTEM_TABLE) $ sh log /system/ful sysuaf*  4 (LNM$SYSTEM_TABLE)      [kernel]  [shareable,system]D                         [Protection=(RWC,RWC,R,R)]  [Owner=[SYSTEM]]     "SYSUAF" [super] = "XXX"/   "SYSUAF" [exec] = "CLUSTER_SYSTEM:SYSUAF.DAT" 5   "SYSUAFALT" [exec] = "CLUSTER_SYSTEM:SYSUAFALT.DAT"   - (LNM$SYSCLUSTER_TABLE)  [kernel]  [shareable] D                         [Protection=(RWC,RWC,R,R)]  [Owner=[SYSTEM]] $   K > And if only one translation can be shown per table, shouldn't the [exec]  ( > take precedence over the [super] one ?  G Why?  Normally, [super] will take precedence over [exec].  (Exception,  H often used by system services: the application itself only uses [exec].)   ------------------------------  % Date: Tue, 05 Dec 2006 19:31:10 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> * Subject: Re: VAX 11/730 SABACKUP questionsJ Message-ID: <paul.sture.nospam-8AD1BE.19311005122006@mac.sture.homeip.net>  G In article <871wne3k4p.fsf@k9.prep.synonet.com>, prep@prep.synonet.com   wrote:  2 > Bob Blunt <RobertDOTblunt@digitalDOTcom> writes: > F > > I also can't remember if the 9-track tapes had bootable standalone > > on them from DEC.  > F > At least some did, I can remember swearing at it! Can't remember the > version of why though... > G > I think some kits shipped a 600' tape with SABACKUP on it, others had . > it on another 2400' tape plus `other stuff'.  H I clearly remember the option being available, because it was something A I'd been wanting all along (with my previous IBM it was standard  H practice to put the equivalent of SABACKUP at the beginning of a master 
 backup tape).   I I believe the functionality was only available for certain tape devices,   and I didn't have one of those.    --  
 Paul Sture   ------------------------------  % Date: Tue, 05 Dec 2006 23:03:41 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> & Subject: Re: VMS  Alpha  Console (VGA)5 Message-ID: <3b6b$45764126$cef8887a$529@TEKSAVVY.COM>    FredK wrote:I > I don't know why you keep asserting that 680x480 is some magic number.      C OK Sorry, I was under the impression that VGA mode implied 640-480.   L 640-480 is what is used when the machine powers up. And it SEEMS (not sure) I that during the booting process, when it switches to the VMS console, it  " remains at 640-480 (is that so ?).  K The reason I mentioned this was that there have been times when, after the  K decw server crashing (happens every few days for me), the NEC monitor gets  K confused and seems to have some problems adjusting to what the VMS console   is trying to do.   ------------------------------   Date: 5 Dec 2006 17:37:41 -0800  From: dean.woodward@gmail.com  Subject: vmstar for IA64? A Message-ID: <1165369061.205999.40170@f1g2000cwa.googlegroups.com>   G I pulled vmstar off freeware 8.0 and tried to compile it for IA64. Then D I fixed BUILD.COM and LINK.COM... to account for I64 architecture...E but it's looking for object files in [.VMS-BINARIES] that don't exist  for either V8 or I64.   C Has anyone built this yet, or am I slogging into unknown territory?    ------------------------------   Date: 5 Dec 2006 17:48:54 -0800  From: dean.woodward@gmail.com  Subject: Re: vmstar for IA64? B Message-ID: <1165369734.400650.233500@73g2000cwn.googlegroups.com>   dean.woodward@gmail.com wrote:E > Has anyone built this yet, or am I slogging into unknown territory?   : Or I could do the obvious, and use the one in [.000Tools].  
 Never mind...    ------------------------------   End of INFO-VAX 2006.670 ************************