1 INFO-VAX	Tue, 28 Oct 2003	Volume 2003 : Issue 597       Contents:( Any good thin clients out there for VMS?, Re: Any good thin clients out there for VMS?* backing up VMS files to PC based CD writer. Re: backing up VMS files to PC based CD writer. Re: backing up VMS files to PC based CD writer. Re: backing up VMS files to PC based CD writer. Re: Daylight to Standard Time Change via Batch. Re: Daylight to Standard Time Change via Batch Degaussing SDLT1 tapes Re: Degaussing SDLT1 tapes Re: Degaussing SDLT1 tapes/ Re: DHCP serving more than one subnet (longish)  Re: DLT tape drive caution Re: EV79 CANCELED !!!!!!!!!  Re: EV79 CANCELED !!!!!!!!!  fiber channel... need help Re: FTP From a Program# Host adapter/scsi card for CRD-5500 ' Re: Host adapter/scsi card for CRD-5500   How are the sales of VMS going ?8 Re: LG14/Telnet print queue problem - no FF between jobs1 Re: LMF licence check has failed. Please help :-) 1 Re: LMF licence check has failed. Please help :-) 1 Re: LMF licence check has failed. Please help :-) 1 Re: LMF licence check has failed. Please help :-) 1 Re: LMF licence check has failed. Please help :-) 1 Re: LMF licence check has failed. Please help :-)  Re: Mozilla 1.5 for OpenVMS?2 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 500/ OpenVMS Rolling Roadmaps (23-Oct-2003) and DCPS 3 Re: OpenVMS Rolling Roadmaps (23-Oct-2003) and DCPS  Pathworks V4.1  - Need copy of:  Re: Patrol x Decnet Management Re: Product problem I Re: Question: Linking directories (not quite the same thing, but similar) I Re: Question: Linking directories (not quite the same thing, but similar) I Re: Question: Linking directories (not quite the same thing, but similar) I Re: Question: Linking directories (not quite the same thing, but similar) I Re: Question: Linking directories (not quite the same thing, but similar) $ Re: Question: Linking directories...$ Re: Question: Linking directories...$ Re: Question: Linking directories...; Re: swishesi -  no results (malformed header error message)  Re: VMS Text Files --> Unix  Re: VMS Text Files --> Unix  Re: VMS Text Files --> Unix  RE: VMS Text Files --> Unix  Re: VMS Text Files --> Unix " Who can help me about this trouble! Re: [TCPware V5.6-2] DST Change ?   F ----------------------------------------------------------------------    Date: 27 Oct 2003 11:50:46 -0800( From: bob@instantwhip.com (Bob Ceculski)1 Subject: Any good thin clients out there for VMS? = Message-ID: <d7791aa1.0310271150.66052cee@posting.google.com>   > needs to have besides the obvious vt220 emulation (powerterm?): internet exploder w/java,128bit support, pdf viewer and an; imap client on a flat panel for under $1000?  I have had no  luck ...   ------------------------------  # Date: Mon, 27 Oct 2003 22:00:51 GMT # From: hoff@hp.nospam (Hoff Hoffman) 5 Subject: Re: Any good thin clients out there for VMS? 2 Message-ID: <nAgnb.7860$2h3.4372@news.cpqcorp.net>  h In article <d7791aa1.0310271150.66052cee@posting.google.com>, bob@instantwhip.com (Bob Ceculski) writes:? :needs to have besides the obvious vt220 emulation (powerterm?) ; :internet exploder w/java,128bit support, pdf viewer and an < :imap client on a flat panel for under $1000?  I have had no	 :luck ...   G   Linux on a mid-speed IA-32 would be a potential option at this price. H   At least one of the business systems is in this price range, including<   a 15" LCD display and Microsoft Windows XP in the package.  D   For various of the corporate Thin Client products -- and I am not F   currently familiar with the pricing nor with the particular contentsD   of the particular  embedded operating system configurations -- see   the website:  3     http://h18004.www1.hp.com/products/thinclients/     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  + Date: Tue, 28 Oct 2003 01:10:46 +0000 (UTC)  From: YYYlmhYYY@cco.caltech.edu 3 Subject: backing up VMS files to PC based CD writer / Message-ID: <bnkfmm$6eb$1@inky.its.caltech.edu>   ?  We have a couple of old VAXStations running VMS 5.5.  Our 8mm  H Exabyte doesn't work after being 'repaired'.  Is it possible to back up J files by ftp'ing them (thru a Unix machine) to a PC and writing them on a  CD ?K  I have tried ftp'ing several files (text, .obj, .exe, and .sav). It looks  G like I can make two sets of files, one transferred in ASCII and one in  I binary, and then get back usable files (rather than trying to sort files  N by type).  However the .sav file would not work (either at default or minimum D 2048 block size) and neither did the .obj file.  [Files transferred J binarily come back with fixed 512 byte length records - this did not seem @ to affect the .exe file; text files sent in ASCII mode seem ok.]#  Is there a better way to do this ? 5  What other files may not be backed up successfully ?   J  [And along the same line, how can I attach a VAX system disk to a PC and J copy the data to the PC for simh ? I used a raw copy routine for the PC I N found on the web but got a file structure error when I tried to boot from the  subsequent disk file.]     thanks
 larry henling    ------------------------------  % Date: Mon, 27 Oct 2003 21:21:43 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>7 Subject: Re: backing up VMS files to PC based CD writer 0 Message-ID: <00A28058.C879374C.25@tachysoft.com>    >From: YYYlmhYYY@cco.caltech.edu >X-Newsgroups: comp.os.vms4 >Subject: backing up VMS files to PC based CD writer, >Date: Tue, 28 Oct 2003 01:10:46 +0000 (UTC) > @ > We have a couple of old VAXStations running VMS 5.5.  Our 8mm I >Exabyte doesn't work after being 'repaired'.  Is it possible to back up  K >files by ftp'ing them (thru a Unix machine) to a PC and writing them on a   >CD ? L > I have tried ftp'ing several files (text, .obj, .exe, and .sav). It looks H >like I can make two sets of files, one transferred in ASCII and one in J >binary, and then get back usable files (rather than trying to sort files O >by type).  However the .sav file would not work (either at default or minimum  E >2048 block size) and neither did the .obj file.  [Files transferred  K >binarily come back with fixed 512 byte length records - this did not seem  A >to affect the .exe file; text files sent in ASCII mode seem ok.] $ > Is there a better way to do this ?6 > What other files may not be backed up successfully ? >     K The problem is that ftp does not save vms file attributes (unless doing ftp N between vms systems), so they are lost by the time the file returns to the vmsL system.  Executables work because they normally have a blocksize of 512, but! savesets have a larger blocksize.   O One easy way around the problem is to zip the files you want to transfer, which N has the added benefit of making the transfer smaller.  If you use the info-zipM version of zip with parameters "-V9", the vms attributes are saved in the zip L file and are perfectly intact when the files are restored.  Zip files do notK care about blocksize, so as long as you ftp in binary mode they will always  work. O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== H Randolph Duke (in Trading Places): "Mother always said you were greedy."1    Mortimer Duke: "She meant it as a compliment!"    ------------------------------  # Date: Tue, 28 Oct 2003 02:05:08 GMT # From: hoff@hp.nospam (Hoff Hoffman) 7 Subject: Re: backing up VMS files to PC based CD writer 2 Message-ID: <o9knb.7884$Sw3.3331@news.cpqcorp.net>  Q In article <bnkfmm$6eb$1@inky.its.caltech.edu>, YYYlmhYYY@cco.caltech.edu writes: @ : We have a couple of old VAXStations running VMS 5.5.  Our 8mm  :...Is it possible to back up K :files by ftp'ing them (thru a Unix machine) to a PC and writing them on a   :CD ?   H   Sure, but you'll want to see the other discussions that were involving*   folks that have headed down this path...  L : I have tried ftp'ing several files (text, .obj, .exe, and .sav). It looks H :like I can make two sets of files, one transferred in ASCII and one in J :binary, and then get back usable files (rather than trying to sort files O :by type).  However the .sav file would not work (either at default or minimum  E :2048 block size) and neither did the .obj file.  [Files transferred  K :binarily come back with fixed 512 byte length records - this did not seem  A :to affect the .exe file; text files sent in ASCII mode seem ok.] $ : Is there a better way to do this ?6 : What other files may not be backed up successfully ?    J   Use zip with the options "-V" -- the quotes are important -- to generateH   a zip archive, then transfer and burn that archive.  (This or a BACKUPH   saveset for bulk file transfers, and particularly if you can unzip theI   files on an OpenVMS system.  The zip archive can be particularly robust H   and transportable when copying files around various operating systems,D   and the "-V" option preserves the OpenVMS file system attributes.)  J   Or hook the CD-R device to OpenVMS and use one of the available tools toL   burn native-format disks directly.  See the OpenVMS FAQ for some pointers,L   for the usual errors, for a pointer to a tool that can correctly reset theI   BACKUP saveset file attributes that are typically found after FTP, etc.   L   (FWIW, there are various CD-R tools that will likely be found on the next I   OpenVMS Freeware CD distribution.  There are others that are referenced K   in the FAQ, and that are available for direct download for use on OpenVMS    VAX or OpenVMS Alpha.)  J   If you want to use the PC to burn the disks, it is easiest to use the LDJ   tool (on the Freeware, and latent in OpenVMS V7.3-1 and later) to createL   a logical disk partition of the correct size (eg: up to 1,200,000 blocks),J   then MOUNT and load it, then DISMOUNT it and transfer the partition file2   over to the PC as a block-by-block ("raw") burn.  K : [And along the same line, how can I attach a VAX system disk to a PC and  # :copy the data to the PC for simh ?   E   You'd need to use a network, then the answer depends on how much of G   SIMH is running.  If you have enough to be running OpenVMS, you would D   probably not be asking the question, of course.  If you don't haveE   OpenVMS running, you are back to your root question involving files D   that end up corrupted when they are transfered through the PC, andG   this is normal and expected when disparate file systems are involved.   K :                                   I used a raw copy routine for the PC I  O :found on the web but got a file structure error when I tried to boot from the   :subsequent disk file.]     @   I'd not expect the disk to boot on OpenVMS unless the disk wasF   configured for it -- a raw copy of a system disk typically won't be.G   The usual approach is to build a bootable disk, then use BACKUP/IMAGE E   to transfer that.  If you are doing the system disk transfer via CD @   media, you will end up learning how the OpenVMS system disk isD   structured, as you'll need to configure it within the LD partition   for the CD media master.  D   I'd hope that one of the emulator websites has detailed directionsB   on what is involved in building a bootable disk.  If not, you'llF   have to see how OpenVMS VAX (in the case of SIMH) sets up the systemG   disk based on the system management documentation, and replicate this D   configuration into the LD partition and then perform the raw burn.  E   Having a direct-attached CD drive will be easier, though if you are B   limited to OpenVMS VAX it'll most likely have to be a SCSI CD-R D   device and these can be slightly more difficult to locate than theG   more widespread ATA devices.  With many of the OpenVMS Alpha systems, E   you can use ATA CD-R or SCSI devices, depending on the I/O adapters    present in the box.     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Tue, 28 Oct 2003 04:24:17 GMT - From: "John E. Malmberg" <wb8tyw@qsl.network> 7 Subject: Re: backing up VMS files to PC based CD writer > Message-ID: <Rbmnb.132871$qj6.9238717@news1.news.adelphia.net>   Hoff Hoffman wrote:  > L >   If you want to use the PC to burn the disks, it is easiest to use the LDL >   tool (on the Freeware, and latent in OpenVMS V7.3-1 and later) to createN >   a logical disk partition of the correct size (eg: up to 1,200,000 blocks),  I And after creating the container file, use the SET FILE/CACHING=NO_CACHE  H command so that what LD writes to the disk is the same as what a future  FTP or ZIP will see.  K This CACHE setting will probably be incorporated in a future version of LD.   L >   then MOUNT and load it, then DISMOUNT it and transfer the partition file4 >   over to the PC as a block-by-block ("raw") burn.   -John  wb8tyw@qsl.network Personal Opinion Only    ------------------------------   Date: 28 OCT 2003 04:13:17 GMT2 From: karcher@kort.waisman.wisc.edu (Carl Karcher)7 Subject: Re: Daylight to Standard Time Change via Batch 4 Message-ID: <28OCT03.04131759@kort.waisman.wisc.edu>  T In a previous article, Rick Millhollin <rickm.REMOVE-THIS-NOSPAM@uoregon.edu> wrote:A ->I'm running VMS 7.3-1 and MultiNet 4.4 on several clustered and D ->stand-alone systems.  In the past with 7.3 I've been able to run aG ->batch job that adjusts the time via a combination of MultiNet actions E ->and executing UTC$CONFIGURE_TDF.COM with no interactive input.  Now C ->with 7.3-1 that tells me to run UTC$TIME_SETUP.COM which has been E ->discussed here.  But it appears to require interaction.  Any way to ) ->change from a batch job now?  Thanks...    Hi Rick.  5 See sys$examples:daylight_savings.com for how to call  utc$time_setup.com.   B Consider setting sysgen parameter AUTO_DLIGHT_SAV=1 on your 7.3 or@ later systems (must be the same on all members of a cluster). ItB does work as advertised and you can forget about all your previousC procedures. This non-dynamic parameter can be set without rebooting ? your systems provided you restart the job controller. There's a : useful DSNlink article on the details of this - search for AUTO_DLIGHT_SAV to find it.    --G -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison 9 --                  karcher.nomoresapm@waisman.wisc.edu      ------------------------------  % Date: Mon, 27 Oct 2003 22:32:39 -0600 ( From: brandon@dalsemi.com (John Brandon)7 Subject: Re: Daylight to Standard Time Change via Batch 1 Message-ID: <03102722323988@dscis6-0.dalsemi.com>    Carl Karcher wroteD > Consider setting sysgen parameter AUTO_DLIGHT_SAV=1 on your 7.3 orB > later systems (must be the same on all members of a cluster). ItD > does work as advertised and you can forget about all your previous
 > procedures.   " Well I wish it was that easy Carl!  H In our application environment can not tolerate a snap backwards in timeN service. It has the potential to cause dupliate records in our RMS ISAM files.  N Too bad there is not an AUTO_DLIGHT_SAV=2 where this option skews the clock byE the combination of AUTO_DLIGHT_TIMEADJUST and AUTO_DLIGHT_TICKLENGTH.   O The other issue is NTP - which we shutdown prior to the start of the time skew.        J*o*h*n B*r*a*n*d*o*n  VMS Systems Administrator * firstname.lastname.spam.me.not@dalsemi.com   ------------------------------  % Date: Mon, 27 Oct 2003 23:11:15 -0000 ! From: Z  <zarlenga@conan.ids.net>  Subject: Degaussing SDLT1 tapes / Message-ID: <vpr9gjch16dsec@corp.supernews.com>   * Does HP sell a degausser for SDLT 1 tapes?  " If so, what's the part # and cost?   ------------------------------  # Date: Tue, 28 Oct 2003 00:07:11 GMT # From: hoff@hp.nospam (Hoff Hoffman) # Subject: Re: Degaussing SDLT1 tapes 2 Message-ID: <Pqinb.7874$iq3.1969@news.cpqcorp.net>  S In article <vpr9gjch16dsec@corp.supernews.com>, Z  <zarlenga@conan.ids.net> writes: + :Does HP sell a degausser for SDLT 1 tapes?  : # :If so, what's the part # and cost?   ?   AFAIK, no, HP does not offer tape media degaussing equipment.   +   For degaussing DLT IV media and based on:   <     http://www.hp.com/products1/storage/products/tapebackup/-       dlt_tapedrives/dlt8000_drives/faqs.html   E   You'll need a unit that can "overrun" media rated at 1850 Oersteds, B   and specifically a unit that can generate triple the media value#   per the information at above URL.   D   The SDLT media coercivity looks to be somewhere up to roughly 1900'   Oersteds, depending on the cartridge.   A   HP Ultrium media can be well above 2000 Oersteds; circa 2350...   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Mon, 27 Oct 2003 19:30:47 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> # Subject: Re: Degaussing SDLT1 tapes ' Message-ID: <3F9DC6C7.378D02B9@fsi.net>    Z wrote: > , > Does HP sell a degausser for SDLT 1 tapes? > $ > If so, what's the part # and cost?  G Many good commercial video cassette (Umatic, Betacam) bulk erasers will   do the job, but you can't hurry.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------   Date: 27 OCT 2003 16:31:52 GMT4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)8 Subject: Re: DHCP serving more than one subnet (longish)6 Message-ID: <27OCT03.16315215@thuria.waisman.wisc.edu>  0 In a previous article, "John E. Malmberg" wrote:  K ->It probably involves making the DHCP server think that all the addresses  C ->are in one larger subnet, but to give out to the fixed addresses  E ->different information than for the dynamic ones for the subnet and   ->network masks.  B This is exactly what we do here. We have four 24 bit discontinuousF networks on the same wire that all use dhcp. We have a dynamic pool onC two of the subnets configured in nets. The netmask for our VMS DHCP H server (one interface) is 255.255.0.0 so it covers all four subnets. OurD entry in netmasks is the entire 16 bit network - 192.168.0.0 in yourD case. For this to work, "proxy arp" would need to be enabled on yourD router (the network people probably won't like that). You also don't> want the router to forward (relay) dhcp or bootp in this case.  E However, if you make these changes you will need to completely reload . your dhcp configuration. By that I mean using:   	pipe dhcpdbdump > dhcp.dat   F to save all leases in a file, delete all DB*.HSH files, (DBJ.HSH holds: your preloaded mac addresses - leave that alone) then use:   	dhcpdbmod -w -i dhcp.dat   ; to repopulate the db files from the file you saved earlier.   ) You will also find Join documentation at:   ?  http://www.fisica.uniud.it/~cabras/assistenza/SW/join/TOC.html   F Michael, E-mail me privately if you'd like more configuration details.  E While this (more than one subnet on the same wire) works in our case, G it's not something I'd recommend. We're planning to eliminate it due to . undesirable side effects I won't mention here.   --G -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison 9 --                  karcher.nomoresapm@waisman.wisc.edu      ------------------------------  % Date: Mon, 27 Oct 2003 19:49:17 -0500 0 From: "Homer Simpson" <hsimpson@burnsenergy.com># Subject: Re: DLT tape drive caution : Message-ID: <R0jnb.18197$Lj6.10787@bignews3.bellsouth.net>  H Likewise, be sure your cleaning tapes are appropriate for your model.  AJ cleaning tape for a different model tape drive took out one of our drives.G Field Service was able to disassemble and remove the cleaning tape, but  threatened to bill next time.   C "Tom Simpson" <tom.simpson@osioutsourcing.bad.com> wrote in message # news:bnj793$efk$1@news.wplus.net... H > This weekend, we had an operator attempt to use super DLT tapes in our TZ89J > drives.  It's a one-way trip.  Once the tapes are inserted, they can not be@ > removed.  It took both of our tape drives out of commission... > K > If you happen to have a mix of tape drives, make sure this doesn't happen  to > you! > K > On a side note, I think it's a pretty lame design to allow the wrong tape  toH > be inserted into a drive and not be able to get them out again without# > disassembling the entire drive...  > 
 > Regards, > Tom  >  >    ------------------------------  % Date: Mon, 27 Oct 2003 15:16:05 -0500 * From: "Bill Todd" <billtodd@metrocast.net>$ Subject: Re: EV79 CANCELED !!!!!!!!!2 Message-ID: <L7idnX6CH9Ca4ACiRVn-hg@metrocast.net>  3 "jlsue" <jefflsxxxz@sbcglobal.net> wrote in message 2 news:rqbqpvknkt73vrn2ombqav5nfn8ggvn6r8@4ax.com...J > On Fri, 24 Oct 2003 21:32:12 -0400, JF Mezei <jfmezei.spamnot@istop.com> > wrote: >  > >Robert Deininger wrote:K > >> The Marvel systems went out the door with the best EV7 CPUs that could  be > >> produced at the time. > >  > > L > >Yet, a few months later, HP admits that the current EV7 can be boosted by 15% K > >because existing productions of EV7 has shown its speed can be increased D > >without changes. Either the engineers were totally incompetent in
 estimatingK > >the highest possible speed for their new EV7, or HP decided to lower the  clock rate.  > J > You have absolutely blinded yourself with this anti-HP rhetorical stance of > yours.  ? Some people are certainly blind here, but JF isn't one of them.   A   Are you saying that ever design that ever gets produced is 100% K > perfect at the time of initial introduction?  And that there is NEVER any ! > room for improvement afterward?   F Funny how this is the first word we've heard that EV7's speed could beI boosted *at all*, isn't it?  I mean, it was originally targeted for 1.2 - L 1.25 GHz, but released at only 1.15 GHz (with *no* explanation and certainlyI no indication that any speed boosts would be possible over time).  And HP I has been awfully quiet since then about EV7 performance, save when Itanic J couldn't cut the mustard against the competition and they had to benchmark/ EV7 (they *still* won't release TPC-C results).   K Now, in an attempt to defuse criticism for blatantly breaking *yet another* I Alpha 'commitment' (yes, Curly used that word in promising that the Alpha K 'plan of record' would be followed by HP - should have known right there to L expect the worst), HP suddenly discovers that EV7 *can* run faster.  What an% amazing, and convenient, coincidence!    >  > > I > >> After several passes of EV79 prototype chips, they did not _work_ at K > >> anything approaching the design speed.  They were absolutely not ready  to
 > >> ship. > > I > >And EV79 wasn't meant to ship until next year. Heck,. EV7 systems have  onlyK > >now beund to ship, you'd think they'd wait a while before unleashing its 
 successor. > > L > >Unless, of course, their goals are not to get the most profits from their > >alpha assets. > K > Or, alternatively, unless of course the delay factor would put it out far J > enough that the current plans for IA64 migration overshadow the need for > it.   K Unfortunately for Itanic, it really doesn't have anything very palatable on L the horizon for the foreseeable future (i.e., the clearly-defined portion ofI its roadmap which runs through 2005 and Montecito).  Tanglewood in 2006-7 L *may* be a winner, but if the Alpha team has really been concentrating on anH 8-core chip rather than a complete rework of the current Itanic core itsJ individual core performance may not be any faster than Montecito's (thoughI in large systems if they've incorporated EV7's on-chip support for memory K and routing Itanic may finally catch up to its competition in those areas - . 3+ years after EV7, and 5 years after POWERx).  C   And in a finite world, with finite resources, it may be better to  > invest elsewhere.   H Right:  never mind any 'commitments' you may have made - customers don't( place any value on integrity these days.   ...    > >>  Throwing tons J > >> of money at it wouldn't have fixed the schedule problem, at least not > >> enough to matter. > > J > >Why are they in such a hurry ? They just unleashed EV7. Customers would beJ > >more than happy to see Alpha's lifetime extended, especially since IA64 is so lackluster.  > L > Well, I suppose you just think that getting a chip to work is all it takesE > to making a successful system, available immediately upon the first + > successful silicon version of the design?   K Perhaps in your misplaced zeal to defend cHumPaq you've forgotten that EV79 D (just like EV7) *was* pretty much the system:  it could use the sameJ external components that EV7 has been using right along, and, indeed, once5 the chip was ready, the systems could start shipping.   L (To a significant degree, this was true of EV8 as well.  So much for much of9 the 'savings' that winding down its development created.)    >  > > J > >> EV79 was NOT a "process shrink", whatever that vague term might mean. > > L > >Well, how come the roadmap, "plan of record" and other propaganda attemps from1 > >Compaq/HP spoke of a process shrink for EV79 ?  > L > Did it ever occur to you that there may be more than one thing going on inH > the design phase, but that process shrink was just one of those goals?  K What seems to have occurred to JF is that either Robert didn't know what he K was talking about any more than you do or that his phrasing was poor.  EV79 K was indeed planned to move to a new process generation (130 nm. vs. 180 nm. L for EV7).  Until early this year, it was *also* planned to have nearly twiceH as much on-chip cache and to run significantly faster:  when HP scrappedK those plans, describing what was left as being merely a 'process shrink' is J appropriate (moving to SOI does raise issues, but if you don't try to takeJ advantage of the move, e.g., by raising the clock rate significantly, theyK are not unmanageable - assuming, that is, that HP still planned the move to E SOI at all after having destroyed all reason for it early this year).    > H > Heck, if it was only a process shrink, that's EXACTLY what the EV7z isL > going to give you.  So I guess you've got nothing to complain about then - > it's just a name after all.   L People with as little command of a subject as you have really should be moreK circumspect in their statements.  EV7z is *not* a shrink of any kind:  it's ? just EV7 running at the speed it could have run at right along.   H By all appearances, EV79 could have been introduced at 1.6 - 1.7 GHz andF come close to 2 GHz during its lifetime (at least that's Paul DeMone'sK opinion, over at realworldtech.com).  Since it would also have had close to I twice the on-chip cache that EV7 has (though that goal was scrapped early F this year), it would have embarrassed next-year's MadisonII and likelyL Montecito in 2005 as well (as a dual-core chip Montecito will likely have toE throttle back its clock rate to not much more than Madison's to avoid K power/cooling issues - unless it disables one of the two cores on the chip; A the problems that Intel is currently having with 'Prescott' power F consumption in its new 90 nm. process only increase that probability).  F And since little old EV79 turns out to have been enough of a threat toI Itanic to cause HP to squash it, the case that EV8 would have left Itanic E *completely* in the dust gains yet another staunch pillar of support. F Fortunately, POWER5 and, on the low end (though by next year it may beJ creeping up), Opteron seem poised to do the job that EV79 (though not EV8) would have.    - bill   ------------------------------  # Date: Tue, 28 Oct 2003 01:10:54 GMT # From: "John Smith" <a@nonymous.com> $ Subject: Re: EV79 CANCELED !!!!!!!!!H Message-ID: <ymjnb.96967$h61.79847@news01.bloor.is.net.cable.rogers.com>   jlsue wrote:. > On Fri, 24 Oct 2003 21:32:12 -0400, JF Mezei$ > <jfmezei.spamnot@istop.com> wrote: >  >> Robert Deininger wrote:D >>> The Marvel systems went out the door with the best EV7 CPUs that" >>> could be produced at the time. >> >>A >> Yet, a few months later, HP admits that the current EV7 can be  >> boosted by 15% A >> because existing productions of EV7 has shown its speed can be  >> increasedD >> without changes. Either the engineers were totally incompetent in
 >> estimating G >> the highest possible speed for their new EV7, or HP decided to lower  >> the clock rate. > C > You have absolutely blinded yourself with this anti-HP rhetorical B > stance of yours.  Are you saying that ever design that ever getsD > produced is 100% perfect at the time of initial introduction?  And9 > that there is NEVER any room for improvement afterward?  >  >>H >>> After several passes of EV79 prototype chips, they did not _work_ atD >>> anything approaching the design speed.  They were absolutely not >>> ready to ship. >>D >> And EV79 wasn't meant to ship until next year. Heck,. EV7 systems >> have onlyG >> now beund to ship, you'd think they'd wait a while before unleashing  >> its successor.  >>F >> Unless, of course, their goals are not to get the most profits from >> their >> alpha assets. > G > Or, alternatively, unless of course the delay factor would put it out E > far enough that the current plans for IA64 migration overshadow the G > need for it.  And in a finite world, with finite resources, it may be  > better to invest elsewhere.  >  >>> >>> post-2004.  The problems were largely out of HP's control. >>E >> Sorry, I don't buy that. Compaq/HP should have known exaxctly what  >> is involved? >> in a process shrink expecially with their supposedly so cosy  >> relationship withG >> Intel. So when they commotted to EV79, they would have known what to 
 >> expect. > = > Of course you don't buy it.  You've reached the pinnacle in A > perfection and can attest to the business success and technical @ > architecture capabilities of something you've never even seen. >  >>>  Throwing tonsE >>> of money at it wouldn't have fixed the schedule problem, at least  >>> not enough to matter.  >>D >> Why are they in such a hurry ? They just unleashed EV7. Customers >> would be E >> more than happy to see Alpha's lifetime extended, especially since  >> IA64 is so lackluster.  > F > Well, I suppose you just think that getting a chip to work is all itE > takes to making a successful system, available immediately upon the 1 > first successful silicon version of the design?  >  >>C >>> EV79 was NOT a "process shrink", whatever that vague term might 	 >>> mean.  >>D >> Well, how come the roadmap, "plan of record" and other propaganda >> attemps from 1 >> Compaq/HP spoke of a process shrink for EV79 ?  > F > Did it ever occur to you that there may be more than one thing goingG > on in the design phase, but that process shrink was just one of those  > goals? > H > Heck, if it was only a process shrink, that's EXACTLY what the EV7z isE > going to give you.  So I guess you've got nothing to complain about $ > then - it's just a name after all.    " As seen on NP's web site today....  B http://www.hp.com/products1/evolution/alpha_retaintrust/index.html  E and I will quote in its entirety so there will be at least one public H archive copy of this (no revisionist history from Mrs. Ceaucescu of HP).  F "The HP Alpha RetainTrust (ART) program underscores HP's commitment toF providing long-term business continuity for AlphaServer customers. TheE program eases the evolution of moving from the Alpha platform to HP's K Integrity systems by ensuring we carry forward the trust you have placed insK us. ART is focused on showing you the business value of moving forward withVG HP as a company, and mitigating the risk associated with transitions toB
 Integrity.# Key components of this program are:t  C   a.. Comprehensive customer initiatives - keeping you informed andSK knowledgeable about our current and future plans with programs designed fori( executive, business and technical staffsF   b.. Excellent products - continued on-schedule delivery of committedK roadmaps***, and ensuring both Alpha and Itanium-based destination productsr are incredibly robust F   c.. Excellent products - continued on-schedule delivery of committedF roadmaps, and ensuring both Alpha and Integrity systems are incredibly robustJ   d.. Strong partner support - working proactively with our ISVs to ensure> continued support for your applications on Alpha and IntegrityI   e.. Extensive service offerings- enabling joint transition planning, ataJ your own pace, to minimize disruption and cost while adding business value through evolution D   f.. Compelling business practices - offering a suite of investmentF protection choices including aggressive trade-in, leasing, and upgrade. programs for both server and storage products" *** emphasis added    A If anyone wants to e-mail carly(tm) with their thoughts about the 1 cancellation of EV79, and other Alpha issues, try : http://www.hp.com/hpinfo/execteam/email/fiorina/index.html   ------------------------------    Date: 27 Oct 2003 21:03:54 -0800! From: eystein17@yahoo.com (mayen)a# Subject: fiber channel... need helpM= Message-ID: <4db787ce.0310272103.37973598@posting.google.com>e   hello everyone..    7 does the S_ID and D_ID refers to SCSI ID of the device?      thanks mayen    ------------------------------  % Date: Mon, 27 Oct 2003 13:41:56 -0600 ( From: brandon@dalsemi.com (John Brandon) Subject: Re: FTP From a Program 1 Message-ID: <03102713415602@dscis6-0.dalsemi.com>i   Barry Treahy wrote> > Yes, but you did not identify which stack you are running...  A Well not sure what Mike Freeman is running - is there a way to do  do using TCPIP V5.0 /V5.1 ?u     J*o*h*n B*r*a*n*d*o*n. VMS Systems Administratori* firstname.lastname.spam.me.not@dalsemi.com   ------------------------------  % Date: Mon, 27 Oct 2003 22:44:15 -0500F, From: "Dave Pampreen" <dave@davesdotcom.com>, Subject: Host adapter/scsi card for CRD-55000 Message-ID: <F92dnRP1969zewCiRVn-vA@comcast.com>  E I have a dual controller CRD-5500 and an Alpha (listed as 21164 PC164-0 443Mhz)  I believe it's been called an Alpha PC.  K Does anyone have any experience with a CRD-5500 and connecting to an Alpha?o) I've tried to plug it in with no success.-  < I also have an Alphastation 250 and tried there too as well.   Any advice will help.u  A The CRD-5500 has 2 controllers, and I have 2 BA-356 with 1 RAID-5r% configured.  I expect 1 disk to show.f   Dave   ------------------------------  % Date: Mon, 27 Oct 2003 23:30:33 -0600-( From: Rich Jordan <duodec@speakeasy.net>0 Subject: Re: Host adapter/scsi card for CRD-55002 Message-ID: <oMKdnRKRjttucgCiXTWc-g@speakeasy.net>  F No experience but I had some notes from a long ago test that a friend H did with a CRD-5000.  First, what SCSI controllers are you using on the D PC164 and/or AS250?  The AS250 had an embedded FNSE controller if I F remember correctly.  The PC164 I have no direct experience with.  Are C you using a PCI card SCSI controller, or the embedded in the AS250?   F The CRD units had to have at least one controller configured for host E I/O and one or more for drive connection.  You could trade off drive  F slots for more host slots.  Some of them were particular about slots; G host cards had to be in certain slots, and might have had to be in one  E particular slot if there was only one host I/O connection.  Also the rF controllers were available in different types, including high voltage F differential, Ultra wide, Ultra narrow, and others.  Are you matching 9 the host I/O controller with the Alpha SCSI adapter type?-  G Thats all I have.  I know my friend had a CRD-5000 working for a while pI back in 1999, I think on an AS800 system with a KZPSA FWD controller and -0 OpenVMS V7.2, but all thats left is a few notes.   Rich   Dave Pampreen wrote:G > I have a dual controller CRD-5500 and an Alpha (listed as 21164 PC164 2 > 443Mhz)  I believe it's been called an Alpha PC. > M > Does anyone have any experience with a CRD-5500 and connecting to an Alpha?s+ > I've tried to plug it in with no success.X > > > I also have an Alphastation 250 and tried there too as well. >  > Any advice will help.e > C > The CRD-5500 has 2 controllers, and I have 2 BA-356 with 1 RAID-5t' > configured.  I expect 1 disk to show.n >  > Dave >  >    ------------------------------    Date: 27 Oct 2003 22:51:25 -0800. From: mistdragon@zdnetonebox.com (mist dragon)) Subject: How are the sales of VMS going ?a= Message-ID: <7500353b.0310272251.454ee0ea@posting.google.com>d  C I have seen a lot of activity lately from vendor to deny that thered? are problems of any kind on moving to Itanium. Even the regulariE posters like Bill and JF have got their part of flame and are claimedlC to spread FUD when they dislike the late news like cancelling EV79.   > Officially everything looks fine from vendor and proceeding asD planned. Alpha is EOL, last small tuning next year, iVMS is running,C albait beta and slowly. Vendor is giving very clear message that noeE matter the arguments, this is the way it is gonna be - take it or cryt and take it.  F However, it seems that questions and opinions here carry larger weightF than vendor would like to and they want to shut them down at any cost.? Some of the answers from vendor seem to reflect desperately thee- 'truths' they have got from their management..   I smell fear here. o  = But fear for what ? If OpenVms is a hen laying golden eggs assC represented in sales figures, then why would anyone kill it and not8D promote it ? Otoh, if the sales figures are not what they seem, then? there is really an actual fear in vendor of the future of iVMS,  Itanium etc.  # So how are the sales of VMS going ?t   ------------------------------  % Date: Mon, 27 Oct 2003 14:27:58 -0500 8 From: "Tom Simpson" <tom.simpson@osioutsourcing.bad.com>A Subject: Re: LG14/Telnet print queue problem - no FF between jobse* Message-ID: <bnjrmn$1991$1@news.wplus.net>  $ I hate answering my own posts but...  K I resolved the problem this morning by deassigning the old UCX logical nameaA UCX$TELNETSYM_SUPPRESS_FORMFEEDS that was still hanging around...   @ Apparently, the old logical name gets checked as well as the newJ TCPIP$TELNETSYM_SUPPRESS_FORMFEEDS logical (which was already deassigned).  0 We are using only the TCPIP$TELNETSYM processor.   Regards, Tomo  C "Tom Simpson" <thomas.simpson1@nospam.comcast.net> wrote in messaget' news:Gswmb.25278$e01.49356@attbi_s02... * > SW Versions: VMS 7.3-1, TCPIP V5.3 eco 2 > System: ES40 > Printer: LG14lF > Network interface: RapidPrint 500, using port 3001 (also tried 9100) >a > Configuration DetailsaL > The LG14 printer is using the factory defaults, i.e. DEC character set, no > special form feed settings. 5 > The TCPIP suppress formfeed logical is not defined.a >r	 > ProblemsL > I can't seem to get a form feed between print jobs.  This queue is workingG > fine as a LAT print queue.  Our systems are moving and the printer iseH > staying, so I need to use Telnet queues so the printer can continue toJ > function over a WAN link.  All of my other queues (to HP laser printers) use=L > Telnet, so I'd like to use Telnet for this printer too (LPD service is not0 > enabled).  Bridging the WANs is not an option. >o > Attempted Solutions F > I have tried specifying a reset module in the device control libraryL > (/separate=(reset=reset)) that contains a form feed character, but it doesL > not help.  The printer has no problem executing a form feed if it's in theF > print job.  Also tried a module containing a <ESC> E and one with an <ESC>cK > (HP support suggestions).  (the above init command syntax is from memory,  so > may not be exactly correct)$ >.L > Anyone run into this before or has a similar configuration that is working; > or have any suggestions on how to get this thing to work?S >i	 > Thanks,  > Tom. >u >m   ------------------------------  # Date: Mon, 27 Oct 2003 19:12:54 GMTa# From: hoff@hp.nospam (Hoff Hoffman) : Subject: Re: LMF licence check has failed. Please help :-)2 Message-ID: <W6enb.7842$8V2.3974@news.cpqcorp.net>  b In article <d627f19f.0310260112.15ea73ec@posting.google.com>, cocacolaeisbaer@gmx.at (joe) writes:E :I am a beginner in OpenVMS and have installed the hobbyist kit on anbD :old but good alpha250. I installed it exactly as it is described inC :the OpenVMS Hobbyist Guide - The Alpha Kit (.pdf) from openvms.orglE :page. After installation the system reboots and I get to a graphicalsC :login where I try to login with my system account but I always getsA :back following error massage box "LMF licence check has failed".n0 :Have I done anything wrong at the installation?) :Or what can I do to get into the system?a5 :I really don't know and I hope anybody can help me. "  H   The OpenVMS Frequently Asked Questions (FAQ) will be of interest here,G   as it describes which two sets of licenses you need of the three setsnG   that are available, and it describes how to register product licensesmB   in this particular situation, given that you cannot log into the   DECwindows display.n  %     http://www.hp.com/go/openvms/faq/-  G   You will want to communcate your confusion to whomever is maintainingDI   the guide you read, as this is (unfortunately) a fairly common mistake,oG   and one that should be covered in the specified document.  (QuestionssH   also occasionally arise here, too, hence the inclusion into the FAQ --I   and the Google newsgroup search should be able to find various of theseI   previous discussions, too.)   H   The sections of the OpenVMS FAQ that are of central interest here are:  2     Questions asked by Hobbyist OpenVMS licensees?#     Resolving License PAK Problems?n7     I've forgotten the SYSTEM password - what can I do?f  I   I'd encourage you to download and search the text-format version of thelG   FAQ, as that version is likely the easiest to download and to search.     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqhN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comm   ------------------------------    Date: 27 Oct 2003 14:03:19 -0800" From: cocacolaeisbaer@gmx.at (joe): Subject: Re: LMF licence check has failed. Please help :-)= Message-ID: <d627f19f.0310271403.46123bbe@posting.google.com>n   Thank you for answering Dirk:-)o  D But I have got the license from montagar and the registration of theA license took place without having error messages at installation.aF After that I enabled the Produkt Authorization Key during installationD process with VMS License Management Utility to load it (I think this was option 10 in the menu).r  * Do you have any idea what I've done wrong?   Greetings - Joex    X Dirk Munk <munk@home.nl> wrote in message news:<bngfs1$c7q$1@news4.tilbu1.nb.home.nl>...( > Did you get and load the licenses from > . > http://www.montagar.com/htbin/ohp_hobreg  ?? > # > It seems to me you did not ......r >  >  >  > joe wrote:H > > I am a beginner in OpenVMS and have installed the hobbyist kit on anG > > old but good alpha250. I installed it exactly as it is described iniF > > the OpenVMS Hobbyist Guide - The Alpha Kit (.pdf) from openvms.orgH > > page. After installation the system reboots and I get to a graphicalF > > login where I try to login with my system account but I always getD > > back following error massage box "LMF licence check has failed".3 > > Have I done anything wrong at the installation?e, > > Or what can I do to get into the system?8 > > I really don't know and I hope anybody can help me. 
 > > mfg - joe    ------------------------------    Date: 27 Oct 2003 15:05:14 -0800" From: cocacolaeisbaer@gmx.at (joe): Subject: Re: LMF licence check has failed. Please help :-)= Message-ID: <d627f19f.0310271505.62bc678f@posting.google.com>    Hello Mr. Hoffman!  D Thank you realy much for your detailed posting but I think I already? registered the right PAK correctly and I have enabled it at the- installation process.lF I did act to your suggestion with the faq but it is like all the other faq's and google searches.E This license problem is realy confusing to me and I fear that I can'te@ solve it and I never can check out this great OS because of this stupid licensing. F This is the reason why I'm hopeing to get a good hint from usenet whatE I exactly should do in my situation. In the meantime I will study theR faq.   Thank you and greetings - Joep  ] hoff@hp.nospam (Hoff Hoffman) wrote in message news:<W6enb.7842$8V2.3974@news.cpqcorp.net>...ed > In article <d627f19f.0310260112.15ea73ec@posting.google.com>, cocacolaeisbaer@gmx.at (joe) writes:G > :I am a beginner in OpenVMS and have installed the hobbyist kit on an F > :old but good alpha250. I installed it exactly as it is described inE > :the OpenVMS Hobbyist Guide - The Alpha Kit (.pdf) from openvms.orgfG > :page. After installation the system reboots and I get to a graphicalpE > :login where I try to login with my system account but I always getDC > :back following error massage box "LMF licence check has failed".l2 > :Have I done anything wrong at the installation?+ > :Or what can I do to get into the system?-7 > :I really don't know and I hope anybody can help me.   > J >   The OpenVMS Frequently Asked Questions (FAQ) will be of interest here,I >   as it describes which two sets of licenses you need of the three sets>I >   that are available, and it describes how to register product licensesnD >   in this particular situation, given that you cannot log into the >   DECwindows display.  > ' >     http://www.hp.com/go/openvms/faq/  > I >   You will want to communcate your confusion to whomever is maintainingnK >   the guide you read, as this is (unfortunately) a fairly common mistake,>I >   and one that should be covered in the specified document.  (QuestionssJ >   also occasionally arise here, too, hence the inclusion into the FAQ --K >   and the Google newsgroup search should be able to find various of theseg >   previous discussions, too.)s > J >   The sections of the OpenVMS FAQ that are of central interest here are: > 4 >     Questions asked by Hobbyist OpenVMS licensees?% >     Resolving License PAK Problems?o9 >     I've forgotten the SYSTEM password - what can I do?d > K >   I'd encourage you to download and search the text-format version of the I >   FAQ, as that version is likely the easiest to download and to search.i >  > P >  ---------------------------- #include <rtfaq.h> -----------------------------M >     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqmP >  --------------------------- pure personal opinion ---------------------------G >         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Mon, 27 Oct 2003 22:50:41 GMTd# From: hoff@hp.nospam (Hoff Hoffman) : Subject: Re: LMF licence check has failed. Please help :-)2 Message-ID: <5jhnb.7868$%l3.3132@news.cpqcorp.net>  b In article <d627f19f.0310271403.46123bbe@posting.google.com>, cocacolaeisbaer@gmx.at (joe) writes:  :Thank you for answering Dirk:-) :yE :But I have got the license from montagar and the registration of therB :license took place without having error messages at installation.G :After that I enabled the Produkt Authorization Key during installation E :process with VMS License Management Utility to load it (I think thisS :was option 10 in the menu). : + :Do you have any idea what I've done wrong?i  C   If you registered "license", you didn't register what you needed.yD   You need "licenses", as in two sets of licences -- one set for theA   base system (OpenVMS VAX or OpenVMS Alpha), and one set for the0B   layered products.  As stated in the message you've probably readA   by now, check the OpenVMS FAQ for details on this and on how toe   get yourself out of this.e    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq:N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comi   ------------------------------  # Date: Mon, 27 Oct 2003 23:46:33 GMTo# From: hoff@hp.nospam (Hoff Hoffman)F: Subject: Re: LMF licence check has failed. Please help :-)1 Message-ID: <t7inb.7872$iq3.519@news.cpqcorp.net>   b In article <d627f19f.0310271505.62bc678f@posting.google.com>, cocacolaeisbaer@gmx.at (joe) writes:  9 :...I think I already registered the right PAK correctly    F   PAK?  PAK implies singular.  You need rather more than one PAK here.  3 :and I have enabled it at the installation process.   J   You must register multiple Product Authorization Keys (PAKs) to get thisJ   configuration to work, and usually you must invoke TWO files of licenses)   for the typical hobbyist configuration.-  H   If you have loaded two sets of licenses, then please post the names ofI   the licenses -- just the names, and not the PAK checksums nor other PAK-;   data -- from the sets of PAKs that you have registered.  -  I   You will typically need to have registered TWO seperate files of one or G   more PAKs within each file, given typical licensing from the hobbyist0   site.   I   If you have ONE file and ONE set of licenses, then you must acquire theaE   additional and required second set of licenses -- you need the baseHF   system license(s) and the layered product licenses, and (when last II   checked the Hobbyist website) this involved two separate files of PAKs.s  H   (If you have acquired and have previously and individually invoked theH   requisite two files of PAKs, then I do not immediately know what mightK   be wrong here.  That said, the problem you are reporting is almost alwaysaI   because the hobbyist has erroneously acquired or has loaded only one ofa"   the two required files of PAKs.)  tJ   Again, the sections of the OpenVMS FAQ that are of central interest here   are:  a2     Questions asked by Hobbyist OpenVMS licensees?#     Resolving License PAK Problems?r7     I've forgotten the SYSTEM password - what can I do?u  G   If any information found in the FAQ is not clear or is wrong, please nE   state what is not clear (or what is wrong) and I and/or others will E   endevour to reword or otherwise resolve the error or the confusion.       N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq.N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Mon, 27 Oct 2003 19:25:01 -0600t1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e: Subject: Re: LMF licence check has failed. Please help :-)& Message-ID: <3F9DC56D.3791B09@fsi.net>  
 joe wrote: >  > Hello Mr. Hoffman! > F > Thank you realy much for your detailed posting but I think I alreadyA > registered the right PAK correctly and I have enabled it at thed > installation process.)H > I did act to your suggestion with the faq but it is like all the other > faq's and google searches.G > This license problem is realy confusing to me and I fear that I can'tdB > solve it and I never can check out this great OS because of this > stupid licensing.rH > This is the reason why I'm hopeing to get a good hint from usenet whatG > I exactly should do in my situation. In the meantime I will study theg > faq.  H Well, what everyone seems to be trying to say is that there are two setsE of licenses. One is just the operating system license. The other is a-G long list of licenses for pieces of software called "layered products".-G The part no one seems to explain fully is that the o.s. license is justSF that: a license for the o.s. The GUI is considered a "layered product" for this purpose.b  G In addition to the OPENVMS-ALPHA license, you need the DW-MOTIF license % from the layered product license set.A  F How do you load that now? Well, you gotta power up the machine withoutH the keyboard connected, with a terminal or terminal program of some kindC attached via the serial (console) port (the default is usually 9600uE baud, 8 bits, no parity, one stop bit). That should make it revert to.C the "serial console". Then you can log in and register the DW-MOTIF F license, shutdown, re-attach the keyboard and power/boot up again. Now your GUI login should work.e  
 Good luck.   -- u David J. Dachteraf dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a   ------------------------------  % Date: Mon, 27 Oct 2003 21:48:16 +0100  From: Dirk Munk <munk@home.nl>% Subject: Re: Mozilla 1.5 for OpenVMS?t2 Message-ID: <bnk0ed$ias$1@news1.tilbu1.nb.home.nl>   Joseph Huber wrote:-Q > In article <bngj8n$t1v$1@swifty.westend.com>, "B.Eckstein" <eck@ivu.de> writes:  > E >>11 days ago, Mozilla 1.5 has been released and there is no 1.5 for gJ >>OpenVMS. Looks overdue for me. Does anybody know about the next release? >  > B > eh ? I definitely am using it, downloaded from the Mozilla site: >  > 	i
 > Mozilla 1.51[ > Mozilla/5.0 (X11; U; OpenVMS Digital_Personal_WorkStation_; en-US; rv:1.5) Gecko/20030929  >  TQ Sorry to disappoint you, but you must be running Mozilla 1.5 Release Candidate 2 oP (at the most). There is no 1.5 final for OpenVMS. The 1.5 Final was released on / 15 October, your version is dated 29 september.t   ------------------------------  % Date: Mon, 27 Oct 2003 13:35:18 -0500a* From: "Bill Todd" <billtodd@metrocast.net>; Subject: Re: OpenVMS I64 ISV application count now over 500i2 Message-ID: <QpydnYpayOP3-ACiRVn-uw@metrocast.net>  3 "jlsue" <jefflsxxxz@sbcglobal.net> wrote in messagea2 news:vr8qpv4tl6cihbcemlq60kp0cb66j1bsb5@4ax.com...K > On Fri, 24 Oct 2003 16:55:59 +0000 (UTC), david20@alpha2.mdx.ac.uk wrote:a >v >dJ > >>Except that some of your comments border on defamation (not to mentionK > >>FUD).  While you certainly have offered your analysis of the Alpha etc. L > >>history, it has little to no bearing on what we are doing now.  And yourI > >>constant rehashing of history in relation to what we are doing now is5 > >>meaningless. > >> > >1= > >The performance of IA64 against Alpha isn't relevent now ?a >sH > Pretty much a moot point now.  Yes.  IA64 is where it's going, and has been > for over 2 years now.c  L And by all appearances customers have been 'going' for over 2 years as well.G Events such as last week's aren't exactly likely to decrease that flow,,J rather the opposite:  *that's* why history is important - it's cumulative.   >cG > >The performance of IA64 against what Alpha would have been with even  minimal'G > >support - ie keeping to the published roadmap - isn't relevent now ?w >tI > That's nothing but conjecture, and is highly dependent on what it wouldcE > have cost to bring it to  fruition compared to what the company was  willing . > to invest (based on expected market return). >aH > We can all speculate, but only those who are actually held responsible must > make the final decisions.h  A And what we're trying to do is make sure that they're indeed heldhI responsible for those decisions.  Funny how some people would just prefer  that they be forgotten.h   ...l  E > >As always seems to be the case with IA64 only the future will tell  whether IA64K > >will be successful. It seems to always be the chip which will win big atu someL > >point in the future. Maybe as with the commercial adoption of Unix in the lateB > >eighties next year will be the year of IA64 but then maybe not. > >  > >e >lG > Er.... exactly how is this different than other new chips, like AMD'sr; > 64-bit chip?  Only the future will tell with any of them.w  H Well, one difference could be that AMD64 has only been available for theG past 6 months and is apparently already in considerable demand, despitelC concerns one might have over its parent's corporate health and somelF stumbling with initial motherboard availability, while Itanic has beenJ available for nearly 2.5 years (IIRC launch was May, 2001) and is still inK negligible demand, despite the best efforts of both Intel and HP to promotewK its success.  While history may be no guarantee of future performance, it'se( at least rather suggestive in this case.   - bill   ------------------------------  % Date: Mon, 27 Oct 2003 14:30:10 -0500i* From: "Bill Todd" <billtodd@metrocast.net>; Subject: Re: OpenVMS I64 ISV application count now over 500e2 Message-ID: <A_CdnQfu5frY7wCiRVn-sg@metrocast.net>  3 "jlsue" <jefflsxxxz@sbcglobal.net> wrote in messagey2 news:k99qpvkd8b79j2bd4qqk5r25470h7e7n2m@4ax.com...J > On Fri, 24 Oct 2003 12:15:41 -0400, "Bill Todd" <billtodd@metrocast.net> > wrote: >k > >l6 > >"jlsue" <jefflsxxxz@sbcglobal.net> wrote in message5 > >news:r6igpvcl3livu622b40u9vfs6ts9glv8ka@4ax.com...n4 > >> On Tue, 21 Oct 2003 10:07:24 -0400, "Bill Todd" <billtodd@metrocast.net> > >> wrote:7 > >> >  > >>? > >> Yeah, I'm sure posting in c.o.v will really help that one.l > >o" > >I'd certainly like to think so. >nF > Dream on then.  Don't know what you're smoking, but it must be good.  L Hey - the figures only tell what happened, they don't tell exactly why.  ButJ what happened was rather significant:  VMS system revenues alone have beenK lower by around $4 billion over the past 2+ years, and profits lower by the F better part of $1 billion - and having had even a *very* small hand inH having helped cause that (even ignoring the parallel impact on Tru64) is> enough to make me feel that my efforts were likely worthwhile.  H Oh, yes:  IIRC Terry also made several explicit statements to the effectI that the discussions here were being picked up and used with considerabletK success by the Sun and IBM competition (and even by the *HP* competition inaC some cases!).  Now, you may not consider Terry to be a particularlynG objective source either (I often don't), but those statements warmed myl heart as well.   >t7 > >After all, if everyone had just gone along [snip...]e > H > Yes, yes.  We all know that you've fully analyzed all the business andJ > technical opportunities available to the (then) Compaq CEO and found theI > flaw in the decisions.  It must be nice to be able to armchair-manage ae2 > multi-national business' decisions with no risk.  H Actually, it was kind of a pain in the ass having to dig up the materialJ that proved just how much of a jackass Curly was.  And it's been even moreL of a pain having to do so repeatedly each time some moron suggests that it'sK all just FUD.  Fortunately, I've already done that enough times here that I # don't feel I have to yet again now.a   >eJ > I fully understand customers who are concerned about these decisions andL > may view HP's business as a bit riskier now.  Depending on where they wereK > in the business cycle, some got hit worse than others and I find no faultuF > with them for an unwillingness to accept things at face value today. > I > But there's never going to be any repercussions along the lines of whata youa > claim is required.  J Don't be *too* sure of that.  If HP's enterprise business indeed goes downF the toilet (which certainly appears to be the direction in which it isJ headed:  no profits, significant erosion in the manpower needed to manage,J design, and build the next generation of products - especially in storage,I complete dependence on a yet-to-be-commercially-accepted processor, and arH service organization headed for India as fast as it can be moved there),I even stockholders as sheep-like as HP's (at least the half that voted fortK the merger - what remains of the other half may still be fairly pissed off)t! may wake up and smell the coffee.d  5   The fact is that in the real world, there are oftenoI > many paths to take to reach your goals, and once one is taken you oftentH > can't go back (and I'm not saying that we would want to go back in any	 > event).7  E 'Going back' hasn't been the point since the merger went through (and-I actually became fairly impossible once it was announced, though if it hadcL been squashed Curly would likely have gotten the boot - as he quite possiblyF would had the merger not existed at all - which would have given AlphaH another chance).  Since then, the intent has been that those responsibleJ should either be fired (with a corporate apology) or perform suitable actsG of contrition and recompense (e.g., make up for the major blow that the H Alphacide dealt to VMS by an aggressive long-term campaign to expand its base).  6 >  And rarely is any particular decision clearly wrong  L So what?  We're not discussing some generalization here, we're talking aboutG a very specific, boneheaded decision.  The fact that on average *other*VC decisions may not be as clearly wrong has no relevance to this one.t    - often theJ > only thing that makes a decision wrong is a lack of commitment to follow
 > through.  K Well, rather pervasive attempts to justify it with out-right lies also cast J it in a more-than-somewhat-dubious light, I would say.  But while the liesH and spin may have contributed to the outrage that followed, the decisionF itself was very clearly wrong (and not only because it broke repeated,K explicit promises that Compaq had been making for years - right up to June,E 2001).  C   It should be apparent by now that HP is commited to this path and C > is working dilligently to follow through - and that's leadership.i  E No, that's pure, unadulterated brass.  And it deserves to be rewarded  accordingly.   >v7 > Will HP be successful?  Nobody can say at this point.   L However, we can not only hope but try to influence the outcome - without, of1 course, sacrificing our integrity as cHumPaq did.s     Continuing to naysay4 > without this information is FUD.  Pure and simple.  F Pure and simple bullshit.  Continuing to criticize cHumPaq is entirelyI appropriate until such time as they act to repair the damage they did (ani@ apology would be nice as well, but hardly sufficient in itself).   - bill   ------------------------------    Date: 27 Oct 2003 13:35:55 -0800- From: djesys@earthlink.net (David J Dachtera)v; Subject: Re: OpenVMS I64 ISV application count now over 500e= Message-ID: <66a00d01.0310271335.54e86608@posting.google.com>f  f jlsue <jefflsxxxz@sbcglobal.net> wrote in message news:<rlaqpv4n1shatf0temssm2l378upbdcsi4@4ax.com>...9 > On Sat, 25 Oct 2003 11:52:46 -0500, "David J. Dachtera">  > <djesys.nospam@fsi.net> wrote: >  > >jlsue wrote:. > >> [snip]>K > >> Except that some of your comments border on defamation (not to mentioniL > >> FUD).  While you certainly have offered your analysis of the Alpha etc.M > >> history, it has little to no bearing on what we are doing now.  And youreJ > >> constant rehashing of history in relation to what we are doing now is > >> meaningless.s > >aI > >Except that as Bill Todd and David Webb have pointed out, if we do not,E > >learn from the mistakes of the past, we are doomed to repeat them.s > >  > J > So you refuse to take any formal stance until they've shown their hand.   B On the contrary, I take the stance that the hand they have already) shown is being discarded ala Machiavelli.o   > I K > have never contended that you need to ignore the past, but not all of thet" > past behavior is without merit.   F Quite. Indeed, *ALL* of the past has merit, positive or negative. WhatE determines future outcomes is the ability to analyze those merits and/6 reshape your future positively based on that analysis.  , > And they clearly have a path that is beingH > pursued today, and that path will take time to demonstrate - naysayingF > before the results can possibly be shown is not stating "fact", it's > generating FUD.o  A However, the path that is being pursued - that is, which is beingTF demonstrated outwardly - and that which is stated as the "path" (read: "roadmap") are incongruent.r   -- David J Dachtera dba DJE Systemsl   ------------------------------  # Date: Mon, 27 Oct 2003 22:14:53 GMTf# From: "John Smith" <a@nonymous.com>t; Subject: Re: OpenVMS I64 ISV application count now over 500 J Message-ID: <xNgnb.79153$3f.28390@twister01.bloor.is.net.cable.rogers.com>   Bill Todd wrote:5 > "jlsue" <jefflsxxxz@sbcglobal.net> wrote in messagee4 > news:k99qpvkd8b79j2bd4qqk5r25470h7e7n2m@4ax.com...2 >> On Fri, 24 Oct 2003 12:15:41 -0400, "Bill Todd"" >> <billtodd@metrocast.net> wrote: >> >>>o7 >>> "jlsue" <jefflsxxxz@sbcglobal.net> wrote in messagei6 >>> news:r6igpvcl3livu622b40u9vfs6ts9glv8ka@4ax.com...4 >>>> On Tue, 21 Oct 2003 10:07:24 -0400, "Bill Todd"$ >>>> <billtodd@metrocast.net> wrote: >>>> >> >>>>? >>>> Yeah, I'm sure posting in c.o.v will really help that one.i >>>o# >>> I'd certainly like to think so.t >>G >> Dream on then.  Don't know what you're smoking, but it must be good.e >cD > Hey - the figures only tell what happened, they don't tell exactlyF > why.  But what happened was rather significant:  VMS system revenuesD > alone have been lower by around $4 billion over the past 2+ years,E > and profits lower by the better part of $1 billion - and having haduE > even a *very* small hand in having helped cause that (even ignoringdA > the parallel impact on Tru64) is enough to make me feel that myu! > efforts were likely worthwhile.t > C > Oh, yes:  IIRC Terry also made several explicit statements to thenE > effect that the discussions here were being picked up and used with4F > considerable success by the Sun and IBM competition (and even by theG > *HP* competition in some cases!).  Now, you may not consider Terry to F > be a particularly objective source either (I often don't), but those% > statements warmed my heart as well.- >- >>8 >>> After all, if everyone had just gone along [snip...] >>E >> Yes, yes.  We all know that you've fully analyzed all the business E >> and technical opportunities available to the (then) Compaq CEO andeB >> found the flaw in the decisions.  It must be nice to be able toE >> armchair-manage a multi-national business' decisions with no risk.u >gA > Actually, it was kind of a pain in the ass having to dig up theiF > material that proved just how much of a jackass Curly was.  And it'sD > been even more of a pain having to do so repeatedly each time someC > moron suggests that it's all just FUD.  Fortunately, I've already H > done that enough times here that I don't feel I have to yet again now. >o >>G >> I fully understand customers who are concerned about these decisions'G >> and may view HP's business as a bit riskier now.  Depending on where5F >> they were in the business cycle, some got hit worse than others andE >> I find no fault with them for an unwillingness to accept things at  >> face value today. >>E >> But there's never going to be any repercussions along the lines off >> what you claim is required. > G > Don't be *too* sure of that.  If HP's enterprise business indeed goes3G > down the toilet (which certainly appears to be the direction in whichpG > it is headed:  no profits, significant erosion in the manpower needed.@ > to manage, design, and build the next generation of products -1 > especially in storage, complete dependence on aIG > yet-to-be-commercially-accepted processor, and a service organization G > headed for India as fast as it can be moved there), even stockholdersdF > as sheep-like as HP's (at least the half that voted for the merger -D > what remains of the other half may still be fairly pissed off) may > wake up and smell the coffee./ >n7 >   The fact is that in the real world, there are oftendD >> many paths to take to reach your goals, and once one is taken youC >> often can't go back (and I'm not saying that we would want to goo >> back in any event). >oG > 'Going back' hasn't been the point since the merger went through (andeG > actually became fairly impossible once it was announced, though if itrC > had been squashed Curly would likely have gotten the boot - as henF > quite possibly would had the merger not existed at all - which wouldD > have given Alpha another chance).  Since then, the intent has beenA > that those responsible should either be fired (with a corporate G > apology) or perform suitable acts of contrition and recompense (e.g.,aB > make up for the major blow that the Alphacide dealt to VMS by an4 > aggressive long-term campaign to expand its base). > 7 >>  And rarely is any particular decision clearly wrongc >g@ > So what?  We're not discussing some generalization here, we'reG > talking about a very specific, boneheaded decision.  The fact that on > > average *other* decisions may not be as clearly wrong has no > relevance to this one. >  >  - often theD >> only thing that makes a decision wrong is a lack of commitment to >> follow through. >tC > Well, rather pervasive attempts to justify it with out-right lies G > also cast it in a more-than-somewhat-dubious light, I would say.  But2B > while the lies and spin may have contributed to the outrage thatD > followed, the decision itself was very clearly wrong (and not onlyC > because it broke repeated, explicit promises that Compaq had beenh- > making for years - right up to June, 2001).U >hE >   It should be apparent by now that HP is commited to this path andyD >> is working dilligently to follow through - and that's leadership. >sG > No, that's pure, unadulterated brass.  And it deserves to be rewardedr > accordingly. >a >>8 >> Will HP be successful?  Nobody can say at this point. >oB > However, we can not only hope but try to influence the outcome -? > without, of course, sacrificing our integrity as cHumPaq did.i >t >   Continuing to naysay5 >> without this information is FUD.  Pure and simple.e >tH > Pure and simple bullshit.  Continuing to criticize cHumPaq is entirelyG > appropriate until such time as they act to repair the damage they didgF > (an apology would be nice as well, but hardly sufficient in itself).    	 Hey Bill,   E I wondering if you're seeing the same thing I seen in this thread....r  K Great flashing and waving of porcupine quills when HP is criticized or wheno7 it is suggested that HP is 'economical with the truth'.-  G Specific questions get asked of HP employees about what they're told bytI management. Lay-up questions ...simple to answer....some even requiring ao simple yes/no response.e   Conspicous silence follows.w    H Maybe the folks who are going to Nashua next month should take a few VMSI engineering people off-site and fill them full of alcohol to loosen theirE6 tongues. Seems to me that the 'fear factor' runs high.   ------------------------------  % Date: Mon, 27 Oct 2003 14:26:58 -0800_/ From: Greg Cagle <news@removethisgregcagle.com>s; Subject: Re: OpenVMS I64 ISV application count now over 500 / Message-ID: <vpr6tq65ntjk6e@corp.supernews.com>1   John Smith wrote:w  L   > Maybe the folks who are going to Nashua next month should take a few VMSK > engineering people off-site and fill them full of alcohol to loosen their:8 > tongues. Seems to me that the 'fear factor' runs high.  E As well it should, this being the end of the fiscal year. More than a # few of my old team got WFRed today.    - Greg -- n
 Greg Cagle gregc at gregcagle dot com   ------------------------------  % Date: Mon, 27 Oct 2003 17:56:56 -0500w* From: "Bill Todd" <billtodd@metrocast.net>; Subject: Re: OpenVMS I64 ISV application count now over 500t2 Message-ID: <EY2dnQRo8eYmPwCiRVn-uw@metrocast.net>  . "John Smith" <a@nonymous.com> wrote in messageD news:xNgnb.79153$3f.28390@twister01.bloor.is.net.cable.rogers.com...   ...d  G > I wondering if you're seeing the same thing I seen in this thread....B >gH > Great flashing and waving of porcupine quills when HP is criticized or when9 > it is suggested that HP is 'economical with the truth'.a >eI > Specific questions get asked of HP employees about what they're told bypK > management. Lay-up questions ...simple to answer....some even requiring ao > simple yes/no response.t >i > Conspicous silence follows.E >c > J > Maybe the folks who are going to Nashua next month should take a few VMSK > engineering people off-site and fill them full of alcohol to loosen theira8 > tongues. Seems to me that the 'fear factor' runs high.  I As Greg noted, there's reason to be fearful.  And to some extent that may K make some HP employees feel that they need to stand up and be counted - not K so much because they think their management reads c.o.v., but simply to tryeF to help improve HP's image and in the process help protect their jobs.  H But, much as I disagree with some of them, I'm inclined to give them theJ benefit of the doubt:  I think they're mostly just misguided good guys whoI manage to find ways not to see - or at least not to believe - things thatc1 would make them uncomfortable sticking up for HP.i   - bill   ------------------------------  % Date: Mon, 27 Oct 2003 16:29:01 -0800 / From: Greg Cagle <news@removethisgregcagle.com> ; Subject: Re: OpenVMS I64 ISV application count now over 500g/ Message-ID: <vpre2mcs1ql715@corp.supernews.com>o   Bill Todd wrote: > K > As Greg noted, there's reason to be fearful.  And to some extent that maynM > make some HP employees feel that they need to stand up and be counted - notsM > so much because they think their management reads c.o.v., but simply to tryyH > to help improve HP's image and in the process help protect their jobs.  A In the new "hp" this is not a winning strategy. The gopher theoryt: applies - keep your head down or it will be mowed off 8^).  = Bear in mind that my entire team is now pretty much gone as ao@ result of "merger-related synergies" at this point. Our team was< a direct victim of the introduction of the Alpha server into< the scientific and technical computing product line. The CPQ9 acquisition has not been a good thing for a lot of old HPi? employees. I say this because I know there's a lot of anger outt: there about the "alphacide" and other similar issues - but: believe me, it isn't one hundredth of the anger you'll seeA from me about the merger. Unfortunately, I am legally constrained ; from saying negative things about "hp" in a public forum orS I would rant a bit more 8^).  G And yes, to me "hp" and HP are different things. HP is Hewlett-Packard, C a distinguished technology company and a place I was proud to work. 8 "hp" is whatever Carly has reinvented it into this week.  J > But, much as I disagree with some of them, I'm inclined to give them theL > benefit of the doubt:  I think they're mostly just misguided good guys whoK > manage to find ways not to see - or at least not to believe - things thatS3 > would make them uncomfortable sticking up for HP.-  @ If your employment, for example, depends on the success of a new> chip (let's call it "Itanium" because it sounds good), you may> NEED to believe in its success at a personal level, even if it@ doesn't always make sense. Besides, it's not all about the chip,> anyway. It's really about the "adaptive infrastructure" - just ask Carly 8^).   --  
 Greg Cagle gregc at gregcagle dot com   ------------------------------  % Date: Mon, 27 Oct 2003 19:55:11 -0500i* From: "Bill Todd" <billtodd@metrocast.net>; Subject: Re: OpenVMS I64 ISV application count now over 500n2 Message-ID: <XLmdnep-0_3vIwCiRVn-tg@metrocast.net>  < "Greg Cagle" <news@removethisgregcagle.com> wrote in message) news:vpre2mcs1ql715@corp.supernews.com...n   ...t  B > If your employment, for example, depends on the success of a new@ > chip (let's call it "Itanium" because it sounds good), you may@ > NEED to believe in its success at a personal level, even if itB > doesn't always make sense. Besides, it's not all about the chip,@ > anyway. It's really about the "adaptive infrastructure" - just > ask Carly 8^).  L If I were an artist, I'd whip up a cartoon showing carly(tm) holding a largeL bottle labeled "I-tonic (2% juice)", with the caption "I coulda had EV8...".   - bill   ------------------------------  # Date: Tue, 28 Oct 2003 01:22:05 GMTi# From: "John Smith" <a@nonymous.com>r; Subject: Re: OpenVMS I64 ISV application count now over 500oH Message-ID: <1xjnb.97033$h61.85658@news01.bloor.is.net.cable.rogers.com>   Greg Cagle wrote:7 > John Smith wrote:8 > F >   > Maybe the folks who are going to Nashua next month should take a	 > few VMSsF >> engineering people off-site and fill them full of alcohol to loosen? >> their tongues. Seems to me that the 'fear factor' runs high.d >sG > As well it should, this being the end of the fiscal year. More than a % > few of my old team got WFRed today.s    I Sorry to hear that.  Care to define 'more than a few'? Which area(s) were'
 they from?   <fascetious>H But look at the bright side...carly(tm) will have no problems making herL mortgage payment. Since she wan't WFRed she must obviously be more importantI to the future of HP than any 1000 HP employees in engineering or customer D support or just about any other department (except VMS advertising).
 </fascetious>o  K However, the obvious rejoinder to that mode of meeting 'budgets' is to lookWF at the other side of the coin, which is to increase sales. And that isH something that HP does not seem to be serious about with respect to VMS.  J Since large system sales cycles are longer than PC sales cycles, HP shouldK be priming the pump with VMS advertising and demand creation now (and for aVI long time before now). I hate to say it, but consider your own future andiI those of your VMS colleagues once the IA64 port is in GA......the port istK done, no demand has been stimulated, a pink slip lands on your desk, VMS is $ declared EOL, customers are screwed.   ------------------------------  % Date: Mon, 27 Oct 2003 18:33:45 -0800I/ From: Greg Cagle <news@removethisgregcagle.com>n; Subject: Re: OpenVMS I64 ISV application count now over 500q/ Message-ID: <vprlclqifsj450@corp.supernews.com>h   John Smith wrote:i   > Greg Cagle (me) wrote:  G >>As well it should, this being the end of the fiscal year. More than aw% >>few of my old team got WFRed today.t > K > Sorry to hear that.  Care to define 'more than a few'? Which area(s) werel > they from?  E  >10 in NA, but all the returns aren't in. I know it's not really big E numbers, but it's the tip of an iceberg. Presales technical resourcestC with any competence should be looking, if not already gone. The newo' "hp" doesn't have room for that luxury.   E Pre-merger, the team was responsible for presales tech consulting foriD the technical computing business for all platforms and all products.B The technical computing business was defined as design (electronicA and mechanical), scientific, computational, and things along that:D line. Basically if you used your computer to do something OTHER than; manage the company, then we were it. Specialized in PA-RISC @ workstations and servers, HP-UX, Linux, Itanium, networking, and> other things as needed. Our team was responsible for designing= the large Itanium Linux cluster at Pacific Northwest National = Labs, and the IA-32 Linux cluster at DreamWorks that Carly is-) so proud of and was used to render Shrek.a  G Post-merger, the team was refocused on IA-32 and RISC workstations only-H because the technical and scientific business were consolidated with the> Alpha server technical and scientific business into a separate: division with its own presales technical consulting force.@ Then the workstation division was rolled up into the PC division= instead of the enterprise division, and all *they* care about6@ is margin in order to compete with Dell. And presales resources,= especially at our expertise level, are expensive in a PC cost:4 model. And things have been downhill ever since 8^).  A The thing that doesn't make sense is that key Linux resources areo? being laid off. I doubt if there's anyone left at "hp" that cana= design or deploy a large Linux cluster. Which I guess is okay > with me, because the demand is there and I'll just do the work as an independent 8^).   > <fascetious>J > But look at the bright side...carly(tm) will have no problems making herN > mortgage payment. Since she wan't WFRed she must obviously be more importantK > to the future of HP than any 1000 HP employees in engineering or customer F > support or just about any other department (except VMS advertising). > </fascetious>  > M > However, the obvious rejoinder to that mode of meeting 'budgets' is to lookoH > at the other side of the coin, which is to increase sales. And that isJ > something that HP does not seem to be serious about with respect to VMS.  B Actually, if you knew the truth, it's not just VMS. There are manyH product lines within HP that could use a promotional boost. For example,8 HP's PA-RISC midrange servers have always been more than/ competitive than Sun - but no one ever knew it.   L > Since large system sales cycles are longer than PC sales cycles, HP shouldM > be priming the pump with VMS advertising and demand creation now (and for acK > long time before now). I hate to say it, but consider your own future and(K > those of your VMS colleagues once the IA64 port is in GA......the port is M > done, no demand has been stimulated, a pink slip lands on your desk, VMS isI& > declared EOL, customers are screwed.  @ See above - I'm not a VMS guy (although I used to be a long time; ago). And I already *have* the pink slip, thanks very much.s   - Greg -- l
 Greg Cagle gregc at gregcagle dot com   ------------------------------  % Date: Mon, 27 Oct 2003 20:40:40 +0100e0 From: Michael Unger <michaelunger@despammed.com>8 Subject: OpenVMS Rolling Roadmaps (23-Oct-2003) and DCPS: Message-ID: <bnjsfp$120nag$1@ID-152801.news.uni-berlin.de>  E On slide 35 of the latest "OpenVMS Running Roadmaps", "DCPS Roadmap -e" Future Functionality" (2005-2006):  
 - USB supportt - parallel port support   F It's really strange, since USB isn't supported by VMS (some exceptionsD on the EV7 models) and the parallel port is considered "legacy" even7 now. And many printers don't even have a parallel port.   . So what's the reason for that "functionality"?   Michaele   -- e; Real names enhance the probability of getting real answers.e@ Please do *not* send "Security Patch Notifications" or "SecurityA Updates"; this system isn't running a Micro$oft operating system.t= My e-mail account at DECUS Munich will expire on 31-Dec-2003.s   ------------------------------  % Date: Mon, 27 Oct 2003 21:59:58 +0100w From: Dirk Munk <munk@home.nl>< Subject: Re: OpenVMS Rolling Roadmaps (23-Oct-2003) and DCPS2 Message-ID: <bnk143$7m1$1@news3.tilbu1.nb.home.nl>   Michael Unger wrote:G > On slide 35 of the latest "OpenVMS Running Roadmaps", "DCPS Roadmap -s$ > Future Functionality" (2005-2006): >  > - USB support  > - parallel port supportg > H > It's really strange, since USB isn't supported by VMS (some exceptionsF > on the EV7 models) and the parallel port is considered "legacy" even9 > now. And many printers don't even have a parallel port.> > 0 > So what's the reason for that "functionality"?  
 Let me guess:V  K In the near future many printers will only have a USB port (or a expensive l network port).Q Maybe there will be USB cards that are supported in pre-EV7 systems (why not ?), t1 so you can use USB printers on older systems too. M In the present versions of DCPS, the sofware always needs 2-way connections, nP because the printer has to 'answer questions'. The new version of DCPS can also K work with LPR/LPD, which is a 1-way connection. (dump the whole lot to the oO printer, and hope it will come out ok). That is also the way the parallel port g9 works on VMS, so there is no problem using that port too.i   ------------------------------    Date: 27 Oct 2003 11:24:19 -0800' From: steven@psds.com (Steven Petersen)c( Subject: Pathworks V4.1  - Need copy of:; Message-ID: <9889b0a.0310271124.a0f1c47@posting.google.com>c  C I'm in dyer need of a copy of Pathworks client V4.1.  If you have as) copy please contact me at steven@psds.comd   Thanks   ------------------------------  % Date: Mon, 27 Oct 2003 18:04:24 -0600 % From: "Mike Naime" <mnaime@kc.rr.com>n' Subject: Re: Patrol x Decnet Management 8 Message-ID: <IQinb.76771$%C5.7893@twister.rdc-kc.rr.com>  9 Fabio Cardoso <fabiopenvms@yahoo.com.br> wrote in messageo7 news:f30679fb.0310270935.33c2c54c@posting.google.com...e; > Anyone know any kind of Patrol KM to manage Decnet Nodes.    Patrol KM for VMS  -- YES. Manage nodes. -- NO!!!  G BMC Patrol is a monitoring tool only.  I would not call it a Management  tool.dB There are specific (Licensed) KM's for VMS, Oracle on VMS, and our Application.  L The BMC guy who was doing our onsite installation/upgrades asked me one timeI if we could remove the "$" from the device names on all of our VMS devicecL names.  (EX: $1$DGA100:)   I told him " NO.  It's part of the OS.  I have no controll over the '$' usage."t  9 > Check if the status is up. Like returning a status fromt > $ MCR NCP LOOP NODE xxxx > etc...  K AMDS, or HP OpenView (Network Monitoring software package) will provide the L same.  AMDS I do not think requires a license on all of the systems like BMC does.n  F > We need to put the Patrol Console  to check the status of ome nodes: >-* > SNA Gateway and X25/Router under Decnet. >c >0	 > Regards  >0 > Fc   ------------------------------  # Date: Mon, 27 Oct 2003 18:21:52 GMTs3 From: hammond@not@peek.ssr.hp.com (Charlie Hammond)e Subject: Re: Product problem1 Message-ID: <4ndnb.7835$tX2.662@news.cpqcorp.net>c  C I have no specific reason to suggest this, but you can see problemsdI similar to this if you do PRODUCT operations while there is a second diska/ mounted with the same label as the system disk.l   -- iJ       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAF           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------    Date: 27 Oct 2003 13:48:05 -08001 From: byer@mail.ourservers.net (Robert Alan Byer) R Subject: Re: Question: Linking directories (not quite the same thing, but similar); Message-ID: <c4bfc78e.0310271348.9330f8@posting.google.com>r   > F > $ def/system project_dir user:[user1.project],user:[user2.project],- > 	user:[user3.project]R >  > $ dir project_dirj >   > Directory USER:[USER1.PROJECT] >  > FILE.TXT;1 >  > Total of 1 file. >   > Directory USER:[USER3.PROJECT] >  > FILE.TXT;1 >  > Total of 1 file. > ( > Grand total of 2 directories, 2 files. > L > The drawback to this approach is that in the case of duplicate file names,J > the one you get will be in the directory which is mentioned first in the3 > searchlist, not necessarily the most recent file.o >    Hmmm...t  D I'm looking for something similar for a porting probject I'm working on.s  B I have a set of two sets of "include" directories and depending onB which item you are building, some of the "include" items can be in either directories.e  = Not usually a problem, but the include directories are in twohB different parts of the tree and are named the same.  In the source file they define a directory
 path like   &          #include "includes/system1.h"&          #include "includes/system2.h"  ? And of couse files "system1.h" and "system2.h" are in differenteE directories.  I've tried for a week playing with the include path andpE have gotten nowhere as I think the directory reference in the includeiD is a problem.  I could just edit all of the one thousand plus files, but that's a pain.  E I've tried defineing "includes" to point to both the directories like 2 you suggested above, but that didn't seem to work.  C (it was originally developed on Unix under GNU C so there are othert! issues, but this is the main one)a  > I'm still messing with it and think I have some ideas, but any thoughts anyone?   ------------------------------  + Date: Mon, 27 Oct 2003 22:26:52 +0000 (UTC)c? From: Graham Burley <burley.not-this@encompasserve-or-this.org>eR Subject: Re: Question: Linking directories (not quite the same thing, but similar)9 Message-ID: <3F9DA865.6DF96EE7@encompasserve-or-this.org>    Robert Alan Byer wrote:e >   D > I have a set of two sets of "include" directories and depending onD > which item you are building, some of the "include" items can be in > either directories.f > ? > Not usually a problem, but the include directories are in twohD > different parts of the tree and are named the same.  In the source > file they define a directory > path like  > ( >          #include "includes/system1.h"( >          #include "includes/system2.h" > A > And of couse files "system1.h" and "system2.h" are in differentrG > directories.  I've tried for a week playing with the include path andnG > have gotten nowhere as I think the directory reference in the include.F > is a problem.  I could just edit all of the one thousand plus files, > but that's a pain. > G > I've tried defineing "includes" to point to both the directories like 4 > you suggested above, but that didn't seem to work. >   @ I think you need rooted logicals and a unix style /INCLUDE, e.g.  6  $ define inc_root disk$a:[abc.def.],disk$a:[abc.xyz.]  $ cc/include="/inc_root".     Graham   ------------------------------  # Date: Mon, 27 Oct 2003 22:48:12 GMT # From: hoff@hp.nospam (Hoff Hoffman)dR Subject: Re: Question: Linking directories (not quite the same thing, but similar)2 Message-ID: <Mghnb.7867$%l3.4297@news.cpqcorp.net>  o In article <c4bfc78e.0310271348.9330f8@posting.google.com>, byer@mail.ourservers.net (Robert Alan Byer) writes:7 :> >G :> $ def/system project_dir user:[user1.project],user:[user2.project],-e :> 	user:[user3.project] :>   :> $ dir project_dir ..  M :> The drawback to this approach is that in the case of duplicate file names,eK :> the one you get will be in the directory which is mentioned first in thea4 :> searchlist, not necessarily the most recent file. ..E :I'm looking for something similar for a porting probject I'm workingb :on. :eC :I have a set of two sets of "include" directories and depending on C :which item you are building, some of the "include" items can be in  :either directories. :l> :Not usually a problem, but the include directories are in twoC :different parts of the tree and are named the same.  In the sources :file they define a directorya :path like c :i' :         #include "includes/system1.h"e' :         #include "includes/system2.h"i : @ :And of couse files "system1.h" and "system2.h" are in different :directories. ...e ..D :I've tried defineing "includes" to point to both the directories...  F   The behaviour of the C compilers has shuffled some in this area overE   the years, and newer versions have cleaner and more logical schemeseG   for referencing the include files.  (I'd expect more recent compilers D   to contend with a correctly-defined includes search list, in otherE   words.  The compilation of X Windows code does something like this,w4   for instance, with the ubiquitous X logical name.)  F   For this C stuff, I'd probably use the DECC$USER_INCLUDE search list"   or the /INCLUDE directory stuff.  E   Its somewhat weird that the files are in different directories, buteE   with the same name.  Are these (or where these involving) symlinks?   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comf   ------------------------------  % Date: Mon, 27 Oct 2003 19:11:52 -0500n1 From: Robert Alan Byer <byer@mail.ourservers.net> R Subject: Re: Question: Linking directories (not quite the same thing, but similar)8 Message-ID: <8kcrpv8913ngt0ff3f5pbrp1nvcpt55ihv@4ax.com>   > G >  The behaviour of the C compilers has shuffled some in this area over,F >  the years, and newer versions have cleaner and more logical schemesH >  for referencing the include files.  (I'd expect more recent compilersE >  to contend with a correctly-defined includes search list, in otherdF >  words.  The compilation of X Windows code does something like this,5 >  for instance, with the ubiquitous X logical name.)l >aG >  For this C stuff, I'd probably use the DECC$USER_INCLUDE search listh# >  or the /INCLUDE directory stuff.r >rF >  Its somewhat weird that the files are in different directories, butF >  with the same name.  Are these (or where these involving) symlinks? >b  E The directories have the same names, but not the files themselves andr they arn't links.n  B Basically there are two different "systems" and depending on whichF one you want to build will dictate which set of trees to use.  But theA problem is that (for example) system1 has it's own self-containedl@ tree, system2 has it's own tree and also uses pieces of system1,( which contains the same directory names.   Right now if I have just...o  %         #include "includes/system1.h"o%         #include "includes/system2.h"   @ where "system1.h" resides in [.system1.includes] and "system2.h"E resides in [.system2.includes] and I define a logical for includes toe point to them...  = 	define includes disk$work:[test.project.system1.includes], -'  ) disk$work:[test.project.system2.includes]   E it compiles just fine, but if I have sub-directories UNDER them like.a  $ 	#include "includes/system1/part1.h"0              #include "includes/system2/part2.h"  : where "part1.h" resides in [.system1.includes.system1] and; "part2.h" resides in [.system2.includes.system2], "part1.h" ( is included just fine, but not "part2.h"  E I'm still playing around and out of the four directories only one hase: sub-directoriies (all different) that I have to deal with.   ------------------------------  # Date: Tue, 28 Oct 2003 01:17:17 GMTe# From: hoff@hp.nospam (Hoff Hoffman)rR Subject: Re: Question: Linking directories (not quite the same thing, but similar)2 Message-ID: <xsjnb.7881$Mv3.6985@news.cpqcorp.net>  l In article <8kcrpv8913ngt0ff3f5pbrp1nvcpt55ihv@4ax.com>, Robert Alan Byer <byer@mail.ourservers.net> writes: ..A :where "system1.h" resides in [.system1.includes] and "system2.h"iF :resides in [.system2.includes] and I define a logical for includes to :point to them...e :a :	define includes -t< :               disk$work:[test.project.system1.includes], -9 :               disk$work:[test.project.system2.includes]l :tF :it compiles just fine, but if I have sub-directories UNDER them like. : % :	#include "includes/system1/part1.h"i1 :             #include "includes/system2/part2.h"u :c; :where "part1.h" resides in [.system1.includes.system1] and < :"part2.h" resides in [.system2.includes.system2], "part1.h") :is included just fine, but not "part2.h"I    D   If you want to use trees of file specifications, then you might beE   running into a problem.  If you want to do paths such as this, lookiC   at exactly how SYS$SYSROOT and similar are established.  (The funSB   here is if you have a mixture of the two specifications, and I'mB   going to guess you have that.  If so, you might end up using theD   /FIRST_INCLUDE stuff and some preprocessor defines to "fix" this.)    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqnN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comu   ------------------------------    Date: 27 Oct 2003 13:44:48 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)m- Subject: Re: Question: Linking directories...n3 Message-ID: <67uPk$tqUXXD@eisner.encompasserve.org>a  r In article <bf17a894.0310270812.3d37879f@posting.google.com>, anon314@mail.ourservers.net (Anonymous #314) writes:E > I have a project at work that needs the following and I'm trying tod/ > figure out if this can be done under OpenVMS.a > F > We have a project where three people need to share a directory underE > their sys$login: directory, BUT ALL need to be accessed as a single  > directory.  A    You mean [a.e], [b.e], and [c.e] all need to be physically them*    same directory?  Yes, that can be done.  H > So if user1, user2 and user3 all have a directory called "PROJECT" theG > "powers that be" want to be able to access all three directories (ande8 > sub directories)as one like PROJECT_DIR: or something., > Can this be done in OpenVMS and if so how?  >    Or do you need the logical name PROJECT_DIR to point to theF    same place for all three users?  It kind of sounds like that's what    you've been told not to do.  F > (making a common directory that all have access to I've been told isA > NOT an option for some reason, which is how I would just do it)j  H    But both of these approaches DO make a common directory that all haveJ    access to.  Or do they really want three separate directories all known    as PROJECT_DIR?      In the first case:       $create/directory [a.e]&    $set file/enter=[b]e.DIR;1 [a]e.dir&    $set file/enter [c]e.DIR;1 [a]e.dirJ    $set file/acl=(identifier=a,access=read+write+control+execute) [a]e.dir/    $set file/acl=(identifier=a,option=default,-a8       access=read+write+control+execute+delete) [a]e.dirJ    $set file/acl=(identifier=b,access=read+write+control+execute) [a]e.dir/    $set file/acl=(identifier=b,option=default,- 8       access=read+write+control+execute+delete) [a]e.dirJ    $set file/acl=(identifier=c,access=read+write+control+execute) [a]e.dir/    $set file/acl=(identifier=c,option=default,-i8       access=read+write+control+execute+delete) [a]e.dir      In the second case:       $create/directory [somewhere]M    $set file/acl=(identifier=a,access=read+write+control+execute) [somewhere]u/    $set file/acl=(identifier=a,option=default,- ;       access=read+write+control+execute+delete) [somewhere]eM    $set file/acl=(identifier=b,access=read+write+control+execute) [somewhere]e/    $set file/acl=(identifier=b,option=default,-e;       access=read+write+control+execute+delete) [somewhere]mM    $set file/acl=(identifier=c,access=read+write+control+execute) [somewhere]a/    $set file/acl=(identifier=c,option=default,-t;       access=read+write+control+execute+delete) [somewhere]e        and in login.com:  (    $define/nolog project_dir [somewhere]      In the third case:l    $create/directory [a.e]    $create/directory [b.e]    $create/directory [c.e]  9       and in login.com (substitute a, b, or c for <user>:t  '    $define/nolog project_dir [<user>.e]a    G    Or better yet, tell us what problem you're trying to solve with thisn4    directory and we'll come up with a real solution.	          v   ------------------------------  # Date: Mon, 27 Oct 2003 19:47:19 GMT # From: hoff@hp.nospam (Hoff Hoffman)t- Subject: Re: Question: Linking directories...U1 Message-ID: <bDenb.7846$8V2.302@news.cpqcorp.net>t  r In article <bf17a894.0310270812.3d37879f@posting.google.com>, anon314@mail.ourservers.net (Anonymous #314) writes:D :I have a project at work that needs the following and I'm trying to. :figure out if this can be done under OpenVMS. :cE :We have a project where three people need to share a directory underfD :their sys$login: directory, BUT ALL need to be accessed as a single :directory.n  F   Some background here, please?  (The solution proposed here is clear,<   the particular rational for choosing the approach is not.)  G :So if user1, user2 and user3 all have a directory called "PROJECT" the F :"powers that be" want to be able to access all three directories (and7 :sub directories)as one like PROJECT_DIR: or something.i :t+ :Can this be done in OpenVMS and if so how?y  E   This is possible, so long as all three directories are on the same  "   disk (or same volume shadowset).  D   That written, the PTB are force-fitting their knowledge of anotherI   platform onto OpenVMS.  (Without details on the background, an approach-F   using this force-fitting technique can be problematic -- alternative)   solutions can be missed, for instance.)h    E :(making a common directory that all have access to I've been told iso@ :NOT an option for some reason, which is how I would just do it)    F   And setting up a common directory would be the recommended approach,F   as well as -- particularly with the configuration and use of what isG   known as a Resource Identifier -- the easiest to use and (on OpenVMS)i%   among the most flexible approaches.e  H   It also means folks are less likely to accidently blow away the entireG   project directory, too -- imagine a system manager that rolls out onetH   of these user's directories to archive media (because, say, one of theH   three folks has moved to another project), and then deletes the user'sH   directory tree.  The alias tree will disappear in all the other roots,   too.  F   Even if you choose the alias (sub)directory approach, you will stillH   want to set up the resource identifier and ownership, as otherwise youK   can get into some confusion over file protections, ownership, and access.b    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqnN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Mon, 27 Oct 2003 21:33:13 -0500 ( From: David Froble <davef@tsoft-inc.com>- Subject: Re: Question: Linking directories...n, Message-ID: <3F9DD569.3000609@tsoft-inc.com>   Keith A. Lewis wrote:e   > anon314@mail.ourservers.net (Anonymous #314) writes in article <bf17a894.0310270812.3d37879f@posting.google.com> dated 27 Oct 2003 08:12:36 -0800: > E >>I have a project at work that needs the following and I'm trying toa/ >>figure out if this can be done under OpenVMS.a >>F >>We have a project where three people need to share a directory underE >>their sys$login: directory, BUT ALL need to be accessed as a singlen >>directory.    P Not enough information.  By accessed, is it just read access, or will new files  be created?     H >>So if user1, user2 and user3 all have a directory called "PROJECT" theG >>"powers that be" want to be able to access all three directories (andn8 >>sub directories)as one like PROJECT_DIR: or something. >>, >>Can this be done in OpenVMS and if so how? >> > F > $ def/system project_dir user:[user1.project],user:[user2.project],- > 	user:[user3.project]n >  > $ dir project_dir. >   > Directory USER:[USER1.PROJECT] >  > FILE.TXT;1 >  > Total of 1 file. >   > Directory USER:[USER3.PROJECT] >  > FILE.TXT;1 >  > Total of 1 file. > ( > Grand total of 2 directories, 2 files. > L > The drawback to this approach is that in the case of duplicate file names,J > the one you get will be in the directory which is mentioned first in the3 > searchlist, not necessarily the most recent file.e > 2 > --Keith Lewis              klewis {at} mitre.org@ > The above may not (yet) represent the opinions of my employer. >     O Another issue with this approach is all new files will be created in the first  F entry in the search list.  In Keith's example that would be Directory P USER:[USER1.PROJECT].  Note that if all access is read, then it isn't an issue. J   Also, if writers would still use the specific directory, then you could $ control where new files are created.  N More detail required, and answers would be much easier if you were a bit more ( specific on what you hope to accomplish.     Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road- Vanderbilt, PA  15486    ------------------------------    Date: 27 Oct 2003 15:46:25 -06004 From: kuhrt@nospammy.encompasserve.org (Marty Kuhrt)D Subject: Re: swishesi -  no results (malformed header error message)3 Message-ID: <7kyfCyOPEn+w@eisner.encompasserve.org>1  c In article <23088ca1.0310270933.22d524ab@posting.google.com>, pmartyn@csc.com (Phil Martyn) writes:mH > I'm built an index using the swish-e port successfully on a DS10 underE > OpenVMS 7.3-1. However, I want to interrogate it using the swishesi / > CGI interface. I've used the demo example at:qG > http://wasd.vsm.com.au/ht_root/src/swish/swishesi/index_doc.html thene@ > modified it to suit my environment and ran it from my browser.D > However, every attempt results in the same error message "InternalG > Server Error" being displayed in my browser window. A look in the logw" > files shows the following error:E > [Mon Oct 27 12:51:00 2003] [error] [client xxx.xxx.x.xxx] malformedtE > header from script. Bad header=.: /apache$root/cgi-bin/swishesi.EXE  > A > Anybody have any experience implementing this. Anybody have anyt8 > pointers as to what I'm doing wrong? Thanks in advance  @ I haven't worked on the swishesi interface, but I have seen thisA type of error before in my Apache logs.  This usually occurs when.= you don't output the Content-type: as the first thing in yourgA POST ACTION program (the program defined in the HTML FORMs actions paramater).u  7 Since you didn't give any information about what you're 3 swishesi.exe program outputs, I give you an example ; test_post.html file and a test_post.cgi and it might give a- little bit of insight. 0  6 --- TEST_POST.HTML (put in your normal html directory) <html> <title>Test Post</title> <body bgcolor="#ffffff">! <h1 align="center">Test Post</h1>1 <p>@> This is a test of posting calling a command procedure (with a . .cgi extension so that IE users can play too). </p>  @ <form name="Main" method="post" action="/cgi-bin/test_post.cgi">  / Enter some data <input type="text" name="TEXT">r <br>9 <input type="submit" name="Submit1" value="sub1_pressed">P <br>9 <input type="submit" name="Submit2" value="sub2_pressed">w <br>@ Check box <input type="checkbox" name="cb1" value="cb1_clicked">   </form>d </body>  </html>o --- TEST_POST.CGI A $! This is the test_post.com file with a .cgi extension to see ifoC $! we can get around IE's non-standard handling of .com extensions.c= $! Read and echo the query string produced by test_post.html c0 $! Output the information as text/plain for now.
 $ set noon? $ write sys$output f$fao("!AS!/!/", "Content-type: text/plain")i $ write sys$output ""s+ $ open/read/error=err_exit inp apache$inputi $ read/error=err_exit inp qs( $ write sys$output " query string: ", qs $ goto exit_coml $!
 $err_exit:5 $ write sys$output " error handling input: ", $status  $!
 $exit_com: $ close inp  $ exit --- end example cgio  ; You may need to fix up where the input and output go in thea> command procedure to to match WASD, as this example I use with CSWS (Apache).  = The important points to consider are that the .html POST williA call the .CGI and the .CGI has to handle outputting something thef? server/browser can handle.  The "Content-type: text/plain" witht? two carriage returns tells the browser that it shouldn't botherd. rendering what is coming back from the server.  ? So I'd say your swishesi.exe isn't outputting the right content ; type, if I were to make a guess based on the info you gave.a   ------------------------------    Date: 27 Oct 2003 13:40:18 -0800- From: djesys@earthlink.net (David J Dachtera)v$ Subject: Re: VMS Text Files --> Unix= Message-ID: <66a00d01.0310271340.7ff24c21@posting.google.com>   v koehler@eisner.nospam.encompasserve.org (Bob Koehler) wrote in message news:<86B5B8hI2Iio@eisner.encompasserve.org>...V > In article <e$+L0YWUD9Rr@eisner.encompasserve.org>, briggs@encompasserve.org writes: > > B > > I don't see any support in my copy of dd for ANSI labelled mag	 > > tape.g > J >    It's not built in.  You have to roll your own knowing how ANSI labels >    tapes.r  B In fact, little UN*X software supports ANSI labelled tapes. It's a foreign concept in UN*X-land.l   > I > > If you can get data from ANSI mag tape to disk, then you really don'tuE > > need dd.  Just copy the tarball onto ANSI tape at the VMS end andlC > > onto Unix disk at the Unix end.  Then extract from the archive.t > E >    IIRC a tarball was given as a suggestion.  While one could storetH >    a tarball on an ANSI labeled tape, it would be unusual and the UNIX6 >    system still wouldn't have direct support for it. > D > > If ANSI tapes won't handle binary data for you then I'd be going > > with unlabelled mag tape.2 > 5 >   ANSI tapes most certainly can handle binary data.m  D Careful there! "ANSI labelled" means exactly that: the label recordsA conform to ANSI standards. The content of the data is irrelevent.    -- David J Dachtera dba DJE Systems8   ------------------------------   Date: 27 Oct 2003 21:34:51 GMT& From: Frank da Cruz <fdc@columbia.edu>$ Subject: Re: VMS Text Files --> Unix6 Message-ID: <slrnbpr3rr.rp.fdc@sesame.cc.columbia.edu>  F In article <86B5B8hI2Iio@eisner.encompasserve.org>, Bob Koehler wrote:V : In article <e$+L0YWUD9Rr@eisner.encompasserve.org>, briggs@encompasserve.org writes: :>  A :> I don't see any support in my copy of dd for ANSI labelled mag  :> tape. : J :    It's not built in.  You have to roll your own knowing how ANSI labels :    tapes.e : G In case anyone is interested, we have some ANSI tape utilities for Unix  here:h  +   http://www.columbia.edu/kermit/utils.htmlo   - Frankr   ------------------------------    Date: 27 Oct 2003 13:49:48 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)e$ Subject: Re: VMS Text Files --> Unix3 Message-ID: <86B5B8hI2Iio@eisner.encompasserve.org>t  T In article <e$+L0YWUD9Rr@eisner.encompasserve.org>, briggs@encompasserve.org writes: > @ > I don't see any support in my copy of dd for ANSI labelled mag > tape.i  H    It's not built in.  You have to roll your own knowing how ANSI labels	    tapes.n  G > If you can get data from ANSI mag tape to disk, then you really don't C > need dd.  Just copy the tarball onto ANSI tape at the VMS end andmA > onto Unix disk at the Unix end.  Then extract from the archive.e  C    IIRC a tarball was given as a suggestion.  While one could store F    a tarball on an ANSI labeled tape, it would be unusual and the UNIX4    system still wouldn't have direct support for it.  B > If ANSI tapes won't handle binary data for you then I'd be going > with unlabelled mag tape.   3   ANSI tapes most certainly can handle binary data.e   ------------------------------  % Date: Mon, 27 Oct 2003 15:53:36 -0800d# From: "Tom Linden" <tom@kednos.com>C$ Subject: RE: VMS Text Files --> Unix9 Message-ID: <CIEJLCMNHNNDLLOOGNJIAEGPIFAA.tom@kednos.com>u  / Google on ansitape. there is freeware available,   >-----Original Message-----.C >From: Bob Koehler [mailto:koehler@eisner.nospam.encompasserve.org],( >Sent: Monday, October 27, 2003 11:50 AM >To: Info-VAX@Mvb.Saic.Com% >Subject: Re: VMS Text Files --> Unixb >f >p5 >In article <e$+L0YWUD9Rr@eisner.encompasserve.org>, u! >briggs@encompasserve.org writes:o >> .A >> I don't see any support in my copy of dd for ANSI labelled magc >> tape. >cI >   It's not built in.  You have to roll your own knowing how ANSI labelsy
 >   tapes. >mH >> If you can get data from ANSI mag tape to disk, then you really don'tD >> need dd.  Just copy the tarball onto ANSI tape at the VMS end andB >> onto Unix disk at the Unix end.  Then extract from the archive. >dD >   IIRC a tarball was given as a suggestion.  While one could storeG >   a tarball on an ANSI labeled tape, it would be unusual and the UNIXo5 >   system still wouldn't have direct support for it.e >aC >> If ANSI tapes won't handle binary data for you then I'd be goingh >> with unlabelled mag tape. >e4 >  ANSI tapes most certainly can handle binary data. >i >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com).nB >Version: 6.0.530 / Virus Database: 325 - Release Date: 10/22/2003 >  ---i& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).A Version: 6.0.530 / Virus Database: 325 - Release Date: 10/22/2003.   ------------------------------  # Date: Tue, 28 Oct 2003 05:24:01 GMTm+ From: "David Pikcilingis" <dcpik@bosbc.com>e$ Subject: Re: VMS Text Files --> Unix. Message-ID: <R3nnb.46660$e01.121374@attbi_s02>  E Boston Business Computing produces and sells VMS style tools for UNIXtI including Vbackup, a VAX BACKUP emulator that can restore VAX BACKUP save J sets on UNIX and can also create save sets on UNIX that can be restored by VAX BACKUP.e  H All of the data could be backed up onto a tape using VMS BACKUP and then* restored on the UNIX system using Vbackup.  + Vbackup is available for most UNIX systems.n  > There are more details available at WWW.BOSBC.com/vbackup.html9 There is a PDF version of the Vbackup manual available at' www.bosbc.com/documentst  . For more information email  sales at bosbc.com   Regards,   David Pikcilingish
 www.bosbc.coms    * "JJ" <jjnojack@yahoo.com> wrote in message6 news:8c7decf3.0310231030.d57989d@posting.google.com...	 > Hi All,  >dG > I have about 25 gig worth of data that I need to put on a tape from asC > vms system that is readable and useable on an unix system. I havenF > tried vmstar and it doesn't write to the tape. The version of VMSTARH > is 3-4.1. VMSTAR will let me however make a huge tar ball on the disk.E > Once I have all the files in a large tarball on the disk, how can I.H > transfer it to a dlt device, so that it can be read on an unix system? >l" > Any help is greatly appreciated. >. > JJ   ------------------------------  % Date: Tue, 28 Oct 2003 11:32:42 +0800s/ From: "Fred Jiang" <fred.jiang@tianjin.mot.com>.+ Subject: Who can help me about this trouble + Message-ID: <bnko3j$q1q$1@newshost.mot.com>h   Friends,  F I configure the raid disks on the vms console (alpha box) and it showsK successfull. When I boot  the box, Console message shows the scan the disks K and I see the new configured disks. But I can't see disks when VMS 7.2-1 uplJ using "$show device d". Normally, I can see draxxx: but now nothing on it.3 Anybody know it, Please help me. Thanks in advance.e   ------------------------------    Date: 27 Oct 2003 17:05:00 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)r* Subject: Re: [TCPware V5.6-2] DST Change ?3 Message-ID: <mTdEOrq9b5ge@eisner.encompasserve.org>a  W In article <3f9d222a$0$257$636a55ce@news.free.fr>, Didier Morandi <no@spam.com> writes:p > Michael Unger wrote: > F >> The "Proposal for a Directive" still says "GMT" -- hasn't that been& >> replaced with "UTC" many years ago? > ! > It was, and here is the reason:P   > which translates to: > G > GMT = solar time i.e. 40,000 years ago discovery, not really accuratey  > UTC = atomic time, much better  H I run my VMS systems on GMT, _not_ UTC.  To imply greater accuracy would( be wrong.  I know some of you do better.   ------------------------------   End of INFO-VAX 2003.597 ************************