1 INFO-VAX	Sat, 22 Jul 2000	Volume 2000 : Issue 407       Contents:? Re: %SYSINIT-E, Error mounting system device, status = 000008c4 ? Re: %SYSINIT-E, Error mounting system device, status = 000008c4 L DO NOT OPEN ANY ATTACHMENT CALLED LIFE_STAGES or JOKE or FUNNY IT	HASA VIRUS4 Re: I need a precise definition of "layered product"" Re: Undocumented commands in UCX ?" Re: Undocumented commands in UCX ?" Re: Undocumented commands in UCX ? Re: Using CMS and NFS + Will Installing C++ Screw Up my C Compiler? / Re: Will Installing C++ Screw Up my C Compiler?  Re: Yahmail installation  F ----------------------------------------------------------------------  % Date: Sat, 22 Jul 2000 10:30:30 -0500 / From: "Dwight Brooks" <dbrooks@prosoftauto.com> H Subject: Re: %SYSINIT-E, Error mounting system device, status = 000008c4: Message-ID: <8lcepr$33g8$1@newssvr03-int.news.prodigy.com>   Richard,< My customer is using /IMAGE but I didn't ask about /NOALIAS. Hwo would that affect it? = On my VAXes, I'm running VMS 6.2 and I cannot mount the disk. , I get illegal volume structure or something.G However, if I take the disk to an Alpha running VMS 7.2, I can mount it  and read it.< Someone else mentioned the ODS structure but my question is:@ The ODS is based on the O/S, why can this disk boot on a 4000-90 and not a 4000-105?  -Dwight     = "Richard B. Gilbert" <DRAGON@compuserve.com> wrote in message 1 news:200007212211_MC2-AD22-4CFB@compuserve.com... D         000008c4 translates as SYSTEM-F-FILESTRUCT, unsupported file structure level.  D         Is your customer using /IMAGE and /NOALIAS to do his backup?  H         What happens when you boot from your own system disk and issue a1 mount command for his; e.g.  MOUNT /OVER=ID DIA3:   F         Once upon a time, the only possibilities for "structure level" were ODS-1 and ODS-2. D I don't think that a VMS system disk can be an ODS-1 disk; that's anJ antique format, supported for compatability with PDP11 systems.  I believe' that ODS-5 is supported only on Alphas.   K         You may have to mount the disk /FOREIGN and use the DUMP command to  examine G the disk.   Each file header in INDEXF.SYS contains, in its seventh and K eighth bytes, the field called FH2BW_STRUCLEV.  The high order byte of this C word contains the structure level.  The low order byte contains the ) Files-11 version used to create the file.   H         Get a copy of "VMS File System Internals" by Kirby McCoy, put on* your Deerstalker hat, and start detecting.  ' Message text written by "Dwight Brooks" : > have a customer running VMS 7.2 on a VAXstation 4000-90.H He is trying to make (copy of) a bootable disk to send me to look at his system. G He is using Standalone backup to copy the disk and it boots fine on his  system. 1 The disk is a StorageWorks "brick" RZ29L (4.3Gb).   J I have a VAX 4000-105A with an HSD10A controller in a StorageWorks shelve.< When I try to boot the disk, I get to the normal VMS banner. Then get DECnet loaded....$ Then I get the aforementioned error.  D I can run SYSBOOT, etc but don't seen anything obvious in the SYSGEN parameters. F I also have a VAX 4000-200 with an HSD10A controller in a StorageWorks shelve! and it does the exact same thing.   J Can anyone out there tell me what we're doing wrong or how to resolve it?<   ------------------------------  % Date: Sat, 22 Jul 2000 13:29:10 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> H Subject: Re: %SYSINIT-E, Error mounting system device, status = 000008c4* Message-ID: <3979D9E3.E9CC1A@videotron.ca>   Dwight Brooks wrote:? > On my VAXes, I'm running VMS 6.2 and I cannot mount the disk. . > I get illegal volume structure or something.I > However, if I take the disk to an Alpha running VMS 7.2, I can mount it  > and read it.  K My initial reaction is that your drive is ODS-5 structure which can only be ! understood by VMS 7.2 and above.    G Can VMS boot from ODS-5 disks, are are these only for secondary disks ?   L Since the drive is the boot drive, it woudl be logical to state (but perhapsI not absolutely sure) that if the drive is in ODS-5 format, that the OS it L contains would be 7.2, and as such, when you boot from that drive, 7.2 wouldL be used and would have no problems with ODS-5, unless VMS 7.2 still requires ODS-2 as boot disk ?   ------------------------------  % Date: Sat, 22 Jul 2000 07:08:29 -0400 1 From: "Hughes, Rick" <Rick.Hughes@dsbn.edu.on.ca> U Subject: DO NOT OPEN ANY ATTACHMENT CALLED LIFE_STAGES or JOKE or FUNNY IT	HASA VIRUS K Message-ID: <10B1EC896FE8D2119D0400062B0011B5D2BADA@dsbnem1.dsbn.edu.on.ca>   F There is a new message going around that may be from myself, or BonnieL McCarthur or just about anyone else that may have opened it. This is a nasty3 one to I highly recommend that you do not open it.    H My computer at home received it through MIRC. Once your machine has beenL infected it will use your address book to send it out to everyone. I did notF open it as it looked suspicious but I did not know that my machine had already been infected.  2 This is a nasty one so DO NOT OPEN THE ATTACHMENT.  L If you did shut down your computer until you get a virus scanning program onH you computer. It will make every effort to clean up the virus, however IF have found that a few programs have been corrupted or deleted. It evenI places a copy of a .TXT.SHS file in the directory that you would normally ' keep your Word Processing documents in.   I Remember, IF YOU DID NOT OPEN THE ATTACHMENT YOU WILL NOT HAVE A PROBLEM.    ------------------------------   Date: 22 Jul 2000 07:13:48 CDT= From: wayne@tachysoft.xxx.293778.killspam.0223 (Wayne Sewell) = Subject: Re: I need a precise definition of "layered product" . Message-ID: <n6UIwgB0LNBn@tachxxsoftxxconsult>  [ In article <3978BEA4.23820B6@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:  > Wayne Sewell wrote: O >> An actual case of an embedded TeX implementation is the former VAX Document, P >> now known as DEC Document and owned by Touch Technologies.  There's no way toO >> tell from the radically different source language (SDML) and user interface, M >> but those in the know have disclosed that a modified TeX lives deep in the  >> product.  > O > TEX files are generated in intermediate steps of VAX DOCUMENT processing, and O > it has the ability to read TEX files as imput, and keep generated (temporary)  > TEX files.  M Oh, yeah.  Forgot about those, since I never save them.  That's a pretty good 1 indicator of the presence of TeX, all right.  :-)    --  O =============================================================================== M Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxx : http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-) O =============================================================================== O Otter, on dining with Bluto:"It's perfectly safe if you keep your arms and legs  			away from his mouth."   ------------------------------  % Date: Sat, 22 Jul 2000 13:19:37 +0200 5 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl> + Subject: Re: Undocumented commands in UCX ? - Message-ID: <39798349.B2A14837@whitehouse.nl>    Marc Van Dyck wrote: >  > Hello, > N > I have been looking in the code of UCX$CONFIG.COM lately, anf found a coupleN > of commands (generate, check, ...) that are not documented. Does anyone haveM > some sort of documentation about those commands ? Specially, I'm interested L > about the /COMMON qualifier for the commands SET CONFIG ENABLE [NO]SERVICE9 > and SHOW CONFIG ENABLE SERVICE. What does it do, etc...   E The /common qualifier specifies that this service is to be enabled on 	 all nodes  in the cluster when UCX starts.    L > While I'm at it, does any one know why the UCX commands have such an awfulJ > and inconsistent syntax ? I was hoping to have all that straightened outJ > with V5 but, much to my disappointment, nothing there has changed a lot.  B I guess the reason that this did not change with V5 is to maintainE backwards compatibility. I would assume more people would complain if 0 the management interface had completely changed.   Regards,   Oswald   ------------------------------  % Date: Sat, 22 Jul 2000 13:22:14 +0200 5 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl> + Subject: Re: Undocumented commands in UCX ? - Message-ID: <397983E6.7A457230@whitehouse.nl>    "Richard B. Gilbert" wrote:   M >         TCPIP services V5.0 is a port of the Digital Unix code.  I've heard I > both that the whole thing is DU and that "major parts" are DU.  I think M > that the "major parts" is closer to the truth; the user interface obviously < > makes a few concessions to VMS and compatibility with UCX>  ? The V5 kernel is exactly the same as the one running on DU. The 8 management interface has not much to do with the kernel.  E There is however also a 'new' management interface (ifconfig, netstat  and friends).   L >         Anyway, what did you expect from a background like that?  Consider6 > yourself lucky if it works at all!!!!  (5.0 didn't!)  " Come on, this is uncalled for IMO.   Oswald   ------------------------------  % Date: Sat, 22 Jul 2000 08:35:05 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>+ Subject: Re: Undocumented commands in UCX ? 7 Message-ID: <200007220835_MC2-AD26-8C84@compuserve.com>   J         Why do you say this is uncalled for?   5.0 was seriously broken. =   =   H I have worked with UCX since release 2.8E (or was it 2.7E?).  Just aboutH every component of UCX had serious and seemingly intractable problems. =  J Remember when SMTP couldn't deliver mail?  When FTP's mput command couldn= 't send more than 32 files?  J         Even the DCL had problems.  The first time I installed UCX 4.x  a= ndI started it, it deleted about 50,000 blocks of log files in SYS$MANAGER. =   H Most of them were not UCX log files.  Several of the startup files did a3 PURGE *.LOG!  A virus couldn't have done it better!   G         UCX never approached the quality that we got from VMS itself or H most of the other layered products.  I attribute most of the problems to UCX's origins in Unix.  ' Message text written by Oswald Knoppers  > D >         Anyway, what did you expect from a background like that? =   Consider6 > yourself lucky if it works at all!!!!  (5.0 didn't!)  # Come on, this is uncalled for IMO.<    ------------------------------   Date: 17 Jul 2000 15:19:38 GMT/ From: warren.spencer@alcan.com (Warren Spencer)  Subject: Re: Using CMS and NFS9 Message-ID: <8F7471889warrenspenceralcanco@142.14.12.164>    Hi,   J I'm not sure we're in the same world here, but I've got a disk mounted on L three nodes (one locally, two via DFS), and can access the CMS libraries it % contains from any of the three nodes.    ws   --   Warren Spencer Systems Analyst  Alcan Aluminum Corporation  J << My employer does not necessarily agree with my opinions - neither do I  >>  & ______________________________________$ tpw@ngat.com (Tony Wright) wrote in 7 <04E02AB064E0D211B24E0008C79F6A0E8E95F8@mail.ngat.com>:   H >I have sucessfully mapped a disk from a 433Au onto a ds10. The point ofF >this was to enable us to develop using one CMS library sitting on theB >433. Unfortunately when sittingat the DS10 and typing CMS SET LIB1 >AUdisk:[wherethecmslibraryis] I get the messages  > > >%CMS-E-NOREF, error referencing audisk:[wherethecmslibraryis]E >-CMS-E-NOTCMSLIB, audisk:[wherethecmslibraryis] is not a CMS library A >-RMS-E-COD, invalid or unsupported type field in XAB at 001AE8E4 & >%CMS-W-UNDEFLIB, library is undefined > + >(AUDISK is a logical that point at dnfs5:)  > # >Is what I'm trying to do possible?  >    ------------------------------   Date: 19 Jul 2000 13:07:05 GMT/ From: warren.spencer@alcan.com (Warren Spencer) 4 Subject: Will Installing C++ Screw Up my C Compiler?9 Message-ID: <8F765EB57warrenspenceralcanco@142.14.12.164>   	 Hi Folks,   K I've got C version 5.3 installed on a 7.1 Alpha, and now I need to install  H C++.  It appears they share some header files (.h) and perhaps some run L time executables.  Am I going to screw up my C compiler by installing C++?  F As a precaution, I've located the 5.3 version of C++, figuring that a L "machted set" of compilers is less likely to be problematic.  Your comments  would be greatly appreciated.    ws   --   Warren Spencer Systems Analyst  Alcan Aluminum Corporation  J << My employer does not necessarily agree with my opinions - neither do I  >>   ------------------------------  % Date: Sat, 22 Jul 2000 16:52:00 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> 8 Subject: Re: Will Installing C++ Screw Up my C Compiler?) Message-ID: <3979B510.42715F02@gtech.com>    Warren Spencer wrote: L > I've got C version 5.3 installed on a 7.1 Alpha, and now I need to installI > C++.  It appears they share some header files (.h) and perhaps some run L > time executables.  Am I going to screw up my C compiler by installing C++?   No.   E (at least I have never had any problems with that and I have had both  on a lot of systems)   Arne   ------------------------------  % Date: Sat, 22 Jul 2000 17:52:07 +0200 . From: stoeri@iap.tuwien.ac.at (Herbert Stoeri)! Subject: Re: Yahmail installation = Message-ID: <stoeri-2207001752070001@eapmc3.iap.tuwien.ac.at>    I would check:  - 1) does an exec rule really apply to yahmail? C 2) looking at a logfile of the http-server at high log level (11?): =        what is the path after translation of the yahmail URL? 9 3) in which order are exec and protect rules in the file? + 4) does another protect rule apply as well? ) 5) what do other rules do (pass, map...)?   E I fought some time with this problem, albeit with a nonstandard setup I using a separate username for yahMAIL. The solution came from analysis of < logfiles, showing the order of application of various rules.  & Here is our protection file (2 lines): <realm> Valid User at IAP  *@*.*.*.*:443 *   > i.e anyone from anywhere using SSL with a password from sysuaf    	 Good luck    Herbert Stoeri    F In article <4.3.2.7.2.20000721190926.00aa9390@otter.bemidji.msus.edu>,4 David Miller <dmiller@cslab.bemidji.msus.edu> wrote:   > YahMAIL experts. >  >  > < > I'm stuck.  I've got the yahmail login prompt but then get > * >          File _protected_ against access > / > and don't know where to turn.  Configuration:  > $ >          OSU HTTP 3.2, VMS/VAX 7.1 > = > One basic question is what to put in level2.prot.  I put in  >  > <realm> yahMAIL  > @cswww.bemidji.msus.edu *  > @* * > 7 > but that's just a guess.  What else do I have to fix?  >  > Thanks, dave.  >  >  >  > >There are the basic steps:  > > O > >1. Download yahMAIL from http://wasd.vsm.com.au/wasd/  (notice vsm, not vms) : > >into www_root:[script_code]. It is named yahmail130.zip > > ! > >2. $ unzip "-V" yahmail130.zip  > >  > >3. $ cd yahmail > > ! > >4. $ @build_yahmail mime links < > >There are other options as well.  This is the one I used. > >  > >5. $ @install install osu > > F > >6. $ @www_root:[system]yahmail_startup www.  Also add this line to  > >systartup_vms.  > > F > >7. $ edt yahmail$config.  Add one line following the [private] line > >         *\*\* M > >which permits all users to access their mail.  Of course if DISMAIL, they   > >can't
 > >I suppose.  > > ; > >8. $ edt http_paths.conf (wherever it is).  Add one line < > >         protect /htbin/yahmail/~* www_system:level2.prot > >  > >9. $ wwwcp restart : > >to force HTTPD to recognize the http_paths.conf update. > >  > >10. To use it, A > >         http://cswww.bemidji.msus.edu/htbin/yahmail/~username $ > >and you should be a login dialog.  D +---------------------------------+--------------------------------+D | Herbert Stoeri                  | Phone: ++43(1)58801/13460      |D | Institut fuer Allgemeine Physik | Fax:   ++43(1)58801/13499      |D | Technische Universitaet Wien    | email: stoeri@iap.tuwien.ac.at |D | Wiedner Hauptstrasse 8-10       |                                |D | A-1040 Wien                     | http://www.iap.tuwien.ac.at/   |D | Austria                         |                                |D +---------------------------------+--------------------------------+   ------------------------------   End of INFO-VAX 2000.407 ************************