From: CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 4-NOV-1988 15:14 To: MRGATE::"ARISIA::EVERHART" Subj: XADRIVER is broken in VMS 5 Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Fri, 4 NOV 88 02:26:39 PDT Received: from Sun.COM by KL.SRI.COM with TCP; Fri, 4 Nov 88 02:13:36 PST Received: from sun.Sun.COM (sun-bb.sun.com) by Sun.COM (4.0/SMI-4.0) id AA09297; Fri, 4 Nov 88 02:11:01 PST Received: from sequent.UUCP by sun.Sun.COM (4.0/SMI-4.0) id AA13749; Fri, 4 Nov 88 02:13:39 PST Received: by sybil.ARPA (4.12/4.7) id AA04026; Thu, 3 Nov 88 23:43:49 est Date: Thu, 3 Nov 88 23:43:49 est From: sequent!sybil!ardai@Sun.COM (Mike Ardai) Message-Id: <8811040443.AA04026@sybil.ARPA> To: sequent!sun!kl.sri.com!info-vax@Sun.COM Subject: XADRIVER is broken in VMS 5 Thanks to all who responded. According to DEC, there is a known bug in XADRIVER which is causing these timeouts. This bug is in 5.0, 5.0-1, and (I think) 5.0-2. It is supposed to be fixed in a 'future release' (probably/hopefully 5.0-3). In the meantime, it is very easy to fix if you don't mind hacking the driver. * Copy SYS$EXAMPLES:XADRIVER.MAR to a working directory * Find the DEVICELOCK macro, and change PRESERVE=NO to PRESERVE=YES in the line above MNEGW UCB$L_XA_DPR(R5),XA_WCR(R4) * Re-assemble the driver with MACRO /LIS/OBJ XADRIVER+SYS$LIBRARY:LIB/LIB * Create a file called BASE_ZERO.OPT containng the line BASE=0 * Link the driver with LINK/NOSYSSHR/NOTRACE/NODEBUG/CONTIG/MAP=XADRIVER/FULL/CROSS - XADRIVER, SYS$SYSTEM:SYS.STB/SELECTIVE,BASE_ZERO/OPT * Copy the new XADRIVER.EXE to SYS$LOADABLE_IMAGES and reboot This has been tested on both a uVAX II and a 730 (with a DRV11 and a DR11W respectively) and everything works fine. \ | / Michael L. Ardai Teradyne EDA DATA Group \|/ Usenet: ...!sun!sequent!sybil!ardai ---*--- --------------------------------------------------------------------- /|\ USnail: 179 Lincoln St. Boston MA 02111 / | \ I don't speak for Teradyne; they don't even know I am speaking...