VAX 6400 booting saga: how to transfer binaries to VMS with k ermit?

From: Carlini, Antonio <Antonio.Carlini_at_riverstonenet.com>
Date: Tue Dec 11 01:52:08 2001

>
> %STDRV-I-STARTUP, OpenVMS startup begun at 10-DEC-2001 22:56:23.89
> %SYSGEN-E-SYSVERDIF, system version mismatch - reassemble and
> relink driver
> -SYSGEN-I-DRIVENAM, driver name is SIDRIVER
> %SYSGEN-E-SYSVERDIF, system version mismatch - reassemble and
> relink driver
> -SYSGEN-I-DRIVENAM, driver name is SIDRIVER
>
> this driver version mismatch prevents me from doing a SYSGEN
> etc. Where can I turn off dependency to this driver?

That's the driver for the DMB32. To hide it from
SYSGEN it just needs to be renamed:

  $ RENAME SYS$COMMON:[SYS$LDR]SIDRIVER.EXE SYS$COMMON:[SYS$LDR]SIDRIVER.OLD

But just in case, it might be worth checking that you
don't have more than one version lying around:

  $ DIR SYS$LOADABLE_IMAGES:SIDRIVER.EXE

Normally I would suggest purging down if multiple files
are kicking around, but since this system is all you have,
I'd go with renaming all of them and keeping the version
numbers the same i.e.
    $ RENAME SYS$COMMON:[SYS$LDR]SIDRIVER.EXE;33
SYS$COMMON:[SYS$LDR]SIDRIVER.OLD;33
or whatever.

The other WAN device drivers you won't care about are
SJDRIVER, SLDRIVER, SFDRIVER, SEDRIVER, ZTDRIVER
and ZWDRIVER ... actually I'm sure there are more,
I've just mislaid my list! If SIDRIVER is out of date
I guess that the rest will be too. However, I assume that
SIDRIVER is getting dragged in because SYSGEN found
a DMB32?



Antonio
Received on Tue Dec 11 2001 - 01:52:08 GMT