1 INFO-VAX	Mon, 19 Apr 2004	Volume 2004 : Issue 216       Contents: Re: Delta Time -followup" Re: need help on fonts for Mozilla Re: Need VAXVMS055 ISO Re: PCanywhere and VAX VMS Re: stop process Re: stop process Re: stop process+ Using Windows XP hyperterminal with OpenVMS / Re: Using Windows XP hyperterminal with OpenVMS / Re: Using Windows XP hyperterminal with OpenVMS  Re: VMS731_LAN-V0900  F ----------------------------------------------------------------------  % Date: Sun, 18 Apr 2004 21:30:08 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>! Subject: Re: Delta Time -followup 6 Message-ID: <408339B0.F34EF090@NeOaSrPtAhMlNiOnWk.net>   William Hymen wrote: > M > "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote in message 2 > news:4081FBBA.D2050073@NeOaSrPtAhMlNiOnWk.net... > > William Hymen wrote: > > > 
 > > > All, > > > . > > > How would I convert this into delta time2 > > > instead of absolute. I could use an example. > > > H > > > $ resub= """"+f$cvtime("TOMORROW","ABSOLUTE","DATE")+" 02:02:00""" > > B > > If I understand the question correctly, my favorite is either: > > 4 > > $ resub = f$cvtime( "02:02:00+1-", "ABSOLUTE", ) > >  > > ...or... > > , > > $ SUBMIT.../AFTER="02:02:00+1-" filespec > : > What does the "+1-" mean .. DELTA or the next occurance?  G It means "02:02:00 (today) plus one day". If today is 18-Apr-2004, then  it means "19-Apr-2004 02:02".    > I think I get it. E > What would the DELTA syntax be for, say, 1hr + 15 minutes from now?   D Spend some time with HELP for Delta times. In a nutshell, delta time	 format is    (+/-)days hh:mm:hh.cc   B In some cases, the days needs to have dash between it and the time! offset, as in "days-hh:mm:ss.cc".   @ The syntax for the answer to your question would be "+01:15:00".   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  + Date: Sun, 18 Apr 2004 19:40:04 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)+ Subject: Re: need help on fonts for Mozilla $ Message-ID: <c5ulik$1ge$1@online.de>  E In article <ba3580506b10m1snk8k6pnbkbbohmvu5np@4ax.com>, Nigel Barker  <nigel@hp.com> writes:    M > OK but you still haven't answered my questions as to which sites give you a P > problem. Of course if the answer is embarrassing just forget I mentioned it:-)  C For example, try http://www.vest.com.mk/ or any site with Cyrillic  D letters.  (OK, this one uses charset=windows-1251, but the "better" ' iso-8859-5 would give similar results.)    ------------------------------  # Date: Mon, 19 Apr 2004 04:05:52 GMT 0 From: glen herrmannsfeldt <gah@ugcs.caltech.edu> Subject: Re: Need VAXVMS055 ISO - Message-ID: <AeIgc.15149$hw5.17188@attbi_s53>    David J. Dachtera wrote:   (snip)  H >>At a guess, as Romax mentions he is a hobbist and is asking for an ISO >>image, he has SIMH.   M >>In which case he can attach the whole ISO image file of the CD as a fake CD  >>drive and boot from that...   6 > ...except that it will still be ODS-2, not ISO-9660.  > In ISO image file is really just an image file that happens to have an ISO format in it.   B It seems, though, that some CD writing programs when told to writeA an ISO image will only write an ISO image.  It seems wrong to me,  but that is the way it is.   -- glen    ------------------------------  # Date: Mon, 19 Apr 2004 04:08:41 GMT 0 From: glen herrmannsfeldt <gah@ugcs.caltech.edu># Subject: Re: PCanywhere and VAX VMS - Message-ID: <dhIgc.24820$yD1.59289@attbi_s54>    Hans Vlems wrote:    (snip regarding PCanywhere)   N > There's no reason it shouldn't work. I used that setup a couple of years agoJ > to solve a queue problem on a VAX. I used PCanywhere to connect to an NTM > system and ran the VT320 emulator that comes (came?) with Pathworks. The NT / > system used LAT to connect to the VAX though. N > Could it be that the PC that runs the PCanywhere server is confused, IP wise
 > that is?N > The VAX obviously runs LAT. Even if it isn't running yet, LAT may be startedC > with @sys$startup:lat$startup and live with the default settings. 9 > Run Powertem over LAT (or DECnet) and see what happens.   C How about a VNC server for VMS?  That would be nice, though I don't  believe that it has been done.   -- glen    ------------------------------  % Date: Sun, 18 Apr 2004 22:38:40 -0000 / From: "John Morrison" <john.morrison@tesco.net>  Subject: Re: stop process : Message-ID: <3tDgc.177$bC4.92@newsfe3-win.server.ntli.net>  
 Dear "Tutor",   G     The various privileges available to anyone under VAX/VMS _may_ seem A complicated: but in practice they are not. In order to be able to J "interfere" (so to speak) with a process which is not one of your own - in= fact, even to be able to "observe" it using such commands as:   " > SHOW PROCESS/ID=<PID>/CONTINUOUS  J - will depend upon process attributes differing from yours. In particular,J should the user whose process it is be in the same GROUP, you will need anJ account with both GROUP (and _most_ emphatically GRPNAM is irrelevant) and SETPTV - in which case:    > SET PROCESS/PRIV=GROUP  K will suffice. (I may not remember correctly here - but SETPRV will _always_ L be sufficient.)Otherwise, SETPRV will suffice, since it will allow you to do this:    > SET PROCESS/PRIV=WORLD  H which will be necessary, before you are able either to observe the innerE workings of a process (as exemplified above) or to terminate it. (The E termination, which is done by forceing a $FORCEX on it, if I remember I aright, is available to anyone with the appropriate powers ... but should K the process be running with, say, SYSTEM privileges, the $FORCEX may merely L make it execute a number of ASTs to handle the insult, should they have been/ set up to do so upon this liberty being taken!)   B     Just a _very_ small amount of VMS is based on UNIX-like ideas.J Privileges such as BYPASS have to do with files, not processes, under VMS;= and SYSPRIV has to do with overall system functional control.   H     I have never found the VMS help files to be anything other than bothL helpful _and_ comprehensive! However, it is a long time since I have had theF pleasure (sic!) of managing a VMS system. I hope that what I have just% written has the following properties:        (i)  it is correct; and      (ii) it helps!  H Should neither of these be the case, I can but apolgize! (And, given theL quality of this group, I have no doubt that I shall be hauled over the coals" for the smallest infringement ...)  
 John Morrison  johnDOTmorrisonATtescoDOTnet --  K "Crash programs fail because they are based on theory that, with nine women = pregnant, you can get a baby in a month." - Wernher von Braun     7 "tutor" <tutor_removespam_@cfl.rr.com> wrote in message 2 news:pkj380pa1dp6dqe2vstt0t8cv6km0c2pac@4ax.com...6 > Haven't tried to be a system admin in over 10 years.5 > Its amazing the "simple" things I have forgotten!!!  >  > % > Need to know how to stop a process.  > 6 > stop process/id= xxxx does not work. not authorized.4 > went into sys$system:authorize and I have syspriv. > 1 > even tried set proces/priv=bypass (not allowed)  > - > please reply to tutor AT cfl DOT rr DOT com  >  > Thank you,	 > Jerrold  >      --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).A Version: 6.0.656 / Virus Database: 421 - Release Date: 09/04/2004    ------------------------------  % Date: Sun, 18 Apr 2004 21:40:38 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> Subject: Re: stop process 6 Message-ID: <40833C26.63A13BB8@NeOaSrPtAhMlNiOnWk.net>   John Morrison wrote: > [snip]J >     I have never found the VMS help files to be anything other than bothN > helpful _and_ comprehensive! However, it is a long time since I have had theH > pleasure (sic!) of managing a VMS system. I hope that what I have just' > written has the following properties:  >  >     (i)  it is correct; and  >     (ii) it helps!  E To help keep your memory from going too stale too soon, here are some  guidelines:   F Privileges like BYPASS, SYSPRV and GRPPRV refer to the protection maskE of an object such as a file, a queue, a logical name table, a device,  etc.  D Privileges like SYSNAM and GRPNAM refer specifically to logical name tables. BYPASS overrides both.  D Privileges GROUP and WORLD refer to processes. BYPASS has no meaning here.   D One that trips a lotta folks up is EXQUOTA. It refers exclusively toC exceeding disk quotas, and is meaningless in the context of process . resource quotas like BIOLM, DIOLM, BYTLM, etc.  2 There's a fair few more, but those are very basic.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Mon, 19 Apr 2004 05:02:50 GMT * From: tutor <tutor_removespam_@cfl.rr.com> Subject: Re: stop process 8 Message-ID: <r8n6809162nc0cslcn6q5mhluojpdomoil@4ax.com>   Found the answer. E    once I had privs to do a   $ set uic [owner/process to be stopped] 0    the next part was easy:    $ stop process/id=   Thanks again, all. J.  * On Sun, 18 Apr 2004 21:40:38 -0500, wrote:   >John Morrison wrote: 	 >> [snip] K >>     I have never found the VMS help files to be anything other than both O >> helpful _and_ comprehensive! However, it is a long time since I have had the I >> pleasure (sic!) of managing a VMS system. I hope that what I have just ( >> written has the following properties: >>   >>     (i)  it is correct; and >>     (ii) it helps!  > F >To help keep your memory from going too stale too soon, here are some >guidelines: > G >Privileges like BYPASS, SYSPRV and GRPPRV refer to the protection mask F >of an object such as a file, a queue, a logical name table, a device, >etc.  > E >Privileges like SYSNAM and GRPNAM refer specifically to logical name  >tables. BYPASS overrides both.  > E >Privileges GROUP and WORLD refer to processes. BYPASS has no meaning  >here. > E >One that trips a lotta folks up is EXQUOTA. It refers exclusively to D >exceeding disk quotas, and is meaningless in the context of process/ >resource quotas like BIOLM, DIOLM, BYTLM, etc.  > 3 >There's a fair few more, but those are very basic.    ------------------------------  % Date: Sun, 18 Apr 2004 21:53:19 +0100 J From: "Alistair Burnett" <alistair.burnett@realitysolutions.no.spam.co.uk>4 Subject: Using Windows XP hyperterminal with OpenVMS0 Message-ID: <IsScnR12opsidx_dSa8jmw@karoo.co.uk>  F I am attempting to replace several old VT420 terminals with PC's + run
 Windows XP9 and use Hyperterminal to communicate with our VMS server.    Issues:   L (1) The VT420 terminals use serial comms to connect to the server. I want to
 use TCP/IP5 (2) How do I find / set up the ip address on OpenVMS? G (3) Will open VMS support a telnet session via TCP/IP from a Window PC? J (4) Do I need additional software - Emulators for PC / TCP/IP services for openVMS?@        [I have heard of Pathworks - but too expensive + too much functionality]  ; (5) Any other advise in connecting Windows PC's to OpenVMS.   2 Any help / links to support docs much appreciated.   ------------------------------  % Date: Sun, 18 Apr 2004 18:39:02 -0400 ' From: John Sauter <J_Sauter@Empire.Net> 8 Subject: Re: Using Windows XP hyperterminal with OpenVMS8 Message-ID: <e006805u1mju8o1mt35kl4aq1ajeaik78q@4ax.com>   Alistair Burnett wrote:   F I am attempting to replace several old VT420 terminals with PC's + run
 Windows XP9 and use Hyperterminal to communicate with our VMS server.    Issues:   D (1) The VT420 terminals use serial comms to connect to the server. I want to use TCP/IP5 (2) How do I find / set up the ip address on OpenVMS? C (3) Will open VMS support a telnet session via TCP/IP from a Window  PC? F (4) Do I need additional software - Emulators for PC / TCP/IP services for openVMS?:  [I have heard of Pathworks - but too expensive + too much functionality]; (5) Any other advise in connecting Windows PC's to OpenVMS.   2 Any help / links to support docs much appreciated.   John Sauter responded:  . Since you want to link to OpenVMS using TCP/IP1 rather than through a serial port on the VAX, you / will need a TCP/IP stack on the OpenVMS system. * You mentioned TCP/IP Services for OpenVMS; that is the one we use.   , When you install TCP/IP Services for OpenVMS- you will need to provide an IP address.  Your 0 network administrator can allocate an IP address) to your OpenVMS system in the same way he , allocates an IP address to a PC.  In my shop) the network administrator keeps a list of ) each computer's IP address, and a new one 2 gets the next address on the list.  Your procedure may differ.   / I have not tried HyperTerminal, but I have used , Telnet and KEA.  Telnet works well enough to* log in to the VAX and run simple programs.* However, it does not emulate enough of the& VT100 to let you run EDT, for example.. In addition, you must remember that the rubout$ key is delete rather than backspace.  % KEA is a commercial terminal emulator , that faithfully emulates the VT420.  We have& never had a compatibility problem with1 it, and it is quite flexible in its presentation.    We have made our OpenVMS system ' a primary domain server using PathWorks & Server, and all of our PCs are members% of the domain.  Before a user can use   a PC he must provide his OpenVMS username and password.%     John Sauter (J_Sauter@Empire.Net)    ------------------------------  % Date: Sun, 18 Apr 2004 22:02:32 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>8 Subject: Re: Using Windows XP hyperterminal with OpenVMS6 Message-ID: <40834148.6A0F7B98@NeOaSrPtAhMlNiOnWk.net>   Alistair Burnett wrote:  > H > I am attempting to replace several old VT420 terminals with PC's + run > Windows XP; > and use Hyperterminal to communicate with our VMS server.   H Windows Hyperterm is hopelessly brain-dead. You're battling upstream for
 a lost cause.   F You'll need to acquire and use commerically available terminal program or some freeware.   D Commercially, WRQ's Reflection terminal emulation is the standard byD which most others are judged. Some folks have issues with ReflectionG (and most folks get the name wrong, calling it "Reflections" instead of H "Reflection" (singular)) and it is quite costly, considering what it is.H That said, WRQ's Reflection Suite for Enterprise includes an FTP server,D and HTTP server and an LPD daemon for the desktop, and includes both; "Reflection for Unix and Digital" (character-cell only, pka : "Reflection/2") and "Reflection for ReGIS Graphics" (VTx4x> functionality, including ReGIS and Textronix graphics terminal emulation, pka "Reflection/4").   D Others swear by the commercial SmartTerm or KEA products. Neither ofF those supported smooth-scrolling last time I tested them, which was an issue for a former site.  E Freeware, there's PuTTY and TeraTerm. I have experience with neither, ' but some folks find them quite usable.    H Kermit also provides a very usable VT emulator, but I have no experience with it.  B Google for articles about all of these for more testimony from the field.  	 > Issues:  > N > (1) The VT420 terminals use serial comms to connect to the server. I want to > use TCP/IP  G Should not be a problem, but make sure you understand why the terminals G connect that way first. There may be a very good over-riding reason why H they are still serial connected to either the system directly or to what  is known as a "terminal server".  7 > (2) How do I find / set up the ip address on OpenVMS?    Depends on the IP stack.   UCX:> $ UCX SHOW COMM to view, @SYS$MANAGER:UCX$CONFIG to configure.   TCP/IP Services for OpenVMS D $ TCPIP SHOW COMM to view, @SYS$MANAGER:TCPIP$CONFIGURE to configure  	 Multinet: / $ MULTINET SHOW/INTERFACE=if_spec	! Usually se0  ...to view, ... @ $ HELP MULTINET CONFIGURE to find the syntax for configuring the! network, services and interfaces.    Not sure about TCPware.   I > (3) Will open VMS support a telnet session via TCP/IP from a Window PC?   + The source is irrelevant. Telnet is telnet.   L > (4) Do I need additional software - Emulators for PC / TCP/IP services for
 > openVMS?  G If you alreday have a TCP/IP stack on VMS, then no. If not, you'll need / to acquire a license and install some software.   . Terminal programs run on the PC, not the host.  B >        [I have heard of Pathworks - but too expensive + too much > functionality]  @ Pathworks itself does not provide the functionality you require.F However, it is now bundled with commercial software known as PowerTermD which provides terminal emulation over serial ports, LAT and TCP/IP.  = > (5) Any other advise in connecting Windows PC's to OpenVMS.   B Make sure the Windows PCs have anti-virus software where the virusC signature data is updated regularly. Once a PC is compromised, your # entire network is at elevated risk.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sun, 18 Apr 2004 14:05:15 -0400  From: norm.raphael@metso.com Subject: Re: VMS731_LAN-V0900 Q Message-ID: <OFC1D2873E.7F01714A-ON85256E7A.0062151D-85256E7A.0063703E@metso.com>   + This is a multipart message in MIME format. " --=_alternative 0063703A85256E7A_=, Content-Type: text/plain; charset="US-ASCII"  B The accompanying ALPHA_V731_MASTER_ECO_LIST.TXT file contains the 
 following:   ============	 INSTALL_1   % List Name: ALPHA_V731_MASTER_ECO_LIST   J LIST OF CURRENT OPENVMS V7.3-1 OPERATING SYSTEM ECO KITS       13-APR-2004   [snip]  = ECO KITS NOT INCLUDED IN UPDATE KIT:    RELEASE DATE COMMENTS 5 ------------------------------------    ------------   ----------------------- G VMS731_LAN-V0900                        13-APR-2004  No new functional   images. H                                                      Released to update  UNDOC                                                      functionality.  ============  
 so if yes.  K helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)    wrote on 04/18/2004 04:08:19 AM:  : > From ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-1/ > E > > Mar 25 06:08  text/plain       .VMS731_LAN-V0800.PCSI-DCX_AXPEXE   1895Kb> > > Mar 25 06:08  text/plain       .VMS731_LAN-V0800.txt  40KbI > > Apr 15 06:07  text/plain       ALPHA_V731_MASTER_ECO_LIST.DCX_AXPEXE   52KbF > > Apr 15 06:07  text/plain       ALPHA_V731_MASTER_ECO_LIST.txt  3Kb > >  > > .  > > .  > > .  > > J > > Apr 14 06:11  text/plain       VMS731_LAN-V0900.PCSI-DCX_AXPEXE 1902Kb= > > Apr 14 06:11  text/plain       VMS731_LAN-V0900.txt  43Kb  > > J > > 6  NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_LAN-V0900
 > >    KIT > > , > >      6.1  Problems addressed in this kit > > H > >           6.1.1  Writeboot not performed if VMS731_LAN-V0800 ECO kit > >                  removed > > 0 > >                6.1.1.1  Problem Description: > > E > >                The VMS731_LAN-V0800 ECO kit contains the APB.EXE   image.F > >                If the kit is removed via the PCSI UNDO option, theC > >                previous APB.EXE is replaced and the boot block   changes.I > >                A writeboot needs to be performed in order to point to C > >                the new boot block.  The kit should perform the  	 writeboot H > >                as part of the UNDO operation but it does not.  This  may A > >                leave the system in an unbootable state if the 3 > >                VMS731_LAN-V0800 kit is removed.  > > J > >                                                                 Page 6 > >  > > G > >                The VMS731_LAN-V0900 ECO kit provides this writeboot  > >                function. > > # > >                Images Affected:  > > $ > >                 -  POST_UNDO.COM > >  > > .  > > .  > > .  > > * > > 7  PROBLEMS ADDRESSED IN PREVIOUS KITS > J > Am I correct in assuming that the ONLY reason to install this patch if II > have installed the previous version is so that I will be able to remove I > it?  In other words, if the previous version is installed and I have no E > plans to remove it, then I don't need to install this new version?     Yes, see above.    > I > Or could it be that the previous version might be implicitly removed as A > part of some other installation, leading to the serious problem & > (unbootable system) described above? >   C UNDO IIRC is cummulative, so if you UNDO an ECO installed prior to  I installing the LAN V8 ECO, then you will of course need to reinstall the  J LAN V9 ECO to get back a bootable system, or do some fancy reconstruction ) on your own before attempting any reboot.   I I am unclear how they did the new code, so if you UNDO LAN V9 ECO either  K explicitly or implicitly later as part of an UNDO to a state before it was    K installed, I do not know what version of AXB.EXE will remain and if or not    D it will be bootable.  This fix implies that it will all work, but...    @ > On another topic: why do the obviously binary files show up as > text/plain?  > G > The display above is generated with LYNX and I regularly use LYNX to  G > download patches and they download correctly (i.e. I can RUN them to  @ > decompress and they then install successfully), so apparently F > advertising them as text/plain has no ill effects (at least for me). >    I cannot help with this topic." --=_alternative 0063703A85256E7A_=+ Content-Type: text/html; charset="US-ASCII"     R <br><font size=2 face="sans-serif">The accompanying ALPHA_V731_MASTER_ECO_LIST.TXT# file contains the following:</font>  <br>- <br><font size=2><tt>============</tt></font> * <br><font size=2><tt>INSTALL_1</tt></font> <br>F <br><font size=2><tt>List Name: ALPHA_V731_MASTER_ECO_LIST</tt></font> <br>H <br><font size=2><tt>LIST OF CURRENT OPENVMS V7.3-1 OPERATING SYSTEM ECO1 KITS &nbsp; &nbsp; &nbsp; 13-APR-2004</tt></font>  <br>' <br><font size=2><tt>[snip]</tt></font>  <br>N <br><font size=2><tt>ECO KITS NOT INCLUDED IN UPDATE KIT: &nbsp; &nbsp;RELEASE DATE COMMENTS</tt></font> S <br><font size=2><tt>------------------------------------ &nbsp; &nbsp;------------ # -----------------------</tt></font> H <br><font size=2><tt>VMS731_LAN-V0900 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;H &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;13-APR-2004 &nbsp;No new functional images.</tt></font>L <br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;L &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;I &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Released to update  UNDO</tt></font>L <br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;L &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Q &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;functionality.</tt></font> - <br><font size=2><tt>============</tt></font>  <br>+ <br><font size=2><tt>so if yes.</tt></font>  <br>M <br><font size=2><tt>helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove 6 CLOTHES to reply) wrote on 04/18/2004 04:08:19 AM:<br> <br>A &gt; From ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-1/<br> 	 &gt; <br> ^ &gt; &gt; Mar 25 06:08 &nbsp;text/plain &nbsp; &nbsp; &nbsp; .VMS731_LAN-V0800.PCSI-DCX_AXPEXE &nbsp;1895Kb<br>R &gt; &gt; Mar 25 06:08 &nbsp;text/plain &nbsp; &nbsp; &nbsp; .VMS731_LAN-V0800.txt &nbsp;40Kb<br>b &gt; &gt; Apr 15 06:07 &nbsp;text/plain &nbsp; &nbsp; &nbsp; ALPHA_V731_MASTER_ECO_LIST.DCX_AXPEXE &nbsp;52Kb<br>[ &gt; &gt; Apr 15 06:07 &nbsp;text/plain &nbsp; &nbsp; &nbsp; ALPHA_V731_MASTER_ECO_LIST.txt 
 &nbsp;3Kb<br>  &gt; &gt; <br> &gt; &gt; .<br>  &gt; &gt; .<br>  &gt; &gt; .<br>  &gt; &gt; <br>] &gt; &gt; Apr 14 06:11 &nbsp;text/plain &nbsp; &nbsp; &nbsp; VMS731_LAN-V0900.PCSI-DCX_AXPEXE  &nbsp;1902Kb<br>Q &gt; &gt; Apr 14 06:11 &nbsp;text/plain &nbsp; &nbsp; &nbsp; VMS731_LAN-V0900.txt  &nbsp;43Kb<br> &gt; &gt; <br>Y &gt; &gt; 6 &nbsp;NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_LAN-V0900<br>  &gt; &gt; &nbsp; &nbsp;KIT<br> &gt; &gt; <br>J &gt; &gt; &nbsp; &nbsp; &nbsp;6.1 &nbsp;Problems addressed in this kit<br> &gt; &gt; <br>F &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 6.1.1 &nbsp;Writeboot not) performed if VMS731_LAN-V0800 ECO kit<br> S &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;removed<br>  &gt; &gt; <br>H &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6.1.1.1 &nbsp;Problem Description:<br> &gt; &gt; <br>U &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The VMS731_LAN-V0800 ' ECO kit contains the APB.EXE image.<br> G &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;If the 0 kit is removed via the PCSI UNDO option, the<br>I &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;previous 3 APB.EXE is replaced and the boot block changes.<br> L &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;A writeboot. needs to be performed in order to point to<br>H &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;the new: boot block. &nbsp;The kit should perform the writeboot<br>H &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;as part9 of the UNDO operation but it does not. &nbsp;This may<br> F &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;leave, the system in an unbootable state if the<br>Q &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;VMS731_LAN-V0800  kit is removed.<br>  &gt; &gt; <br>H &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;L &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;L &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Page 6<br>  &gt; &gt; <br> &gt; &gt; <br>U &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The VMS731_LAN-V0900 # ECO kit provides this writeboot<br> N &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;function.<br> &gt; &gt; <br>G &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Images 
 Affected:<br>  &gt; &gt; <br>[ &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp;POST_UNDO.COM<br>  &gt; &gt; <br> &gt; &gt; .<br>  &gt; &gt; .<br>  &gt; &gt; .<br>  &gt; &gt; <br>9 &gt; &gt; 7 &nbsp;PROBLEMS ADDRESSED IN PREVIOUS KITS<br> 	 &gt; <br> H &gt; Am I correct in assuming that the ONLY reason to install this patch if I<br>P &gt; have installed the previous version is so that I will be able to remove<br>G &gt; it? &nbsp;In other words, if the previous version is installed and 
 I have no<br> G &gt; plans to remove it, then I don't need to install this new version?  </tt></font> <br>0 <br><font size=2><tt>Yes, see above.</tt></font> <br><font size=2><tt><br> 	 &gt; <br> I &gt; Or could it be that the previous version might be implicitly removed  as<br>H &gt; part of some other installation, leading to the serious problem<br>- &gt; (unbootable system) described above?<br> 	 &gt; <br>  </tt></font>N <br><font size=2><tt>UNDO IIRC is cummulative, so if you UNDO an ECO installed prior to </tt></font> G <br><font size=2><tt>installing the LAN V8 ECO, then you will of course " need to reinstall the </tt></font>I <br><font size=2><tt>LAN V9 ECO to get back a bootable system, or do some ! fancy reconstruction </tt></font> J <br><font size=2><tt>on your own before attempting any reboot.</tt></font> <br>F <br><font size=2><tt>I am unclear how they did the new code, so if you# UNDO LAN V9 ECO either </tt></font> F <br><font size=2><tt>explicitly or implicitly later as part of an UNDO% to a state before it was </tt></font> J <br><font size=2><tt>installed, I do not know what version of AXB.EXE will! remain and if or not </tt></font> H <br><font size=2><tt>it will be bootable. &nbsp;This fix implies that it! will all work, but...</tt></font>  <br> <br>G <br><font size=2><tt>&gt; On another topic: why do the obviously binary  files show up as<br> &gt; text/plain? <br> 	 &gt; <br> F &gt; The display above is generated with LYNX and I regularly use LYNX to <br> F &gt; download patches and they download correctly (i.e. I can RUN them to <br> G &gt; decompress and they then install successfully), so apparently <br> M &gt; advertising them as text/plain has no ill effects (at least for me).<br> 	 &gt; <br>  </tt></font>? <br><font size=2><tt>I cannot help with this topic.</tt></font> $ --=_alternative 0063703A85256E7A_=--   ------------------------------   End of INFO-VAX 2004.216 ************************                                                                                                                                                           bytes) started.9 >>> 226 Transfer completed.  916 (8) bytes transferred.t! <<< PORT 207,111,205,53,223,191e7 >>> 200 Port 223.191 at Host 207.111.205.53 accepted.  <<< RETR VARGAS.DQT;1Ad >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]VARGAS.DQT;1 (79665 bytes) started.; >>> 226 Transfer completed.  79055 (8) bytes transferred.1! <<< PORT 207,111,205,53,223,192r7 >>> 200 Port 223.192 at Host 207.111.205.53 accepted.  <<< RETR WDSTK1.PQC;1Ac >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]WDSTK1.PQC;1 (1471 bytes) started.e9 >>> 226 Transfer completed.  577 (8) bytes transferred.2! <<< PORT 207,111,205,53,223,193t7 >>> 200 Port 223.193 at Host 207.111.205.53 accepted.o <<< RETR WDSTK2.PQC;1.b >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]WDSTK2.PQC;1 (522 bytes) started.9 >>> 226 Transfer completed.  502 (8) bytes transferred.o! <<< PORT 207,111,205,53,223,194c7 >>> 200 Port 223.194 at Host 207.111.205.53 accepted.e <<< RETR WDSTK3.PQC;1Xc >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]WDSTK3.PQC;1 (2898 bytes) started.a: >>> 226 Transfer completed.  2222 (8) bytes transferred.! <<< PORT 207,111,205,53,223,195c7 >>> 200 Port 223.195 at Host 207.111.205.53 accepted.e <<< RETR XMAS1.PQC;1b >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS1.PQC;1 (4812 bytes) started.: >>> 226 Transfer completed.  4404 (8) bytes transferred.! <<< PORT 207,111,205,53,223,196 7 >>> 200 Port 223.196 at Host 207.111.205.53 accepted.r <<< RETR XMAS10.PQC;1Vc >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS10.PQC;1 (3289 bytes) started. : >>> 226 Transfer completed.  2855 (8) bytes transferred.! <<< PORT 207,111,205,53,223,197 7 >>> 200 Port 223.197 at Host 207.111.205.53 accepted.e <<< RETR XMAS11.PQC;1Xc >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS11.PQC;1 (1056 bytes) started.n9 >>> 226 Transfer completed.  992 (8) bytes transferred.t! <<< PORT 207,111,205,53,223,198e7 >>> 200 Port 223.198 at Host 207.111.205.53 accepted.e <<< RETR XMAS12.PQC;15c >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS12.PQC;1 (2189 bytes) started.n: >>> 226 Transfer completed.  1907 (8) bytes transferred.! <<< PORT 207,111,205,53,223,199e7 >>> 200 Port 223.199 at Host 207.111.205.53 accepted.e <<< RETR XMAS13.PQC;15c >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS13.PQC;1 (1986 bytes) started.s: >>> 226 Transfer completed.  1086 (8) bytes transferred.! <<< PORT 207,111,205,53,223,200e7 >>> 200 Port 223.200 at Host 207.111.205.53 accepted.e <<< RETR XMAS14.PQC;15c >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS14.PQC;1 (3588 bytes) started.n: >>> 226 Transfer completed.  3580 (8) bytes transferred.! <<< PORT 207,111,205,53,223,201e7 >>> 200 Port 223.201 at Host 207.111.205.53 accepted.e <<< RETR XMAS15.PQC;15c >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS15.PQC;1 (1041 bytes) started.n: >>> 226 Transfer completed.  1007 (8) bytes transferred.! <<< PORT 207,111,205,53,223,202e7 >>> 200 Port 223.202 at Host 207.111.205.53 accepted.e <<< RETR XMAS16.PQC;15c >>> 150 IMAGE retrieve of DISK$MISC:[DECUS.VAX85D.UALR.POSTERS]XMAS16.PQC;1 (1573 bytes) started.n: >>> 226 Transfer completed.  1499 (8) bytes transferred.! <<< PORT 207,111,205,53,223,203e7 >>> 200 Port 223.203 at Host 207.111.205.53 accepted.e <<< RETR XMAS17.PQC;15c >>> 