tencati@VLSI.JPL.NASA.GOV (Ron Tencati) (03/18/88)
I have an 11/780 with a Fuji Eagle as a system disk. This is running on an Emulex SC7000 controller which requires that DRDRIVER be patched in order to boot from this volume. I am currently running VMS V4.5 with the V4.4 patched version of DRDRIVER. There were no patches made to DRDRIVER by V4.5, so I re-used the driver successfully. I now am upgrading to V4.6/V4.7 and will need a patched driver once again. I have not gotten any patches from Emulex. Can V4.7 does not patch DRDRIVER. I'm not sure if 4.6 does or not, but you get a new image with the distribution. Questions: Can I re-apply the V4.4 patches to the V4.7 version of DRDRIVER? Can I re-use the V4.4 version of DRDRIVER that I have used under V4.5? Do patches exist from Emulex for V4.6/4.7? Thanks in advance for any information. Ron Tencati Jet Propulsion Laboratory (818) 354-8359 TENCATI@VLSI.JPL.NASA.GOV
jim@rtech.UUCP (Jim Gessling) (03/23/88)
In article <880317125914.51c@VLSI.JPL.NASA.GOV>, tencati@VLSI.JPL.NASA.GOV (Ron Tencati) writes: > I have an 11/780 with a Fuji Eagle as a system disk. This is running on > an Emulex SC7000 controller which requires that DRDRIVER be patched in order > to boot from this volume. > > I now am upgrading to V4.6/V4.7 and will need a patched driver once again. I > have not gotten any patches from Emulex. > > Can V4.7 does not patch DRDRIVER. I'm not sure if 4.6 does or not, but you get > a new image with the distribution. > > Questions: > > Can I re-apply the V4.4 patches to the V4.7 version of DRDRIVER? > Can I re-use the V4.4 version of DRDRIVER that I have used under V4.5? > Do patches exist from Emulex for V4.6/4.7? > > Thanks in advance for any information. > > Ron Tencati > Jet Propulsion Laboratory > (818) 354-8359 > TENCATI@VLSI.JPL.NASA.GOV Those of you saddled with Emulex SC750 or SC780 disk controllers know that patching DRdriver.exe is required to run Fujitsu Eagles and other expanded disk emulations. Rather than wait for Emulex to come out with the patches for VMS 4.6 I went ahead and figured them out for myself. I was just a matter of changing the offsets for the patches that had moved in the driver. It seems the driver got 4 bytes longer so 4 had to be added in the appropriate places. If you are booting off one of these disks then you need to patch VMB.exe as well. I didn't have to do that so it is left as an exercise to the reader. Please have a good backup of your system disk before playing with this. Then copy drdriver to a safe place and do @drpatch.v46. Copy drdriver back to sys$system and reboot. No warranty is given with this posting. Diffs follow. Jim@Rtech ************ File SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V45;2 26 $ ASSIGN/USER NL: SYS$OUTPUT: 27 $ patch/journal=vmi$kwd:drdriver/output=vmi$kwd:drdriver vmi$kwd:drdriver.exe 28 ****** File SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V46;2 26 $ patch/journal=drdriver/output=drdriver drdriver.exe 27 ************ ************ File SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V45;2 34 DEFINE PATCH = DR$DDT+0A3B ! put patch at end of driver 35 DEFINE PATCH2 = DR$DDT+0A3D ! second part of patch 36 DEFINE PATCH_SIZE = 79 ! size of patch 37 DEFINE DRIVER_END = DR$DDT+0A3E ! end of unpatched driver 38 ****** File SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V46;2 33 DEFINE PATCH = DR$DDT+0A3F ! put patch at end of driver 34 DEFINE PATCH2 = DR$DDT+0A41 ! second part of patch 35 DEFINE PATCH_SIZE = 79 ! size of patch 36 DEFINE DRIVER_END = DR$DDT+0A42 ! end of unpatched driver 37 ************ ************ File SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V45;2 123 REPLACE/INST DR$DDT+5FE ! Make sure it's the correct 124 'SUBB2 #4,R1' ! patch loc ****** File SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V46;2 122 REPLACE/INST DR$DDT+602 ! Make sure it's the correct 123 'SUBB2 #4,R1' ! patch loc ************ Number of difference sections found: 3 Number of difference records found: 7 DIFFERENCES /IGNORE=()/MERGED=1/OUTPUT=SYS$SYSROOT:[SYSMGR.EMULEX]DIFF.DAT;2- SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V45;2- SYS$SYSROOT:[SYSMGR.EMULEX]DRPATCH.V46;2