1 INFO-VAX	Fri, 10 Nov 2006	Volume 2006 : Issue 618       Contents:8 Re: An increasingly-rare island of corporate inspiration8 Re: An increasingly-rare island of corporate inspiration Help with WPS again  Re: Help with WPS again  Re: Help with WPS again ? How can one distinguish an IDE/ATA(PI) drive from a SCSI drive? $ Re: illegal image section descriptor$ Re: illegal image section descriptor 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: Novice's questions Re: Novice's questions TIE/MSAI Re: TIE/MSAI= Re: UnixAdminTalk (was: Re: illegal image section descriptor)  Re: Where to get a cable?  Re: Where to get a cable?   F ----------------------------------------------------------------------   Date: 9 Nov 2006 11:56:27 -0800  From: davidc@montagar.com A Subject: Re: An increasingly-rare island of corporate inspiration C Message-ID: <1163102187.510253.154630@h48g2000cwc.googlegroups.com>    Bill Gunshannon wrote:E > In article <1163089210.946479.247210@b28g2000cwb.googlegroups.com>,  > 	davidc@montagar.com writes: > > - > > In some ways, POSIX was before it's time.  > E > Oh puleezzze.  POSIX was just another bad attempt at something that C > was tried long before which the computing industry in it's myopic E > wisdom failed to see the value of and thus has repeatedly ended out ) > trying to do it again.  Take a look at: L >      http://www.dcs.gla.ac.uk/~joe/auxiliary/papers/Personal/VirtualOS.pdf  C POSIX was a more complete implementation that even what's mentioned D there.  It went beyond what they spec'd and included a lot more, and> could actually pass FIPS 151.2 - something some Unix's didn't.  G > >                                           From a software developer I > > point of view, even if you're a Unix programmer, you generally try to K > > code to the API's that are most common or are cross platform.  The goal H > > was to make is easier to port software from one platform to another. > F > Yes, the goal way back in 1980.  POSIX.1 wasn't published until 1988  C But that goal wasn't reached anywhere, unless it was an actual Unix E system (which is pretty much what the VirtualOS specified, as defined F by Appendix A).  Even the Appendix D points the main commonality was aC working RATFOR and support for I/O primitive (essentially the early  version of libc) at the time.   J > > There are initiatives to make various Unix flavors more compatible, toI > > ease vendor porting even across UNIX platforms.  LSB is an initiative J > > to make all LInux distributions very similar.  POSIX, at the time, wasH > > an attempt to do this for OpenVMS.  And there was some sucess there. > D > And The Software Tools Virtual Operating System was a much earlier4 > attempt and wasn't limited to just Unix platforms.  C How many of those platforms exist today?  How many of the COMPANIES G exist today?  Notice that what's happened isn't so much that effort has C gone into making other platforms look like Unix, but that tools and B language environments bridge O/S differences.  Most software isn'tC bound to the O/S as much as it is to the libraries it's built upon.   C > But, like so much of our history, this has been forgotten and the B > research taht went into it lost.  And now the industry can waste0 > lots of time and money re-inventing the wheel.  E The research isn't lost, the whole computing environment from 25 year D ago is radically different.  From custom boards, to commodity parts.B Computers used to be EXPEN$IVE and ran by computer scientists, nowG Joe-Bob's Blackberry has more processing power and memory than anything D available 25 years ago.  Instead of writing a VirtualOS on your O/S,C the "VirtualOS" is actually the O/S (or Windows, but that's another F story) and supporting tools. Instead of making the "shell" ubiquitous,G everything is graphical point-and-click (which is about as O/S agnostic " as anything) or web-based/enabled.  F The article points out the goal "primitives" (open, close, etc) of theG VirtualOS, and today those are enhanced beyond just a few system calls. B  Like I mentioned, now it's enablers like Java, PHP, Python, Perl,G Apache; tools like libc/DECC$RTL, XML, ODBC, and a myriad of underlying F libraries; applications which may be completely web-based and the user# has no clue what O/S is underneath.   F And the software tools and "uniform interfaces" that they suggested beF written back in the 80's - well, they are here now, in the form of allC those things I've mentioned here.  We'll never reach the "ultimate" F goal of the VirtualOS where there is a single "platform" for computingE - unless Microsoft gets it's way and Windows is the only platform out  there.   ------------------------------   Date: 9 Nov 2006 20:28:29 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)A Subject: Re: An increasingly-rare island of corporate inspiration / Message-ID: <4rhhbcFrbpeaU1@mid.individual.net>   C In article <1163102187.510253.154630@h48g2000cwc.googlegroups.com>,  	davidc@montagar.com writes: >  > Bill Gunshannon wrote:F >> In article <1163089210.946479.247210@b28g2000cwb.googlegroups.com>, >> 	davidc@montagar.com writes:  >> >. >> > In some ways, POSIX was before it's time. >>F >> Oh puleezzze.  POSIX was just another bad attempt at something thatD >> was tried long before which the computing industry in it's myopicF >> wisdom failed to see the value of and thus has repeatedly ended out* >> trying to do it again.  Take a look at:M >>      http://www.dcs.gla.ac.uk/~joe/auxiliary/papers/Personal/VirtualOS.pdf  > E > POSIX was a more complete implementation that even what's mentioned F > there.  It went beyond what they spec'd and included a lot more, and@ > could actually pass FIPS 151.2 - something some Unix's didn't.  G I think you missed the point.  POSIX was an attempt to do someting that H a bunch of Grad Students started doing back in 1980.  After they got outF of school, like most grad projects, it just withered and died.  It wasD a good idea in 1980.  It certainly was still a good idea when it wasC revisited almost a decade later.  And it was still a good idea when E POSIX decided to hijack the process and claim they invented the idea. G If the industry were not so myopic it would have latched onto STVOS and * by now we would have a real universal API.   > H >> >                                           From a software developerJ >> > point of view, even if you're a Unix programmer, you generally try toL >> > code to the API's that are most common or are cross platform.  The goalI >> > was to make is easier to port software from one platform to another.  >>G >> Yes, the goal way back in 1980.  POSIX.1 wasn't published until 1988  > ) > But that goal wasn't reached anywhere,    @ Of course the goal was reached.  I used it on two very different? architectures myself.  Prime/PRIMOS and UNIVAC/EXEC8.  Programs A written to the API were portable even given the major differences > in the machines and base OSes.  And, the originators graduated? (which was the primary goal of the project! :-)  But then, when = industry should have picked up on the research and carried it A forward to a realistic commercial project (after all, that is not B the goal of grad students) they, as usual, dropped the ball.  It's! not like the research was hidden.   E >                                        unless it was an actual Unix G > system (which is pretty much what the VirtualOS specified, as defined  > by Appendix A).     B And what does POSIX define?  Sure looks Unixy to me.  Maybe that's@ because witht the operating system being designed for relativelyB easy portability the API and I/O primitives were pretty well layed out for just such a project.  H >                  Even the Appendix D points the main commonality was aE > working RATFOR and support for I/O primitive (essentially the early  > version of libc) at the time.   B And your point is?  Most machines had Fortran already available so? RATFOR was a pretty good candidate for writting more structured A programs.  Kernighan & Plauger did their software tools in Pascal < to, but there were more Fortan compilers around than Pascal.   > K >> > There are initiatives to make various Unix flavors more compatible, to J >> > ease vendor porting even across UNIX platforms.  LSB is an initiativeK >> > to make all LInux distributions very similar.  POSIX, at the time, was I >> > an attempt to do this for OpenVMS.  And there was some sucess there.  >>E >> And The Software Tools Virtual Operating System was a much earlier 5 >> attempt and wasn't limited to just Unix platforms.  > E > How many of those platforms exist today?  How many of the COMPANIES  > exist today?    F What's that got to do with anything?  Once the API had been defined itE would have followed along with changes in systems.  Its intent was to  bridge all these architectures.   H >              Notice that what's happened isn't so much that effort hasE > gone into making other platforms look like Unix, but that tools and D > language environments bridge O/S differences.  Most software isn'tE > bound to the O/S as much as it is to the libraries it's built upon.   D Yes, but in most cases, those underlying libraries are a part of theB OS.  And you are certainly not trying to say that supporting POSIX9 doesn't make your system look like Unix at the API level?    > D >> But, like so much of our history, this has been forgotten and theC >> research taht went into it lost.  And now the industry can waste 1 >> lots of time and money re-inventing the wheel.  > G > The research isn't lost, the whole computing environment from 25 year F > ago is radically different.  From custom boards, to commodity parts.D > Computers used to be EXPEN$IVE and ran by computer scientists, nowI > Joe-Bob's Blackberry has more processing power and memory than anything F > available 25 years ago.  Instead of writing a VirtualOS on your O/S,E > the "VirtualOS" is actually the O/S (or Windows, but that's another  > story) and supporting tools.    F It isn't and probably never will be on VMS.  It will be some librariesH that run on top of VMS.  The only difference between then and now is howG deep the hooks go into the OS.  Given more time, it is safe to bet that G the hooks for STVOS would have gotten very deep into the systems it ran H on.  But we stopped and now people are trying to do it all again, badly.  I >                               Instead of making the "shell" ubiquitous,   F The shell was ubiquitous.  I have seen Bourne like shells on damn nearE everything at some point, even VMS.  But that is just user interface. B The purpose of STVOS was so that once written anyone who wanted it+ could put that same shell on every machine.   I > everything is graphical point-and-click (which is about as O/S agnostic $ > as anything) or web-based/enabled.  H Really?  Ever try running Windows on anything other than MS's underlying= os?  How about the Mac GUI from System7?  Hardly OS agnostic.    > H > The article points out the goal "primitives" (open, close, etc) of theI > VirtualOS, and today those are enhanced beyond just a few system calls.   B Well duh.  It was a graduate project.  It had only a couple peopleC doing it for at most a year to a year and ahalf.  My point is if it A had been continued rather than abandoned only to be started again 7 from scratch 8-10 years later, where would it be today?   D >  Like I mentioned, now it's enablers like Java, PHP, Python, Perl,  ' Those are just languages.  Like RATFOR.   I > Apache; tools like libc/DECC$RTL, XML, ODBC, and a myriad of underlying H > libraries; applications which may be completely web-based and the user% > has no clue what O/S is underneath.   G And, when will all these "enablers" make it possible to run Open Office F on VMS?  A common programming level API would have made that possible.   > H > And the software tools and "uniform interfaces" that they suggested beH > written back in the 80's - well, they are here now, in the form of allE > those things I've mentioned here.  We'll never reach the "ultimate" H > goal of the VirtualOS where there is a single "platform" for computingG > - unless Microsoft gets it's way and Windows is the only platform out  > there.   bill     --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 9 Nov 2006 20:46:34 -0800  From: tomarsin2015@comcast.net Subject: Help with WPS againC Message-ID: <1163133994.385296.198910@h54g2000cwb.googlegroups.com>    JF< It seems you know WPS really good, could I e-mail with a few questions??  thanks phil   ------------------------------  % Date: Fri, 10 Nov 2006 00:29:52 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>   Subject: Re: Help with WPS again8 Message-ID: <f15a6$45540e4b$cef8887a$21589@TEKSAVVY.COM>   tomarsin2015@comcast.net wrote: > > It seems you know WPS really good, could I e-mail with a few
 > questions??   D Humm, I'll have to think about it. I think I may have to setup some < committee and strike some task forces to study the question.   ------------------------------  % Date: Fri, 10 Nov 2006 00:31:34 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>   Subject: Re: Help with WPS again8 Message-ID: <98677$45540eb1$cef8887a$21589@TEKSAVVY.COM>   tomarsin2015@comcast.net wrote: > > It seems you know WPS really good, could I e-mail with a few
 > questions??   J After considerable debate and production of many powerpoint presentations K to study the pros and cons of your question, all committes and task forces  ' have unanimously approved your request.   J You may therefore contact me with your questions... jfmezei at vaxination 	 period ca    :-) ;-) :-) :-) :-)    ------------------------------  * Date: Thu, 9 Nov 2006 19:55:55 -0600 (CST)* From: sms@antinode.org (Steven M. Schweda)H Subject: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive?2 Message-ID: <06110919555548_2020028F@antinode.org>  E    Is there some semi-convenient way (in a program) to distinguish an H IDE/ATA(PI) drive from a SCSI drive, other than looking for "DK" or "DQ" in the device name?   @    The only thing I've found so far is the dev$v_scsi bit in theG device-dependent characteristics (2), but it appears to be set for both 
 device types.   H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------   Date: 9 Nov 2006 13:27:42 -0800 / From: "Volker Halle" <volker_halle@hotmail.com> - Subject: Re: illegal image section descriptor A Message-ID: <1163107662.742388.54900@m7g2000cwm.googlegroups.com>   D As already said in ITRC, use ANAL/IMAGE to find possible problems in> your image. Try this both on your V7.1 and your V7.3-1 system.   Cross-Reference:  L http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1074707   Volker.    ------------------------------  % Date: Fri, 10 Nov 2006 00:55:01 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> - Subject: Re: illegal image section descriptor J Message-ID: <paul.sture.nospam-0B2467.00550110112006@mac.sture.homeip.net>  8 In article <rajeshkumar.2h0rtp@no-mx.unixadmintalk.com>,/  rajeshkumar <rajesh_bka@rediffmail.com> wrote:   
 > rajeshkumar J > ------------------------------------------------------------------------5 > rajeshkumar's Profile: http://unixadmintalk.com/445 D > View this thread: http://unixadmintalk.com/showthread.php?t=238711  D FFS don't put links which require registration to read into your sig   --  
 Paul Sture   ------------------------------   Date: 9 Nov 2006 13:15:33 -0800  From: madcrow.maxwell@gmail.com # Subject: Most "classic" VMS version A Message-ID: <1163106933.892553.16520@m7g2000cwm.googlegroups.com>   B I've recently come across a treasure trove of classic VMS releasesF online. I'd LOVE to be able to try this out in SIMH (I have a hobbyistG license, so this is all legal). I am wondering what version of VMS best F represents it's "classic" form so that I know what the best version toF get is. Also, does anybody know where I can find an installation guide1 so that I can actually get it all up and running?    ------------------------------  % Date: Thu, 09 Nov 2006 18:15:09 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>' Subject: Re: Most "classic" VMS version ( Message-ID: <ej0cpt$req$1@pyrite.mv.net>    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?       Classic?  V1.0, V5.5-2, ...  G    The start of the installation process for OpenVMS VAX hasn't really  D changed in eons.  (Since V3.0 or so.)  Restore the VMS0%%.B saveset @ using standalone BACKUP (and most any equal or newer version of G standalone BACKUP should work well enough to restore the saveset), and  E boot it.  (Can't say I've run an installation for a release prior to  ; V3.0, as I didn't get handed system management until then.)   G    The documentation on the OpenVMS VAX installation is available with   the rest of the manuals:  &    <http://www.hp.com/go/openvms/doc/>  ;    You should be able to follow the baseline documentation.   C    The usual difficulties involve picking a release older than the  C minimum version for the current platform, or dealing with the boot  C sequence for the particular platform.  The VAX-11/780 has specific  E requirements around setting up and using the boot command files, for  I instance.  (This isn't particularly specific to the OpenVMS VAX version.)   A    If you should encounter problems with the BACKUP saveset file  I attributes when using FTP to transfer the files from the 'trove, see the  F RESET_BACKUP*.COM command procedure available in the OpenVMS Freeware  000TOOLS directory.   ;    <http://h71000.www7.hp.com/freeware/freeware80/000tools/ .      reset_backup_saveset_file_attributes.com>  F    If the 'trove is protecting the BACKUP saveset file attributes via  use of zip "-V", ignore this.   G    It might well be worth working with HP to authorize it, and to then  C verify, package (via zip, etc) and otherwise make these (I assume)  E ancient releases available via a server or via a distro of some sort.    ------------------------------   Date: 9 Nov 2006 16:43:34 -0800 + From: "madcrow" <madcrow.maxwell@gmail.com> ' Subject: Re: Most "classic" VMS version B Message-ID: <1163119414.850494.52710@f16g2000cwb.googlegroups.com>   Stephen Hoffman wrote:" > madcrow.maxwell@gmail.com wrote:  H >    The start of the installation process for OpenVMS VAX hasn't reallyE > changed in eons.  (Since V3.0 or so.)  Restore the VMS0%%.B saveset A > using standalone BACKUP (and most any equal or newer version of H > standalone BACKUP should work well enough to restore the saveset), andF > boot it.  (Can't say I've run an installation for a release prior to= > V3.0, as I didn't get handed system management until then.)  > H >    The documentation on the OpenVMS VAX installation is available with > the rest of the manuals: > ( >    <http://www.hp.com/go/openvms/doc/> > = >    You should be able to follow the baseline documentation.  > D >    The usual difficulties involve picking a release older than theD > minimum version for the current platform, or dealing with the bootD > sequence for the particular platform.  The VAX-11/780 has specificF > requirements around setting up and using the boot command files, forK > instance.  (This isn't particularly specific to the OpenVMS VAX version.)  > B >    If you should encounter problems with the BACKUP saveset fileJ > attributes when using FTP to transfer the files from the 'trove, see theG > RESET_BACKUP*.COM command procedure available in the OpenVMS Freeware  > 000TOOLS directory.  > = >    <http://h71000.www7.hp.com/freeware/freeware80/000tools/ 0 >      reset_backup_saveset_file_attributes.com> > G >    If the 'trove is protecting the BACKUP saveset file attributes via  > use of zip "-V", ignore this.  > H >    It might well be worth working with HP to authorize it, and to thenD > verify, package (via zip, etc) and otherwise make these (I assume)G > ancient releases available via a server or via a distro of some sort.   C The files look to be gzipped tape images. Hopefully, one could just E mount those in SIMH directly. Is BACKUP generally the first record on > the tape? I assume that tapes work differently than CDs or didF DEC/Compaq/HP just approach the CD-ROM as a small, flat tape with lots	 of space?    ------------------------------  % Date: Thu, 09 Nov 2006 19:58:20 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ' Subject: Re: Most "classic" VMS version 8 Message-ID: <c1407$4553cea7$cef8887a$24100@TEKSAVVY.COM>  K Looking back at history, I would think that 5.5-2 was the most significant  I release. It signaled the end of Digital. And it probably happened at the  B peak ofthe VMS installed base.  And it is still widely used today.  I As I recall, it was also the last of the releases before the first Alpha   release.  K There is a document somwehere on the VMS web site that celebrates 25 years  L of VMS. In it, it includes the many major kilometrestones for each release. > This may give you some ideas of where there was major changes.   ------------------------------  % Date: Thu, 09 Nov 2006 20:45:41 -0500 6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>' Subject: Re: Most "classic" VMS version 7 Message-ID: <4553d9ba$0$49205$14726298@news.sunsite.dk>    JF Mezei wrote: A > Looking back at history, I would think that 5.5-2 was the most  G > significant release. It signaled the end of Digital. And it probably  I > happened at the peak ofthe VMS installed base.  And it is still widely  
 > used today.  > K > As I recall, it was also the last of the releases before the first Alpha  
 > release.  3 I think VMS Alpha 1.0 and 1.5 was same time as 5.5.    Arne   ------------------------------  % Date: Fri, 10 Nov 2006 01:40:10 -0500 ' From: Dave Froble <davef@tsoft-inc.com> ' Subject: Re: Most "classic" VMS version 9 Message-ID: <_ridncH-mr-agsnYnZ2dnUVZ_uadnZ2d@libcom.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?  >   H You'll get lots of opinions.  SIMH would indicate a VAX.  My opinion is H that V7.3 is the most capable.  Guess I'm just not into antiques.  I've H had all I want of V2.*, V3.*, V4.*, V5.*, V6.*, and anything else prior  to V7.2.   --  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: 9 Nov 2006 12:11:30 -0800  From: "MZN" <MikeZmn@gmail.com>  Subject: Re: Novice's questions B Message-ID: <1163103090.814956.147290@e3g2000cwe.googlegroups.com>  C Now I'm trying to receive hobbyist license. Web form asked me about B workstation model (I have XP1000 that isn't listed) and CPU serial+ number. Where I can find CPU serial number?    Thanks.  Mike   ------------------------------  * Date: Thu, 9 Nov 2006 14:54:40 -0600 (CST)* From: sms@antinode.org (Steven M. Schweda) Subject: Re: Novice's questions 2 Message-ID: <06110914544054_2020028F@antinode.org>   From: "MZN" <MikeZmn@gmail.com>   E > Now I'm trying to receive hobbyist license. Web form asked me about D > workstation model (I have XP1000 that isn't listed) and CPU serial- > number. Where I can find CPU serial number?   D    What, "Unlisted Worstation" isn't good enough for you?  An XP1000B owner should quickly adjust to its orphan status (firmware version$ complaints when booting, and so on).  F    The system (not really CPU) serial number is normally on a stuck-onG label on the rear panel.  (Just above the PCI slots on mine.)  However, G the Hobbyist license generator is not very fussy about what you specify B for a "CPU Serial Number", so you could say almost anything there.  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------  # Date: Thu, 09 Nov 2006 19:50:08 GMT " From:   VAXman-  @SendSpamHere.ORG Subject: TIE/MSAI 0 Message-ID: <00A5E796.D066F448@SendSpamHere.ORG>   I go to install these and get:    Y %PCSI-E-READERR, error reading DSA0:[SYS0.SYSMGR]HP-I64VMS-TIE-V0100--1.PCSI$COMPRESSED;1 7 -RMS-W-RTB, 894 byte record too large for user's buffer a %PCSI-E-OPENIN, error opening DSA0:[SYS0.SYSMGR]HP-I64VMS-TIE-V0100--1.PCSI$COMPRESSED;1 as input " %PCSI-E-S_OPFAIL, operation failedM %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition   Z %PCSI-E-READERR, error reading DSA0:[SYS0.SYSMGR]HP-I64VMS-MSAI-V0100--1.PCSI$COMPRESSED;17 -RMS-W-RTB, 903 byte record too large for user's buffer b %PCSI-E-OPENIN, error opening DSA0:[SYS0.SYSMGR]HP-I64VMS-MSAI-V0100--1.PCSI$COMPRESSED;1 as input" %PCSI-E-S_OPFAIL, operation failedM %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition       F Does anybody know of if there a place where I can download viable kits
 for these? --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  # Date: Thu, 09 Nov 2006 20:07:31 GMT " From:   VAXman-  @SendSpamHere.ORG Subject: Re: TIE/MSAI 0 Message-ID: <00A5E799.3E2EAD4A@SendSpamHere.ORG>   In article <1163102423.292335.181900@b28g2000cwb.googlegroups.com>, "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> writes:  >  >  >   >VAXman-@SendSpamHere.ORG wrote:! >> I go to install these and get:  >> >>\ >> %PCSI-E-READERR, error reading DSA0:[SYS0.SYSMGR]HP-I64VMS-TIE-V0100--1.PCSI$COMPRESSED;1: >> -RMS-W-RTB, 894 byte record too large for user's bufferd >> %PCSI-E-OPENIN, error opening DSA0:[SYS0.SYSMGR]HP-I64VMS-TIE-V0100--1.PCSI$COMPRESSED;1 as input% >> %PCSI-E-S_OPFAIL, operation failed P >> %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition >>] >> %PCSI-E-READERR, error reading DSA0:[SYS0.SYSMGR]HP-I64VMS-MSAI-V0100--1.PCSI$COMPRESSED;1 : >> -RMS-W-RTB, 903 byte record too large for user's buffere >> %PCSI-E-OPENIN, error opening DSA0:[SYS0.SYSMGR]HP-I64VMS-MSAI-V0100--1.PCSI$COMPRESSED;1 as input % >> %PCSI-E-S_OPFAIL, operation failed P >> %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition >> >> >>I >> Does anybody know of if there a place where I can download viable kits 
 >> for these?  > F >Have you tried checking the RMS record format to verify that they areH >correct? All of the PCSI$COMPRESSED files I have are seq, fixed 512byte >records  J This could be it.  I downloaded these from the HP web site.  They are both  G Record format:      Stream_LF, maximum 32767 bytes, longest 32767 bytes    --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  % Date: Thu, 09 Nov 2006 19:30:21 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>F Subject: Re: UnixAdminTalk (was: Re: illegal image section descriptor)( Message-ID: <ej0h6v$sqk$1@pyrite.mv.net>   Paul Sture wrote:   F > FFS don't put links which require registration to read into your sig  H    Based on a quick look, this UnixAdminTalk.Com site simply appears to G vacuums up content from comp.os.vms -- there are increasing numbers of  H content aggregators filling the search engines, and many are apparently C seeking to use the newsgroups to increase hits for their ads using  E usenet as their content provider.  This site looks to be another one.   I    If you register with UnixAdminTalk, they'll give you (free) rights to  G post here in usenet -- something which might be useful for those folks  I that don't have another source for an nntpd feed, and that haven't heard  D about or chosen to use other sites, like Google's Groups.Google.Com J service.  Or for folks that want to try to hide their identity, of course.   ------------------------------  % Date: Thu, 09 Nov 2006 18:00:00 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>" Subject: Re: Where to get a cable?( Message-ID: <ej0btf$r87$1@pyrite.mv.net>   davidc@montagar.com wrote:  E > I've just been making my own cables for that.  Got a roll of silver ? > satin, and local electroncs store has the various parts.  See H > http://www.montagar.com/padapters/padapters.html for some pin-outs.  I6 > mirrored it from a DEC web site before it went away.  H    With Warren's help, I had also stashed a copy of that data over at...  2    http://h71000.www7.hp.com/wizard/padapters.html4    http://h71000.www7.hp.com/wizard/cable-guide.html  D    Both URLs are accessible via the left navigation of the ATW site.  I    There are various specific DECconnect part numbers accumulated in the  
 FAQ, as well.   %    http://www.hoffmanlabs.org/vmsfaq/   F    BC16E or equivalent is silver-satin with MMJs.  (There looks to be F another part for that cable, based on what David T. has posted.)  And H adapters run between US$10 and US$25 or so, in my experience.  Or less, 3 if you have the parts and a crimper kicking around.    ------------------------------  % Date: Thu, 09 Nov 2006 20:14:11 -0500 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> " Subject: Re: Where to get a cable?: Message-ID: <re2dnefRTfL_T87YnZ2dnUVZ_v6dnZ2d@comcast.com>  # The Grue - James T. Sprinkle wrote:   N > Where is a good place to get a resonably priced mmj <-> db9f cable?  I just H > got a MicroVAX 3100 and it is just sitting there waiting for me to do  > something with it.  : )  >  > The Grue   >  >   G I never heard of such a cable.  The normal procedure would be to use a  F mmj<-->mmj cable and an MMJ to DB9 adapter.  There were two different G adapters, one for the MicroVAX II, MicroVAX 2000, VAXStation 2000, and  D the other for DB9 ports with "normal" PC pinouts.  I think I have a L 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    ------------------------------   End of INFO-VAX 2006.618 ************************                                                                                                                                                                            X|#:dkFr<gCrM0,^3*]9a;:vUOc
;4tH?Z//?^}/5MfSUZ?@݃GGϲdsukJ6r2Zϴ[312OXF)tpg
aq*1WK\~}b8uߥg,5665}!ԑü(%dSG[F^wN}%NC;`CۤMɽe}J8-[ߍ%cNL^k,ċ;P&~y[Cg?])_32OQYҗT?>o(M887/,úAd	GqxUj_#s@sB{FBٶ M)1sL8(41odT?.urpPILi9q8C1D
ܣ%2͒h&DG)\M9elK{Z|c>;"B3>?r(N\GDi0sJ
LlTϣlRD٢zܳmWQ6gC* q1]#Q]uS{U0*s@Op0tX43uFkr󘁜vUgߘTwXw/h{fM߁^z5?;XxQԻ$!6cXƁvQ8 tq19g+9	0`
V#{D_ӂgsw'HC8/7\xƐĜsu\NC9Z9%)oa*b`P7R^6pK$۝F辤Ot
ܟ ĳ>|Kx].
%bcb;b=6],rBn_L{uL4QQϣlRU'