1 INFO-VAX	Sun, 05 Nov 2000	Volume 2000 : Issue 618       Contents:F Re: %EDT-F-INTERERR, Internal software error; contact a Compaq support/ Announcement: SAMBA 2.0.6 for OpenVMS Alpha 7.2  Re: RECALL question/suggestion.  Re: sys$output problem Re: TCP/IP 5.0A ECO Appears   F ----------------------------------------------------------------------   Date: 5 Nov 2000 06:44:59 GMT - From: djweath@attglobal.net (Dave Weatherall) O Subject: Re: %EDT-F-INTERERR, Internal software error; contact a Compaq support 5 Message-ID: <DTiotGxQ0bj6-pn2-gdrupeHrXEDN@localhost>   ? On Sat, 4 Nov 2000 01:25:34, Shane.F.Smith@Healthnet.com wrote:    > M > I have often edited EVE journal files. There used to be a bug in DECWindows I > EVE that used to crash the session after a certain combination of edits M > (never did track down what). I think it was on Alpha VMS 1.5. Rerunning the J > whole journal file would crash it again, so you had to chop the last fewM > buffer updates out of the journal file before running it. It worked, but it L > was sometimes a bit of a puzzle working out where one update ended and theF > next one started, so you didn't truncate in the middle of an update.  D I've done that. But I just wrote a bit macro-32 that would chop off E the last record or two. Didn't need it that often but it did save my  F bacon a couple of times. Haven't needed it in years though. SEDT just  got more stable I guess.    Cheers - Dave.   ------------------------------  $ Date: Sat, 4 Nov 2000 22:05:47 -0600) From: "John E. Malmberg" <wb8tyw@qsl.net> 8 Subject: Announcement: SAMBA 2.0.6 for OpenVMS Alpha 7.2/ Message-ID: <t09n2p1qq9a5b4@corp.supernews.com>   <     SAMBA 2.0.6 for OpenVMS ALPHA is now in shape for a more     general test.   B     The VAX build still has problems with the NMBD.  I do not know4     when I will be able to do anything more with it.  >     See http://eisner.decus.org/~malmberg/samba/ for the kits.  9     This version needs the FRONTPORT shared image porting !     library that can be found at:   /     http://eisner.decus.org/~mamberg/frontport/   D     There are two source kits, one is the original UNIX sources in a@     ZIP archive instead of a GZIP archive for the convenience ofB     VMS users.  The other kit is just the VMS specific source code     in a ZIP archive.   D     If you just want the images, the "BASE" kit has object files andC     a procedure that will link them on your system.  Also procedure $     to add it to the system startup.  G     I do not know if this is faster or slower than the earlier versions =     of SAMBA for OpenVMS.  It is very close to having all the &     functionality of the UNIX version.  $     Some highlights for SAMBA 2.0.6.  )     * Server supports Encrypted Passwords        * Oplocks and RMS locking.  %     * SMBSTATUS reports locked files.   <     * Incoming NET SEND messages addressed to the server are#       translated to OPCOM messages.   ?     * The SMBD program can be run interactively or by the TCPIP B       auxiliary server.  When run interactively, the output can be?       redirected on the command line if the debug level is 4 or 
       higher.   E     * You can specify the attributes of files that are created on the ?       SMBD server.  A template file is provided for .EXE files.   >     Large files that are pushed from an NT system must be sentG     with an extension that is configured for a fixed format file.  This $     is a limitation in this release.  =     I found in testing the sending of an 8 Megabyte file that A     Windows NT will send sections of the file out of order, and I -     do not know how big a file triggers this.   A     As it is a very complex program, I have not been able to test      every feature and setting.  B     I suspect that I have one of the shared image transfer vectors@     wrong on the VAX version, but I do not know when I will have     time to look at it.   @     To build the source, you need DEC C 6.0 or later, and either     Compaq MMS or MadGoat Make.   A     The layout of source is designed to make it easier to keep in ?     synchronization with the UNIX Samba versions.  Most patches @     for the SAMBA product can be directly applied to the source.  @     I may not be able to give timely responses to questions, but:     post them on the samba_vms@samba.org or comp.os.vms or@     info-vax@mvb.saic.com mailing list, and possibly someone can     help with them.        So have fun.   -John  wb8tyw@qsl.network   ------------------------------  # Date: Sun, 05 Nov 2000 01:21:20 GMT * From: Alan E. Feldman <alan48@my-deja.com>( Subject: Re: RECALL question/suggestion.) Message-ID: <8u2cmd$970$1@nnrp1.deja.com>   ) In article <8ts0vf$6c7$1@nnrp1.deja.com>, -   Alan E. Feldman <alan48@my-deja.com> wrote: / > In article <u9fM5.1284$Nw6.3969@news.iol.ie>, 4 >   "Tom Wade" <t.wade@vms.eurokom.ie.nospam> wrote:? > > OK, while we're making suggestions for RECALL, here's mine.  > > G > > Following a RECALL DIR command, I should be able to enter SHIFT/up-  > arrow @ > > repeatedly and scroll through all the previous DIR commands. > >  > F > I suggest RECALL/OUTPUT/PREPEND_DOLLAR_SIGNS or RECALL/OUTPUT/DOLLARE > which would prepend "$ " to each line in the output file. One could ? > even add /BLANKS=n to put n spaces between $ and the command.   B I'd also like to see a way to bring back a very long line that youD typed, after which you went for the left or right arrow key, but youC missed and pressed the down arrow key instead! Perhaps it should be G called RECALL 0. And perhaps the up arrow key ought to bring it back to 
 life also.  G For this reason I find it useful to use control-D and control-F instead ! of the left and right arrow keys.   C BTW, DOSKEY is very cool. DOSKEY also provides move-by-word command C line editing. DCL let's you delete leftwards by word, but a word is @ sometimes a lot more than you bargained for if there are certain special characters in the line!    -- Disclaimer: JMHO Alan E. Feldman    w:   alan48  &-)        afeldman  &-) dellnet.com        gfigroup.com     & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  $ Date: Sat, 4 Nov 2000 18:47:31 -08002 From: "Randy Park" <rjpark@mindspring.com.nospaam> Subject: Re: sys$output problem 3 Message-ID: <8u2i40$lct$1@nntp9.atl.mindspring.net>   5 That's the default behavior the VMS uses when it does 2 not know that your login device has the ability to2 overwrite a character using a backspace character.  4 Based upon what you have written, it appears that by7 pressing the backspace key, you are sending it a delete 5 (or rubout) character (hex 7F).  This is good because ( backspace (hex 08) means something else.  4 To set the characteristics of your interactive login+ device, read the documentation/help for the . SET TERMINAL command.  You may want to use the /PERMANENT qualifier also.  4 Yeah, right... <wild@intercomm.com> wrote in message2 news:k4bfvskqsqjqefepnsotuvjd8b7ttbnnr3@4ax.com... > B > I'm a newbie, having just installed my hobbyist VAX-VMS 7.2 on aE > VAXstation 3100/76 SPX.  My problem:  When prompted for a username, B > and you incorrectly type in the name, pressing the backspace keyF > causes the incorrect text to be spit out mirror image.  How do I getE > the (loginout.exe?) keyboard input routine to stop regurgitating my  > input as a mirror image?   ------------------------------  $ Date: Sat, 4 Nov 2000 21:03:53 -00001 From: "NewsReader" <NewsReader@NotOnYourLife.Com> $ Subject: Re: TCP/IP 5.0A ECO Appears4 Message-ID: <ZR_M5.11$iB4.10761@news.enterprise.net>  J I contacted Compaq after downloading the patch & not able to install. TheyI said the PCSI kit wasn't available! (that was a week after the TCP/IP ECO L was released). Now what is the point of releasing a kit we can't install? To$ tease us perhaps... I'm waiting too.  7 "Peter LANGSTOEGER" <eplan@kapsch.net> wrote in message $ news:3a02fe79$1@news.kapsch.co.at...0 > In article <39dd80e2.71178799@news.hccnet.nl>,4 a.koopman@markgraaf.nl.nospam (Adri Koopman) writes:H > >Had the same problem on my mVAX 3100. Could not install the TCPIP_ECOI > >kit, neither after applying VAXUPDATE1_072, allthough the PCSI version H > >was V7.2-101. The readme said that there were problems with V7.2-100,I > >so I thought that the ECO would install. I contacted DEC support about   > >that problem and they send me> > >DEC-VAXVMS-VMS72_PCSI-A0100--4.PCSI-DCX_VAXEXE, which is anD > >upgrade/patch to PCSI, which brings it to version V7.2-108. After> > >applying this kit, I was able to install the TCPIP_ECO kit. > F > Did anyone know, what has happened to the final version of this kit.F > The target date (1-nov) passed by, and I'm still not able to install) > the ECO 1 for TCPIP V5.0A on my VAXes ?  > 
 > Please ! >  > -Peter > 2 > PS: God, how I like my TCPware (on my server)... > --> > Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651= > Network and OpenVMS system manager  Fax.    +43 1 81111-888 > > <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netJ > A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------   End of INFO-VAX 2000.618 ************************