INFO-VAX Thu, 30 Oct 2008 Volume 2008 : Issue 586 Contents: AlphaServer 8400 for Trade Converting CMS to a Linux based code/source management system Re: DCPS setpagedevice PS error on a Xerox WCP 35 Re: DCPS setpagedevice PS error on a Xerox WCP 35 Re: DCPS setpagedevice PS error on a Xerox WCP 35 Re: DCPS setpagedevice PS error on a Xerox WCP 35 Re: EST Fubar Re: Fortran, debugger and Alpha/VMS 7.3-2 Re: Java for OpenVMS registration for download broken Re: Seamonkey browser port for Alpha now available Re: Seamonkey browser port for Alpha now available USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 VAX-11/785 microdiagnostics help requested ---------------------------------------------------------------------- Date: Wed, 29 Oct 2008 11:53:37 -0700 (PDT) From: vaxorcist Subject: AlphaServer 8400 for Trade Message-ID: I will trade off my AlphaServer 8400 for a VAX-11/750. This is the AlphaServer 8400 current configuration: 8 CPUs = 4*Dual-CPU 300 MHz E2056-DA 4GB Memory = 2*2GB MS7CC-FA 2 KFTIA I/O Modules (4*SCSI / 2*Network) E2054-AA 1 Bus-Terminator E2034-AA 3 48V DC Power Supplies 303379602 3 BA356 StorageWorks SCSI-Boxes 12 DEC SCSI-Drives (RZs) 1 AlphaServer 8400 PCI Box There are some AlphaServer 8400 spares that will go together with the computer: 1 48V DC Power Supply 303379602 2 CPUs = 1*Dual-CPU 300 MHz E2056-DA 2GB Memory = 1*2GB MS7CC-FA 1 Bus-Terminator E2034-AA 1 Box BA655-AA The AlphaServer 8400 is in working condition, but without software and licenses. The only known deficiency is that the console CDROM drive (RRD45) does not open properly, but is nevertheless usable. The condition of the spares is unknown. The AlphaServer 8400 system is located in Northern Germany. What do I expect in return: - A VAX-11/750 in working order - 1MB VAX-11/750 memory - A working VAX-11/750 disk subsystem (controller & drive, any model) - A DEUNA or DELUA UNIBUS ethernet adapter All items are negotiable. The VAX-11/750 will become part of my private collection of VAX computers and will be used to run VMS version 2, 3 & 4, ULTRIX-32 and some old UNIX versions. Regards, Ulli (The VAXorcist) ------------------------------ Date: Wed, 29 Oct 2008 16:25:52 -0400 From: "Ken Robinson \(GMail\)" Subject: Converting CMS to a Linux based code/source management system Message-ID: <025001c93a04$8b7bdb00$a2739100$@com> Has anyone converted files stored in CMS to a Linux based code/source management system? If so, which Linux system was the target and could it be done automatically? We are currently running CMS Version V4.2 on OpenVMS 7.3-2. Thanks in advance. Ken Robinson Ken(removethis)rbnsn@gmail.com(.removethistoo) ------------------------------ Date: Wed, 29 Oct 2008 14:25:13 -0400 From: JF Mezei Subject: Re: DCPS setpagedevice PS error on a Xerox WCP 35 Message-ID: <4908ac78$0$3373$c3e8da3@news.astraweb.com> Jan-Erik Söderholm wrote: > If a DCPS queue is set to PCL by having "DATA_TYPE=PCL" > in the DCPS$STARTUP file (and the DCPS$_PARAMETER > logical is setup to "DATA_TYPE=PCL" just fine), does it > still print some PS code to the printer ? Perhaps Mr Anderson can confirm this, but my gut tells me that DCPS would send its own postscript code to setup the printer and get page count, then switch to PCL code to send your print file, and then switch back to postscript to get the new page count. > I also setup the queue to print PS (DATA_TYPE=ANSI) DATA_TYPE=ANSI invokes the ascii to postscript translator. DATA_TYPE=POSTSCRIPT should pass your postscript to the printer untranslated. (but still with the DCPS header and footer). > and now I get a PS-only spool file. The weired > think is that I can not find any "setpagedevice" > in the spool file created today. "setpagedevice" > was what the printer barfed at on Tuesday... What was the person printing ? For instance, if I create some postcript job on my macintosh that is spooled via LPD to my alpha and then DCPS to the printer, the Mac generated postscript will have a complete setup by itself, including setpagedevice etc since the Mac will have likely used a .PPD file to read all the characteristics of the printer and know the valid setup commands. so, when sending to the printer, DCPS would send it own setup commands and then the original postscript file which would have various commands , including the setpagedevice to get the printer to act in the exact way that the Mac application wanted it to act. Now, if the user on a Mac were to pretend he had a fancy Linotype printer and use the linotype .PDD file, this would result in the Mac application generating poscript code which may cause the Xerox to barf at some of the printer-specific commands (such as setpagedevice). If the files to be printed are simple text files that are being translated to postscript by DCPS, then the faulty setpagedevice would come from DCPS. ------------------------------ Date: Wed, 29 Oct 2008 15:19:00 -0400 From: Paul Anderson Subject: Re: DCPS setpagedevice PS error on a Xerox WCP 35 Message-ID: In article , Jan-Erik Söderholm wrote: > If a DCPS queue is set to PCL by having "DATA_TYPE=PCL" in the > DCPS$STARTUP file (and the DCPS$_PARAMETER logical is setup to > "DATA_TYPE=PCL" just fine), does it still print some PS code to the > printer ? Yes. > I get a bunch of PS code in the spool file, and then : > > %-12345X@PJL > @PJL ENTER LANGUAGE = PCL > > before the actual printout (which I want to be printed). DCPS controls the print job with PostScript. If the user file is PCL, DCPS tells the printer to switch to PCL with the code you mentioned above. Then it will switch back to PostScript to finish the job. > I was think9ng that by running DCPS in "PCL-mode" one could use > non-PS printers also. You can't use DCPS with a printer that does not have PostScript. > I also setup the queue to print PS (DATA_TYPE=ANSI) and now I get a > PS-only spool file. Since the printer doesn't understand ANSI, DCPS translates your ANSI file to PostScript. > The weired think is that I can not find any "setpagedevice" in the > spool file created today. "setpagedevice" was what the printer barfed > at on Tuesday... Then something else must be different about the queue setup or file you are printing. When printing with bi-directional protocols like RawTCP, DCPS sends some PostScript code called prologues to the printer and stores them on the printer so they don't have to be sent each time. This would make the first job printed to the printer after power-up larger as it contains these prologues. But with a uni-directional protocol like LPD, prologues are not checked since the printer can't respond to the DCPS query about whether the prologues exist. So the prologues are sent each time and, in your case, a 'setpagedevice' command that's in one LPD job should also be in another LPD job. Paul -- Paul Anderson OpenVMS Engineering Hewlett-Packard Company ------------------------------ Date: Thu, 30 Oct 2008 00:23:00 GMT From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= Subject: Re: DCPS setpagedevice PS error on a Xerox WCP 35 Message-ID: JF Mezei wrote: > What was the person printing ? We have two kind of printouts. They are both text files, one without and one with embeded PCL commands. We does not create *any* PS files of our own. *All* PS code sent to the printer(s) comes from DCPS. This comment from Paul : > You can't use DCPS with a printer that does not have PostScript. tells me that I had missunderstood that. I thought that the "DATA_TYPE=PCL" was a way to use the DCPS "infrastructure" to print PCL on non-PS printers. Guess not... Seems as I have to get back to the drawingboard to take a second look on the whole printing setup on this system... Jan-Erik. ------------------------------ Date: Thu, 30 Oct 2008 00:20:20 -0400 From: JF Mezei Subject: Re: DCPS setpagedevice PS error on a Xerox WCP 35 Message-ID: <49093533$0$2092$c3e8da3@news.astraweb.com> Jan-Erik Söderholm wrote: > tells me that I had missunderstood that. I thought that > the "DATA_TYPE=PCL" was a way to use the DCPS "infrastructure" > to print PCL on non-PS printers. Guess not... The error message you posted here is typical of a POSTSCRIPT printer. I would be willing to bet a chocolate bar that the printer does support Postcript. As you have seen in the postscript modules sent to the printer, there are many postscript commands sent to the printer prior to a setpagedevice command. A PCL-only printer would likely have complained well before getting to a setpagedevice, and it would have had no concept of a stack and that a dictionary had been put on the stack just before calling setpagedevice. ------------------------------ Date: Wed, 29 Oct 2008 10:54:40 -0700 (PDT) From: etmsreec@yahoo.co.uk Subject: Re: EST Fubar Message-ID: <45eda97f-5a16-4885-ba27-1c2f0d4d8942@y79g2000hsa.googlegroups.com> On 29 Oct, 12:48, "Tim E. Sneddon" wrote: > Bob Koehler wrote: > > In article , koeh...@eisner.nosp= am.encompasserve.org (Bob Koehler) writes: > >> =A0 =A0I wonder what our PBS stations here abouts are using. =A0My VCR= /DVD > >> =A0 =A0recorder is supposed to pick up time code from PBS. =A0Last nig= ht > >> =A0 =A0I see that it jumped forward an hour (wrong day and wrong way). > > > =A0 =A0I have the same problem, in the same area. =A0They're always off > > =A0 =A0by an hour for a week. =A0We have to set our VCR to manual clock > > =A0 =A0settings for a while. > > Did someone notice a wormhole open up somewhere? Maybe it's just my > news service, but Bob's reply just came in. However, the message he > was replying to was from a year ago (or at least that's what my > news client says :-). > > Tim. This is at least the second thread to see this today - the one about VMS's 30th Birthday being on the HP home page has been resurrected too... Steve ------------------------------ Date: 30 Oct 2008 05:21:03 GMT From: "David Weatherall" Subject: Re: Fortran, debugger and Alpha/VMS 7.3-2 Message-ID: <6msuhuFil7t3U1@mid.individual.net> tadamsmar wrote: > On Oct 29, 1:17 am, "David Weatherall" wrote: > > tadamsmar wrote: > > > On Oct 28, 1:43 am, "David Weatherall" > > > wrote: > > > > We finally upgraded the Alphas in our cluster from V7.3-1 to -2 > > > > last week. As expected, we never saw any problem until my > > > > colleague needed to use the debugger with her Fortran (V7.5...) > > > > program. > > > > > > It contains a Structure/record like > > > > > >         structure /asd$record/ > > > >            character*36         asd_name > > > >            character*36         efile_name > > > >            character*12         other_name > > > > ... > > > >         end structure > > > > > >         record /asd$record/ asd_record > > > > > > In the debugger we can > > > > > >         EXA ASD_RECORD > > > > > > without problem but > > > > > >         EXA ASD_RECORD.ASD_NAME > > > > > > generates the following error :- > > > > > > %DEBUG-E-INTERR, debugger error in DBGADDEXP\DETERMINE_TYPE > > > > unknown arg type or session corruption > > > > > > T'was fine on 7.3-1. Anybody know what's going on? John? > > > > > > Kristine, my colleague, is less than impressed. > > > > > > Cheers - Dave > > > > > > Now that I look at it, the $ in asd$record is a bit suspicious > > > > perhaps. > > > > > > -- > > > > > I just tried it on a 7.3-2 system and it worked. > > > > > But, my Fortran ver is 7.2-180 > > > > > My fortran symbol was: > > > > > "FORTRAN /NOLIST /DEBUG /NOOPT /NOALIGN / > > > CHECK=(BOUN,FP_E,OVER,NOUNDE) /WARN=(NOALIGN,NOUNINIT)/EXTEND" > > > > > Perhaps you should get your patches up to date if you have not > > > done so.  Mine are pretty close to up to date,  (within a year or > > > so maybe). > > > > Thanks > >        our Fortran version is 7.5 somethings. I've tried it with two > > standards. I didn't want to update our Fortran compiler to the > > latest standard because I'm in a position to do 'incremental Q/A' > > that way. If I upgrade and can't produce a bit-compatible .EXE I > > have to do the 3-week Q/A job all over again. Partly because of the > > rules and partly for peace of mind. > > > > Thomas, our SysMAn, is sure that he applied all patches when he > > upgraded two weeks ago. Could you an ANALYZE /IMAGE on the debugger > > .EXE please. > > > > Cheers - Dave. > > > > --- Hide quoted text - > > > > - Show quoted text - > > Is the be part of the ANALYZE/IMAGE that you want?: > > Image Identification Information > > image name: "DEBUG" > image file identification: "V7.3-200" > image file build identification: "X9ZK-0060100000" > link date/time: 1-OCT-2003 21:19:12.22 > linker identification: "A11-50" > > Patch Information > > There are no patches at this time. Thanks Mark that is exactly the bit I was after. My memory is that ours has link date in 2007. I'll forward this to work and check again when I get there. Cheers - Dave. -- ------------------------------ Date: Wed, 29 Oct 2008 15:53:53 -0700 (PDT) From: sean@obanion.us Subject: Re: Java for OpenVMS registration for download broken Message-ID: <63ad873a-f56c-4ab2-b142-29c6c8f31f24@1g2000prd.googlegroups.com> Yesterday afternoon, I successfully downloaded and installed "JAVA150 V1.5-4" Now onto CIFS and Netbeans. Google Groups was running a little slow yesterday, so I waited until today to try posting again... Sean On Oct 28, 10:41=A0am, s...@obanion.us wrote: > Update: from my ITRC post I got an email stating that this is a known > problem and it's being worked on. > > I was given a URL to a different server to do the download from, but > was asked not to share it. > > I'll update this thread a little later as to how this goes... > > Sean > > On Oct 27, 6:00=A0pm, s...@obanion.us wrote: > > >http://h18012.www1.hp.com/java/download/ovms/1.5.0/jdk5.0_form.html > > > Above is the web site for downloading Java for OpenVMS. > > When submitting it's filled out registration form, connection to > > ONLINECGI03.COMPAQ.COM times out, which also does not respond to > > PING. > > > The support page for the above page points to the same > > ONLINECGI03.COMPAQ.COM so a direct complaint is not possible. > > I've submitted this problem through ITRC... > > > Or is this just me? > > > Sean ------------------------------ Date: Thu, 30 Oct 2008 03:03:38 +0100 (CET) From: BRAD@rabbit.turquoisewitch.com (Brad Hamilton) Subject: Re: Seamonkey browser port for Alpha now available Message-ID: In article <4908a209$0$3358$c3e8da3@news.astraweb.com>, JF Mezei wrote: >Found my original post on the subject of file protections: > >http://groups.google.com/group/comp.os.vms/browse_thread/thread/ >702c085ab976f497/3dcebfe78cc06f6e?hl=xx-elmer&lnk=st&q=#3dcebfe78cc06f6e > >I had noticed it due to chrome.rdf file in the .cswb tree. If you used >a privileged account, it would recreate that file in the common >directory with protections that would not let unprivileged users access it. Luckily, I don't see this problem in Seamonkey. Seamonkey works better for me today, after the nightly reboot. All I really want to do with it is to play with Mail and Newsgroups. I'm going to attempt to find out how to invoke *only* the mail program, since the browser, although more stable than yesterday, is *slow*. [...] ------------------------------ Date: Thu, 30 Oct 2008 00:24:04 -0400 From: JF Mezei Subject: Re: Seamonkey browser port for Alpha now available Message-ID: <49093611$0$2092$c3e8da3@news.astraweb.com> Brad Hamilton wrote: > want to do with it is to play with Mail and Newsgroups. I'm going to attempt > to find out how to invoke *only* the mail program, since the browser, although > more stable than yesterday, is *slow*. > [...] With Mozilla, this is in the preferences panels where you specify what window you want to begin with. ( mail&newsgroup or navigator/browser) ------------------------------ Date: Wed, 29 Oct 2008 22:20:03 +0000 (UTC) From: moroney@world.std.spaamtrap.com (Michael Moroney) Subject: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Message-ID: What USB to RS-232 serial line adapters work with OpenVMS? I've been chasing a problem that has finally been traced to a port on a Digiboard 16 line interface randomly dropping characters. In addition, other Digiboards won't even configure properly on VMS. I finally was able to do the USB commands Forrest mentioned earlier so I can file a problem report regarding the nonconfiguration. I vaguely remembered reading that a Radio Shack adaptor supposedly worked with VMS but a quick trip showed that not true (doesn't even show up). ------------------------------ Date: Thu, 30 Oct 2008 00:14:23 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Message-ID: <00A81D83.0426DC60@SendSpamHere.ORG> In article , moroney@world.std.spaamtrap.com (Michael Moroney) writes: >What USB to RS-232 serial line adapters work with OpenVMS? I've been >chasing a problem that has finally been traced to a port on a Digiboard 16 >line interface randomly dropping characters. In addition, other Digiboards >won't even configure properly on VMS. I finally was able to do the USB >commands Forrest mentioned earlier so I can file a problem report >regarding the nonconfiguration. > >I vaguely remembered reading that a Radio Shack adaptor supposedly worked >with VMS but a quick trip showed that not true (doesn't even show up). I have a USB/serial I use on Linux and OS X. It's a KeySpan USA19HS. I have never tried it with VMS but it seems to work well everywhere else I have used it. I suppose I could see if I can get it to function on the Itanium. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM ... pejorative statements of opinion are entitled to constitutional protection no matter how extreme, vituperous, or vigorously expressed they may be. (NJSC) Copr. 2008 Brian Schenkenberger. Publication of _this_ usenet article outside of usenet _must_ include its contents in its entirety including this copyright notice, disclaimer and quotations. ------------------------------ Date: Wed, 29 Oct 2008 20:25:27 -0400 From: "forrret.kenney@hp.com_nospam" Subject: Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Message-ID: There is a Radio shack one that works and some that do not. The one with a 6' cable should work it has a PL2303. I know that the keyspan one does not work. Do you have the latest USB patchs for V8.3 Digi changed out the electronics in their controllers to meet RHOS rules. But in their infinite wisdom did not change the oerder number for it. We issued a kit with drivers for these newer Digi controllers. Sorry I don't have the kit name handy. We have support for FTDI232 and PL2303 controllers. Go to USBSTUFF and pick up on that says it has either chip in it. Forrest "Michael Moroney" wrote in message news:geanij$fb9$1@pcls6.std.com... > What USB to RS-232 serial line adapters work with OpenVMS? I've been > chasing a problem that has finally been traced to a port on a Digiboard 16 > line interface randomly dropping characters. In addition, other > Digiboards > won't even configure properly on VMS. I finally was able to do the USB > commands Forrest mentioned earlier so I can file a problem report > regarding the nonconfiguration. > > I vaguely remembered reading that a Radio Shack adaptor supposedly worked > with VMS but a quick trip showed that not true (doesn't even show up). ------------------------------ Date: Thu, 30 Oct 2008 00:42:09 -0000 From: "John Wallace" Subject: Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Message-ID: "Michael Moroney" wrote in message news:geanij$fb9$1@pcls6.std.com... > What USB to RS-232 serial line adapters work with OpenVMS? I've been > chasing a problem that has finally been traced to a port on a Digiboard 16 > line interface randomly dropping characters. In addition, other Digiboards > won't even configure properly on VMS. I finally was able to do the USB > commands Forrest mentioned earlier so I can file a problem report > regarding the nonconfiguration. > > I vaguely remembered reading that a Radio Shack adaptor supposedly worked > with VMS but a quick trip showed that not true (doesn't even show up). USB to serial adapters can be quite "fun" (if you like that kind of thing). I haven't been following what Forrest's been up to, and my recent experience on this subject hasn't been VMS-specific, but a lot of the fun is OS-independent anyway. Apologies if what follows is already known to you. The core innards of many of the smaller adapters likely come from a company called ftdi (see www.ftdichip.com). In fact some of the bigger USB->serial adapters consist of a USB hub and multiple FTDI chips - why not take the lid off your Digiboard and see what's inside? If you have multiple ports active at the same time, you might want to make sure its intermal USB hub chip (if applicable) is a true USB2 hub and not a lower-throughput USB1 hub pretending to be a USB2 device, whilst actually being unable to keep up the throughput. FTDI have been mentioned previously in comp.os.vms but unfortunately I'm not aware of working VMS drivers for FTDI USB->serial hardware (doesn't mean they don't exist). FTDI make a selection of similar USB->serial chips which have a few relatively minor differences among the families. One of the capabilities these chips have is to work with a dirt cheap SROM which contains the PCI vendor ID and device ID and a handful of other customisation options, so that otherwise-identical USB->serial adapters based on the same electronics can be made to look like different bits of kit as far as the PCI autoconfig software (which loads drivers etc) are concerned. So there are lots of apparently different USB->serial adapters on the market which are to all intents and purposes identical inside apart from the vendor and device ID in the SROM. And the reverse may also apply - two identically-badged adapters may have different device and vendor IDs inside, based on whatever the Chinese factory had on the shelf at the time of order... that may well apply with badges like Radio Shack or even Belkin. That leaves the OS (or the driver provider) to sort out the different IDs using the same driver. FTDI's website contains lots of useful info, including some on the pitfalls of USB->serial adapters, which are legion, especially when used in "more demanding" applications. For example, applications which use short message packets and "ping pong" acknowledgement protocols may well take a substantial performance hit when moving from a conventional serial port (low latency) to a USB->serial setup (more latency). Depending on your needs, you may find a LAN->serial device may be more appropriate, but you'll have to pay a *lot* more for one of those than for a simple USB->serial adapter, However, for a multiport adapter the prices are likely to be more comparable. The programmer's view of the device may be different than a conventional VMS terminal device (I've no idea how the Digi USB boxes are presented to VMS). For much of this year I've been using a four port Moxa Nport 6450 serial->LAN box with considerable success (and a few limitations) in a high speed serial data acquisition application where the data is presented on IP sockets. Worth a look. More recently I've been using a Moxa Universal Communicator 7420 which is conceptually similar to the 6450 but comes with a user-programmable embedded Linux inside so you can do protocol handling and time-critical stuff like that in the 7420 rather than on the host system. It seems to be doing the job, so far, although the Linux OS is perfectly capable of obstructing as well as helping. Various folk make PCI->serial cards (obviously including Digi). In some cases they can be a more sensible alternative to these trendy new LAN and USB things; don't rule them out too quickly. ------------------------------ Date: Thu, 30 Oct 2008 04:12:08 +0000 (UTC) From: moroney@world.std.spaamtrap.com (Michael Moroney) Subject: Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Message-ID: "forrret.kenney@hp.com_nospam" writes: > There is a Radio shack one that works and some that do not. The one >with a 6' cable should work it has a PL2303. I know that the keyspan >one does not work. Radio Shack now stocks Gigaware devices. I remember seeing a different package in the past and I actually checked 3 RS's looking to see if any had a different kind. I checked their web site and they have at least 5 different kinds, the Gigaware, two Cables to Go and two others. I don't know which of these they stocked in the past. > Do you have the latest USB patchs for V8.3 Yes, if the latest is the VMS83I USB V1.0 kit (only one on HP's V8.3 I64 patch page) > We have support for FTDI232 and PL2303 controllers. Go to USBSTUFF >and pick up on that says it has either chip in it. OK. Thanks. ------------------------------ Date: Thu, 30 Oct 2008 04:25:22 +0000 (UTC) From: moroney@world.std.spaamtrap.com (Michael Moroney) Subject: Re: USB to Serial Line interface for OpenVMS Itanium/VMS 8.3 Message-ID: "John Wallace" writes: >The core innards of many of the smaller adapters likely come from a company >called ftdi (see www.ftdichip.com). In fact some of the bigger USB->serial >adapters consist of a USB hub and multiple FTDI chips - why not take the lid >off your Digiboard and see what's inside? The Digiboards we have are 2 8 line devices internally. They also seem to make one with 8 2 line cards with the same part number, but we don't seem to have them. >If you have multiple ports active at the same time, you might want to make >sure its intermal USB hub chip (if applicable) is a true USB2 hub and not a >lower-throughput USB1 hub pretending to be a USB2 device, whilst actually >being unable to keep up the throughput. Dunno about that. There are additional expansion USB out jacks so there's definitely a hub of some sort in there. There's not a lot of throughput. The Digi cards are dropping characters from someone hitting return on a terminal. >FTDI have been mentioned previously in comp.os.vms but unfortunately I'm not >aware of working VMS drivers for FTDI USB->serial hardware (doesn't mean >they don't exist). Forrest has mentioned FDTI parts. >Depending on your needs, you may find a LAN->serial device may be more >appropriate, but you'll have to pay a *lot* more for one of those than for a >simple USB->serial adapter, However, for a multiport adapter the prices are >likely to be more comparable. The programmer's view of the device may be >different than a conventional VMS terminal device (I've no idea how the Digi >USB boxes are presented to VMS). They show up as TXDn:. I think the third letter indicates which driver (ultimately which chip) is being used. Unfortunately, the customer doesn't want to use a terminal server for some reason. >Various folk make PCI->serial cards (obviously including Digi). In some >cases they can be a more sensible alternative to these trendy new LAN and >USB things; don't rule them out too quickly. Ones that work with VMS I64? ------------------------------ Date: 29 Oct 2008 20:43:03 -0400 From: Rich Alderson Subject: VAX-11/785 microdiagnostics help requested Message-ID: We have rebuilt the power supplies in two 785s (one native, one a 780-5, i. e. field-upgraded from a 780), and are starting out with diagnostics. The 11/03 front ends run the LSI-11 diagnostics fine. When we boot the system floppy, insert the Microdiagnostics floppy, and type TEST, we do not get the results we expect from the documentation. On the 785, we get a complaint about the SBI, and drop into ODT. On the 780-5, we drop into ODT. Does anyone here remember far enough back to impart a clue or two as to what is going on? -- Rich Alderson "You get what anybody gets. You get a lifetime." news@alderson.users.panix.com --Death, of the Endless ------------------------------ End of INFO-VAX 2008.586 ************************