1 INFO-VAX	Sat, 28 Oct 2006	Volume 2006 : Issue 593       Contents:( Re: decw$sylogin.com doesn't seem to run Mylex controller update  Re: Mylex controller update  Re: Mylex controller update  Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questionsG Re: OT: Babylon-5 (was Heads up: La Fiorina's book coming out nextweek) 1 Re: simple improvements to disk write performance 1 Re: simple improvements to disk write performance 1 Re: simple improvements to disk write performance 1 Re: simple improvements to disk write performance 1 Re: simple improvements to disk write performance % SYSMAN oddity (username on same node) ) Re: SYSMAN oddity (username on same node) - TCP/IP Services EAK for IPsec or Multinet 5.2 1 Re: TCP/IP Services EAK for IPsec or Multinet 5.2  Re: VMS installation crash Re: VMS installation crash  F ----------------------------------------------------------------------  + Date: Sat, 28 Oct 2006 17:46:15 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)1 Subject: Re: decw$sylogin.com doesn't seem to run $ Message-ID: <ei0517$bt4$1@online.de>  C In article <1162006882.073019.173150@f16g2000cwb.googlegroups.com>, & "Charles" <ceharon@gmail.com> writes:   2 > I can't get sys$manager:decw$sylogin.com to run. > I > I've been through the DECWindows Motif Management Guide, and everything " > seems to be configured properly. > 7 > sys$manager:decw$sylogin.com only contains two lines: * > $ notice :== mcr dka0:[notice]notice.exe > $ create/term notice/new/text  > ( > Any suggestions of where to look next?  ( File protections?  Disk mounted /SYSTEM?   ------------------------------  % Date: Sat, 28 Oct 2006 15:05:12 +0200 # From: "H Vlems" <hvlems@freenet.de>   Subject: Mylex controller update4 Message-ID: <ehvke0$ej2$1@registered.motzarella.org>  K Last week I reported problems with Mylex controllers (KZPSC), I have two, a L single channel (KZPSC-AA) and a three channel (KZPSC-CB). Neither would workF in an Alpha Server 1200. As it happens, both controllers had different1 problems but to the Alpha they all appeared dead.   L The -AA has Mylex V3.52 firmware and two firmware chips. I tried the RA200FLE and the DAC960FL utilities to downgrade to DEC firmware version 2.70. I The RA200FL program wouldn't run: program too large for available memory. J The host PC is a Compaq EP model with 512 MB and I hit F5 when DOS booted.> However DAC960FL did run, but refused to downgrade from V3.52.  J The -CB had a jumper block missing and was not recognized by neither AlphaL nor PC. Since the -AA wasn't going to work anyway, I pulled its jumper blockH and the -CB was suddenly recognized by the Alpha. It ran V2.50 and I wasJ able to upgrade the firmware to V2.70. The three RZ1DF drives were seen byL the controller and right now it's building a RAID5 set from these three 9 GB drives. $ That is expected to take 90 minutes.   ------------------------------    Date: 28 Oct 2006 07:24:30 -0700) From: "WWWebb" <William.W.Webb@gmail.com> $ Subject: Re: Mylex controller updateC Message-ID: <1162045469.973840.164300@k70g2000cwa.googlegroups.com>    H Vlems wrote:M > Last week I reported problems with Mylex controllers (KZPSC), I have two, a N > single channel (KZPSC-AA) and a three channel (KZPSC-CB). Neither would workH > in an Alpha Server 1200. As it happens, both controllers had different3 > problems but to the Alpha they all appeared dead.  > N > The -AA has Mylex V3.52 firmware and two firmware chips. I tried the RA200FLG > and the DAC960FL utilities to downgrade to DEC firmware version 2.70. K > The RA200FL program wouldn't run: program too large for available memory. L > The host PC is a Compaq EP model with 512 MB and I hit F5 when DOS booted.@ > However DAC960FL did run, but refused to downgrade from V3.52. > L > The -CB had a jumper block missing and was not recognized by neither AlphaN > nor PC. Since the -AA wasn't going to work anyway, I pulled its jumper blockJ > and the -CB was suddenly recognized by the Alpha. It ran V2.50 and I wasL > able to upgrade the firmware to V2.70. The three RZ1DF drives were seen byN > the controller and right now it's building a RAID5 set from these three 9 GB	 > drives. & > That is expected to take 90 minutes.   Congratulations, and good luck.   4 It may take considerably longer, from my experience.   WWWebb   ------------------------------  % Date: Sat, 28 Oct 2006 16:51:24 +0200 # From: "H Vlems" <hvlems@freenet.de> $ Subject: Re: Mylex controller update4 Message-ID: <ehvql3$l6p$1@registered.motzarella.org>  6 "WWWebb" <William.W.Webb@gmail.com> schreef in bericht= news:1162045469.973840.164300@k70g2000cwa.googlegroups.com...  >  > H Vlems wrote:H > > Last week I reported problems with Mylex controllers (KZPSC), I have two, aK > > single channel (KZPSC-AA) and a three channel (KZPSC-CB). Neither would  workJ > > in an Alpha Server 1200. As it happens, both controllers had different5 > > problems but to the Alpha they all appeared dead.  > > H > > The -AA has Mylex V3.52 firmware and two firmware chips. I tried the RA200FL I > > and the DAC960FL utilities to downgrade to DEC firmware version 2.70. E > > The RA200FL program wouldn't run: program too large for available  memory. F > > The host PC is a Compaq EP model with 512 MB and I hit F5 when DOS booted. B > > However DAC960FL did run, but refused to downgrade from V3.52. > > H > > The -CB had a jumper block missing and was not recognized by neither Alpha J > > nor PC. Since the -AA wasn't going to work anyway, I pulled its jumper block L > > and the -CB was suddenly recognized by the Alpha. It ran V2.50 and I wasK > > able to upgrade the firmware to V2.70. The three RZ1DF drives were seen  byK > > the controller and right now it's building a RAID5 set from these three  9 GB > > drives. ( > > That is expected to take 90 minutes. > ! > Congratulations, and good luck.  > 6 > It may take considerably longer, from my experience. >  > WWWebb >   L The first 5% took a little under 5 minutes, extrapolating from that I got 90$ minutes. Eventually it took 1hr55...D Right now I'm booting VMS 8.2 for the first time since the Mylex wasE installed and SRM at least detects dra0 as a three member RAID 5 set. I Whar is dispappointing is that 3 members, 9 GB each give me only 35545088 J blocks of storage, a little under 18 GB so I one drive! I did not select aK hot spare drive so either RAID5 is inefficient or I'm still doing something 
 wrong here...    ------------------------------    Date: 27 Oct 2006 23:50:06 -0700 From: "MZN" <MikeZmn@gmail.com>  Subject: Novice's questions A Message-ID: <1162018206.560483.44380@e3g2000cwe.googlegroups.com>   D Recently I bought XP1000 w/o HDD. I added to it HP Surestore Dat40i,G Adaptec 39160 , Seagate 18Gb HDD and Toshiba DVD-ROM. From the hardware @ side all of it looks working (it detects normal). Then I installC OpenVMS 8.2, and now I have the following questions (some or all of  them may be stupid):  G 1. Does exist some analog of PC BIOS, and, if yes how to enter to it? I G can see SRM console only and when I upgraded firmware, I suspect that I  saw something else.   0 2. What is last revision of firmware? I use 5.9.  8 3. How to see complete result of command or scroll back?  B 4. How to find tecnical manuals for that machine? Where I can find2 motherboard jumpers functions. In electronic form.  C 5. What's differences between original and PC keyboards? I use last  one.  B 6. I have 512Mb of RAM. Can I upgrade it to 4Gb by 8 regular 512Mb8 PC100 ECC reg DIMMs (by 2 sets of four identical DIMMs)?  E 7. How I can get all needed licenses for my system? (I have no one) I C tried to do that through DECUS Canada and DECUS Germany without any  response. I'm live in Russia.   D 8. What graphics card is better for my system PowerStorm 300 (I have it) or Radeon 7500?   C 9. What is the best way for data exchanging between XP1000 (running G OpenVMS) and Windows XP computers? I mean storage devices, not network.    A lot of thanks in advace,   Mike   ------------------------------  % Date: Sat, 28 Oct 2006 03:55:03 -0500 % From: Dan Foster <usenet@evilphb.org>  Subject: Re: Novice's questions 5 Message-ID: <slrnek66n7.5bi.usenet@zappy.catbert.org>   ` In article <1162018206.560483.44380@e3g2000cwe.googlegroups.com>, MZN <MikeZmn@gmail.com> wrote:F > Recently I bought XP1000 w/o HDD. I added to it HP Surestore Dat40i,I > Adaptec 39160 , Seagate 18Gb HDD and Toshiba DVD-ROM. From the hardware B > side all of it looks working (it detects normal). Then I installE > OpenVMS 8.2, and now I have the following questions (some or all of  > them may be stupid): > I > 1. Does exist some analog of PC BIOS, and, if yes how to enter to it? I I > can see SRM console only and when I upgraded firmware, I suspect that I  > saw something else.   ) The XP1000 supports two different BIOSes:   
 ARC/AlphaBIOS  SRM   F The first was geared towards supporting the Windows port to Alpha manyB years ago. The second is geared towards Tru64 and OpenVMS support.  A They are the analog of a PC BIOS, but better in some ways. SRM is E different from a PC BIOS; it is more like a server class BIOS used in  various UNIX and VMS servers.   E In the VMS (and UNIX) world, we call it 'firmware' instead of 'BIOS', * but you'll be understood with either term.  % For more information on SRM commands:   I http://www.hoffmanlabs.org/vmsfaq/vmsfaq_contents_002.html#toc_chapter_14    See section 14.3.1.   I It's all command line based rather than menu based, but very easy to use.   K If you ever need to switch between the two firmwares, see section 14.3.7.3.   < (Usually the only time a SRM-based system will boot into theH ARC/AlphaBIOS firmware is if its battery has expired. That's why the FAQE entry was written, so you could switch back to SRM if that happened.)   2 > 2. What is last revision of firmware? I use 5.9.  A http://ftp.digital.com/pub/DEC/Alpha/firmware/readmes/xp1000.html    says V5.9-1.  5 To see what revision you have (if it's 5.9 or 5.9-1):    $ show cpu/full   : (I think this needs to be done from a privileged account.)   or  . $ write sys$output f$getsyi("palcode_version")  : > 3. How to see complete result of command or scroll back?  F Best to use a serial console instead of graphical console for this, ifB you want to save console information prior to starting DECwindows.  H Reason? With your favorite communication program (for a serial console),4 you can save or copy-n-paste scrollback buffer data.  C Or you can temporarily power off, disconnect monitor, attach serial D console cable to a PC (or whatever you have available), power on theG XP1000, interrupt its boot if necessary, do whatever you want with SRM,  copy/save the scrollback data.  @ Then power off again and switch back to a graphical monitor (and5 disconnect the serial cable), then power on and boot.   2 That's one way to do it if your need is temporary.  D > 4. How to find tecnical manuals for that machine? Where I can find4 > motherboard jumpers functions. In electronic form.  U http://h18002.www1.hp.com/alphaserver/workstations/retired/xpseries/xp1000/index.html   A It might be there somewhere. If not, ask specific questions about 3 specific jumpers you would like to know more about.   E In general, there are not many officially documented jumpers. You can B find bits and pieces of information in various places, such as theG jumpers for CPU frequency change. (I don't generally recommend altering C anything on VMS hardware like jumpers unless you have a real need.)   E > 5. What's differences between original and PC keyboards? I use last  > one.  E Traditional VMS keyboards uses some extra keys. They're not critical; $ you can run with PC style keyboards.  F I believe currently shipping VMS keyboards are closer to a PC keyboardG now, but I'm not 100% sure as I haven't bought a new keyboard in years.   D > 6. I have 512Mb of RAM. Can I upgrade it to 4Gb by 8 regular 512Mb: > PC100 ECC reg DIMMs (by 2 sets of four identical DIMMs)?  E Maximum amount of memory known to work is 2 GB total. I'm not sure if I VMS can see beyond 1 GB on this model... maybe, maybe not, give it a try.   G I would don't know if you could get 4 GB since the memory controller in = the XP1000 was made before the higher density DIMMs came out.   E Maybe, maybe not, so try it if you really want to know. But if you're 0 buying DIMMs, safer to go with the 256 MB DIMMs.  G > 7. How I can get all needed licenses for my system? (I have no one) I E > tried to do that through DECUS Canada and DECUS Germany without any  > response. I'm live in Russia.   H If you really can't get a response from someone, maybe try Encompass US.G (Encompass was originally DECUS but then changed name a few years ago.)    http://www.encompassus.org  E and contact someone there to see if they can help you or refer you to  someone who can help.   F > 8. What graphics card is better for my system PowerStorm 300 (I have > it) or Radeon 7500?   C It depends. How are you planning on using graphics? For 2D work? 3D B work? 8 bit, 16 bit, or 24 bit color? What kind of monitor are you using; CRT or LCD?  E > 9. What is the best way for data exchanging between XP1000 (running I > OpenVMS) and Windows XP computers? I mean storage devices, not network.   F Hmm. For physical media-only transport, maybe ISO9660 with extensions?  E I'm not sure if OpenVMS can read FAT16 or FAT32. I know it can't read ( most other filesystems (including NTFS).  D You do have another option: use OpenVMS's native ODS-2 filesystem onF your storage device and then use special third-party Windows utilities to read/write data to/from it.  B For example, the ODS2 utility which can run under both Windows and UNIX/Linux:   9 http://vms.process.com/ftp/vms-freeware/fileserv/ods2.zip   ? It's command line based rather than drag-n-drop but works well.    -Dan   ------------------------------  % Date: Sat, 28 Oct 2006 10:19:57 +0100 ! From: baldrick <nosp@[127.0.0.1]>  Subject: Re: Novice's questions A Message-ID: <454320be$0$8712$ed2619ec@ptn-nntp-reader02.plus.net>   
 MZN wrote:  F > Recently I bought XP1000 w/o HDD. I added to it HP Surestore Dat40i,I > Adaptec 39160 , Seagate 18Gb HDD and Toshiba DVD-ROM. From the hardware B > side all of it looks working (it detects normal). Then I installE > OpenVMS 8.2, and now I have the following questions (some or all of  > them may be stupid): > I > 1. Does exist some analog of PC BIOS, and, if yes how to enter to it? I I > can see SRM console only and when I upgraded firmware, I suspect that I  > saw something else.   F The SRM that you see is part of the Alphabios controls that you would I set on a PC, e.g. the boot device and order. It is similar, not the same.    > 2 > 2. What is last revision of firmware? I use 5.9.  G This is correct, many alpha's have not had or needed a firmware update   for some while.   : > 3. How to see complete result of command or scroll back?  H Its not directly possible on the console, but when the operating system > is booted, you need to run windowing software that gives this G functionality. There are other methods to capture the information that  I scrolls off the screen by using start up parameters but this is a little  C advanced for now (SYSTARTUP_P2="D" captures startup to a log file).    > D > 4. How to find tecnical manuals for that machine? Where I can find4 > motherboard jumpers functions. In electronic form. >   8 There is more and growing collection online, use Google.  E > 5. What's differences between original and PC keyboards? I use last  > one.  H It is the DO, HELP and the F17 to F20 keys that are missing from the PC G keyboard, also the labeling and layout is slightly different, the page  0 up/down, delete, insert are in different places.    D > 6. I have 512Mb of RAM. Can I upgrade it to 4Gb by 8 regular 512Mb: > PC100 ECC reg DIMMs (by 2 sets of four identical DIMMs)?  I Probably yes. Not supported is how HP/Compaq/Digital would call this but  H this should work. However I do not immediately know if this motherboard D does support 4 GB. However one thing to bear in mind is that memory ; management on VMS is very good, 512MB is quite respectable.    > G > 7. How I can get all needed licenses for my system? (I have no one) I E > tried to do that through DECUS Canada and DECUS Germany without any  > response. I'm live in Russia.   I Basically you need to register yourself with one of the user groups, and  H use that ID. http://www.encompassus.org/ is an alternative . Then go to - http://www.openvmshobbyist.com/ for licenses.   5 Another excellent resource is http://www.openvms.org/    > F > 8. What graphics card is better for my system PowerStorm 300 (I have > it) or Radeon 7500?   H Depends what you want to do and if the card is supported on your system.  E > 9. What is the best way for data exchanging between XP1000 (running I > OpenVMS) and Windows XP computers? I mean storage devices, not network.   H Not quite clear here. There are some programs that allow VMS systems to F read non native hardware, but if it is just file transfer, NFS or FTP F would be best. Samba (soon to be CIFS for OpenVMS) is currently being I developed as a more functional alternative providing traditional Windows  G compatible file and print services, but that is at least 6 months from  = now, but evaluation copies are available for download at the  C http://www.hp.com/go/openvms web site. that does however require a  @ network and I think you're suggesting you do not want to use it. >  > A lot of thanks in advace,   > Mike  
 Good luck.  
 Regards, Nic.    --  1 aka. Mr. C. P. Charges, nclews "at" csc dot c o m    ------------------------------    Date: 28 Oct 2006 14:26:47 +02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: Novice's questions * Message-ID: <454368a7@news.langstoeger.at>  c In article <1162018206.560483.44380@e3g2000cwe.googlegroups.com>, "MZN" <MikeZmn@gmail.com> writes: E >Recently I bought XP1000 w/o HDD. I added to it HP Surestore Dat40i, H >Adaptec 39160 , Seagate 18Gb HDD and Toshiba DVD-ROM. From the hardwareA >side all of it looks working (it detects normal). Then I install D >OpenVMS 8.2, and now I have the following questions (some or all of >them may be stupid):  > H >1. Does exist some analog of PC BIOS, and, if yes how to enter to it? IH >can see SRM console only and when I upgraded firmware, I suspect that I >saw something else.  F The Alpha has a console program for booting and manipulating hardware.G It is called SRM (with the dead sergeant prompt ">>> ") for OpenVMS and I Digital UNIX aka Tru64 UNIX and the ARC or AlphaBIOS for Windows-NT Alpha J which looks like a PC BIOS (Linux can work with both of them last I heard)  1 >2. What is last revision of firmware? I use 5.9.   E The XP1000 has no newer firmware than 5.9-1. And so some things (like F WWIDMGR for the FibreChannel Adapters; USB; ...) won't work on XP1000.E And even VMS mentions during boot that this firmware version is below C the recommended firmware version (but is above the required version < and thus will work without problems). For firmware check out  / 	http://ftp.digital.com/pub/DEC/Alpha/firmware/   9 >3. How to see complete result of command or scroll back?   . Don't understand. Do you mean a $ RECALL/ALL ?  C >4. How to find tecnical manuals for that machine? Where I can find 3 >motherboard jumpers functions. In electronic form.   4 Don't know. Have you tried the following and google?  J    http://www.compaq.com/alphaserver/workstations/retired/xpseries/xp1000/  D >5. What's differences between original and PC keyboards? I use last >one.   I The layout. Not only the 6 keys above the cursor keys, but also 3 instead I of 2 keys above the rightmost "enter" key and the 20 (instead of only 12) I function keys. 108 keys instead of 101 (without the newer "windows" keys) 2 I recommend a VT one (at least for editing on VMS)  C >6. I have 512Mb of RAM. Can I upgrade it to 4Gb by 8 regular 512Mb 9 >PC100 ECC reg DIMMs (by 2 sets of four identical DIMMs)?    Maybe.  F >7. How I can get all needed licenses for my system? (I have no one) ID >tried to do that through DECUS Canada and DECUS Germany without any >response. I'm live in Russia.  B Can't think of that. DECUS Germany has members from many countriesB around germany (AFAIK including russia). Eg. Austria is only a LUG# (local user group) of DECUS Germany   8 	http://www.decus.de/mitgliedschaft/mitgliedsantrag.html, 	http://www.openvmshobbyist.com/register.php  E >8. What graphics card is better for my system PowerStorm 300 (I have  >it) or Radeon 7500?   Don't know. PS300 is older.   D >9. What is the best way for data exchanging between XP1000 (runningH >OpenVMS) and Windows XP computers? I mean storage devices, not network.  3 A LanMan Fileserver (like SAMBA or ADVANCEDSERVER)?    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 28 Oct 2006 06:06:53 -0700 From: "MZN" <MikeZmn@gmail.com>  Subject: Re: Novice's questions C Message-ID: <1162040813.467418.303300@f16g2000cwb.googlegroups.com>    Thanks to all of you!    1. Questtion resolved.   2. Resolved. I have last.   C 3. Speaking more precisely, if I input command (like sh dev) in SRM F or/and in OVMS, and its output is more then one full screen, how I canF read all that output?  What means 'serial console'? In hardware sense.  A 4. I tried both Google and link mentioned by you, and find almost & nothing. Did XP1000 have some manuals?   5. Resolved.  F 6. Resolved. 2Gb is official maximum, and if 512Mb is sufficient, it's OK.   D 7. For http://www.encompassus.org membership some payment requred. IA tried and Im try now all your advices. Now I'm wait for response.   = 8. I need in 2D, but with higher resolution and refresh rate.   C 9. I meaned media exchange mostly (an example FDD, CD etc.) ISO9669 C looks good. Hope I can burn CDs under OVMS? What about DVD burning?      Thanks,  Mike   ------------------------------    Date: 28 Oct 2006 07:43:40 -0700) From: "WWWebb" <William.W.Webb@gmail.com>  Subject: Re: Novice's questions C Message-ID: <1162046620.179028.235320@h48g2000cwc.googlegroups.com>   
 MZN wrote: > Thanks to all of you!  >  > 1. Questtion resolved. >  > 2. Resolved. I have last.  > E > 3. Speaking more precisely, if I input command (like sh dev) in SRM H > or/and in OVMS, and its output is more then one full screen, how I canH > read all that output?  What means 'serial console'? In hardware sense. > C > 4. I tried both Google and link mentioned by you, and find almost ( > nothing. Did XP1000 have some manuals?  3 Here's one filename.  Look for it online as a . pdf   C Compaq Professional Workstation XP1000 Installation and Setup Guide  EK-CPWXP-SI-B01      >  > 5. Resolved. > H > 6. Resolved. 2Gb is official maximum, and if 512Mb is sufficient, it's > OK.  > F > 7. For http://www.encompassus.org membership some payment requred. IC > tried and Im try now all your advices. Now I'm wait for response.   A Associate membership is free- and that's all that is required for  hobbyist licenses.> But if you *do* pay, you get some nice benefits and discounts. > ? > 8. I need in 2D, but with higher resolution and refresh rate.  > E > 9. I meaned media exchange mostly (an example FDD, CD etc.) ISO9669 E > looks good. Hope I can burn CDs under OVMS? What about DVD burning?  >   E There's a resident expert here who can tell you everything- Eberhard, 
 have you been  reading as of late?      WWWebb > 	 > Thanks,  > Mike   ------------------------------  + Date: Sat, 28 Oct 2006 09:36:00 -0500 (CDT) * From: sms@antinode.org (Steven M. Schweda) Subject: Re: Novice's questions 2 Message-ID: <06102809360004_20225020@antinode.org>   From: "MZN" <MikeZmn@gmail.com>   E > 3. Speaking more precisely, if I input command (like sh dev) in SRM H > or/and in OVMS, and its output is more then one full screen, how I canH > read all that output?  What means 'serial console'? In hardware sense.  
    >>>help      >>>show device | more  D You can connect a serial terminal (like a VT220) to one of the 9-pin@ serial ports, and use it instead of the workstation keyboard and graphics display.   C > 4. I tried both Google and link mentioned by you, and find almost ( > nothing. Did XP1000 have some manuals?  *       ftp://antinode.org/misc/xp1000sg.exe/       http://antinode.org/ftp/misc/xp1000sg.exe   H > 6. Resolved. 2Gb is official maximum, and if 512Mb is sufficient, it's > OK.   E    Up to 2GB is supported.  I haven't tried any more.  Look for PC100 G registered, ECC, CAS latency = 2 ("PC100-222-622R").  Two banks of four  modules.  E > 9. I meaned media exchange mostly (an example FDD, CD etc.) ISO9669 E > looks good. Hope I can burn CDs under OVMS? What about DVD burning?       VMSTAR and your DAT?  Also:  ,       http://antinode.org/dec/sw/mtools.html  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------  % Date: Sat, 28 Oct 2006 10:01:26 -0500 % From: Dan Foster <usenet@evilphb.org>  Subject: Re: Novice's questions 5 Message-ID: <slrnek6s66.5bi.usenet@zappy.catbert.org>   b In article <1162040813.467418.303300@f16g2000cwb.googlegroups.com>, MZN <MikeZmn@gmail.com> wrote: > E > 9. I meaned media exchange mostly (an example FDD, CD etc.) ISO9669 E > looks good. Hope I can burn CDs under OVMS? What about DVD burning?   $ For OpenVMS CD/DVD burning software:  ; For CDs, CDRECORD. That comes with recent OpenVMS versions.   5 For DVDs, Dr. Heuser-Hofmann's software (DVDwrite) at C http://www.dvdwrite.de. He offers a free version for hobbyists with  restricted functionality.   C Or you can use either MKISOFS to prepare ISO9660 *or* LDD (LDDRIVER B driver utility) to prepare OpenVMS native ODS-2 disk images on theG OpenVMS system then copy through network to a PC and burn it there with ! any CD or DVD recording software.   . MKISOFS for OpenVMS is an additional download.  @ LDD comes with recent versions of VMS; it is also available as aB download from the VMS Freeware CD. (This CD is downloadable, too.)   -Dan   ------------------------------  % Date: Sat, 28 Oct 2006 12:27:48 -0400 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org> Subject: Re: Novice's questions ) Message-ID: <ei00e3$12eo$1@pyrite.mv.net>   
 MZN wrote:  E > 9. I meaned media exchange mostly (an example FDD, CD etc.) ISO9669 E > looks good. Hope I can burn CDs under OVMS? What about DVD burning?   G    CDRECORD on V7.3-1 and later, and COPY/RECORDABLE_MEDIA on V8.3 and  D (as available) later.  CDRECORD is also available via the Freeware. G There are various discussions of DVD recording on OpenVMS here in this  F newsgroup, and there is a commercial package (with hobbyist licenses, A IIRC) around, and the COPY/RECORDABLE_MEDIA can also provide for   DVD+R/RW recording.   E    The OpenVMS FAQ has a section on recordable media on OpenVMS, and  C with linkages to various OpenVMS-related web sites with details on  I recording optical media on OpenVMS.  The FAQ is available at various web  9 sites including via <http://www.hoffmanlabs.org/vmsfaq/>.   I    There have been various discussions of devices that work with OpenVMS  H here in the newsgroup.  (A Google search of the archives should turn up  at least a few of these.)   H    There are tools that can record ISO-9660 around, mkisofs.  Check the E Freeware and various sites for CDRECORD and mkisofs.  OpenVMS itself  G supports the core set, and not various of the extensions.  (IIRC, this  / ISO-9660 support is also discussed in the FAQ.)    ------------------------------  % Date: Sat, 28 Oct 2006 10:31:21 -0700 4 From: Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com> Subject: Re: Novice's questions % Message-ID: <1162056520.429351@smirk>    Dan Foster wrote:   2 >>2. What is last revision of firmware? I use 5.9.  C > http://ftp.digital.com/pub/DEC/Alpha/firmware/readmes/xp1000.html  > says V5.9-1. > 7 > To see what revision you have (if it's 5.9 or 5.9-1):  >  > $ show cpu/full  > < > (I think this needs to be done from a privileged account.) >  > or > 0 > $ write sys$output f$getsyi("palcode_version")  9 These will show you the Palcode version (1.88-27) but not 8 the Firmware (SRM Console) version (V5.9-1), at least on  my VMS v8.3 XP1000.   See below.   Alan      >>>show config   6                            Compaq Computer Corporation<                       COMPAQ Professional Workstation XP1000   Firmware4 SRM Console:    V5.9-1          Dec 14 2000 16:19:05C PALcode:        OpenVMS PALcode V1.88-27, u64 UNIX PALcode V1.83-22  Serial Rom:     SROM A.9 PIC:            0.36  	 Processor  DECchip (tm) 21264-3    500MHz    
 <Boot VMS>  . $ write sys$output f$getsyi("palcode_version") 1.88-27    $ show cpu/full   4 System: SLUG, COMPAQ Professional Workstation XP1000  0    SMP execlet   = 3 : Disabled : Uniprocessing.    Config tree   = None     Primary CPU   = 0    HWRPB CPUs    = 4    Page Size     = 8192     Revision Code =    Serial Number =    Default CPU Capabilities:          System: QUORUM RUN      Default Process Capabilities:          System: QUORUM RUN   G CPU 0    State: RUN                CPUDB: 81C16000     Handle: * None * 3         Process: Frisbie #10          PID: 00000448     Capabilities:(          System: PRIMARY QUORUM RUN RAD0    Slot Context: 860BA180 =       CPU     -  State..........: RC, PA, PP, CV, PV, PMV, PL 7                  Type...........: EV6 (21264), Pass 2.2 )                  Speed..........: 500 Mhz C                  Variation......: VAX FP, IEEE FP, Primary Eligible !                  Serial Number..: !                  Revision.......: #                  Halt Request...: 0 %                  Software Comp..: 0.0 )       PALCODE -  Revision Code..: 1.88-01 $                  Compatibility..: 27#                  Max Shared CPUs: 1 J                  Memory  Space..: Physical = 00000000.00000000  Length = 0J                  Scratch Space..: Physical = 00000000.00000000  Length = 0    Bindings:A       NETACP           PID = 0000041B  Reason: PRIMARY Capability F       DECW$SERVER_0    PID = 0000042C  Reason: Affinitized to this CPU    Fastpath:
          PKA0 
          PKB0 
          PKC0           BG0    Features:       Autostart - Enabled.5       Fastpath  - Selection enabled as Preferred CPU.    ------------------------------  % Date: Sat, 28 Oct 2006 12:33:46 -0500 % From: Dan Foster <usenet@evilphb.org>  Subject: Re: Novice's questions 5 Message-ID: <slrnek753q.5bi.usenet@zappy.catbert.org>   [ In article <1162056520.429351@smirk>, Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com> wrote:  > ; > These will show you the Palcode version (1.88-27) but not : > the Firmware (SRM Console) version (V5.9-1), at least on > my VMS v8.3 XP1000.   A Ugh, indeed... I goofed since I had been thinking of a recent and ) separate discussion when I wrote that. :)   . $ write sys$output f$getsyi("console_version")  " ...is for the SRM console version.  < Even better is that it doesn't require privs or any parsing.   -Dan   ------------------------------  % Date: Sat, 28 Oct 2006 10:01:27 -0400 ) From: "Neil Rieck" <n.rieck@sympatico.ca> P Subject: Re: OT: Babylon-5 (was Heads up: La Fiorina's book coming out nextweek)< Message-ID: <45436252$0$14829$9a6e19ea@news.newshosting.com>  4 "Neil Rieck" <n.rieck@sympatico.ca> wrote in message5 news:45279b7c$0$5934$9a6e19ea@news.newshosting.com...  >    [...snip...]  I I just purchased a 5 year DVD kit of Babylon 5 (the complete seasons) for  US$99 from this link:  www.savingcity.net/specials   L The web site is in Markham, Ontario (just north of Toronto) but the kit cameK from China. Unlike some products coming from Amsterdam, these disks are not G burned with a stuck-on label. They appear to be pressed with a painted  0 label. Only a small amount of Asian lettering on/ the disks. Format is letterbox. 30 disks total.     
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.! http://www3.sympatico.ca/n.rieck/    ------------------------------  % Date: Sat, 28 Oct 2006 04:13:58 -0500 % From: Dan Foster <usenet@evilphb.org> : Subject: Re: simple improvements to disk write performance5 Message-ID: <slrnek67qm.5bi.usenet@zappy.catbert.org>   { In article <paul.sture.nospam-EF6D89.17231027102006@mac.sture.homeip.net>, Paul Sture <paul.sture.nospam@hispeed.ch> wrote: % >> >Does OpenVMS support SATA drives?  >>  L >> No, not at present.  Some have been tried and they work, but they haven't* >> been tested under stressful conditions.  J > Please be aware that the transfer rates quoted for SATA drives are peak E > rates, not sustained ones. Also, SATA 2 (or II)? is no more than a  J > renaming of the standards body concerned - it does *not* imply a faster  > disk.   F Well, actually, it does make certain features mandatory which provides: some performance boost such as Next Command Queuing (NCQ).  H My impression of the NCQ implementation is that it is a weaker cousin ofG SCSI's Tagged Command Queuing (TCQ), but certainly better than nothing.   A I can only speculate this was an intentional move in order to not 9 undercut the more expensive SCSI drive sales for servers.   D With that said, it isn't an eye-popping boost in performance for theG most part. It's just one of many things to evaluate if one is going all 9 out in getting the most out of tuning their entire setup.   G Still does behooves the application developer to tune their app as well D as how it interfaces with the system (e.g. with RMS tuning and maybe@ bypassing the RTL stuff if determined it's not using optimal I/O strategies).  G The '150 MB/sec' and '300 MB/sec' figures often bandied around by drive H manufacturers for SATA (I and II, or 1 and 2 -- take your pick :-) ) are just pure marketing fluff.  H They refer to the maximum the controller can handle, but this is more of? a theoretical maximum because you are still limited by physical E constraints such as platter design which doesn't tend to dramatically 4 change performance-wise in leaps and bounds. (Alas.)  G My general recollection is that the drive platters can actually deliver H approximately 65 MB/sec sustained at most for today's drives, regardless of drive technology.  F (Drive or controller caching can inflate these figures to make it look faster than what it really is.)   D Thus, it doesn't really matter which version of the SATA standard isD used; you're still constrainted by drive performance, underlying busH performance (PCI, PCI-X, etc), I/O controller hub design, OS performance; with driver and lower level stacks, and application design.   ' > Cheap, fast, reliable - pick any two.  > E > Or in the case of SATA drives, maybe just concentrate on the first  	 > option.   H Indeed. I know from extensive firsthand experience spanning thousands ofA drives that ATA and SATA drives we have (with appropriate chassis G cooling, placement, data centre cooling, etc) will generally last about @ 3 years. Our SCSI drives will generally last about 5 to 7 years.  F Supposedly, SCSI and SATA drives are often physically manufactured theA same but has differences such as drive electronics board and host G attachment connector form factor, but what I see very clearly in actual E production with drives all over the world suggests there is something / that makes the longevity so markedly different.   F We use SATA only where there is a large price differential versus SCSIG for a relatively less demanding application or service requirement that B is much more tolerant of failures and does not need 10K or 15K RPMH drives. We have to do extra work to buttress these setups to ensure that@ it won't be catastrophic when (and not if) these drives do fail.  A I have one of the older SATA drives for personal use; the Western @ Digital Raptor which is a 36GB SATA drive at 10K RPM. It's nice.E Impression I got was that this was a SCSI drive adapted for SATA use.   > Unfortunately, it hasn't gotten much use because my data needsH significantly outgrew it by at least 10x (mostly due to emulator relatedD work -- 220 GB+ worth of dozens of virtual machine disk images along3 with install CD images fleshing out the remainder).    -Dan   ------------------------------  % Date: Sat, 28 Oct 2006 04:25:01 -0500 % From: Dan Foster <usenet@evilphb.org> : Subject: Re: simple improvements to disk write performance5 Message-ID: <slrnek68fd.5bi.usenet@zappy.catbert.org>   b In article <ehtced$c4m$1@pyrite.mv.net>, Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org> wrote: > G > (And potentially RAID, though having RAID across a clump of disks all ? > from the same manufacturing batch can itself be, um, somewhat A > hazardous.  Best to spread your batches and/or vendors around.)    Mildly put.   E We had dozens of IBM RS/6000 B50 servers... retired most of them now, " with remainders being retired now.  H Whenever an internal drive failed, we usually replaced both because fromJ experience, the second drive would fail within 4 to 36 hours of the first.  F From an examination of information on the drive labels, it looked like: they generally all came from the same batch for each pair.  C We also made several large purchases, thus we'd have a lot of drive F failures within a group of purchased systems around the same timeframe( approximately five years after purchase.  B If nothing else, it made budget planning much easier when we could3 reliably and accurately predict the year it'd fail.   G With IBM's cheap SCSI disk enclosure (think of it as being like a basic D Storageworks array although without any controller smarts so no RAIDF support or anything fancy) -- the 2104-DU3, we had each 14 drive array! fail at almost all the same time.   ! Five drives replaced on one call. ! Seven drives replaced on another.   B Finally, IBM gave up and proactively (without us prompting for it)D ordered and installed sixteen drives -- two to replace the final twoG drives in one array and fourteen in another array. The service engineer = was shaking his head in amazement when he brought out all 16.   G (And, yes, long before this point, support had ruled out a wide variety A of culprits: firmware revs, driver rev, bugs, cooling, placement, G cabling, hardware failure in the enclosure, amongst many other things.)   E They had to wait a bit because internally, the local field office was D fighting for allocation of remaining drives of a particular type and? launched a national search. That was an interesting experience.   $ Homogenity isn't always an asset. ;)   -Dan   ------------------------------  # Date: Sat, 28 Oct 2006 12:37:16 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger) : Subject: Re: simple improvements to disk write performance[ Message-ID: <rdeininger-2810060837520001@dialup-4.233.173.215.dial1.manchester1.level3.net>   @ In article <slrnek67qm.5bi.usenet@zappy.catbert.org>, Dan Foster <usenet@evilphb.org> wrote:    >In article J <paul.sture.nospam-EF6D89.17231027102006@mac.sture.homeip.net>, Paul Sture% <paul.sture.nospam@hispeed.ch> wrote: & >>> >Does OpenVMS support SATA drives? >>> M >>> No, not at present.  Some have been tried and they work, but they haven't + >>> been tested under stressful conditions.  > K >> Please be aware that the transfer rates quoted for SATA drives are peak  F >> rates, not sustained ones. Also, SATA 2 (or II)? is no more than a K >> renaming of the standards body concerned - it does *not* imply a faster   >> disk. > G >Well, actually, it does make certain features mandatory which provides ; >some performance boost such as Next Command Queuing (NCQ).   E Unfortunately, even required features are optional.  If it works well G enough to mostly work in the commodity Windows world, they'll ship it.  C All they care about is minimizing their time to market.  We find it J usually takes one or two firmware updates before a new drive is marginally useable.  I >My impression of the NCQ implementation is that it is a weaker cousin of H >SCSI's Tagged Command Queuing (TCQ), but certainly better than nothing. > B >I can only speculate this was an intentional move in order to not: >undercut the more expensive SCSI drive sales for servers.  J I doubt it.  Features that are hard to implement correctly will get shoved. aside if it saves a few weeks on the schedule.  I The financial models for these products usually assume that any sales you I miss at the beginning of the product's lifetime will NEVER be recovered.  G The product's end of life is pre-determined by the roll-out of the next I generation.  I don't know if these models are valid, but they drive a lot  of product decisions.   E SCSI disks are fading away in any case.  There's not much more in the F pipeline.  FibreChannel and SAS disks will replace SCSI in the market.   ------------------------------  % Date: Sat, 28 Oct 2006 12:19:48 -0400 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>: Subject: Re: simple improvements to disk write performance) Message-ID: <ehvvv2$129e$1@pyrite.mv.net>    Bob Gezelter wrote:   G > I quite agree with Paul.  Having done a variety of informal bencharks F > over the years, the /EXTEND parameter is critical, provided that you6 > have some approximate idea of how big the files are.  G    Tweak the process settings and try it, and then tweak it and try it  F again.  In the last configuration I can recall having run this -- and F this was some time ago -- somewhere around 500 was the knee.  Setting I extent sizes beyond a range of, say, the 500 to 1000 range, there wasn't  G a particularly measurable benefit.  YMMV, obviously.  That written, if  ? the application knows what file size it needs, by all means do  @ preallocate it and/or set the extent size appropriately for the  application norms.  E > If I am regularly transferring 10's of MB, I would recommend a file  > extend to match.  G    Potentially within the context of the particular server process, if   that is allowed/configurable.   H    I'd expect to see the value these days (on a typical disk) being the    disk cluster factor.  H    The system value is accessable via SET RMS/SYSTEM and via the system @   parameter RMS_EXTEND_SIZE.  At the volume level -- if you can G partition  your big files onto one (logical or physical) disk spindle,  6 you can set  the extend size on the volume basis, too.  G    In practice, you waste half the disk cluster factor times the total  E number of files on a disk, but then there are also always trade-offs  H involved.  Setting the extent default at a multiple of the disk cluster I   factor can be an easy approach toward this compromise, as (worst case)  H   you can truncate to recover the unused space.  (Cluster factors of 16 I to 32, or a multiple, are what various of the OpenVMS I/O engineers were   recommending...)  F    Did anybody mention highwater marking?  With sequential operations H that would be typical of file copies, I'd not expect to see that become F   visible.  But if you should happen to write rather more randomly or I otherwise get the EOF placed far out in an otherwise empty file, you can  H   really hammer your file system performance when highwater is enabled. F   (And then there's erase-on-delete, but that's fodder for throttling  the  deletion speed.)    ------------------------------  % Date: Sat, 28 Oct 2006 18:18:07 +0100 5 From: "Tom Garcia" <tgarcia-REMOVE-THIS@hivemind.org> : Subject: Re: simple improvements to disk write performance7 Message-ID: <454390d2$0$634$5a6aecb4@news.aaisp.net.uk>    Bill Todd wrote:  B > Most likely, it's a sign that C isn't very suave about using the@ > underlying RMS I/O facilities.  My vague and possibly entirelyG > out-of-data recollection is that C uses simple RMS block I/O, and the   K It seems opening in record mode gives an immediate improvement over stream  H mode, which as you suggest seems to be the default. Disk write cache is D disabled. "ctx=rec" below gives me around 30MB/sec. Substitute with 1 "ctx=stm" and this goes down to previous 9MB/sec.   L I'm guessing the improvement here is due to write-behind caching being used J ("rop=wbh") for record operations when opening in record mode. Although I M haven't requested it explicitly, I think this is default when the file isn't  K opened with sharing ("shr=put" gives rec and stm methods both dragged down  H to ~3MB/sec.). Table REF-3 of the Run-Time Library Ref Manual indicates M "rop=wbh" is for "record processing operations" - does this mean no WBH when   in stream mode?   K Explicit "shr=nil", "fop=dfw", "alq=409558" (the final size) don't seem to   make a difference.  ) f = fopen("needless.bin", "w", "ctx=rec", 4     "rfm=stmlf", "deq=65535", "mbf=127", "mbc=127");F /* nonsense has size CHUNK=32767 with all 'a's, terminating in '\n' */? for (x=1; x<=200*MEG/CHUNK; x++) fwrite(nonsense, CHUNK, 1, f); 
 fclose(f);  K Similar improvement if I use fixed length records. One possible conclusion  J is that Unix porters wanting to think of a (binary) file as a byte stream G might try adding arguments to treat files as fixed-length records with  	 rat=none.    --  ! Tom Garcia | tgarcia@hivemind.org    ------------------------------  % Date: Sat, 28 Oct 2006 04:13:29 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> . Subject: SYSMAN oddity (username on same node), Message-ID: <4543111D.D7C57886@teksavvy.com>  9 This seems to be documented, but I cannot understand WHY:    (from node BIKE, user SYSTEM)   	 MC SYSMAN K SYSMAN> SET ENV/NODE=(BIKE,VELO,WHEEL)/USER=BRIAN_GRIFFIN/PASSWORD=MILKBONE   C It mentions that use BNRIAN_GRIFFIN will be use on non-local nodes.   H Doing a DO SHOW PROC/RIGHTS  confirms that BRIAN_GRIFFIN is used on VELO= and WHEEL, but that SYSTEM is used for BIKE (the local node).     G Why is it that the specified username is NOT used for the local node ?  F Is there some magical logical that can be set to change this behaviourD so that the specified username is used on all specified nodes for DO
 commands ?   ------------------------------    Date: 28 Oct 2006 14:36:04 +02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)2 Subject: Re: SYSMAN oddity (username on same node)* Message-ID: <45436ad4@news.langstoeger.at>  \ In article <4543111D.D7C57886@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:: >This seems to be documented, but I cannot understand WHY:  E And I don't think this is documented at all. I see it still as a bug.    >(from node BIKE, user SYSTEM) > 
 >MC SYSMANL >SYSMAN> SET ENV/NODE=(BIKE,VELO,WHEEL)/USER=BRIAN_GRIFFIN/PASSWORD=MILKBONE > D >It mentions that use BNRIAN_GRIFFIN will be use on non-local nodes.  E Yes, but it uses a subprocess of the SMISERVER on/of the remote nodes F and it uses a subprocess of the current process (and not the SMISERVERE on the local node) for the local node. It does this since decades and  it is still wrong in my eyes.   I >Doing a DO SHOW PROC/RIGHTS  confirms that BRIAN_GRIFFIN is used on VELO > >and WHEEL, but that SYSTEM is used for BIKE (the local node).  E Yes. And if it ain't SYSTEM and you start a shutdown of the localnode D it kills itself (in fact its parent) during shutdown and so shutdown never completes.  H >Why is it that the specified username is NOT used for the local node ? G >Is there some magical logical that can be set to change this behaviour E >so that the specified username is used on all specified nodes for DO  >commands ?   ? Don't think it is a logical, I think it is a long standing bug. H And I doubt it will ever be fixed (but am hopefully wrong in this case).  K I hate this since many years, because I can't SYSMAN SHUTDOWN NODE/POWEROFF G my Alpha from my VAX (because the code is not in the SYSMAN of the VAX) J and I can't shutdown the Alpha with SYSMAN (because it is the local node).H Batchjobs (and @SYS$SYSTEM:SHUTDOWN) is the way to go. Is SYSMAN a help? Not in this case...    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sat, 28 Oct 2006 20:24:32 +0800 3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> 6 Subject: TCP/IP Services EAK for IPsec or Multinet 5.21 Message-ID: <ehvhum$gme$1@news-02.connect.com.au>    Hi  H Does anyone know the state of play with the Early Adopters Kit (EAK) forL IPsec with TCP/IP Services? My understanding is that TCP/IP Development wereI floundering to such an extent that they couldn't deliver for VMS 8.3, but L that they'll all come up from the beach again soon and we won't have to wait) for 8.next to get IPsec. Is that correct?   H The HP road maps I see say early next year; is that still the case? WillJ that version have "Automatic Key Exchange"? or will it rely on Static KeysK or Pre-Shared Secrets? The client base is gagging for this! You missed 8.3; 3 you are woefully late! What the fuck are you doing?   I Does it work with Windows? Can I secure the Transaction Internet Protocol   pipe between MSDTC and hotTIP???  K What about multinet? Last I heard, Richard Whalen from Process Software was K working on a 5.2 release that was aiming at Automatic Key Exchange. I think K I saw some sort of webinar announcment about 5.2, is that correct? Is there J an ETA? (For those who don't know, Multinet already supports IPsec on VMS! But only will Static Keys)   Regards Richard Maher    ------------------------------  % Date: Sat, 28 Oct 2006 16:35:54 +0200 / From: Paul Sture <paul.sture.nospam@hispeed.ch> : Subject: Re: TCP/IP Services EAK for IPsec or Multinet 5.2J Message-ID: <paul.sture.nospam-0950DA.16355428102006@mac.sture.homeip.net>  1 In article <ehvhum$gme$1@news-02.connect.com.au>, 5  "Richard Maher" <maher_rj@hotspamnotmail.com> wrote:    > Hi > J > Does anyone know the state of play with the Early Adopters Kit (EAK) forN > IPsec with TCP/IP Services? My understanding is that TCP/IP Development wereK > floundering to such an extent that they couldn't deliver for VMS 8.3, but N > that they'll all come up from the beach again soon and we won't have to wait+ > for 8.next to get IPsec. Is that correct?    Hi Richard,   @ You may be interested in this announcement, posted yesterday on  vmsnet.networks.tcp-ip.multinet    From: Lauren Maschio* Subject: MultiNet V5.2 beta testers wanted  H > We are looking for MultiNet beta testers. MultiNet v5.2 beta test will> > run from November 17 to January 5. The new features include: >  > - BIND9 server. > - IPSEC (with layer 3 VPN tunneling and IKE) > - SSH upgrade  > - NTP v4.2 > - IPv6 support# > - Kernel performance improvements  > ; > If you are interested in participating, please sign-up at * > http://www.process.com/tcpip/mnbeta.asp. >  > Thanks > Lauren > 1 > -----------------------------------------------  > Lauren Maschio > Director of Marketing  > Process Software2 > ------------------------------------------------   --  
 Paul Sture   ------------------------------    Date: 28 Oct 2006 10:12:50 +02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)# Subject: Re: VMS installation crash , Message-ID: <45432d22$1@news.langstoeger.at>  h In article <7629b$45429dac$cef8887a$21439@TEKSAVVY.COM>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:F >For what it is worth, my DS10L from the wonderful people at IslandCo I >came with SRM version 7.2-1 dated June 9 2006 if I remember well. And I  C >have not have a problem with crashing VMS during install or while  # >running with both 8.2 and now 8.3.  > F >But I did not install VMS from CD, I installed it via an MSCP served  >disk on another node. > J >I'd have to crash the node again to get the PAL code version though, and : >in doing so would lose this message before it is sent :-(   Why?  . $ WRITE SYS$OUTPUT F$GETSYI("CONSOLE_VERSION") V7.1-1. $ WRITE SYS$OUTPUT F$GETSYI("PALCODE_VERSION") 1.98-83   0 As you can see, my DS10 is one version behind...  F But then again, the firmware of this newer systems now finally catched  up the version number of my PWS:  . $ WRITE SYS$OUTPUT F$GETSYI("CONSOLE_VERSION") V7.2-1. $ WRITE SYS$OUTPUT F$GETSYI("PALCODE_VERSION") 1.20  * (which is at V7.2-1 for many years now ;-)   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 28 Oct 2006 09:56:10 -0700  From: "Mike" <mlpoole@gmail.com># Subject: Re: VMS installation crash B Message-ID: <1162054569.999336.184860@m7g2000cwm.googlegroups.com>  G I got 7-3_2 up and running beautifully and was ready to move it to it's G new home on my desk plugged into my router so I could access it through  telnet/Reflection.  G I had forgotten that I didn't put a boot command in the NVRAM and I had G to make the world's longest serial cable to plug in to tell it to boot.   G I tried creating an NVRAM script with boot dqa0 -flags 0,0  and now the / thing just initializes over and over in a loop.   F I understand I can use the halt button to break the loop and erase the+ NVRAM script but I am just not having luck.   F Forgive my PC-entric question, but is there a jumper/battery/switch on' the motherboard that would clear NVRAM?    Mike          Peter 'EPLAN' LANGSTOEGER wrote:j > In article <7629b$45429dac$cef8887a$21439@TEKSAVVY.COM>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:G > >For what it is worth, my DS10L from the wonderful people at IslandCo J > >came with SRM version 7.2-1 dated June 9 2006 if I remember well. And ID > >have not have a problem with crashing VMS during install or while% > >running with both 8.2 and now 8.3.  > > G > >But I did not install VMS from CD, I installed it via an MSCP served  > >disk on another node. > > K > >I'd have to crash the node again to get the PAL code version though, and < > >in doing so would lose this message before it is sent :-( >  > Why? > 0 > $ WRITE SYS$OUTPUT F$GETSYI("CONSOLE_VERSION") > V7.1-10 > $ WRITE SYS$OUTPUT F$GETSYI("PALCODE_VERSION")	 > 1.98-83  > 2 > As you can see, my DS10 is one version behind... > H > But then again, the firmware of this newer systems now finally catched" > up the version number of my PWS: > 0 > $ WRITE SYS$OUTPUT F$GETSYI("CONSOLE_VERSION") > V7.2-10 > $ WRITE SYS$OUTPUT F$GETSYI("PALCODE_VERSION") > 1.20 > , > (which is at V7.2-1 for many years now ;-) >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   End of INFO-VAX 2006.593 ************************