MajenkoProjects/vs2k-patch-roms
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added patches and docs

Browse Source
This commit is contained in:
Matt Jenkins
2025-07-15 10:56:56 +01:00
parent 4c46a09d42
commit cab6fc6efb
22 changed files with 1991 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
Patches/pk2k/00readme.txt Normal file
View File

@@ -0,0 +1,40 @@
wjm 18-apr-1999: Almost finalized PK2K kits (Vs3100-like SCSI support
for VAXstation 2000 & microVAX 2000) for various flavors
of OpenVMS VAX. Packaging to be improved at some later date.
wjm 10-may-1999: All kits successfully tested (except for the STABACKIT part,
which I might well never use). Consider the files "frozen".
wjm 06-jul-1999: Kits added for oVMS V7.2 (DIF & SRC identical to V7.1).
... NOTE: PK2K is as "unsupported" as can be ...
... but highly likely to just work fine, for you as it does for me ...
PK2K_0013-BIN.ZIP Binaries for VMS V5.5-2, plus the README
(slight update from the 0012 version).
PK2K_0013-BIN.README (ASCII!) Usage notes for the V5.5-2 version.
Applies equally well to the following kits,
with the respective VMS version substituted
for "V5.5-2".
PK2K_0013-061BIN.ZIP Binaries for oVMS V6.1
PK2K_0013-062BIN.ZIP Binaries for oVMS V6.2
PK2K_0013-071BIN.ZIP Binaries for oVMS V7.1
PK2K_0013-072BIN.ZIP Binaries for oVMS V7.2 (NEW!)
PK2K-BOOT_0013.ZIP "Secondary VMB" SYSBOOT images for booting into
a SCSI disk, to be loaded via DUAn: or ESA0:
KA410W_V23_ROM-0013.PATCH
(ASCII!) PATCH command file for improving
upon the "KA410-B V2.3" ROM, allowing it
to boot from SCSI disks, instead of "MUA0".
The bootstrap code within is identical
to the one in PK2K-BOOT_0013.ZIP .
... NOTE: PK2K is as "unsupported" as can be ...
... but highly likely to just work fine, for you as it does for me ...
w.j.moeller, <moeller@gwdg.de>

21
Patches/pk2k/index.html Normal file
View File

@@ -0,0 +1,21 @@
<html>
<head><title>Index of /pub/vms/pk2k/</title></head>
<body>
<h1>Index of /pub/vms/pk2k/</h1><hr><pre><a href="../">../</a>
<a href="old/">old/</a> 11-Jul-2000 12:52 -
<a href="00readme.txt">00readme.txt</a> 06-Jul-1999 07:36 1546
<a href="ka410w_v23_rom-0013.patch">ka410w_v23_rom-0013.patch</a> 10-Apr-1999 00:54 25212
<a href="pk2k-boot_0013.zip">pk2k-boot_0013.zip</a> 10-Apr-1999 00:51 94506
<a href="pk2k_0013-061bin.zip">pk2k_0013-061bin.zip</a> 10-Apr-1999 00:51 17324
<a href="pk2k_0013-061dif.zip">pk2k_0013-061dif.zip</a> 10-Apr-1999 00:53 14885
<a href="pk2k_0013-062bin.zip">pk2k_0013-062bin.zip</a> 10-Apr-1999 00:51 16803
<a href="pk2k_0013-062dif.zip">pk2k_0013-062dif.zip</a> 10-Apr-1999 00:53 14572
<a href="pk2k_0013-071bin.zip">pk2k_0013-071bin.zip</a> 18-Apr-1999 01:03 16966
<a href="pk2k_0013-071dif.zip">pk2k_0013-071dif.zip</a> 18-Apr-1999 01:03 14601
<a href="pk2k_0013-072bin.zip">pk2k_0013-072bin.zip</a> 06-Jul-1999 07:36 16943
<a href="pk2k_0013-072dif.zip">pk2k_0013-072dif.zip</a> 06-Jul-1999 07:36 14601
<a href="pk2k_0013-bin.readme">pk2k_0013-bin.readme</a> 10-May-1999 18:55 4767
<a href="pk2k_0013-bin.zip">pk2k_0013-bin.zip</a> 10-Apr-1999 00:53 19186
<a href="pk2k_0013-dif.zip">pk2k_0013-dif.zip</a> 10-Apr-1999 00:53 14736
</pre><hr></body>
</html>

1670
Patches/pk2k/ka410w_v23_rom-0013.patch Normal file
View File

File diff suppressed because it is too large Load Diff

12
Patches/pk2k/old/index.html Normal file
View File

@@ -0,0 +1,12 @@
<html>
<head><title>Index of /pub/vms/pk2k/old/</title></head>
<body>
<h1>Index of /pub/vms/pk2k/old/</h1><hr><pre><a href="../">../</a>
<a href="test/">test/</a> 10-May-1999 18:08 -
<a href="00readme.txt">00readme.txt</a> 19-Sep-1997 17:27 3715
<a href="pk2k-boot_0010.zip">pk2k-boot_0010.zip</a> 22-Feb-1999 22:35 93009
<a href="pk2k_0012-bin.zip">pk2k_0012-bin.zip</a> 19-Sep-1997 17:28 18644
<a href="pk2k_0012-dif.zip">pk2k_0012-dif.zip</a> 19-Sep-1997 17:28 14283
<a href="pk2k_0012-src.zip">pk2k_0012-src.zip</a> 19-Sep-1997 17:28 130462
</pre><hr></body>
</html>

BIN
Patches/pk2k/pk2k-boot_0013.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-061bin.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-061dif.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-062bin.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-062dif.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-071bin.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-071dif.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-072bin.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-072dif.zip Normal file
View File

Binary file not shown.

132
Patches/pk2k/pk2k_0013-bin.readme Normal file
View File

@@ -0,0 +1,132 @@
wjm 02-apr-1999: PK2KDRVR & assorted patches to system programs, V1.3
Changes over V1.2: Support non-zero SCSI host id (like Vs3100).
*** This is for VMS V5.5-2 only ***
PK2KDRVR is a driver for the Vs2000/uVAX2000 SCSI port
(traditionally known as the "tape controller port").
>>> EXPERIMENTAL software, NO WARRANTIES at all! <<<
Apart from one `feature' and one restriction mentioned next,
it _ought_ to behave just like the Vs3100 SCSI driver (PKNDRIVER).
SCSI host id determination:
The SCSI host adapter _by_default_ used the SCSI id 0
(not 6 or 7, as customary with other SCSI adapters),
meaning you can't use a device on the bus with this id.
This setting can be checked from the ">>> T 50" display,
which under "TPC" shows a longword for each of the SCSI ids
0..7 - the host id is indicated by a longword of FFFFFF03.
Analogous to the ">>> SET SCSI[A]" commands found with other
VAXen, the setting can be changed permanently (saved in NVRAM),
in a somewhat non-intuitive way:
For a host id of ... enter at the >>> prompt ...
7 D/U/P 200B00BC 1C
6 D/U/P 200B00BC 18
5 D/U/P 200B00BC 14
4 D/U/P 200B00BC 10
3 D/U/P 200B00BC 0C
2 D/U/P 200B00BC 08
1 D/U/P 200B00BC 04
0 D/U/P 200B00BC 00
Note: The `field sevice utility' ">>> T 73" (or better,
">>> T 20000073"), aka. "tpmker", does not correctly
cope with a non-zero host id. This is a ROM bug.
T 73 likely has little use to anyone these days.
Known restriction:
PK2KDRVR won't do data transfers of 16kB or more.
This has the effect of limiting the block size
that can be used with SCSI tapes, and also will
break any program that _attempts_ to read 16kB or more.
The only VMS program that does so (which I'm aware of)
is DUMP - see below for a patch.
Disclaimer:
This is *EXPERIMENTAL* SOFTWARE that theoretically
*could* not only crash your system, but *could* cause
CORRUPTION on all media connected to the computer on
which it's installed. (In fact, PK2KDRVR has plenty
of code that *attempts* to crash the system if a chance
for corruption gets noticed. I haven't observed any problem,
let alone a crash, with PK2K on VMS V5.5-2, since the release
of V1.2 in late August 1997, in spite of trying pretty hard :-)
Fact is, the Vs2000/uVAX2000 hardware has never been
"qualified" by anyone to work correctly with SCSI devices.
>>> NO WARRANTIES at all! <<<
Installation & use:
*** This is for VMS V5.5-2 only ***
The "binary kit" contains PK2KDRVR.EXE (not spelled PK2KDRIVER
for quite "technical" reasons) plus 5 patch command files.
Place PK2KDRVR.EXE in SYS$LOADABLE_IMAGES.
Use
$ PATCH @2KSYSGEN.COM
to create 2KSYSGEN.EXE in the current directory.
>>> Make sure that no MUA0 shows up, and that TVDRIVER
>>> (the Vs2000/uVAX2000 magtape driver) is _not_ loaded.
Use
$ MCR [dir]2KSYSGEN AUTOCONFIGURE ALL
to load PK2KDRVR (ought to show up as device PKA0)
and autoconfigure the SCSI devices, just like on a Vs3100.
If you're confident enough in the driver that you want
the machine to auto-configure the SCSI at boot time,
create two more programs (which _may_ only be required
if the machine is a cluster member),
2KSTACONFIG.EXE via $ PATCH @2KSTACONFIG.COM
plus 2KCONFIGURE.EXE via $ PATCH @2KCONFIGURE.COM
and copy
2KSYSGEN.EXE to SYS$SYSTEM:SYSGEN.EXE
2KSTACONFIG.EXE to SYS$SYSTEM:STACONFIG.EXE
2KCONFIGURE.EXE to SYS$SYSTEM:CONFIGURE.EXE
Each of these programs supposedly behaves just like
the VMS "original", when executed on a VAX other than
a Vs2000 or uVAX2000.
For completeness' sake, there are two more patch command
files that create PK2K-aware versions of STASYSGEN.EXE and
STANDCONF.EXE . Both of these are only used by stand-alone
BACKUP - in order to build a PK2K-aware kit, place the
patched programs into SYS$SYSTEM under the original name,
and modify SYS$UPDATE:STABACKIT-TABLE.DAT by replacing
"TVDRIVER.EXE" with "PK2KDRVR.EXE". You may also wish to
change STABACKIT.COM such that it accepts generic SCSI tape
(devtype 28) and on that occasion make it refer to a differently
named *-TABLE.DAT - I did find a non-DEC DAT drive from which
a Vs2000 did boot, with the tape configured as MKA100
(">>> B MUA0" expects the tape to have a SCSI id of 1).
Lastly, there's 2KDUMP.COM which will create 2KDUMP.EXE
via $ PATCH @2KDUMP.COM
Use the result instead of the original SYS$SYSTEM:DUMP.EXE
in order to DUMP blocks from a SCSI tape drive, e.g. via
$ DEFINE/USER DUMP dev:[dir]2KDUMP.EXE
$ DUMP MKAu00:
or similar. Contrary to standard DUMP, 2KDUMP will - independent of
hardware - read at most 16k-1 bytes per tape block (no big deal :-).
Wolfgang J. Möller, Göttingen, F.R.Germany <moeller@gwdg.de>

BIN
Patches/pk2k/pk2k_0013-bin.zip Normal file
View File

Binary file not shown.

BIN
Patches/pk2k/pk2k_0013-dif.zip Normal file
View File

Binary file not shown.