Xref: utzoo comp.graphics:9359 comp.os.vms:21581
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!dino!hascall
From: hascall@cs.iastate.edu (John Hascall)
Newsgroups: comp.graphics,comp.os.vms
Subject: Re: Help with Iris 1200 XNS driver on VAX/VMS
Keywords: Iris 1200, XNS driver, VAX/VMS
Message-ID: <288@dino.cs.iastate.edu>
Date: 15 Jan 90 19:59:35 GMT
References: <1393@ssc-bee.ssc-vax.UUCP>
Sender: usenet@dino.cs.iastate.edu
Followup-To: comp.graphics
Organization: Iowa State Univ. Computation Center
Lines: 29


   (sorry to post, mail is being stupid again)

In article <1393> okinaka@ssc-vax.UUCP (Nathan Okinaka) writes:
}We just upgraded our VAX 11/780 from VMS 4.7 to VMS 5.2 and now our
}Iris 1200 graphics processor from Silicon Grahpics will not communicate
}with our VAX.  The Iris 1200 is connected to our VAX via ethernet using
}the XNS protocol.  The XNS driver that we have on the VAX is no longer 
}compatible with VMS 5.2 and we do not have the source to recompile and 
}relink the driver.  
 
      A possible solution is to patch the driver image so that it
      looks like it was compiled under VMS 5.x.  The version number 
      is stored at offset DPT$W_VERSION (x18) in the Driver Prologue
      Table (which just happens to be the first thing in the driver :-)
      So what you need to do is:

	    $ patch disk:[dir]xxDRIVER.EXE
	    PATCH> examine/word 18
	    00000018:  0004                    <--- version 4
	    PATCH> deposit/word 18 = 5         <--- version 5
	    PATCH> update                      <--- write file back
	    PATCH> exit

      and give it a try (might work, might not, depends on if the
      driver does any VMS 4.x specific things).

Best of luck,
John Hascall  /  ISU Comp Ctr