1 INFO-VAX	Mon, 04 Sep 2000	Volume 2000 : Issue 494       Contents:- Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question - Re: Alpha 200 4/233 firmware upgrade question   Best bizop seekers e-mail leads!  Re: CETS2000- Hotel Reservations5 DEC 3000 model 300, help with firmware/serial console " Re: DECWindows not starting in 6.1 Re: Latent bug in 6.1 Backup? & Re: Please help a poorly Microvax 3100& Re: Please help a poorly Microvax 3100 Re: scsi tape drive  Re: scsi tape drive 2 Small system success, was Re: Big AlphaServer Sale! Re: Sun Hardware problems persist ! Re: Sun Hardware problems persist ( Re: TCP/IP 5.0A PatchList or ECO Summary( Re: TCP/IP 5.0A PatchList or ECO Summary( Re: TCP/IP 5.0A PatchList or ECO Summary( Re: TCP/IP 5.0A PatchList or ECO Summary( Re: TCP/IP 5.0A PatchList or ECO Summary  F ----------------------------------------------------------------------  $ Date: Sun, 3 Sep 2000 13:14:05 -0500+ From: "James L. Wiley" <Wiley@Tarleton.edu> 6 Subject: Re: Alpha 200 4/233 firmware upgrade question( Message-ID: <8ou4fe$b0b$1@news.tamu.edu>  H I tried powering up with the floppy in the drive - no indication it evenH accesses the floppy drive.  When I type "arc" it says "no such command".   Thanks   James     B "David J. Dachtera" <djesys.nospam@earthlink.net> wrote in message' news:39B27D37.7600DE91@earthlink.net...  > "James L. Wiley" wrote:  > > K > > I recently bought the Open/VMS Hobbiest CD and am trying to install VMS  onK > > an Alpha 200 4/233.  The installation gets far enough to tell me that I  needL > > more current firmware on the Alpha.  I have downloaded the firmware to a" > > floppy.  The instructions say: > > H > > ARC Console: Place the floppy in the target system, and from the ARC Console ( > > menu, select "Install new firmware".J > > AlphaBIOS Console: Place the floppy in the target system, and from the. > > AlphaBIOS menu, select "Update AlphaBIOS". > > H > > I can't find either one of these menus.  The firmware running on the machine  > > now is version 6.1-2.  > > G > > I don't have access to a firmware CD.  Is there any way to load the  firmware > > from the floppy? > I > Try this: turn the unit off, insert the floppy and power it back on. It E > may see the floppy on power-up and execute the fwupdate.exe program D > (that's the name it needs to have on the diskette, unless I'm very > mistaken). > 3 > If that doesn't work, what happens when you type:  >  > >>>arc > - > ...at the "dead sargeant" (console) prompt?  >  > -- > David J. Dachtera  > dba DJE Systems  > http://www.djesys.com/ > < > Unofficial Affordable OpenVMS Home Page and Message Board:! > http://www.djesys.com/vms/soho/  > H > This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings > is to be expected. > B > Feel free to exercise your rights of free speech and expression. > H > However, attacks against individual posters, or groups of posters, are > strongly discouraged.    ------------------------------  % Date: Sun, 03 Sep 2000 15:43:51 -0400  From: mhr <mhr@sunline.net> 6 Subject: Re: Alpha 200 4/233 firmware upgrade question+ Message-ID: <39B2A9F7.A4D4D276@sunline.net>    "James L. Wiley" wrote:   J > I tried powering up with the floppy in the drive - no indication it evenJ > accesses the floppy drive.  When I type "arc" it says "no such command". >  > Thanks >  > James  > D > "David J. Dachtera" <djesys.nospam@earthlink.net> wrote in message) > news:39B27D37.7600DE91@earthlink.net...  > > "James L. Wiley" wrote:  > > > M > > > I recently bought the Open/VMS Hobbiest CD and am trying to install VMS  > onM > > > an Alpha 200 4/233.  The installation gets far enough to tell me that I  > needN > > > more current firmware on the Alpha.  I have downloaded the firmware to a$ > > > floppy.  The instructions say: > > > J > > > ARC Console: Place the floppy in the target system, and from the ARC	 > Console * > > > menu, select "Install new firmware".L > > > AlphaBIOS Console: Place the floppy in the target system, and from the0 > > > AlphaBIOS menu, select "Update AlphaBIOS". > > > J > > > I can't find either one of these menus.  The firmware running on the	 > machine  > > > now is version 6.1-2.  > > > I > > > I don't have access to a firmware CD.  Is there any way to load the 
 > firmware > > > from the floppy? > > K > > Try this: turn the unit off, insert the floppy and power it back on. It G > > may see the floppy on power-up and execute the fwupdate.exe program F > > (that's the name it needs to have on the diskette, unless I'm very > > mistaken). > > 5 > > If that doesn't work, what happens when you type:  > > 
 > > >>>arc > > / > > ...at the "dead sargeant" (console) prompt?  > >  > > -- > > David J. Dachtera  > > dba DJE Systems  > > http://www.djesys.com/ > > > > > Unofficial Affordable OpenVMS Home Page and Message Board:# > > http://www.djesys.com/vms/soho/  > > J > > This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings > > is to be expected. > > D > > Feel free to exercise your rights of free speech and expression. > > J > > However, attacks against individual posters, or groups of posters, are > > strongly discouraged.   L It apears you are running the SRM console which would require a VMS bootableM floppy; if the alphastation has the required sroms containing the ARC console O then type (at >>> ) set os_type NT. This will bring up the ARC menu for loading N the newer firmware. Be sure you load the latest SRM image in order to run VMS.> Remember to change your console back to SRM (set os_type VMS).   mhr    ------------------------------  % Date: Sun, 03 Sep 2000 23:18:35 +0200 ) From: Martin Heller <mheller@mheller.org> 6 Subject: Re: Alpha 200 4/233 firmware upgrade question+ Message-ID: <39B2C02B.5A5113F6@mheller.org>   < If you got a DOS/WINDOWS PC, you can make a SRM diskette the following way: 1. download mkboot.exe from 3 ftp.digital.com/pub/Digital/Alpha/firmware/utilites   : 2. download the file as_200_v7_0.exe from ../v5.8/alpha200  < 3. get a command prompt, change into the directory where you=    downloaded the files and type "mkboot as_200_v7_0.exe A:". 3    This will give you a bootable firmware diskette    : 4. power the Alpha up and put the firmware diskette inside9    and type "boot dva0" srm should now boot the firmware  E    diskette. The rest should be easy as it's more or less menu driven     nowadays.  @ IF OpenVMS / or Tru64 is installed on a disk, you can create the" firmware diskette as described in O ftp.digital.com/pub/Digital/Alpha/firmware/v5.8/doc/alpha200_v70_fw_relnote.txt    Hope this helps  MARTIN   ------------------------------  $ Date: Sun, 3 Sep 2000 18:35:02 -0500+ From: "James L. Wiley" <Wiley@Tarleton.edu> 6 Subject: Re: Alpha 200 4/233 firmware upgrade question( Message-ID: <8ounap$g9v$1@news.tamu.edu>  K I was able to get the disk written, and the firmware update process ran ok, K but after I cycled power, the machine won't boot properly.  It goes through G the ea.eb... stuff but then scrolls a bunch of information about saving K registers, and what looks like the contents of registers and it reboots and L repeats the process endlessly.  I can move the middle jumper on the front ofI the board, and get it to boot off of the floppy I created, and reload the K firmware, but I have tried the 6.9 version as well as the 7.0 with the same K results.  If I load the ARC firmware the machine will boot and come up with K a menu to load NT, and do some other things, but I need the SRM console not L ARC - I don't want to run NT on this box.  Strangely, when I pick the optionH to "load full update", it does not load both SRM and ARC, but one or the6 other depending on which was in last.  Is this normal?   Thanks   James     6 "Martin Heller" <mheller@mheller.org> wrote in message% news:39B2C02B.5A5113F6@mheller.org... > > If you got a DOS/WINDOWS PC, you can make a SRM diskette the > following way: > 1. download mkboot.exe from 5 > ftp.digital.com/pub/Digital/Alpha/firmware/utilites  > < > 2. download the file as_200_v7_0.exe from ../v5.8/alpha200 > > > 3. get a command prompt, change into the directory where you? >    downloaded the files and type "mkboot as_200_v7_0.exe A:". 4 >    This will give you a bootable firmware diskette > < > 4. power the Alpha up and put the firmware diskette inside: >    and type "boot dva0" srm should now boot the firmwareG >    diskette. The rest should be easy as it's more or less menu driven  >    nowadays. > B > IF OpenVMS / or Tru64 is installed on a disk, you can create the# > firmware diskette as described in  > L ftp.digital.com/pub/Digital/Alpha/firmware/v5.8/doc/alpha200_v70_fw_relnote. txt  >  > Hope this helps  > MARTIN   ------------------------------  " Date: Sun, 3 Sep 2000 23:57:15 GMT( From: Terry Kennedy <terry@gate.tmk.com>6 Subject: Re: Alpha 200 4/233 firmware upgrade question' Message-ID: <G0C57G.98I@spcuna.spc.edu>   + James L. Wiley <Wiley@tarleton.edu> writes: N > ARC Console: Place the floppy in the target system, and from the ARC Console& > menu, select "Install new firmware".H > AlphaBIOS Console: Place the floppy in the target system, and from the, > AlphaBIOS menu, select "Update AlphaBIOS". > N > I can't find either one of these menus.  The firmware running on the machine > now is version 6.1-2.   K   I expect your system is running the SRM console (prompt is ">>>") and not K the ARC console (window-like console menus). If this is a typical AS200, it M is "half-flashed" and doesn't have space in flash memory for both at the same $ time, so you can't just switch over.  N > I don't have access to a firmware CD.  Is there any way to load the firmware > from the floppy?  H   Yes, but unfortunately it requires a running VMS system with a floppy.H I don't know why Compaq doesn't distribute floppy images and the rawrite utility.  )   I've performed the various steps - see: M ftp://gatekeeper.dec.com/pub/DEC/Alpha/firmware/readmes/astn200.html#method_2 L to produce a bootable VMS floppy with the update code on it, and placed bothJ an image of the floppy and the MS-DOS utility to write it back to a floppy at:   ) http://www.tmk.com/transient/as200v70.img ( http://www.tmk.com/transient/rawrite.com  @   Please read the following *IMPORTANT* notes before using this:  D   1) If at all possible, use the supported code on the DEC web site.J   2) I take *no* responsibility for any problems you may have or damage toJ      your system - I verified the code by upgrading one of my AS200's, butG      that's no guarantee it'll work for you. In particular, people have J      reported problems updating using the _supported_ methods, and I don'tC      want to be held responsible for any of those problems, either. J   3) DEC/Compaq have an *UNDOCUMENTED* memory requirement for this versionH      of the code - the AS200 *MUST* have a minimum of 32MB installed forJ      the new console to boot, or else it will bugcheck. 24MB or less won'tH      work, and you'll end up with an inoperable system if you try to up-H      grade and have less than 32MB installed. Use the "show mem" command1      before upgrading if you're at all uncertain. I   4) When upgrading a "half-flash" AS200 for VMS, select the "update SRM" 3      option, not "update ARC" or "update full ROM". K   5) I posted the files for the original poster *only*. If the DECUS Hobby- J      ist Program wants to make these available, contact me via email and IK      will make up a complete set for all systems (or show them how to do it       themselves). K   6) This is only to get existing systems up to a SRM release than can boot L      a recent VMS version - after that, users should follow the DEC instruc-<      tions for "update from system disk" for future updates.  - 	Terry Kennedy             http://www.tmk.com 5         terry@tmk.com             Jersey City, NJ USA    ------------------------------  % Date: Sun, 03 Sep 2000 19:37:37 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> 6 Subject: Re: Alpha 200 4/233 firmware upgrade question- Message-ID: <39B2EED1.553FC168@earthlink.net>    "James L. Wiley" wrote:  > M > I was able to get the disk written, and the firmware update process ran ok, M > but after I cycled power, the machine won't boot properly.  It goes through I > the ea.eb... stuff but then scrolls a bunch of information about saving M > registers, and what looks like the contents of registers and it reboots and N > repeats the process endlessly.  I can move the middle jumper on the front ofK > the board, and get it to boot off of the floppy I created, and reload the M > firmware, but I have tried the 6.9 version as well as the 7.0 with the same M > results.  If I load the ARC firmware the machine will boot and come up with M > a menu to load NT, and do some other things, but I need the SRM console not N > ARC - I don't want to run NT on this box.  Strangely, when I pick the optionJ > to "load full update", it does not load both SRM and ARC, but one or the8 > other depending on which was in last.  Is this normal?    Ah! Now this one I *DO* know....  D The new firmware, like OpenVMS V7.x and later, requires a minimum of- 32MB of RAM. How much memory does YOURS have?   9 You can try most any 72 pin parity SIMMs, 70ns or faster.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  " Date: Mon, 4 Sep 2000 00:50:41 GMT( From: Terry Kennedy <terry@gate.tmk.com>6 Subject: Re: Alpha 200 4/233 firmware upgrade question' Message-ID: <G0C7oH.Anr@spcuna.spc.edu>   + James L. Wiley <Wiley@tarleton.edu> writes: M > I was able to get the disk written, and the firmware update process ran ok, M > but after I cycled power, the machine won't boot properly.  It goes through I > the ea.eb... stuff but then scrolls a bunch of information about saving   	   That...   N > ARC - I don't want to run NT on this box.  Strangely, when I pick the optionJ > to "load full update", it does not load both SRM and ARC, but one or the8 > other depending on which was in last.  Is this normal?  I   ...and that... are covered in the "important notes" I put at the end of 
 my post...  - 	Terry Kennedy             http://www.tmk.com 5         terry@tmk.com             Jersey City, NJ USA    ------------------------------  $ Date: Sun, 3 Sep 2000 20:50:45 -0500+ From: "James L. Wiley" <Wiley@Tarleton.edu> 6 Subject: Re: Alpha 200 4/233 firmware upgrade question( Message-ID: <8ouvag$kke$1@news.tamu.edu>  K Thanks for all the help.  The problem did turn out to be that I didn't have F enough memory to run the newer firmware.  I put another 16Mb in and itK works.  Now I think I have a video card problem.  VMS comes up to the point I of saying "OpenVMS (TM) Alpha Operating System, Version 7.2" and seems to L stop there.  I have tried a Diamond Multimedia VGA and a generic Trident VGA= cards with the same result.  I assume I need a specific card?   J I will connect a terminal to the com1 port and see if I can get it to work	 that way.   K Is there a FAQ for all this?  If so, maybe if someone can point me at it, I  won't ask so many questions...  " Thanks again for everyone's help!!   James L. Wiley Wiley@Tarleton.edu   ------------------------------  % Date: Sun, 03 Sep 2000 22:33:08 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> 6 Subject: Re: Alpha 200 4/233 firmware upgrade question- Message-ID: <39B317F4.A7D16B59@earthlink.net>    "James L. Wiley" wrote:  > M > Thanks for all the help.  The problem did turn out to be that I didn't have H > enough memory to run the newer firmware.  I put another 16Mb in and itM > works.  Now I think I have a video card problem.  VMS comes up to the pointoK > of saying "OpenVMS (TM) Alpha Operating System, Version 7.2" and seems toaN > stop there.  I have tried a Diamond Multimedia VGA and a generic Trident VGA? > cards with the same result.  I assume I need a specific card?e  0 Sort of. Not sure either of those are supported.  eL > I will connect a terminal to the com1 port and see if I can get it to work > that way.g  F Disconnect the keyboard and it should default to COM1, 9600, 8-none-1.  tM > Is there a FAQ for all this?  If so, maybe if someone can point me at it, It  > won't ask so many questions...  9 Not specific to any one machine, but try the OpenVMS FAQ:l  6 http://www.openvms.digital.com/wizard/openvms_faq.html  
 ***CAUTION*** @ VERY large HTML file. May take a while to d/l on a dial-up link.  e$ > Thanks again for everyone's help!!   Wish we could help more, but...a   --   David J. Dachtera  dba DJE SystemsL http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.f   ------------------------------   Date: Sun, 3 Sep 2000 17:30:58 From: <ems806@lycos.com>) Subject: Best bizop seekers e-mail leads!p$ Message-ID: <271529321@MVB.SAIC.COM>  A              *******New List TODAY!!********                     t
                   eB The key to success in marketing online is reaching the people who " are really interested in your ad!   9 You need targeted e-mails of business opportunity seekersp< who are ACTIVELY marketing online and trying to expand their business TODAY!o  ? These are going to be the lowest prices for deliverable, fresh,oA opportunity seekers you are going to find anywhere! We strive to e# clean our lists on a DAILY basis!     " http://www.homepagez.com/plgpencil  0  10,000 opportunity seekers e-mails for only $15 **New List 9-01-00**0  25,000 opportunity seekers e-mails for only $200  50,000 opportunity seekers e-mails for only $350 100,000 opportunity seekers e-mails for only $500 190,000 opportunity seekers e-mails for only $75  
 - Promotions!e  A **FREE with EVERY order, demo of ListMan e-mail manager software  @ to manage your e-mails list and Credit Helper E-book with Links  to Guaranteed Visa's and MC's!  B **Order 50,000 or more e-mails and receive Express Mail Server to  send your e-mails FREE!  e; -Send your e-mails safely bypassing your ISP's mail server! = -This is not a demo but a permanent license for the software!>  B **Order 100,000 or more e-mails and receive, CheckMAN software to A accept checks online, by phone, or fax, and InfoDisk  with 1000+   Money Making Reports and MORE!? _______________________________________________________________ B I received your e-mail as someone interested in Internet Business A Opportunities. If I received your e-mail in error, or you are no r= longer interested, please reply with "remove" in the subject.aA _________________________________________________________________o    d     -  -  -  -  -  -  -  -     e  u  0  e  0  1  3      ------------------------------  # Date: Mon, 04 Sep 2000 02:24:55 GMTr  From: jlsue <jlsuexxxz@home.com>) Subject: Re: CETS2000- Hotel Reservations 8 Message-ID: <6o16rs0cpe6lep36h92gdbbp0pdhk4nu2c@4ax.com>  D I suggest you call the 800-236-7957 number to verify which pre-symp.F seminar(s) you get.  I was surprised to learn my original first-choiceC had been canceled, and I wasn't assigned another - and there was no B notice sent to me (they *have* my e-mail address, they e-mailed my confirmation).  @ On 31 Aug 2000 16:55:58 -0500, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) wrote:  O >In article <39AE7EB2.9FE698AF@ipact.com>, Earl Lakia <lakia@ipact.com> writes: G >> So I registered but did not get a room or plane ticket.  Tried to go  >> back and J >> do that, but the web page won't let me add a room.  The Symposia packetD >> didn't include phone numbers so now I have to find them myselves. >e< >I signed up for a room reservation when I first registered.? >They said they would mail a hotel confirmation and a Symposiume+ >confirmation.  So far it has not happened.e >n# >> Anyone else have these problems?n >n? >From the discussions it seems that nobody has exactly the sameo= >problems.  The variety of problems exceeds the set of people  >willing to disclose them.  1 Not speaking for anyone, certainly not DEC/Compaqr- (get rid of the xxxx in my address to e-mail)    ------------------------------  $ Date: Sun, 3 Sep 2000 21:47:31 -07001 From: Tobin Fricke <tobin@bombay.CS.Berkeley.EDU>s> Subject: DEC 3000 model 300, help with firmware/serial consoleN Message-ID: <Pine.GSO.4.10.10009032135240.14448-100000@bombay.CS.Berkeley.EDU>  H My roommate and I have come across a DECstation 3000 model 300, which weJ am trying to network boot.  We do not have a keyboard or display, so we'reH using the serial console only, and we have no removable media (CD-ROM orH floppy) so we need to boot over the ethernet. We've updated the firmwareI successfully using the MOP protocol (something like bootp but proprietarypD to DEC) and mopd for linux. Now, however, with the new firmware, theG serial console has stopped working fully; although we receive data from I the machine, we can't seem to send anything, and thus we can't accomplish I anything. However, if we boot into the existing operating system (OSF/1),nI the serial connection works in both directions.  Here is what we get over  the serial console:    DEC 3000 - M300e Digital Equipment CorporationuI      VPP PAL V5.56-80800101/OSF PAL V1.45-80800201 - Built on 28-JAN-1997h 10:54:25.34-! TCINFO      DEVNAM        DEVSTAT," ------      --------      --------M                  CPU      OK KN16-AA -V7.0-S889-I21F-sV2.0-DECchip 21064 P3.0r!                  OSC      150 MHz.                 ASIC      OK                  MEM      OK                FEROM      OK 6w                  CXT      OK 5f                  NVR      OK                  SCC      ? 60                   NI      OK                 ISDN      OK 4.                 SCSI      OK@ 0) Dansk                             8) Franais (Suisse Romande)0 1) Deutsch                           9) Italiano3 2) Deutsch (Schweiz)                 10) Nederlandsu. 3) English                           11) Norsk1 4) English (British/Irish)           12) Portugus - 5) Espaol                           13) Suomir/ 6) Franais                          14) SvenskaS. 7) Franais (Canadien)               15) Vlaams    3 >>>     J If anyone could help us out, perhaps by pointing us to where we may obtain> manuals or a description of the SCC error, it would be greatly appreciated.   Thanks,- Tobin <tobin@sji.org>p   ------------------------------  $ Date: Sun, 3 Sep 2000 10:57:22 -07001 From: "Randy Park" <rjpark@mindspring.com.nospam>e+ Subject: Re: DECWindows not starting in 6.1a2 Message-ID: <8ou3fc$j9$1@nntp9.atl.mindspring.net>  2 John E. Malmberg <wb8tyw@qsl.net> wrote in message1 news:2b8b01c01514$196df660$020a0a0a@xile.realm...a4 > "Randy Park" <rjpark@mindspring.com.nospam> wrote: >t2 > > About 25% of the time DECWindows doesn't start: > > when I boot my Vaxstation 3100/30 running OpenVMS 6.1.6 > > There is an error message on the console displayed9 > > after the interactive login limit is set, which meansd3 > > after the site specific startup files have beeni: > > processed.  The message is:  'Shareable images must be8 > > installed to run privileged image'.  It is referring5 > > to the LIBRTL.EXE shareable image.  LIBRTL.EXE ish4 > > obviously supposed to be installed, but for some3 > > reason it isn't. I've examined my site specificf. > > startup files and LIBRTL isn't referenced. > 
 > A guess: >eC > Your SYSGEN parameters are set too low, probably global sections.  > J > This would be the case where you have just enough resources under normalG > conditions to run, but no extra resources at all.  Because of variousi timingK > conditions that may be present on your system sometimes a startup processiK > that temporarily uses some resources may not complete before another parto of > the startup needs them.t >cK > I would make an Image backup of the system, or at the vary least a backup  of7 > the various autogen parameters files as a first step.o >  > Then I would run autogen:  > I > @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES FEEDBACK to get it's opinion ofb your > current parameters.  > H > Using the report from SYS$SYSTEM:AGEN$PARAMS.REPORT, check it's resultL > against the requirements of the products that you have and the contents of > MODPARAMS.DAT. > E > Also study the guide to system tuning in the OpenVMS documentation.h >iI > With out detailed knowledge of your environment, it can be difficult toA give! > precise tuning advice remotely.  >eH > You may want to use the MIN_ prefix on any parameters that the AutogenL > reports need to be adjusted because of feedback.  Basically you want to beI > in the state where Autogen will generate the same SETPARAMS.DAT file ifo you:I > have feedback on or off.  Feedback is a valueable tool, but I have seene4 > system managers get burned by over reliance on it. >tI > There should only be one MIN_ line for each parameter, and in some rareaK > cases a MAX_ line.  Generally the ADD_ prefixes for parameters do nothinguJ > useful, so I remove those lines, using the MIN_ values instead to insure& > that the proper amounts are present. >n3 > Also when you are done, and you run Autogen with:I >h0 > @sys$update:autogen getdata setparams feedback >s3 > This will save the parameters for your next boot.  >eF > One warning:  If someone has been setting critical system parameters throughhJ > SYSGEN, and not through Autogen, doing this will lose the settings.  TheJ > only way to verify this is to compare the SYSGEN settings of the running> > system before the reboot with the new SETPARAMS.DAT setting. >'# > $define/user sys$output test1.lis 
 > $mcr sysgenp
 > use currentD
 > show/all > exit# > $define/user sys$output test2.lisu
 > $mcr sysgenME > use sys$system:vaxvmssys.par !The one you just created with autogenl
 > show/all > exit >l > $diff test1.lis test2.lisp > J > Resolve any unexpected differences, and test carefully all applications. >t > -Johnc > wb8tyw@qsl.network >o  1 Running AUTOGEN not a bad idea.  There could someI6 resourses than Oracle7, Ingres 6.4, and four different5 versions of Rdb, which all start up after DECWindows,s# don't use that are in short supply.    ------------------------------   Date: 3 Sep 2000 21:24:47 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)& Subject: Re: Latent bug in 6.1 Backup?6 Message-ID: <8oufiv$2kt$1@mailint03.im.hou.compaq.com>  f In article <8opddh$sd5$1@slb7.atl.mindspring.net>, "Randy Park" <rjpark@mindspring.com.nospam> writes:  I   Please, the "novella"-format problem report is entertaining, but it is aH   rather difficult for me to figure out exactly what was done, and what I   really happened.  I need the specific commands used, the specific (and iI   complete) error message(s) received, etc.  I need specific details, in a   other words.  E   Also, what is your long-term goal here?  Transfering files from an )I   OpenVMS system to a remote OpenVMS system by way of a PC-connected Zip?   / :Could I have found a bug in Backup 6.1 (Vax)?    
   Unclear.  J   Do you have the "current" BACKUP ECO kit installed for OpenVMS VAX V6.1?  4 :I backed up over 500 files (60+MB) into 7 different' :savesets on my OpenVMS VAX 6.1 system.a     OpenVMS VAX system type?  D :The savesets were disk files. I copied them (binary mode) to a ZIP-# :100 drive on my Windows 98SE PC.        Via binary-mode FTP?   :Took the disk tou3 :a remote site 5 miles away to reverse the process.o5 :After restoring the VMS attributes, all the savesets . :restore correctly except one where it reports6 :an 'excessive error rate reading ...' error mesage on :the 20th file in the saveset.  F   Clogged disk head?  Flaky disk drive?  (I have a possibly incorrect F   recollection that there were some reports of some problems and some D   lost fules with some of the early Zip drives -- and I've seen mostH   any series of storage widget have a small number of members that are,    um, seemingly possessed.)d  I :...I went back to my original computer and issued a BACKUP/LIST command uE :on the errant saveset.  Lo and behold I get the same error message. a  6   Please don't abbreviate or omit error messages(s)...  E   The portion of this that is discussing the PC is then not relevent?   B   Was this the original source of the errant saveset, or the copy?  , :...I created the first saveset, I recreated5 :it, but this time not specifying /NOCRC.  (I usually - :use /NOCRC when the output is a disk file.) e  D   I would use /CRC for most transfers on devices that I trusted, andD   that are known to have good error correction implemented.  In the D   case of removable disk media or network transfers or transfers via!   a PC, I would tend to use /CRC.C  A :No errors on the backup.  Let's try to get a listing. Same errorr6 :but now on a different file, one that is farther down
 :the list....V     Command used?r  G :...try a backup again, same set of files, but use /VERIFY.  Now I get  D :the same error on the verify pass.  Ok, do we have any disk errors?8 :SHOW ERROR and SHOW DEV/FULL say no error on any disks.  0   What (if anything) is in the system error log?  5   What specific make and model of disk(s) are in use?O  4 :I'm stumped.  Is this possibly a backup bug in 6.1?  
   Could be.  e     Did you try different media?  &   Did you use the same FTP command(s)?     Which FTP?  8 :Command used:  BACKUP/LOG/INTERCHANGE input output/SAVE  A   No offense intended, but you've used quite a few commands here.p  6 :Ok, Ok.  I should be using a more recent version, but7 :older systems are quite useful when you are developingn4 :and selling a commercial product.  It's not exactly2 :customer friendly to tell your customers that you6 :haven't tested your software on older versions of the* :OS.  But that's really a different issue.  H   It may be a different issue, but it is related -- and I can definitelyL   sympathize with the effort involved in keeping support for older releases.K   Older releases have fewer fixes, and releases such as V6.1 have not seen lF   fixes in a while -- V6.1 in particular is no longer available under F   standard or Prior Version Support, meaning it doesn't get any newer G   fixes.  Also in the specific case of V6.1, it also predates the work yF   that permits OpenVMS to better adapt to the needs of j-random weird J   SCSI device.  (That work has occured in releases such as V6.2 and V7.1.)G   With V7.1  and later, folks have reported success with Zip drives on j;   OpenVMS -- you could probably make the transfer directly.D  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Sun, 03 Sep 2000 14:11:43 -0500M7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>p/ Subject: Re: Please help a poorly Microvax 3100t, Message-ID: <39B2A26F.D751348@earthlink.net>   Chris Hedley wrote:A > / > In article <39B1B9D6.83A47213@earthlink.net>,iC >         "David J. Dachtera" <djesys.nospam@earthlink.net> writes: I > > Well, I don't know if I'd go QUITE *THAT* far! You do, after all, geteH > > this display on the console terminal, correct? Do you need more than	 > > that?r  , To address your comments in reverse order...  H > replacing the serial controller on a VS3100/76 is out of the question   6 Ah HAH! A VAXstation! Now, that's a different critter!  E O.k. What makes you think the serial interface is bad? Have you tried-5 using a terminal or a PC running a terminal program? e  wK > The firmware is the variety (or at least this is the way it's configured) J > that stops an autoboot if even minor (one "?") errors are detected, so I > have to enter "B DKA200" h   When you type:   >>>SHOW HALT    What does it display? How 'bout:   >>>SHOW BOOT   ...?  2 > Not too much of an issue, except that it appearsH > to be the same serial controller that handles both direct and terminalK > keyboard input - getting messages *out* of the thing isn't a problem, buttE > there's that annoying heiroglyphics problem when trying to input...o  @ Hhmmm... So, you're saying that when you type it echoes garbage?  G Do you have another keyboard you can try? They do go bad sometimes... IsF think any old VT220(or later)-compatible keyboard will do. The consoleE program may be less sensitive than VMS to incorrect data format, etc.,  G Does your VS have a TK50 or TZ30? If it does, I could send you a SABKUP_G tape. You could try to boot THAT up and see if it still echoes garbage. F That would help isolate it to hardware or software. See if your system disk has an "E" root:a   >>>B/E0000000 DKA200  F Also, I'm seeing another pattern here: the system board battery (whichG retains config info.) may have gone bad. Just another thought you mighth
 explore...   -- r David J. Dachterao dba DJE Systemsi http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/a  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------   Date: 3 Sep 2000 19:37:30 GMT 7 From: cbh@REMOVE_THIS.teabag.fsnet.co.uk (Chris Hedley)i/ Subject: Re: Please help a poorly Microvax 3100 ( Message-ID: <8ou99q$eku$3@teabag.cbhnet>  , In article <39B2A26F.D751348@earthlink.net>,: 	"David J. Dachtera" <djesys.nospam@earthlink.net> writes:. > To address your comments in reverse order...  	 Thanks...l  8 > Ah HAH! A VAXstation! Now, that's a different critter!  D Oops: I should really know better than that, but to this day I still muddle VSs with MVs... :/1  G > O.k. What makes you think the serial interface is bad? Have you tried07 > using a terminal or a PC running a terminal program? t  E I've tested the terminal with a loopback connector and that's okay; IoE thought it may be the cable so I connected a monitor and keyboard butt/ I still got gobbledegook when I typed things...n   > When you type: > 
 >>>>SHOW HALTo  & Something like ""  This is anF approximation: it seems like the high-bit is on permanently but it mayF be more convoluted than that.  Anyway, I don't get much of a result...  B > Hhmmm... So, you're saying that when you type it echoes garbage?  
 Er... yes.  I > Do you have another keyboard you can try? They do go bad sometimes... I H > think any old VT220(or later)-compatible keyboard will do. The consoleG > program may be less sensitive than VMS to incorrect data format, etc._  C I have two LK201(?)s; I haven't ruled out the possibility that theyl might both be a bit duff...e  I > Does your VS have a TK50 or TZ30? If it does, I could send you a SABKUP I > tape. You could try to boot THAT up and see if it still echoes garbage._H > That would help isolate it to hardware or software. See if your system > disk has an "E" root:  >  >>>>B/E0000000 DKA200  > H > Also, I'm seeing another pattern here: the system board battery (whichI > retains config info.) may have gone bad. Just another thought you mightr > explore...  F I'm pretty sure it doesn't have an E root (I don't remember seeing oneG last time I mucked about with it and, unless it's a default install, itID won't be there as I didn't do it when I installed the OS a few yearsF back!)  Unfortunately I don't have a TK%0 unit attached to it althoughG I guess that might be moot as the firmware isn't interested in a word I  say anyway!   H I've tried various baud-rates to transmit to the VS, but haven't had anyE joy with them or different parity settings, although AIUI the defaultsG setting's 8/-/1 (b/p/s) anyway.  But if there is an obscure config thatgE might be the source of my poor VS' woes I'd be glad to hear about it!    Thanks for your help,d   Chris.   ------------------------------  % Date: Sun, 03 Sep 2000 14:30:00 -0500r7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>t Subject: Re: scsi tape drive- Message-ID: <39B2A6B8.5C189843@earthlink.net>i  * yyyc186.illegaltospam_@flashcom.net wrote: > 3 > In <39AB0F8E.269F28A9@earthlink.net>, on 09/03/00 I >    at 11:19 AM, "David J. Dachtera" <djesys.nospam@earthlink.net> said:h > L > There used to be an external TZ85 version which could read/write both, but/ > I don't remember the exact model designation.e  G AFAIK, none of the Tx8x(x)'s are/were write compatible with either TK5010 or TK70. I could be wrong, of course, as always.   -- y David J. DachteraC dba DJE Systemsh http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/r  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.e   ------------------------------  % Date: Sun, 03 Sep 2000 14:38:52 -0500t7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>n Subject: Re: scsi tape drive- Message-ID: <39B2A8CC.7F864C8E@earthlink.net>i  * yyyc186.illegaltospam_@flashcom.net wrote: [snip]I > There used to be a version of the TZ85 which was capable of this, but Io$ > don't remember which model number.  E AFAIK, none of the Tx8x(x)'s are write-compatible with either TK50 or  TK70.s  G Unless I'm badly mistaken, Tx88 and later won't even read them, either.m  8 ...again, AFAIK. I could be wrong, of course, as always.   -- 1 David J. Dachtera1 dba DJE Systems- http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/8  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------   Date: 3 Sep 2000 19:46:24 GMT 2 From: mathog@seqaxp.bio.caltech.edu (David Mathog); Subject: Small system success, was Re: Big AlphaServer Sale , Message-ID: <8ou9qg$s1t@gap.cco.caltech.edu>  R In article <39AEAF6D.ED271DA9@genetek.com>, Mark Sun <marksun@genetek.com> writes: >Bill Todd wrote:r >> >@ >> > >>> It doesn't include small scale technical computing, <<< >> >K >> > While OVMS obviously does not dominate the WS industry, take a look at M >> > http://www.genetek.com/ - they have an extremely competitive workstationnN >> > offering (on OpenVMS) because it takes advantage of many of the Alpha andO >> > OpenVMS specific features. Floating point 64bit performance is a killer on-L >> > the Alpha and their seismic solution takes advantage of these features. >>K >> Why they chose Alpha seems obvious.  It would be interesting to find outsO >> exactly why they chose VMS over Tru64 (Linux wasn't an option back when theytH >> developed their application), which one would assume would be equally >> competitive in performance. >>O >OpenVMS is not mentioned on Genetek's web site because it is irrelevant to theIN >geoscientists that use our products.  I can't say much on this except that weK >chose OpenVMS for many reasons, mainly because it is easy to maintain, has Q >continued support and development from a single vendor (not committee based) andeG >has features that make it more cost effective in a TOC sense than UNIXg >offerings.f >i > M >We didn't want our clients to have an IT guy around just to support his UNIXtO >system.  With OpenVMS, we have large clients where the IT department never hasfP >had to spend supporting our workstations.  We also have very small clients thatI >have no IT department that requires little or no support, because of theb >stability of OpenVMS.  I Here we finally have somebody with a real product saying what we all knowrI to be true - that a VMS workstation can be configured (easily!) in such aoJ way that nobody will later need to screw with it, which makes the cost of J ownership after the purchase, very low.  So that the "TOC" argument reallyH does hold even at the low end.   This would make an interesting "successI story" for Compaq because (for once) it's an application outside the data  center.w   Regards,   David Mathog mathog@seqaxp.bio.caltech.eduT? Manager, sequence analysis facility, biology division, Caltech s   ------------------------------  # Date: Sun, 03 Sep 2000 18:51:45 GMT % From: hg/jb <shsrms@bellatlantic.net>h* Subject: Re: Sun Hardware problems persist0 Message-ID: <39B29DC5.60F85021@bellatlantic.net>   "Terry C. Shannon" wrote:d > M > They say there is no such thing as bad press, but I rather doubt that ScottfM > McNealy and Larry Hambly are amused by the recent coverage. It's clear that I > Sun is suffering from some reliability issues right now (indeed, I havejM > talked to one very large customer not cited in the ComputerWorld article orgI > in this forum about ongoing UE10K problems). I am no fan of the "you'veoN > gotta sign an NDA to get the problem solved" approach to problem resolution;M > it reminds me of Oracle's old "you can benchmark our database but you can't 8 > publicly disclose the results" Risky Marketing Scheme. > L > That said, product flaws are not restricted to any single vendor (rememberH > the VAX 9000 or the infamous RA-82 disk?). Sooner or later, it will be& > another vendor's turn in the barrel.H Hmm, If I slip the clock back to 1978- dec's advanced manufacturing crew in shrewsbury.C Elevated temp, even without power found a bunch of infant mortality  probs.) Elevated temp with power found some more.eB Powering up the box/board/chip, with just eleveated temp, and then running thes9 boards or chips showed a higher MTBF for shipped product.s  E Static? Static? we solved that in 74...I could tell some test stories. but I better not.... bob/   ------------------------------  # Date: Mon, 04 Sep 2000 02:20:54 GMT   From: jlsue <jlsuexxxz@home.com>* Subject: Re: Sun Hardware problems persist8 Message-ID: <6c16rs4th3qeb89727lavopi6i9qgti1jf@4ax.com>  E On Fri, 01 Sep 2000 11:01:55 +0100, Andrew Harrison SUNUK Consultancye! <andrew.nospam@uk.sun.com> wrote:y  O >Most customers seem to assume that if they keep systems within their operating O >temperature ranges and humidity ranges they will be reliable, when in fact theeP >systems will be more reliable (from all vendors) if they are operated in a much. >tighter range of temperatures and humidities.  D Hmm... Well, we ran computer rooms with IBM Mainframes (1401, 3033),F PDP-11, several VAX systems, many different disk types, tape drives of@ different varieties, etc.  Never worried about "tighter range ofD temperatures and humidities" to keep them going.  Ever.  Never, everF became a problem... makes me wonder how much you really know about all this.i  C On the other hand, I *do* remember the RA-81 glue problems, and, inaE fact, we had problems with DEC drives up through RA92.  However, thateA is a *long* time ago, and all of the quality Quantum hardware (rzpB disks and DLT tapes)  you see today were originally architected at; DEC, so they learned a bit from those experiences, I'd say.t1 Not speaking for anyone, certainly not DEC/CompaqZ- (get rid of the xxxx in my address to e-mail)    ------------------------------  % Date: Sun, 03 Sep 2000 14:45:46 -0500l7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>61 Subject: Re: TCP/IP 5.0A PatchList or ECO Summary - Message-ID: <39B2AA6A.F2110054@earthlink.net>T   Peter LANGSTOEGER wrote: > [snip] > L > Why do I have the feeling, that this is a very bad sign ? TCPIP is said toK > be a vital part of VMS now and seeing no improvement for such a long timepG > is very frightening. And all this during the sensible phase of UCX toe > TCPIP migration.  E Is third-party TCP/IP not an option? (Multinet / TCPware, I recommendn
 Multinet.)  P > "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998  G The more signs I see of - whatever the relationship may be - the more IdC believe that OpenVMS V8.something is more likely to be what W/NT V3eG should have been and what M$ wanted W/NT V4 to be. Of course, cost willt; continue to stifle OpenVMS until it goes the way of Novell.    ...IMHO.   -- n David J. DachteraI dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/s  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged./   ------------------------------   Date: 3 Sep 2000 23:17:20 +0200s* From: eplan@kapsch.net (Peter LANGSTOEGER)1 Subject: Re: TCP/IP 5.0A PatchList or ECO Summarye* Message-ID: <39b2bfe0$1@news.kapsch.co.at>  g In article <39B2AA6A.F2110054@earthlink.net>, "David J. Dachtera" <djesys.nospam@earthlink.net> writes:  >Peter LANGSTOEGER wrote:.M >> Why do I have the feeling, that this is a very bad sign ? TCPIP is said to.L >> be a vital part of VMS now and seeing no improvement for such a long timeH >> is very frightening. And all this during the sensible phase of UCX to >> TCPIP migration.S > F >Is third-party TCP/IP not an option? (Multinet / TCPware, I recommend >Multinet.)s  H We already use TCPware for many years now, but only on servers (which isC now only one). All other systems use TCPIP (used to be UCX before).   : And, is Multinet the excuse (or the suggestion) of Q now ?   -- m< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888s< FBFV/Information Services           E-mail  eplan@kapsch.netF <<< KAPSCH AG  Wagenseilgasse 1     PSImail PSI%(0232)281001141::EPLANH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"N "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998   ------------------------------   Date: 3 Sep 2000 22:07:37 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)1 Subject: Re: TCP/IP 5.0A PatchList or ECO Summaryi6 Message-ID: <8oui39$34h$1@mailint03.im.hou.compaq.com>  W In article <39b27b91$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes: K :Why do I have the feeling, that this is a very bad sign ? TCPIP is said to J :be a vital part of VMS now and seeing no improvement for such a long timeF :is very frightening. And all this during the sensible phase of UCX to :TCPIP migration.d  0   You have an interesting idea of "frightening".  G   With my recent experiences with TCP/IP Services, this isn't the least 0   bit frightening.  I kinda like it, actually...  H   There were no wide-spread nor critical bugs and thus no need to spend K   time creating an ECO kit when time could be spent on new TCP/IP Services nM   work (V5.1 has stuff that has not been mentioned in this or other threads) -J   and on IP-related engineering projects such as COE -- and the customers K   that did encounter and did need specific fixes could get these fixes via r   CSC.  I   More than a few of the local engineering clusters are running "vanilla" K   V5.0A -- I've not seen more than a handful of problem reports with V5.0A aK   from any internal or external sources.  (I've been chasing down more thanIL   a few IP printer discussions -- thus I've added details to the FAQ and to I   other locations on printing, and have updates queued for the next FAQ.)i     This is bad _how_? e  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 04 Sep 2000 02:13:52 +0400a4 From: "Ruslan R. Laishev" <Laishev@SMTP.DeltaTel.RU>1 Subject: Re: TCP/IP 5.0A PatchList or ECO Summary 0 Message-ID: <39B2CD20.189992C1@SMTP.DeltaTel.RU>   Hoff Hoffman wrote:  > C >   Warning: All schedules and dates referenced here are subject toe: >   change, and are subject to change without notice, etc. > Y > In article <39b00fab$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes:hN > :Yes, there are patches (unofficial, call your Qsupport) but not on the net.L > :The latest I have (since Dec-1999) is PTRV50A-05. I don't know of a newer# > :one, but this is not surprising.a > F >   If folks are having specific problems with TCP/IP Services, please8 >   contact the Compaq Customer Support Center directly.E 	Sorry, Hoff, but CCS can't offer anything, I have contacted with UCXeE engineering a couple month ago and they was going to silence ! In theS= same time other TCP/IP for VMS vendor(s) keep "eyes" is open.a  G 	Sorry, I don't want to be a rude but UCX/TCPIP still have had problemst* and still these problems not are fixed. :(  < 	Why UCX/TCPIP engineering guys don't read this conference ?   > P >  --------------------------- pure personal opinion ---------------------------N >    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   --   Regards, Ruslan.F +.....................pure personal opinion..........................+B     Free & commercial software for ISP -> HTTP://WWW.RadiusVMS.COM. 	Cel:+7 (901) 971-3222, Fax:+7 (812) 115-1035
   ------------------------------   Date: 3 Sep 2000 23:36:30 GMTs2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)1 Subject: Re: TCP/IP 5.0A PatchList or ECO Summaryo6 Message-ID: <8oun9u$3md$1@mailint03.im.hou.compaq.com>  g In article <39B2CD20.189992C1@SMTP.DeltaTel.RU>, "Ruslan R. Laishev" <Laishev@SMTP.DeltaTel.RU> writes:iG :>   If folks are having specific problems with TCP/IP Services, pleasek9 :>   contact the Compaq Customer Support Center directly.kF :	Sorry, Hoff, but CCS can't offer anything, I have contacted with UCX? :engineering a couple month ago and they was going to silence !H  A   To the point: Details of the specific problem(s) or request(s)?r  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   End of INFO-VAX 2000.494 ************************