1 INFO-VAX	Sat, 26 Nov 2005	Volume 2005 : Issue 660       Contents:4 Re: CSWS PHP 1.3 and GD support (PHP Version 4.3.10)* Re: Decent alpha system for OpenVMS newbie* Re: Decent alpha system for OpenVMS newbie* Re: Decent alpha system for OpenVMS newbie* Re: Decent alpha system for OpenVMS newbie% DECwindows on a graphics-less machine  moving Apache... Re: moving Apache...% Suggestion for VMS web site (and FAQ)  Re: System services and DCL  Re: System services and DCL  Re: T4 Graphs via TLviz , Re: Vaxstation 3100 1gig limit & MOP booting, Re: Vaxstation 3100 1gig limit & MOP booting, Re: Vaxstation 3100 1gig limit & MOP booting, Re: Vaxstation 3100 1gig limit & MOP bootingM Re: Weird screen color ... greenish screens likely card-video incompatibility M Re: Weird screen color ... greenish screens likely card-video incompatibility   F ----------------------------------------------------------------------  % Date: Sat, 26 Nov 2005 17:52:41 +1030 * From: Mark Daniel <mark.daniel@vsm.com.au>= Subject: Re: CSWS PHP 1.3 and GD support (PHP Version 4.3.10) / Message-ID: <4388084d$1@duster.adelaide.on.net>    Peter Weaver wrote: 9 > "Mark Daniel" <mark.daniel@vsm.com.au> wrote in message + > news:43875cea$1@duster.adelaide.on.net...  > ? >>If my reporting utility is correct this seems rather limited:  >> >>     * GD support: yes" >>     * GD Version: 2.0 or higher >>     * FreeType Support: no  >>     * T1Lib Support: no >>     * GIF Read Support: no  >>     * GIF Create Support: no  >>     * JPG Support: no >>     * PNG Support: no >>     * WBMP Support: no  >>     * XBM Support: no- >>     * JIS-mapped Japanese Font Support: no  >>...  >  > K > Thank you, I posted the same thing on the VAMP board but nobody responded   I I think with a small community such as that supporting VMS that it is in  E that communitys own interest to try and consolidate its resources as   much as possible.   " The reverse seems to be happening.3 VAMP, HPs ITRC, c.o.v., private BBSs, and so forth.   I I have also posted this to the ITRC.  Not that it has a better interface  A than c.o.v. (far from  it), just because the s/n ratio is better.   5 Pity about the public USENET.  Just my AU$0.05 worth.   J > with either yes or no, so I started wondering if it was just me. I triedN > recompiling PHP_GD using HAVE_LIBJPEG, it compiles with just one InformationB > error, but GD_INFO() reports the same thing. If I recompile withJ > HAVE_LIBFREETYPE I get a lot of errors in GDFT.C and PHP_GD doesn't evenM > load. Not being a C programmer I'm not sure how to fix all the errors. BTW: L > I have recompiled with the default HAVE_* and PHP_GD works the same as the> > original version, so I assume my build procedure is correct.   ------------------------------  + Date: Sat, 26 Nov 2005 10:53:32 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)3 Subject: Re: Decent alpha system for OpenVMS newbie $ Message-ID: <dm9erc$u3q$1@online.de>  F In article <1132913184.792139.259920@g14g2000cwa.googlegroups.com>, "H# Vlems" <hvlems@freenet.de> writes:    G > check Ebay for Digital Server auctions. The Digital Server 3000, 5000 G > and 7000 series are equivalent to the AlphaServer 800, 1200 and 4100. H > These so called white box Alpha's were intended to run WindowsNT only,F > but a small (and easy to apply) software modification makes them run > VMS and Tru64.    D I second this recommendation.  The modification is a one-time thing G involving a line or two you type in at the console.  Runs Mozilla fine.   ' Look into the "OSU" web server as well.    ------------------------------  + Date: Sat, 26 Nov 2005 10:55:01 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)3 Subject: Re: Decent alpha system for OpenVMS newbie $ Message-ID: <dm9eu5$u3q$2@online.de>  B In article <1132927692.524319.87190@g47g2000cwa.googlegroups.com>,. "jfragemann" <jfragemann@hotmail.com> writes:    > A Digital Server 5000  > Part number: FR-K8F5W-AA >  >     * Alpha 5/533MHz CPU >     * 128MB Memory >     * 3 x 4GB SCSI Discs >     * Graphics Card 
 >     * CDRom  >     * Floppy Disc  >  > OR >  > A Digital Server 3000  > Part number: FR-K7F4W-WA >  >     * Alpha 500MHz CPU >     * 256MB Memory >     * 4 x 9GB SCSI Discs >     * Mylex Raid Controller  >     * S3 Graphics Card >     * DE500 Ethernet
 >     * CDRom  >     * Floppy Disc  >     * No O/S?  > B > As a newcomer, I have no idea which system is perferrable to runD > OpenVMS on. Also, I understand that they would need to be patched. > G > Well, "5000" sounds cooler and better, and the enclosure looks nicer, 7 > but choosing a system based on that would be lame ;-)   G You definitely want the 256 MB for Mozilla.  I don't think 128 MB will  < be enough.  512 would be better (and definitely sufficient).   ------------------------------    Date: 26 Nov 2005 09:30:40 -0800, From: "rcyoung" <rcyoung@aliconsultants.com>3 Subject: Re: Decent alpha system for OpenVMS newbie C Message-ID: <1133021613.801552.264720@o13g2000cwo.googlegroups.com>   F While not an Alpha, the SIMH Vax simulator can be a great VMS learningA tool while you shop for an Alpha. I have recently been giving the G simulator (runs on Alphas, Windows, OS/X, & Linux) some tests, and I am F most impressed. We have Oracle Rdb running successfully, and have usedE the C compiler successfully. The best feature is of course, ITS FREE. F Plus, you can get it now w/out having to wait. OpenVMS is most readilyF obtained through the Hobbyist program ( media ends up costing $30 US).  G Ebay is an excellent source for inexpensive Alphas. We've obtained both E an Alpha 2100 and a 2100A off ebay for only a couple of hundred each. F The shipping ended up costing as much as the system n each case ( theyG are heavy). A smaller system (and less expensive to ship) is a 2000/axp * which is about the size of a standard PC .   ------------------------------    Date: 26 Nov 2005 09:33:04 -0800, From: "rcyoung" <rcyoung@aliconsultants.com>3 Subject: Re: Decent alpha system for OpenVMS newbie B Message-ID: <1133022049.617784.35820@g43g2000cwa.googlegroups.com>  G As a way of learning OpenVMS, try looking at the SIMH Vax simulator. It 8 runs on Linux, OS/X, Windows, and even on Alpha OpenVMS.  A I have been testing it on OS/X and I am impressed. We have Oracle F (formerly DEC) Rdb running, and have compiled programs successfully on it.   D Best of all, its FREE. You still need a copy of Vax OpenVMS, but you; can get one through the Hobbyist program for about $30 USD.    ------------------------------  % Date: Sat, 26 Nov 2005 06:21:06 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> . Subject: DECwindows on a graphics-less machine, Message-ID: <438844FE.43CA8C24@teksavvy.com>  B If I have a server that is without graphics card, is there a magicD incantation during startup to cause DECwindows software to started /G INSTALLed, but no X-server started ? (since there is no graphics head).   ? Essentially, I'd like to be able to do SET DISPLAY and run decw J applications on that graphics-less node to be  displayed on a workstation.  D I had once tried this on my all mightly Microvax II, but the startup@ procedure complained bitterly about a missing graphics card, andB subsequent SET DISPLAY complains about a no-such-device available.  C Is it just a question of manually doing a SYSGEN CONNECT command to ! create the WSA0 template device ?    ------------------------------  % Date: Sat, 26 Nov 2005 07:27:56 -0500 ) From: "Neil Rieck" <n.rieck@sympatico.ca>  Subject: moving Apache... 9 Message-ID: <XwYhf.7780$e43.458495@news20.bellglobal.com>    Execution phase starting ...  7 The following product will be installed to destination:   9 DEC AXPVMS VMS732_UPDATE V5.0 DISK$ALPHASYS:[VMS$COMMON.]     = %PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPHASYS   M -PCSI-E-REQVOLSPC, 405085 blocks required; 339260 blocks free; -65825 blocks   net   D Terminating is strongly recommended. Do you want to terminate? [YES]  
 ##########  K We need to get Apache off our system disk (development + production). This  K weekend I was able to get OpenVMS-7.3-2 onto our development system (after  G some extreme purging of our system disk) but I was not able to install  	 UPDATE-5.    We must do this on KAWC09 ) KAWC15 should be kept in sync with KAWC09 J Because Apache content is on the system disk, we are not backing up those  files.   Neil @ home    ------------------------------  % Date: Sat, 26 Nov 2005 08:06:33 -0500 ) From: "Neil Rieck" <n.rieck@sympatico.ca>  Subject: Re: moving Apache... 9 Message-ID: <85Zhf.7797$e43.459694@news20.bellglobal.com>   5 "Neil Rieck" <n.rieck@sympatico.ca> wrote in message  3 news:XwYhf.7780$e43.458495@news20.bellglobal.com...  > Execution phase starting ... > 9 > The following product will be installed to destination:  > ; > DEC AXPVMS VMS732_UPDATE V5.0 DISK$ALPHASYS:[VMS$COMMON.]  >  > ? > %PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPHASYS  > H > -PCSI-E-REQVOLSPC, 405085 blocks required; 339260 blocks free; -65825  > blocks net > F > Terminating is strongly recommended. Do you want to terminate? [YES] >  > ########## > M > We need to get Apache off our system disk (development + production). This  M > weekend I was able to get OpenVMS-7.3-2 onto our development system (after  I > some extreme purging of our system disk) but I was not able to install   > UPDATE-5.  >  > We must do this on KAWC09 + > KAWC15 should be kept in sync with KAWC09 L > Because Apache content is on the system disk, we are not backing up those  > files. > 
 > Neil @ home  > K I'm losing my mind. Please disregard the previous post. It was meant to go   to my colleagues at work.   
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.9 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html     ------------------------------  % Date: Sat, 26 Nov 2005 04:49:20 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> . Subject: Suggestion for VMS web site (and FAQ), Message-ID: <43882F81.F7136AA8@teksavvy.com>  ; Wanted to look for the Systems and Options Catalog archive.   H Had to use dja news to find a post by Hoff as part of the FAQ. Google'sF terrible interface shows only part of each message that is part of theH FAQ so I had to hunt for the specific message then display its source to get the text giving the URL...  # Of course, it is an old compaq URL. P         http://www.compaq.com/products/quickspecs/soc_archives/SOC_Archives.html   It should be replaced with: L http://h18000.www1.hp.com/products/quickspecs/soc_archives/SOC_Archives.html    C Also, It should be on the VMS web site on its front page in the VMS 9 resources or information lists at the bottom of the page.    Another suggestion:   H Instead of having to reference "http://h18000.www1.hp.com/products...."   O it would be nice if one could simply say http://www.hp.com/go/vms/products...."   D This way, it would provide a long term archive of the correct URL inC google and elsewhere no matter what name individual web servers are  given.      G *I* knew that the SOC was available somewhere because I remember seeing G it mentioned in comp.os.vms. Imagine a customer or new hobbyist for VMS G who wants to buy old DEC hardware and doesn't know those catalogs still   exist, he would never find them.   ------------------------------  % Date: Sat, 26 Nov 2005 13:42:44 +0100 & From: Paul Sture <paul.sture@decus.ch>$ Subject: Re: System services and DCL, Message-ID: <3ur3i3F12he0mU1@individual.net>   Jeff Cameron wrote: L > On 11/22/05 9:31 PM, in article 4383FE99.AB5E93E1@teksavvy.com, "JF Mezei"' > <jfmezei.spamnot@teksavvy.com> wrote:  >  >  >>Larry Kilgallen wrote: >>9 >>>Perhaps you could outline the behavior you expect for:  >>> ( >>>        F$CALLSYS("CMKRNL",arg1,arg2) >>> 6 >>>The contents of both arg1 and arg2 are of interest. >> >>Simple.... >>F >>arg1: the name of a DCL subroutine label. All statements inside thatI >>subroutine until the RETUN will execute in kernel mode :-) A DCL syntax $ >>error crashes the whole system :-) >>F >>arg2: a string containing coma delimited list of arguments which are. >>passed to the subroutine as P1, P2, P3 etc). >> >>I >>Seriously, not all system services/ RTL can logically be mapped to DCL. F >>But there might be a lot which could be used. But perhaps individualI >>lexical implementation is a better way. Shirley the VMS engineers would  >>have discussed this ?  > K > How would you construct complex data structures such as Item lists, which * > are common arguments to system services? >   H A selection of the LIB$ routines might be be suitable candidates, since C they were designed to be an easier way to use system services than   calling those directly.    ------------------------------    Date: 26 Nov 2005 08:09:15 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) $ Subject: Re: System services and DCL3 Message-ID: <DSZQs17njrvW@eisner.encompasserve.org>   U In article <3ur3i3F12he0mU1@individual.net>, Paul Sture <paul.sture@decus.ch> writes:   J > A selection of the LIB$ routines might be be suitable candidates, since E > they were designed to be an easier way to use system services than   > calling those directly.   L And in fact "selection of" is the way that lexical functions are implemented
 currently.   ------------------------------  % Date: Sat, 26 Nov 2005 09:10:54 +0100 2 From: martin@radiogaga.harz.de (Martin Vorlaender)  Subject: Re: T4 Graphs via TLviz; Message-ID: <4388188e.524144494f47414741@radiogaga.harz.de>   ( Ken Robinson <kenrbnsn@gmail.com> wrote:I > I'm generating T4 Graphs using the program TLviz (V1.5-12). It's a nice H > interface except for one problem. There's no explanation or indicationH > of what is being displayed. For example, I selected "[MON.DSK]Rsp" forI > a particular drive. It showed a spike at a certain time. The problem is ? > that there are numbers on the left and right, but there is no 8 > indication of the units. The numbers go from 0 to 110. >  > Any help or explanation?  = AFAIK, there's no publicly available documentation for TLViz.   D That said, "MON" stands for data gathered by the MONITOR utility, soC "[MON.DSK]RespT" (as that is what I have in my data, gathered by T4 B V3.3) probably is data from some MONITOR DISK, especially as there/ are "[MON.DSK]OpRate" and "[MON.DSK]QLen", too.   H As for the units, TLViz V1.5 unfortunately re-scales the values, withoutE a hint towards the scale factor (e.g. in my data, I have a peak value F of 14326 where the actual value is 143.26). Fortunately, V1.6 (which IH got through private channels - no idea whether it's available yet) fixesA this. I'd gather it's milliseconds for the drive's response time.    [shameless plug]C For those who do not have or want a MS Windoze system: I've written C a pure Java re-implementation of TLViz called JTLviz which has been B tested to run with J2SDK V1.4.2 under OpenVMS Alpha V7.3-2. Please  see www.openvms.org for details.   cu,    Martin --  <                         | Martin Vorlaender | OpenVMS rules!1  OpenVMS: Where do you  | work: mv@pdv-systeme.de D  want to BE today?      |   http://www.pdv-systeme.de/users/martinv/8                         | home: martin@radiogaga.harz.de   ------------------------------  % Date: Sat, 26 Nov 2005 07:30:08 -0800 # From: "Tom Linden" <tom@kednos.com> 5 Subject: Re: Vaxstation 3100 1gig limit & MOP booting ( Message-ID: <ops0utcih3zgicya@hyrrokkin>  . On Fri, 25 Nov 2005 20:22:17 -0500, JF Mezei  % <jfmezei.spamnot@teksavvy.com> wrote:   J > I understand that the firmware in the Vaxstation 3100 is limited to 1gigH > disks, and that when you boot from the disk, since the disk is mountedG > by the firmware code, the 1gig limit exists even once VMS has fully   	 > booted.  > J > But if you boot from ethernet, is it correct to assume that you can then > have the disk of any size ?  > G > How difficult would it be to modify the boot process so that it would A > just mount the vaxstation's disk and point the logicals so that G > everything else executes from the disk instead of over the ethernet ?  > D > Is it correct to state that the first DCL that executes during theI > booting process is done from STARTUP.COM ? So would it be a question of H > hacking the STARTUP.COM on that system's root on the boot node to justI > mount the disk and then invoke the real STARTUP.COM on that drive after D > making sure already defined logicals such as SYS$DISK poing to the > vaxstation's drive ?   http://groups.google.com/group/comp.os.vms/browse_thread/thread/75699a8071f5d7f1/aa745c1ab653cf19?lnk=st&q=wolfgang+moeller+rom&rnum=2#aa745c1ab653cf19    ------------------------------  % Date: Sat, 26 Nov 2005 11:38:29 -0500 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>5 Subject: Re: Vaxstation 3100 1gig limit & MOP booting - Message-ID: <43884935.14404.198F50@localhost>   * On 26 Nov 2005 at 2:14, John Santos wrote:3 > Remember the 1GB limit *ONLY* applies to booting.   D The issue is crashing, not booting.  If the system bugchecks, it'll B trash the system disk.  It's all explained in the VMS FAQ (off of  www.hp.com/go/vms).   H > BTW, does anyone know if DOSD (? - dump file off system disk) works on% > a VS3100 on a bigger-than-1GB drive   ) It doesn't -- DOSD only works in Alpha...   
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com) "OpenVMS, when downtime is not an option"    ------------------------------  + Date: Sat, 26 Nov 2005 18:12:16 +0000 (UTC) 7 From: moroney@world.std.spaamtrap.com (Michael Moroney) 5 Subject: Re: Vaxstation 3100 1gig limit & MOP booting ( Message-ID: <dma8i0$jfc$2@pcls4.std.com>  4 "Stanley F. Quayle" <squayle@insight.rr.com> writes:  + >On 26 Nov 2005 at 2:14, John Santos wrote: 4 >> Remember the 1GB limit *ONLY* applies to booting.  E >The issue is crashing, not booting.  If the system bugchecks, it'll  C >trash the system disk.  It's all explained in the VMS FAQ (off of   >www.hp.com/go/vms).  G The issue is crashing AND booting.  The console code can read and write D only to the first 1GB of the disk.  If it tries to read in a portionC of VMS that's not in the first 1GB, it'll read the wrong blocks and E likely won't boot.  If the dumpfile isn't the first 1GB, a crash dump D will write to the wrong blocks and trash the drive (or at least many files).    ------------------------------  + Date: Sat, 26 Nov 2005 18:29:15 +0000 (UTC) 7 From: moroney@world.std.spaamtrap.com (Michael Moroney) 5 Subject: Re: Vaxstation 3100 1gig limit & MOP booting ( Message-ID: <dma9hr$jfc$3@pcls4.std.com>  / JF Mezei <jfmezei.spamnot@teksavvy.com> writes:   I >I understand that the firmware in the Vaxstation 3100 is limited to 1gig G >disks, and that when you boot from the disk, since the disk is mounted L >by the firmware code, the 1gig limit exists even once VMS has fully booted.  G No.  Once VMS is up, the VMS SCSI driver is used, which, of course, can  handle larger drives just fine.   I >But if you boot from ethernet, is it correct to assume that you can then  >have the disk of any size ?  5 Yes, since the console SCSI driver is never involved.   F >How difficult would it be to modify the boot process so that it would@ >just mount the vaxstation's disk and point the logicals so thatF >everything else executes from the disk instead of over the ethernet ?  E Another way is to insure that everything accessed by the console code G is in the first 1GB of a larger drive.  To do this you'll have to do an ? $ INIT /INDEX=BEGIN, and have most stuff in SYS$LDR and much in D SYS$SYSTEM, particularly the dump file and the directories (SYSn.DIRE and VMS$COMMON.DIR) in the first 1GB.  Of course upgrades to VMS will 5 break everything unless you put the new files "back".   C Someone I know actually made a dummy file that consumed the rest of D the first 1GB during normal usage, and when it was time to patch or C upgrade VMS, this file would be deleted and another one created to  H consume everything _but_ the first 1GB, the upgrade performed (anything H new was forced into the first 1GB), then this dummy file stuff reversed.   ------------------------------    Date: 26 Nov 2005 10:04:10 -0800( From: "pbritto" <britto.paulo@gmail.com>V Subject: Re: Weird screen color ... greenish screens likely card-video incompatibilityC Message-ID: <1133028250.690055.196260@z14g2000cwz.googlegroups.com>   > I changed the decw$private_server_setup.com, I uncommented theF decw$default_visual_class = "3,4,0" to decw$default_visual_class = "3"E in order to set my video to PseudoColor (whatever it means) because I < was having problems installing this software called VXL. The. decw$default_visual_class was commented in theE decw$private_server_setup.com (in fact it was template before, when I F uncommented it I rename it .com), but it still green. One thing that IE noticed, I changed that because this software support told me to, but D before that, for troubleshooting he asked me to issue a command thatF said the default video setting was 1024x1248, something very high res,9 but this screen doesn't look this high res in DECWindows.    ------------------------------    Date: 26 Nov 2005 10:04:45 -0800( From: "pbritto" <britto.paulo@gmail.com>V Subject: Re: Weird screen color ... greenish screens likely card-video incompatibilityC Message-ID: <1133024974.736726.214550@g43g2000cwa.googlegroups.com>    Hi Ray, E  I thought that would be the decw$default_visual_class, I set it to 3 D (PseudoColor) which I need it like that because of a software called. VXL (supervisory system) I had to install (theG decw$default_visual_class was commented before). So I removed the ! and E set decw$default_visual_class = "3". Could I keep it Pseudo color and B get rid of the grayscale at the same time? I don't know how eitherD decw$default_visual_class work or what PseudoColor really is, I justG was told to make it like that so then I got to install the application.     
 Ray escreveu:   7 > > I got a video which now allows me to barely see the 8 > > graphics mode, but I can see the DECWindows running.F > > It's a dark greenish screen, is this really video x  graphics card > > incompatibility? > M > Check your decw$private_server_setup.com. Your description sounds like what M > you get when the display is color, but you've defined it to grayscale. When G > decw$default_visual_class is 1, they don't drive the red and blue, so / > everything would be green on a color monitor.    ------------------------------   End of INFO-VAX 2005.660 ************************