1 INFO-VAX	Fri, 10 Nov 2006	Volume 2006 : Issue 619       Contents:3 Apache 2.1-1 and %SYSTEM-F-ACCVIO, access violation 9 Hobbyist License for VAX-VMS: producer=hp v producer=dec? = Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec? = Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec? = Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec? = Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec? C Re: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive? C Re: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive? C Re: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive?  Re: Most "classic" VMS version Re: Most "classic" VMS version Re: Most "classic" VMS version Re: Most "classic" VMS version Re: Most "classic" VMS version Re: Most "classic" VMS version Re: Most "classic" VMS version3 Performance comparison Alpha ES40 vs Itanium rx3600 # Re: Qbus scsi cards and DLT support A Re: Recommendations for a Windows client for accessing Decwindows  Re: TK50 Re: TK50# Re: Tool to convert BMP image to PS = Re: UnixAdminTalk (was: Re: illegal image section descriptor)  Re: Where to get a cable? 6 Re: writing fixed size records with one shorter record6 Re: writing fixed size records with one shorter record6 Re: writing fixed size records with one shorter record6 Re: writing fixed size records with one shorter record  F ----------------------------------------------------------------------  % Date: Fri, 10 Nov 2006 13:50:17 +0100 ' From: "Klaus-D. Bohn" <info@it-bcsb.de> < Subject: Apache 2.1-1 and %SYSTEM-F-ACCVIO, access violation7 Message-ID: <45547586$0$23651$9b622d9e@news.freenet.de>    Hello,  K i have installed Apache 2.1-1 and PHP 4.3.10 on my Itanium with OpenVMS 8.3  and i get the following error:    I64/SYSTEM> type APACHE$SWS.LOG;
 $ Set NoOn/ $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) ; %SYSTEM-F-ACCVIO, access violation, reason mask=FE, virtual : address=0000000000000000, PC=FFFFF80208AAAB10, PS=0000001B/ %TRACE-F-TRACEBACK, symbolic stack dump follows K image     module    routine               line      rel PC           abs PC ? DECC$SHR  C$SIGNAL  gsignal              27907 0000000000001130  FFFFF80208AAAB10? DECC$SHR  C$SIGNAL  raise                27996 0000000000001280  FFFFF80208AAAC60- DECC$SHR  C$SIGPENDING  decc$$deliver_signals ?                                          12457 0000000000000890  FFFFF80208C0B0E0. DECC$SHR  C$SIGPROCMASK  decc$$sigprocmask_ast?                                          12715 0000000000001880  FFFFF80208C0A810, DECC$SHR  C$$MAIN_COND_HAND  generate_signal?                                          22961 0000000000000CA0  FFFFF80208F08500, DECC$SHR  C$$MAIN_COND_HAND  decc$$cond_hand?                                          22777 00000000000006A0  FFFFF80208F07F00. DECC$SHR  C$SHELL_HANDLER  decc$$shell_handler?                                           5570 00000000000002A0  FFFFF80208616810?                                              0 FFFFFFFF803CC120  FFFFFFFF803CC120K image     module    routine               line      rel PC           abs PC ? APACHE$APU_SHR  APR_RMM  apr_rmm_free    17912 0000000000001A31  0000000000068F815 MOD_LDAP  UTIL_LDAP_CACHE_MGR  util_ald_destroy_cache ?                                          47752 00000000000015C0  0000000000A5C2906 MOD_LDAP  UTIL_LDAP_CACHE  util_ldap_cache_module_kill?                                          48051 0000000000001D60  0000000000A60550+ APACHE$APR_SHR  APR_POOLS  apr_pool_destroy ?                                          30001 0000000000001CF0  00000000001DE5A0+ APACHE$APR_SHR  APR_POOLS  apr_pool_destroy ?                                          28775 0000000000001C30  00000000001DE4E0? APACHE$HTTPD  MAIN  main                 49989 0000000000002AB0  0000000000012AB0? APACHE$HTTPD  MAIN  __main               50141 0000000000000870  0000000000010870?                                              0 FFFFFFFF80B59F20  FFFFFFFF80B59F20? DCL                                          0 000000000006B9C0  000000007AE0B9C0% %TRACE-I-END, end of TRACE stack dump 7   APACHE$WWW   job terminated at 9-NOV-2006 15:13:50.80      Accounting information: D   Buffered I/O count:               3310      Peak working set size: 45200 @   Direct I/O count:                  694      Peak virtual size: 282432>   Page faults:                      2188      Mounted volumes: 0 C   Charged CPU time:        0 00:00:00.64      Elapsed time:       0  00:00:34.92  I64/SYSTEM>      and     $ I64/SYSTEM> type APACHE$SWS0003.LOG;
 $ Set NoOn/ $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))   L proc_mutex_vmsdlm_child_init: Fname is null        <======================== ??????????????????????  ; %SYSTEM-F-ACCVIO, access violation, reason mask=FE, virtual : address=0000000000000000, PC=FFFFF80208AAAB10, PS=0000001B/ %TRACE-F-TRACEBACK, symbolic stack dump follows K image     module    routine               line      rel PC           abs PC ? DECC$SHR  C$SIGNAL  gsignal              27907 0000000000001130  FFFFF80208AAAB10? DECC$SHR  C$SIGNAL  raise                27996 0000000000001280  FFFFF80208AAAC60- DECC$SHR  C$SIGPENDING  decc$$deliver_signals ?                                          12457 0000000000000890  FFFFF80208C0B0E0. DECC$SHR  C$SIGPROCMASK  decc$$sigprocmask_ast?                                          12715 0000000000001880  FFFFF80208C0A810, DECC$SHR  C$$MAIN_COND_HAND  generate_signal?                                          22961 0000000000000CA0  FFFFF80208F08500, DECC$SHR  C$$MAIN_COND_HAND  decc$$cond_hand?                                          22777 00000000000006A0  FFFFF80208F07F00. DECC$SHR  C$SHELL_HANDLER  decc$$shell_handlerL                                           5570 00000000000002A0 FFFFF8020861 6810?                                              0 FFFFFFFF803CC120  FFFFFFFF803CC120K image     module    routine               line      rel PC           abs PC ? PHPSHR                                       0 0000000000206670  0000000000CDC670? PHPSHR                                       0 0000000000195A30  0000000000C6BA30? MOD_PHP_APACHE-2_0                           0 0000000000032870  0000000000AE8870+ APACHE$HTTPD_SHR  CONFIG  ap_invoke_handler ?                                          50695 0000000000002440  00000000002A16902 APACHE$HTTPD_SHR  HTTP_REQUEST  ap_process_request?                                          46314 0000000000000940  00000000002769407 APACHE$HTTPD_SHR  HTTP_CORE  ap_process_http_connection ?                                          46331 0000000000000A00  00000000002E01E03 APACHE$HTTPD_SHR  CONNECTION  ap_process_connection ?                                          43825 0000000000001080  00000000002CE690? APACHE$HTTPD_SHR  PREFORK  ChildCore    102669 0000000000008030  00000000002D8D30? APACHE$HTTPD_SHR  PREFORK  ap_mpm_run   102341 0000000000002260  00000000002D2F60? APACHE$HTTPD  MAIN  main                 50427 0000000000001EB0  0000000000011EB0? APACHE$HTTPD  MAIN  __main               50141 0000000000000870  0000000000010870?                                              0 FFFFFFFF80B59F20  FFFFFFFF80B59F20? DCL                                          0 000000000006B9C0  000000007AE0B9C0% %TRACE-I-END, end of TRACE stack dump 7   APACHE$WWW   job terminated at 9-NOV-2006 15:13:34.84      Accounting information: D   Buffered I/O count:               3920      Peak working set size: 76144 @   Direct I/O count:                  525      Peak virtual size: 319696>   Page faults:                      4354      Mounted volumes: 0 C   Charged CPU time:        0 00:00:00.92      Elapsed time:       0  00:00:16.17  I64/SYSTEM>       ) Does have anybody an idea what can i do ?    Thanks  	     Klaus    ------------------------------  % Date: Fri, 10 Nov 2006 15:33:58 -0000 2 From: "Nick Glazzard" <nick.glazzard@speedsix.com>B Subject: Hobbyist License for VAX-VMS: producer=hp v producer=dec?5 Message-ID: <MYudneWuO-R7BsnYnZ2dnUVZ8sydnZ2d@bt.com>   3 I'm sure I must have missed something here, but ...   L This morning I got new licenses for my VAX from the hobbyist site, that timeC of year having come around again. Everything seemed to go fine with - installing these new licenses. But I now get:   > %LICENSE-E-NOAUTH, DEC VAX-VMS is not authorized on this node.  3 (The same applies to all the layered products too).   J And this would seem to be fair comment, as the new license would appear to be for:   
 HP VAX-VMS  J The old licenses always had /PRODUCER=DEC. The new ones have /PRODUCER=HP.  F I can hardly believe that this really is the problem, however, becauseK surely many other people would have run into this already. I can't find any E mention of such a problem after (extensive) searches on the Internet.   L Any ideas would be gratefully received, as I have absolutely no idea what to	 try next!   K BTW: I tried to register with the Hobbyist Forum on www.openvmshobbyist.org I to ask this question, but on registering, something seemed to think I was I trying to send SPAM ... somehow ... Perhaps this is a good day to do some  gardening instead ... :-)    Thanks for any info or ideas.    Nick Glazzard.   ------------------------------  + Date: Fri, 10 Nov 2006 10:31:48 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)F Subject: Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec?2 Message-ID: <06111010314872_2020028F@antinode.org>  2 From: "Nick Glazzard" <nick.glazzard@speedsix.com>  @ > %LICENSE-E-NOAUTH, DEC VAX-VMS is not authorized on this node.  <    Assuming that you actually got the things registered, ...  F    PAKs with the NOSHARE option (like VAX-VMS) may need to have a nodeF name specified.  "@ SYS$UPDATE:VMSLICENSE.COM", and look for something> like "MODIFY an existing Product Authorization Key".  I quote:  <    Use the MODIFY option to change the following information1    for a product currently in a license database.   D         o  The number of license units available from a license that)            includes the MOD_UNITS option.   @         o  The node or nodes in a VMScluster that can access the            licensed product.    5 > (The same applies to all the layered products too).   .    Really?  So you didn't get them registered?  H    Exactly what have you done so far, and what happened when you did it?  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------    Date: 10 Nov 2006 08:58:35 -0800; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> F Subject: Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec?B Message-ID: <1163177915.663708.11720@k70g2000cwa.googlegroups.com>   Steven M. Schweda wrote:4 > From: "Nick Glazzard" <nick.glazzard@speedsix.com> > B > > %LICENSE-E-NOAUTH, DEC VAX-VMS is not authorized on this node. > > >    Assuming that you actually got the things registered, ... > H >    PAKs with the NOSHARE option (like VAX-VMS) may need to have a nodeH > name specified.  "@ SYS$UPDATE:VMSLICENSE.COM", and look for something@ > like "MODIFY an existing Product Authorization Key".  I quote: > > >    Use the MODIFY option to change the following information3 >    for a product currently in a license database.  > F >         o  The number of license units available from a license that+ >            includes the MOD_UNITS option.  > B >         o  The node or nodes in a VMScluster that can access the >            licensed product. >  > 7 > > (The same applies to all the layered products too).  > 0 >    Really?  So you didn't get them registered? > J >    Exactly what have you done so far, and what happened when you did it? > J > ------------------------------------------------------------------------ > 5 >    Steven M. Schweda               sms@antinode-org 6 >    382 South Warwick Street        (+1) 651-699-9818 >    Saint Paul  MN  55105-2547     E My most recent VAX and Alpha license PAK's (generated on 27-Oct-2006) E have DEC as the producer while the Itanium license PAKs (generated on = 7-NOV-2007) have HP as the producer.  Perhaps there was a bug G introduced when the Itanium license generation was added to the script. F  I also haven't tried to load the Itanium licenses yet so I don't know' if there is a problem with them or not.   A I would think that the product name change from DEC VAX-VMS to HP G VAX-VMS would be a real problem, but I'm not an expert on license PAKs. G  Though Steven is right about the NO_SHARE... if your system is part of E a cluster then you need to modify the PAK after installing it to bind D it to a certain system name or else it won't load - I know this from experience. ;-)   C The fact that the layered products didn't work either is bothersome E since they aren't limited by the NO_SHARE option.  The new licenses I ? have have a load command after each, I'm assuming yours do too. F Otherwise a $ License Load * command should be given after running the license script.   E If you can't get a message on the OpenVMS Hobbyist Forum then sending @ an email to Mr. Cathey at Montagar is also good.  He's been very helpful to me in the past.  #   Hope something in that lot helps.      John H. Reinhardt    ------------------------------  % Date: Fri, 10 Nov 2006 17:33:31 -0000 2 From: "Nick Glazzard" <nick.glazzard@speedsix.com>F Subject: Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec?+ Message-ID: <s7adnVr2JsxyKsnYRVnyvQ@bt.com>   E Thanks John, that is very helpful. I'm actually not certain about the L layered products. I thought I saw some OPCOM messages about LICENSE-E-NOAUTHA for TCPIP things, but I can't see them in the operator.log files.   I My VAX machine isn't part of a cluster (unfortunately - I've got an Alpha C too, but I've not found the time to get the two clustered ... yet).    I may try emailing Mr. Cathey.   Thanks,    Nick.   + <johnhreinhardt@yahoo.com> wrote in message < news:1163177915.663708.11720@k70g2000cwa.googlegroups.com... >  > Steven M. Schweda wrote:6 > > From: "Nick Glazzard" <nick.glazzard@speedsix.com> > > D > > > %LICENSE-E-NOAUTH, DEC VAX-VMS is not authorized on this node. > > @ > >    Assuming that you actually got the things registered, ... > > J > >    PAKs with the NOSHARE option (like VAX-VMS) may need to have a nodeJ > > name specified.  "@ SYS$UPDATE:VMSLICENSE.COM", and look for somethingB > > like "MODIFY an existing Product Authorization Key".  I quote: > > @ > >    Use the MODIFY option to change the following information5 > >    for a product currently in a license database.  > > H > >         o  The number of license units available from a license that- > >            includes the MOD_UNITS option.  > > D > >         o  The node or nodes in a VMScluster that can access the  > >            licensed product. > >  > > 9 > > > (The same applies to all the layered products too).  > > 2 > >    Really?  So you didn't get them registered? > > L > >    Exactly what have you done so far, and what happened when you did it? > > L > > ------------------------------------------------------------------------ > > 7 > >    Steven M. Schweda               sms@antinode-org 8 > >    382 South Warwick Street        (+1) 651-699-9818! > >    Saint Paul  MN  55105-2547  >  > G > My most recent VAX and Alpha license PAK's (generated on 27-Oct-2006) G > have DEC as the producer while the Itanium license PAKs (generated on ? > 7-NOV-2007) have HP as the producer.  Perhaps there was a bug I > introduced when the Itanium license generation was added to the script. H >  I also haven't tried to load the Itanium licenses yet so I don't know) > if there is a problem with them or not.  > C > I would think that the product name change from DEC VAX-VMS to HP I > VAX-VMS would be a real problem, but I'm not an expert on license PAKs. I >  Though Steven is right about the NO_SHARE... if your system is part of G > a cluster then you need to modify the PAK after installing it to bind F > it to a certain system name or else it won't load - I know this from > experience. ;-)  > E > The fact that the layered products didn't work either is bothersome G > since they aren't limited by the NO_SHARE option.  The new licenses I A > have have a load command after each, I'm assuming yours do too. H > Otherwise a $ License Load * command should be given after running the > license script.  > G > If you can't get a message on the OpenVMS Hobbyist Forum then sending B > an email to Mr. Cathey at Montagar is also good.  He's been very > helpful to me in the past. > % >   Hope something in that lot helps.  >  >   John H. Reinhardt  >    ------------------------------  % Date: Fri, 10 Nov 2006 13:02:35 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>F Subject: Re: Hobbyist License for VAX-VMS: producer=hp v producer=dec?) Message-ID: <ej2err$1ck0$1@pyrite.mv.net>   F This is an error in the licenses being generated at the Hobbyist site.  I I expect David C. will wander through and see this message, but I'd have  E to assume here that part(s) of the DCL commands that are needed when  C generating licenses for OpenVMS I64 were erroneously activated for   OpenVMS VAX.  H AFAIK, licenses with a producer of HP won't work on most (all?) OpenVMS D VAX versions, and there's no ECO to add this.  These licenses won't  work, in simplest terms.   ------------------------------  % Date: Fri, 10 Nov 2006 09:55:25 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>L Subject: Re: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive?) Message-ID: <ej23st$1964$1@pyrite.mv.net>    Steven M. Schweda wrote:G >    Is there some semi-convenient way (in a program) to distinguish an J > IDE/ATA(PI) drive from a SCSI drive, other than looking for "DK" or "DQ" > in the device name?  > B >    The only thing I've found so far is the dev$v_scsi bit in theI > device-dependent characteristics (2), but it appears to be set for both  > device types.   @    ATA is different from ATAPI.  (The former is a comparatively H primitive device-level register-based I/O interface for magnetic disks, F while the latter is a packetized SCSI command set for removable media > and devices that require more control than available via ATA.)  G    What might you be up to here?  (I have written stuff that needed to  H know the difference, but it's fairly rare to need to differentiate.  If H you are aiming IO$_DIAGNOSE at the device, you do tend to need to know.)  ,    What sorts of devices are you looking at?  &    What OpenVMS releases are involved?  L    Are you using DEV$V_SCSI or DEV$M_SCSI here?  (I've made this mistake...)  ?    Do you (expect to) need to add USB to the particular fracas?    ------------------------------  + Date: Fri, 10 Nov 2006 09:52:56 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)L Subject: Re: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive?2 Message-ID: <06111009525688_2020028F@antinode.org>  8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>  B >    ATA is different from ATAPI.  (The former is a comparatively J > primitive device-level register-based I/O interface for magnetic disks, H > while the latter is a packetized SCSI command set for removable media @ > and devices that require more control than available via ATA.)      Ok.  ATAPI, then.  I >    What might you be up to here?  (I have written stuff that needed to  J > know the difference, but it's fairly rare to need to differentiate.  If J > you are aiming IO$_DIAGNOSE at the device, you do tend to need to know.) > . >    What sorts of devices are you looking at? > ( >    What OpenVMS releases are involved?  G    Just an update to cdrtools/cdrecord, so CD- and DVD-writing drives.  B Any VMS version where I can get the stuff to work without too muchE trouble.  (So far, if you don't need large-file support for a DVD, it  should still work on a VAX.)  G    Currently cdrecord uses that annoying "dev=i,j,k" (where i, j, and k F are integers) scheme to specify a device, and I was trying to allow anE ordinary device name instead, but the code needs to sense ATAPI-ness, B and currently it looks for the values of "i" which it maps to "DQ"A devices.  Rather than trying to map ordinary device names back to D "i,j,k", I was looking for a more general test (especially useful if% some new device type were specified).   N >    Are you using DEV$V_SCSI or DEV$M_SCSI here?  (I've made this mistake...)  G    So far, I've just looked at DEVCHAR2 using DCL, and as I review what B I was doing, I appear to have been looking at the wrong device (anH external SCSI CD-R/RW drive instead of the internal IDE/ATAPI drive), so1 dev$v_scsi may actually do what I want after all.   A >    Do you (expect to) need to add USB to the particular fracas?   C    I hadn't thought about it, but I suppose that it would be a good D idea.  Should I assume that a USB drive would appear as a "DN" (likeH "DNA0:"), and that it should be treated as an ATAPI?  Or is it all worse
 than that?  B    I'm not sure that I can actually avoid always having an "i,j,k"G mapping for devices, so now would probably be a good time to add a "DN" G mapping.  (Or to convert some of the current 8 = DQA, 9 = DQB, ... 33 = F DQZ assignments to DNA, DNB, and so on.  I haven't tried more than oneB USB card.  Is there such a thing as a "DNBxx"?  As I've never seenG anything beyond DQB on my junk, I tend to imagine that most of those DQ G assignments are useless, but perhaps an IA64 system could get an add-in  IDE card to spoil my dreams?)       Everything's complicated.  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------  % Date: Fri, 10 Nov 2006 13:40:03 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>L Subject: Re: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive?) Message-ID: <ej2h23$1d99$1@pyrite.mv.net>    Steven M. Schweda wrote:  6 >    Currently cdrecord uses that annoying "dev=i,j,k"  I    If you dig around in the source code, you'll find that the values are  G mapped and re-assembled into an OpenVMS device specification deep down  . at the bottom of the cdrecord.exe source code.    O >>    Are you using DEV$V_SCSI or DEV$M_SCSI here?  (I've made this mistake...)  > I >    So far, I've just looked at DEVCHAR2 using DCL, and as I review what D > I was doing, I appear to have been looking at the wrong device (anJ > external SCSI CD-R/RW drive instead of the internal IDE/ATAPI drive), so3 > dev$v_scsi may actually do what I want after all.   F    Macro32 and Bliss tend to like the $V.  Macro32, Bliss and various D other languages can and do use $M.  ($V is the bit offset.  $M is a I bitmask.)  If you use the $V bit offset within your DCL, I'll assume you  F are using a lexical function (eg: f$cvui) to extract the bit, or that C you are using the $M value or a bit-shift of the $V value to get a  G bitmask) and the .AND. operator.  (upon grok, do please ignore this --  F but then, it's not often that an opportunity to mention f$cvui/f$cvsi  comes up. :-)  )  D    You're wading into a comparatively weak part of OpenVMS here, as G OpenVMS does not provide a mechanism that reports device capabilities.  I (The traditional device-specific bit flags and the device type and class  H codes are limited in their capabilities.)  You can lob SCSI commands at H the device and retrieve this data yourself, but OpenVMS doesn't present E this data to the user.  There's no array of capabilities or features  G available to users from within the drivers, though the drivers do have  : to collect this sort of data as part of normal operations.    B >>    Do you (expect to) need to add USB to the particular fracas? > E >    I hadn't thought about it, but I suppose that it would be a good F > idea.  Should I assume that a USB drive would appear as a "DN" (likeJ > "DNA0:"), and that it should be treated as an ATAPI?  Or is it all worse > than that?  H    ATAPI is SCSI.  USB is SCSI.  SAS is SCSI.  "SATAPI" (which isn't in F particular use as yet) is (wait for it) SCSI.  And SCSI itself is, by   definition, not quite SCSI.  :-)  G    What's additionally "fun" here is that the OpenVMS driver I/O paths  I are (slightly) different for the IO$_DIAGNOSE paths.  IIRC, DN/USB works  H like DQ/ATAPI here, and uses the same IO$_DIAGNOSE paths -- the biggest G difference between DQ/ATAPI and DN/USB is that DN/USB does not provide  	 timeouts.   D >    I'm not sure that I can actually avoid always having an "i,j,k"I > mapping for devices, so now would probably be a good time to add a "DN" 
 > mapping.  F    The cdrecord.exe port that the HP folks provided includes mappings G for these, and a command procedure wrapper.  The source code should be  E on the Freeware.  (The mappings changed somewhere in the V8.* range,  F too, IIRC -- the old DQ x,y,z code was bumped upwards somewhere along 
 the line.)  D    The command option parsing code within cdrecord.exe doesn't lend D itself to fixing this, unfortunately.  Changes here are undoubtedly B quite feasible, though the command-parsing support is non-trivial.    ? > (Or to convert some of the current 8 = DQA, 9 = DQB, ... 33 = H > DQZ assignments to DNA, DNB, and so on.  I haven't tried more than oneD > USB card.  Is there such a thing as a "DNBxx"?  As I've never seenI > anything beyond DQB on my junk, I tend to imagine that most of those DQ I > assignments are useless, but perhaps an IA64 system could get an add-in  > IDE card to spoil my dreams?)   H    There are up to four DQ devices around on various systems, and there & can be DQ/IDE and DN/USB PCI adapters.  I    IIRC, the solution used by the SYS$MANAGER:CDRECORD.COM is to map the  H device values to the cdrecord.exe dev=x,y,z value.  Hugely ugly, but it H has the advantage of working.  The other approach was to supplement the H recording capabilities with the V8.3 COPY/RECORDABLE_MEDIA command, and  related tools.  C    I'd probably look to tweak the cdrecord.exe tool to implement a  H vmsdev=ddcu: command option, were I going after this source code change.   ------------------------------  % Date: Fri, 10 Nov 2006 03:57:29 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ' Subject: Re: Most "classic" VMS version 8 Message-ID: <d49dd$45543ead$cef8887a$28783@TEKSAVVY.COM>   Dave Froble wrote: >  My opinion is  C > that V7.3 is the most capable.  Guess I'm just not into antiques.     I 7.3 marks a significant decision to not make a new release fully upwards  O compatible since support for Display Postscript was removed between 7.2 and 7.3   J 7.3 brings better compatibility with Alpha VMS, especially the ability to J mount ODS-5 disks. And it is apparanetly the very last version of VMS for J vax. It is thus a current version. 5 years from now, I suspect there will # be more VAX running 5.5-2 than 7.3.    ------------------------------    Date: 10 Nov 2006 08:17:11 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ' Subject: Re: Most "classic" VMS version 3 Message-ID: <gd+GX+WtTgNH@eisner.encompasserve.org>   p In article <1163119414.850494.52710@f16g2000cwb.googlegroups.com>, "madcrow" <madcrow.maxwell@gmail.com> writes: > E > The files look to be gzipped tape images. Hopefully, one could just G > mount those in SIMH directly. Is BACKUP generally the first record on @ > the tape? I assume that tapes work differently than CDs or didH > DEC/Compaq/HP just approach the CD-ROM as a small, flat tape with lots > of space?  >   >    BACKUP makes tape savesets as files deliniated according toD    ANSI/ASCII tape labeling standards.  It makes disk saveset eitherB    as files or as single file disks.  The CDs just contain lots ofC    such files.  The gzipped files are probably from disk files, not ?    entire tape images.  To make a tape image you'ld have to add @    ANSI tape labels, each of which looks like a physical file on    a real tape.    ------------------------------  % Date: Fri, 10 Nov 2006 09:46:34 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>' Subject: Re: Most "classic" VMS version ) Message-ID: <ej23c9$190o$1@pyrite.mv.net>    madcrow wrote:  E > The files look to be gzipped tape images. Hopefully, one could just G > mount those in SIMH directly. Is BACKUP generally the first record on @ > the tape? I assume that tapes work differently than CDs or didH > DEC/Compaq/HP just approach the CD-ROM as a small, flat tape with lots > of space?   I    CDs?  Those are a construct that first appeared as distribution media  E around the V5.0 release.  (Technically yes, CD media did appear with  F OpenVMS products and such a little earlier than that.  The CD distros  went mainline at V5.0.)   D    The earliest distros were available on either magtape or on RX02 F eight inch floppy or on a disk pack.  CDs arrived over a decade later.  H    There are various ways to do this; to package up the OpenVMS distros  as zip archives.  F    Some approaches work nicely, and some, well, are going to make the G restoration and installation more difficult.  If whomever created this  G "treasure trove" used zip "-V", you're in luck.  If not, it'll be more   work to reset the attributes.   F    Do fire up unzip and see what is in the archives you have.  If you I wish assistance with the identification of the contents, please post the  ' listings that can be produced by unzip.   F    If you see VMS0%%.A, .B, .C..., and/or DECW0%%.A, .B, ... then you 3 (probably) have a zip archive of installation kits.   I    If you see something with a filename with a .BCK or .SAV or some such  I extension -- something that is probably a BACKUP saveset of some sort --  I then you'll need to unzip to extract the saveset(s), then use the BACKUP  C utility (via standalone BACKUP bootable environment or via another  J OpenVMS system) to restore the saveset, then go look to see what you have.  C    It's distinctly possible you have copies of installed disks, or  I copies of distros, or (unfortunately) just random sequences of bits with  I potentially interesting filenames...  I've seen all sorts of attempts at  0 packaging kits over the years.  Some successful.  F    The other approach here is to enlist the expertise of someone that F can more directly assist you; that can directly access and unpack and I verify the contents of this "treasure trove" of OpenVMS VAX kits for you.    ------------------------------  + Date: Fri, 10 Nov 2006 14:56:33 +0000 (UTC) 7 From: moroney@world.std.spaamtrap.com (Michael Moroney) ' Subject: Re: Most "classic" VMS version ( Message-ID: <ej23v1$80t$1@pcls6.std.com>    madcrow.maxwell@gmail.com wrote:D > I've recently come across a treasure trove of classic VMS releasesH > online. I'd LOVE to be able to try this out in SIMH (I have a hobbyistI > license, so this is all legal). I am wondering what version of VMS best H > represents it's "classic" form so that I know what the best version toH > get is. Also, does anybody know where I can find an installation guide3 > so that I can actually get it all up and running?   K Interest in a 'classic' anything implies that something about the 'classic' H version that's better than the current version, or something took a stepE backwards.  So where do you think VMS took steps backwards?  The most I obvious is killing of Alpha, and some future version of VMS won't support F it.  But that's not something VMS itself did.  A better example is theF killing of display postscript.  If you need this, newer versions won't0 cut it.  What else was a step backwards for VMS?   ------------------------------    Date: 10 Nov 2006 07:50:35 -0800$ From: "AEF" <spamsink2001@yahoo.com>' Subject: Re: Most "classic" VMS version B Message-ID: <1163173835.148982.291030@m7g2000cwm.googlegroups.com>   Richard B. Gilbert wrote: " > madcrow.maxwell@gmail.com wrote:F > > I've recently come across a treasure trove of classic VMS releasesJ > > online. I'd LOVE to be able to try this out in SIMH (I have a hobbyistK > > license, so this is all legal). I am wondering what version of VMS best J > > represents it's "classic" form so that I know what the best version toJ > > get is. Also, does anybody know where I can find an installation guide5 > > so that I can actually get it all up and running?  > >  >  > Define "classic"!   G Well, I can't give an actual definition, but perhaps the following is a 
 good example:        WordPerfect V5.1  B But I'm not sure there really is a "classic" version of VMS by any reasonable definition.  I > Others have offered 4.7, 5.5-2, 6.2 etc. as "classics" without defining F > "classic" either.  I've run most releases from V3.6 on but, being of- > sound mind, skipped 4.0, 5.0, 6.0, and 7.0.  > J > 4.7, 5.5-2 and 6.2 were all fine releases in their day but I wouldn't go' > back there (unless somebody paid me).    AEF    ------------------------------    Date: 10 Nov 2006 08:30:11 -0800- From: "Doug Phillips" <dphill46@netscape.net> ' Subject: Re: Most "classic" VMS version C Message-ID: <1163176210.324384.298630@f16g2000cwb.googlegroups.com>    Dave Froble wrote:" > madcrow.maxwell@gmail.com wrote:F > > I've recently come across a treasure trove of classic VMS releasesJ > > online. I'd LOVE to be able to try this out in SIMH (I have a hobbyistK > > license, so this is all legal). I am wondering what version of VMS best J > > represents it's "classic" form so that I know what the best version toJ > > get is. Also, does anybody know where I can find an installation guide5 > > so that I can actually get it all up and running?  > >  > I > You'll get lots of opinions.  SIMH would indicate a VAX.  My opinion is I > that V7.3 is the most capable.  Guess I'm just not into antiques.  I've I > had all I want of V2.*, V3.*, V4.*, V5.*, V6.*, and anything else prior 
 > to V7.2. >   G I so totally agree. Unless someone wants to revisit the days of PIP and F all those other little utilities whose names I've finally been able to flush from my memory.   F There's nothing to be learned from running old versions. Comparing theD source at the different version steps would be an interesting hobby,2 though, should one find himself suddenly immortal.   ------------------------------  % Date: Sat, 11 Nov 2006 02:18:35 +0800  From: prep@prep.synonet.com ' Subject: Re: Most "classic" VMS version 0 Message-ID: <87y7qjb1xg.fsf@k9.prep.synonet.com>  : Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org> writes:  E >    The earliest distros were available on either magtape or on RX02 A > eight inch floppy or on a disk pack.  CDs arrived over a decade  > later.  F And RX50s. You have not lived until you have installed VMS onto a 8200D from a LARGE pile of RX50s... It super sucks when this is onto a HSC7 disk in a room of running machines, but the manager....    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Fri, 10 Nov 2006 11:32:38 -0500 * From: "Syltrem" <syltremzulu@videotron.ca>< Subject: Performance comparison Alpha ES40 vs Itanium rx36000 Message-ID: <12l9ad84ba33tdf@corp.supernews.com>   Hi  F This is possibly not the best forum to ask this, but I can't find the  information.  L How can I compare the performance of an Alpha ES40 with 4-833Mhz CPUs to an % Integrity rx3600 with 2-1.4Ghz CPUs ?   7 Everywhere they have benchmarks with different metrics.   M I just need to know approximately how much faster the rx3600 is, compared to   my ES40 F Or how am I supposed to make a decision as to what Itanium box to get?  8 This server will run a number of things including Oracle   Thanks !   --   Syltrem L http://pages.infinit.net/syltrem (OpenVMS information and help, en franais)   ------------------------------  + Date: Fri, 10 Nov 2006 17:44:16 +0000 (UTC) , From: cdl@deeptow.ucsd.edu (Carl Lowenstein), Subject: Re: Qbus scsi cards and DLT support* Message-ID: <ej2dpg$2pk6$1@news1.ucsd.edu>  C In article <1163089404.827390.232230@h48g2000cwc.googlegroups.com>, "  <tomarsin2015@comcast.net> wrote: >HelloB >I noticed that most (well all) of my qbus scsi tape cards supportD >9-track tapes (ie TSZ05/07). I was wondering if there are/were qbusC >scsi tape controllers that would support a DLT 2000/4000 series of  >drives?  L Aren't you really saying "my qbus SCSI tape cards support SCSI tape drives"?B Then the next question should be "are there DLT SCSI tape drives".F I have a Quantum DLT VS80 with SCSI interface sitting here on my desk. There are probably othes too.        carl   --  B     carl lowenstein         marine physical lab     u.c. san diegoB                                                  clowenst@ucsd.edu   ------------------------------  # Date: Fri, 10 Nov 2006 08:45:21 GMT . From: Jack Patteeuw <jack.patteeuw@nospam.net>J Subject: Re: Recommendations for a Windows client for accessing Decwindows9 Message-ID: <B_W4h.187$Sw1.43@newssvr13.news.prodigy.com>   $ > on 5-11-2006 6:15 Gremlin wrote... >> Please?   > / > Assuming you mean a Windows X display server:   H I am currently working in a shop where we have well over 1000 copies of C Hummingbird Exceed installed to interface with VAX/VMS, Alpha/VMS,  ' Tru64, Solaris and who knows what else.   H We use it on many, many different type of PCs (laptop, low end desktops H w/integrated graphics, high-end "workstations" with 3D graphics) and on G both Win2K and WinXP.  I have seen it spin a wire frame (requires lots  F of network band width) and a shaded solid model (using the 3D upgrade ' package) with "reasonable" performance.   E This software is do "bulletproof" we are comfortably running 4 major  G version behind "production" and have not seen any issues (that weren't    self inflicted) in over 7 years.  ? Exceed even works with PuTTY/SSH for remote access through VPNs   F It is not "free", and I don't normally give any software such glowing  endorsements, but I love it    Jack   ------------------------------    Date: 10 Nov 2006 05:20:55 -0800" From: "kczwei" <kaycee@kaycee.net> Subject: Re: TK50 C Message-ID: <1163164855.546388.312550@b28g2000cwb.googlegroups.com>    Bill Gunshannon wrote:E > Anybody got TK50 drives they no longer need?  I can sure use a few.  > Spare parts too.  A I think i've got a few.  contact me. kelly domain= kaycee dot net    ------------------------------    Date: 10 Nov 2006 07:17:34 -0800  From: "Mike" <mlpoole@gmail.com> Subject: Re: TK50 B Message-ID: <1163171854.802880.178510@e3g2000cwe.googlegroups.com>  B On 'The Office' last night they said they are closing the Scranton	 branch...      :)     Bill Gunshannon wrote:E > Anybody got TK50 drives they no longer need?  I can sure use a few.  > Spare parts too. > ! > And while I am out looking.....  > F > Any chance anyone within driving distance of Scranton, PA might haveI > a SCSI 9-track they want to get rid of? (Real slim chance but you don't  > know until you ask. :-)  >  > bill >  > --L > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>   ------------------------------  # Date: Fri, 10 Nov 2006 08:23:37 GMT L From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing), Subject: Re: Tool to convert BMP image to PS6 Message-ID: <00A5E7E6.EE0F035A@SSRL.SLAC.STANFORD.EDU>  R In article <1163017017_23@sp6iad.superfeed.net>, Kevin Handy <kth@srv.net> writes:  >apogeusistemas@gmail.com wrote:= >> Do you know any tool to convert a bmp image to postcript ? I >> I need convert a .bmp logo to postscript, to print in my VMS system...  > ( >in addition to those already mentioned,* >'gimp' can be used to convert file types.& >Load in the image, and 'save-as' your# >prefered type. You can also do any   >cropping/adjustments necessary.  ' Does the GIMP run on VMS?  If so, cool!    -- Alan    ------------------------------  % Date: Fri, 10 Nov 2006 09:38:34 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> F Subject: Re: UnixAdminTalk (was: Re: illegal image section descriptor)J Message-ID: <paul.sture.nospam-8801E7.09383410112006@mac.sture.homeip.net>  ( In article <ej0h6v$sqk$1@pyrite.mv.net>,:  Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org> wrote:   > Paul Sture wrote:  > H > > FFS don't put links which require registration to read into your sig > J >    Based on a quick look, this UnixAdminTalk.Com site simply appears to I > vacuums up content from comp.os.vms -- there are increasing numbers of  J > content aggregators filling the search engines, and many are apparently E > seeking to use the newsgroups to increase hits for their ads using  G > usenet as their content provider.  This site looks to be another one.  > K >    If you register with UnixAdminTalk, they'll give you (free) rights to  I > post here in usenet -- something which might be useful for those folks  K > that don't have another source for an nntpd feed, and that haven't heard  F > about or chosen to use other sites, like Google's Groups.Google.Com L > service.  Or for folks that want to try to hide their identity, of course.  @ Thanks for doing the dirty work :-)  It's always useful to have % alternative access methods available.    --  
 Paul Sture   ------------------------------  % Date: Fri, 10 Nov 2006 01:27:36 -0500 ' From: Dave Froble <davef@tsoft-inc.com> " Subject: Re: Where to get a cable?9 Message-ID: <_ridncb-mr-KgcnYnZ2dnUVZ_uadnZ2d@libcom.com>    Richard B. Gilbert wrote: % > The Grue - James T. Sprinkle wrote:  > J >> Where is a good place to get a resonably priced mmj <-> db9f cable?  I H >> just got a MicroVAX 3100 and it is just sitting there waiting for me   >> to do something with it.  : ) >> >> The Grue  >> > I > I never heard of such a cable.  The normal procedure would be to use a  H > mmj<-->mmj cable and an MMJ to DB9 adapter.  There were two different I > adapters, one for the MicroVAX II, MicroVAX 2000, VAXStation 2000, and  F > the other for DB9 ports with "normal" PC pinouts.  I think I have a J > couple of the old VAX style adaptors and might be persuaded to sell one  > iff: > a. I can find it, and  > b. I'm offered enough money   G As others have mentioned, the pinout on the DB9 needs to be configured  I for the intended use.  I've put together more than one cable with an MMJ  F on one end and a DB9 at the opposite end.  Normal usage is to allow a F terminal emulator on a PC act as a console for a VAX, or, to use a VT C terminal as a console for an Alpha.  I've also used the MMJ to DB9   adapters, more versatile.   G Having a couple hundred dollars in tools and parts is the key.  If you  I make more than a few, or do wiring jobs, it's worth it.  Otherwise, it's   better to purchase.    --  4 David Froble                       Tel: 724-529-0450> Dave Froble Enterprises, Inc.      E-Mail: davef@tsoft-inc.com DFE Ultralights, Inc.  170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------    Date: 10 Nov 2006 16:03:09 +0100/ From: huber@NIRWANA-mppmu.mpg.de (Joseph Huber) ? Subject: Re: writing fixed size records with one shorter record + Message-ID: <UqNZs2mut9hy@vms.mppmu.mpg.de>   m In article <u1fe24-4ud.ln1@news.hus-software.de>, Albrecht Schlosser <ajs567XNewsX-XNewsX@tiscali.de> writes:  > Hi,  > S > the problem I've encountered is to write a binary (in this case TIFF image) file  M > with fixed length 512 bytes records, but with the last record "incomplete"   > (shorter than 512 Bytes).  > Q > At least that's what I can see how such image files look, after they have been  * > transfered (binary) with ftp or similar. > O > Right now, my (FORTRAN) program can write all the records correctly, but the  M > last (shorter) record always gets padded with blanks up to 512 bytes. This  Q > doesn't really matter for the display of these particular files, but you never  
 > know ... > R > Question: is there a way to write the last shorter record in a FORTRAN program, P > or would I need to modify the file header information before or after closing 0 > the file? If this would be the case, then how? > # > This is how the file gets opened:  > ! >          OPEN    (UNIT   = LUN, " >       *           FILE   = NAME,# >       *           TYPE   = 'NEW', + >       *           CARRIAGECONTROL='NONE', ) >       *           RECORDTYPE = 'FIXED', ! >       *           RECL   = 512, " >       *           ERR    = 2900)  L I think with Fortran record IO You can't avoid padding fixed length records.K Eventually F90/F95 "stream" files would work, but I haven't experience with  that.   L One way: use VMS block IO instead Fortran IO for write. Then the last write N can be shorter than 512, and the correct byte used count will be set on close.  % If You have no BIO package, use mine: 5   http://www.huber-joseph.de/util/bio.for  , bio.inc.     --  @    Joseph Huber , Muenchen,Germany:  http://www.huber-joseph.de/   ------------------------------  % Date: Fri, 10 Nov 2006 17:43:42 +0100 9 From: Albrecht Schlosser <ajs567XNewsX-XNewsX@tiscali.de> ? Subject: Re: writing fixed size records with one shorter record 1 Message-ID: <8rme24-ipn.ln1@news.hus-software.de>    Joseph Huber wrote: J > In article <u1fe24-4ud.ln1@news.hus-software.de>, Albrecht Schlosser <a=& js567XNewsX-XNewsX@tiscali.de> writes: >> Hi, >>J >> the problem I've encountered is to write a binary (in this case TIFF i=
 mage) file=20 J >> with fixed length 512 bytes records, but with the last record "incompl= ete"=20  >> (shorter than 512 Bytes). >> >>=20    [...snip...]   >=20J > I think with Fortran record IO You can't avoid padding fixed length rec= ords. J > Eventually F90/F95 "stream" files would work, but I haven't experience = with > that.  >=20J > One way: use VMS block IO instead Fortran IO for write. Then the last w= rite=20 J > can be shorter than 512, and the correct byte used count will be set on=  close.  >=20' > If You have no BIO package, use mine: 7 >   http://www.huber-joseph.de/util/bio.for  , bio.inc.  > =20   H Thanks, looked at it, and may be a way, at least a good example code :-)  J If I would have to do block i/o, then maybe I will use it. Thank you for =
 sharing=20
 this code.  , But maybe someone else knows an easier way ?     Gr=FC=DFe nach M=FCnchen :-)   Albrecht   ------------------------------    Date: 10 Nov 2006 08:59:29 -0800< From: "Hein RMS van den Heuvel" <heinvandenheuvel@gmail.com>? Subject: Re: writing fixed size records with one shorter record B Message-ID: <1163177969.695697.21200@i42g2000cwa.googlegroups.com>   Albrecht Schlosser wrote:  > Hi,  > R > the problem I've encountered is to write a binary (in this case TIFF image) fileL > with fixed length 512 bytes records, but with the last record "incomplete" > (shorter than 512 Bytes).   9 Well, it is not really a fixed length 512 file is it now? 8 Just some tools seemed to find it handy to call it that.  G I would  recommend to call the RMS record interface directly (SYS$GET / F SYS$PUT, not SYS$READ / SYS$WRITE) and set the file characteristics to what it really is: 'undefined'   SET FILE /ATTR=RFM:UDF9  -->  FAT$V_RTYPE=FAT$C_UNDEFINED     FAB$B_RFM=FAB$C_UDF   E This will the program to read any number up bytes up to 32K and still > gives you rms buffering for read-ahead, write-behind and such.   Hein.    ------------------------------  % Date: Fri, 10 Nov 2006 18:43:18 +0100 9 From: Albrecht Schlosser <ajs567XNewsX-XNewsX@tiscali.de> ? Subject: Re: writing fixed size records with one shorter record 1 Message-ID: <0bqe24-hkr.ln1@news.hus-software.de>    Hein RMS van den Heuvel wrote: > Albrecht Schlosser wrote:  >> Hi, >>S >> the problem I've encountered is to write a binary (in this case TIFF image) file M >> with fixed length 512 bytes records, but with the last record "incomplete"  >> (shorter than 512 Bytes). > ; > Well, it is not really a fixed length 512 file is it now? : > Just some tools seemed to find it handy to call it that.   agreed  I > I would  recommend to call the RMS record interface directly (SYS$GET / H > SYS$PUT, not SYS$READ / SYS$WRITE) and set the file characteristics to  > what it really is: 'undefined' >  > SET FILE /ATTR=RFM:UDF; >  -->  FAT$V_RTYPE=FAT$C_UNDEFINED     FAB$B_RFM=FAB$C_UDF   P I understand "FAB$B_RFM=FAB$C_UDF", but what does "FAT$V_RTYPE=FAT$C_UNDEFINED" 8 mean? (guess: the same, but what language/tool/context?)   > G > This will the program to read any number up bytes up to 32K and still @ > gives you rms buffering for read-ahead, write-behind and such.  N I think that I will give that a try. Just found a piece of my own C code that O writes a (real fixed length) file with sys$put. Setting the correct attributes  N should not be a big deal, but I do hope that the resulting file would then be  usable.    > Hein.    Thanks,    Albrecht   ------------------------------   End of INFO-VAX 2006.619 ************************