• Please review our updated Terms and Rules here

INSTRUCTIONS For installing RT11 on a SCSI2SD card - PDP11/83

8008guy

Veteran Member
Joined
Jun 25, 2014
Messages
584
Location
Salt Lake City, Utah
Hi,

As promised, here are the end to end instructions to get RT11 on a SCSI2SD card and running on a PDP11/83 with an Emulex UC07 controller. I used SIMH to build the disks. This should work with a real SCSI drive as well.. All of this is cut and paste from a live session, so there should not be errors. Although, if you spot something please let me know.

Thank you to ALL those who have provided examples and the hard work of making this possible.

len


################################################################################

1. These instructions assume that you have a working SCSI2SD card. (I am
running firmware 3.6-RC2.)

2. A functional PDP11/83 with a Emulex UC07 controller card.

3. A working version of SIMH installed on a Linux box that has a SCSI
controller to connect to the SCSI2SD card.


We will configure the SCSI2SD card to look like a RA82 (608M)

57 Sect/Track * 15 Track/Cyl * 1423 Cyl = 1,216,665 Total Sectors

1,216,665 Sectors * 512 bytes = 622,932,480 byte (608.3325 MB)

For convenience I built two SCSI2SD cards. I keep one in my Linux machine
that I use for my PDP11 emulator, and the other in my PDP11. (It just makes
life easier...) Configure both SCSI2SD cards the same.

################################################################################

First run scsi2sd-config.exe without any arguments to see the current
configuration.


C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>scsi2sd-config.exe
SCSI2SD Configuration Utility.
Copyright (C) 2013 Michael McMaster <michael@codesrc.com>

USB device parameters
Vendor ID: 0x04B4
Product ID: 0x1337
Device Found
Firmware Version: 3.6

Current Device Settings:
SCSI ID: 0
Vendor: " codesrc"
Product ID: " SCSI2SD"
Revision: " 3.5"

Parity Checking: enabled
Unit Attention Condition: enabled
Bytes per sector: 512
Maximum Size: Unlimited

C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>

################################################################################


If you have an existing configuration you can get back to the factory default
setting by running:

scsi2sd-config.exe --reset.

You can also view the help screen by running:

scsi2sd-config.exe --help


C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>scsi2sd-config.exe --help
SCSI2SD Configuration Utility.
Copyright (C) 2013 Michael McMaster <michael@codesrc.com>

USB device parameters
Vendor ID: 0x04B4
Product ID: 0x1337
Device Found
Firmware Version: 3.6
scsi2sd-config.exe: unknown option -- help
Usage: scsi2sd-config [options...]

--id={0-7} SCSI device ID.

--parity Check the SCSI parity signal, and reject data where
the parity is bad.

--no-parity Don't check the SCSI parity signal.
This is required for SCSI host controllers that do not provide
parity.

--attention Respond with a Unit Attention status on device reset.
Some systems will fail on this response, even though it is
required by the SCSI-2 standard.

--no-attention Disable Unit Attention responses.

--blocks={0-4294967295}
Set a limit to the reported device size.
The size of each block/sector is set by the --sector parameter.
The reported size will be the lower of this value and the SD
card size. 0 disables the limit.
The maximum possible size is 2TB.

--sector={64-8192}
Set the bytes-per-sector. Normally 512 bytes.
Can also be set with a SCSI MODE SELECT command.

--apple Set the vendor, product ID and revision fields to simulate an
apple-suppled disk. Provides support for the Apple Drive Setup
utility.

--vendor={vendor} Sets the reported device vendor. Up to 8 characters.

--prod-id={prod-id} Sets the reported product ID. Up to 16 characters.

--rev={revision} Sets the reported device revision. Up to 4 characters.

--reset Revert all settings to factory defaults.



The current configuration settings are displayed if no options are supplied


C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>


################################################################################

Let's set up our SCSI2SD card to be the size of a RA82. I am also going to set
the Vendor and Product ID to something that makes more sense, these are both
optional.


C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>scsi2sd-config.exe --blocks=1216665
SCSI2SD Configuration Utility.
Copyright (C) 2013 Michael McMaster <michael@codesrc.com>

USB device parameters
Vendor ID: 0x04B4
Product ID: 0x1337
Device Found
Firmware Version: 3.6

Saving configuration... Done.

Current Device Settings:
SCSI ID: 0
Vendor: " codesrc"
Product ID: " SCSI2SD"
Revision: " 3.5"

Parity Checking: enabled
Unit Attention Condition: enabled
Bytes per sector: 512
Maximum Size: Unlimited




C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>scsi2sd-config.exe --vendor=SCSI2SD
SCSI2SD Configuration Utility.
Copyright (C) 2013 Michael McMaster <michael@codesrc.com>

USB device parameters
Vendor ID: 0x04B4
Product ID: 0x1337
Device Found
Firmware Version: 3.6

Saving configuration... Done.

Current Device Settings:
SCSI ID: 0
Vendor: " codesrc"
Product ID: " SCSI2SD"
Revision: " 3.5"

Parity Checking: enabled
Unit Attention Condition: enabled
Bytes per sector: 512
Maximum Size: 594.07MB (1216665 sectors)



C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>scsi2sd-config.exe --prod-id=RA82
SCSI2SD Configuration Utility.
Copyright (C) 2013 Michael McMaster <michael@codesrc.com>

USB device parameters
Vendor ID: 0x04B4
Product ID: 0x1337
Device Found
Firmware Version: 3.6

Saving configuration... Done.

Current Device Settings:
SCSI ID: 0
Vendor: "SCSI2SD "
Product ID: "RA82 "
Revision: " 3.5"

Parity Checking: enabled
Unit Attention Condition: enabled
Bytes per sector: 512
Maximum Size: 594.07MB (1216665 sectors)

C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>


To verify that everything worked properly run scsi2sd-config.exe without
arguments.


C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>scsi2sd-config.exe
SCSI2SD Configuration Utility.
Copyright (C) 2013 Michael McMaster <michael@codesrc.com>

USB device parameters
Vendor ID: 0x04B4
Product ID: 0x1337
Device Found
Firmware Version: 3.6

Current Device Settings:
SCSI ID: 0
Vendor: "SCSI2SD "
Product ID: "RA82 "
Revision: " 3.5"

Parity Checking: enabled
Unit Attention Condition: enabled
Bytes per sector: 512
Maximum Size: 594.07MB (1216665 sectors)

C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>

########################################

Since my Emulator box has an existing SCSI drive with an ID of "Zero" I
set the SCSI2SD card for my emulator box to "One."


C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>scsi2sd-config.exe --id=1
SCSI2SD Configuration Utility.
Copyright (C) 2013 Michael McMaster <michael@codesrc.com>

USB device parameters
Vendor ID: 0x04B4
Product ID: 0x1337
Device Found
Firmware Version: 3.6

Saving configuration... Done.

Current Device Settings:
SCSI ID: 1
Vendor: "SCSI2SD "
Product ID: "RA82 "
Revision: " 3.5"

Parity Checking: enabled
Unit Attention Condition: enabled
Bytes per sector: 512
Maximum Size: 594.07MB (1216665 sectors)

C:\tmp\PDP\0_MY_PDP\SCSI2SD\SW\v3.6-RC2>


################################################################################

Next Boot your PDP11 and configure your UC07 SCSI controller. (I shamelessly
copied these instructions from "Matlocks" posting from the tread below.

Thank you Matlock!!!

http://www.vintage-computer.com/vcforum/showthread.php?43516-SCSI2SD-help/page3

Once your PDP11 is at the console prompt toggle the halt switch to get it into
the ODT and duplicate the follow steps.


########################################

Testing in progress - Please wait
Memory Size is 4088 K Bytes
9 Step memory test
Step 1 2 3 4 5 6 7 8 9


Message 04 Entering Dialog mode

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key:


165240
@17772150/000000 1
17772152/005400 30003
@/000400 42000
@17772152/002000
@200g


Disk Firmware-Resident Diagnostic
Copyright (c) 1988 Emulex Corporation all rights reserved
UC07/8 controller, firmware revision level R
IP address = 172150

Option Menu
----------------------------------------------------------------------------
1 - Format 2 - Verify
3 - Format & Verify 4 - Data Reliability
5 - Format, Verify, & Data Reliability 6 - Read Only
7 - List Known Units 8 - Replace Block
9 - Write RCT 10 - Optical Read all Diag Sectors
11 - Optical Write a Diag Sector 12 - Issue Mode Select
13 - Display Novram 14 - Edit / Load Novram

Enter option number: 14

Emulex automatic set-up of UCxx [Y or N, def=N]? Y

ALL DEVICES MUST BE POWERED UP AND READY

Hit any key to continue

SCSI ADDRESS 0 LUN 0, SCSI2SD , RA82 , REV LEVEL = 3.5

Unit offset if alternate controller address is selected, or
unit number to autoboot from if not alternate controller.
Enter unit offset/auto-boot unit number [0-15,def=0]:

Do you want to configure another unit [Y or N,def=N]?

Do you want to change any parameters [Y or N,def=N]? Y

Dma threshold [1-8,def=1]: 8

Dma burst delay in multiples of 2 [2-32,def=4]: 2

Host adapter scsi address [0-7,def=7]:

Enable scsi parity checking [Y or N,def=N]?

Enable ESP chip slow cable mode [Y or N,def=N]? Y

Unit offset if alternate controller address is selected, or
unit number to autoboot from if not alternate controller.
Enter unit offset/auto-boot unit number [0-15,def=0]:

ST506 = 1 ESDI/EMBEDDED = 2 Optical = 3 Auto-size = 4
Type code [1-4,def=4]: 4

Current media ID is: RA81

Do you want to change media ID [Y or N, def = N]? Y

Please select a media ID number from this table - [0-5]
or type RETURN to use current default

0 = RA81
1 = RA82
2 = RA90
3 = RA91
4 = RA92
5 = RD54
Media ID,def=0]: 1

Full capacity mode [Y or N,def=Y]?

Do you want to enable transparent replacements [Y or N,def=Y]?

Do you want to ignore FCT errors [Y or N,def=N]?

Disable scsi disconnects [Y or N,def=N]?

Prevent manual spin-down of mounted media [Y or N,def=N]?

Enable synchronous data transfers [Y or N,def=N]?

Disable host adaptor polling of drive [Y or N,def=N]?

Scsi controller address [0-7,def=0]:

Scsi logical unit number [0-7,def=0]:

Do you want to configure another unit [Y or N,def=N]?

Do you want to change any parameters [Y or N,def=N]?

** ALL DATA ON DRIVE CAN BE LOST **
DO YOU WANT TO LOAD THE NOVRAM [Y or N]? Y

Option Menu
----------------------------------------------------------------------------
1 - Format 2 - Verify
3 - Format & Verify 4 - Data Reliability
5 - Format, Verify, & Data Reliability 6 - Read Only
7 - List Known Units 8 - Replace Block
9 - Write RCT 10 - Optical Read all Diag Sectors
11 - Optical Write a Diag Sector 12 - Issue Mode Select
13 - Display Novram 14 - Edit / Load Novram

Enter option number: 7

Drive Status Unit Size
-------------------------------
0 Available 1216601

Hit any key to continue

Option Menu
----------------------------------------------------------------------------
1 - Format 2 - Verify
3 - Format & Verify 4 - Data Reliability
5 - Format, Verify, & Data Reliability 6 - Read Only
7 - List Known Units 8 - Replace Block
9 - Write RCT 10 - Optical Read all Diag Sectors
11 - Optical Write a Diag Sector 12 - Issue Mode Select
13 - Display Novram 14 - Edit / Load Novram

Enter option number: 13

Dma threshold [1-8] = 8

Dma burst delay in multiples of 2 [2-32] = 2

Host adapter scsi address [0-7] = 7

Enable scsi parity checking [Y or N] = N

Enable ESP chip slow cable mode [Y or N] = Y

Unit offset if alternate controller address is selected, or
unit number to autoboot from if not alternate controller.
Enter unit offset/auto-boot unit number [0-15] = 0

Hit any key to continue

ST506 = 1 ESDI/EMBEDDED = 2 Optical = 3 Auto-size = 4
Type code [1-4] = 4

Current media ID is: RA82

Full capacity mode [Y or N] = Y

Do you want to enable transparent replacements [Y or N] = Y

Do you want to ignore FCT errors [Y or N] = N

Disable scsi disconnects [Y or N] = N

Prevent manual spin-down of mounted media [Y or N] = N

Enable synchronous data transfers [Y or N] = N

Hit any key to continue

Disable host adaptor polling of drive [Y or N] = N

Scsi controller address [0-7] = 0

Scsi logical unit number [0-7] = 0

Hit any key to continue

Option Menu
----------------------------------------------------------------------------
1 - Format 2 - Verify
3 - Format & Verify 4 - Data Reliability
5 - Format, Verify, & Data Reliability 6 - Read Only
7 - List Known Units 8 - Replace Block
9 - Write RCT 10 - Optical Read all Diag Sectors
11 - Optical Write a Diag Sector 12 - Issue Mode Select
13 - Display Novram 14 - Edit / Load Novram

Enter option number:

########################################

Now power down your PDP 11 and move to your Emulator. If you only have
one SCSI2SD you will need to move it to your Emulator box.

################################################################################

From your Linux prompt check to see if your controller sees the SCSI2SD card.
Use dmesg to display the boot messages and then search through the results
for your SCSI2CD drive.


root@pdpe:~/SIMH# dmesg | less
[16.636815] scsi 2:0:1:0: Direct-Access SCSI2SD RA82 3.5 PQ: 0 ANSI: 2 CCS
[20.078253] sd 2:0:1:0: [sdb] 1216665 512-byte logical blocks: (622 MB/594 MiB)


If you see your SCSI2SD card you are ready to build your RT11 boot disk. You also
need to indentify which device your RA82 is on.

Grab this RT11 working disk.

ftp://ftp.trailing-edge.com/pub/rt_dists/dists/rt56b.dsk


It may also be helpful to download the following RT11 documentation.

http://bitsavers.trailing-edge.com/pdf/dec/pdp11/rt11

AA-H376F-TC_RT-11_Installation_Guide_Aug91
AA-PDU0A-TC_RT-11_Commands_Manual_Aug91

Before you install RT11 you may want to refer to Chapter 1 and 4
for more detail about the manual installation process.


In your Emulators working directory create a new RA82 blank image using the
following command:

root@pdpe:~/SIMH# dd bs=512 count=1216665 < /dev/zero > rt11_83_RA82.dsk

Start your Emulator and execute the following commands:

root@pdpe:~/SIMH# pdp11

PDP-11 simulator V4.0-0 Beta git commit id: 18175040
sim> set rl enable
sim> set cpu 4m
Disabling RK
Disabling HK
Disabling TM
sim> set cpu 11/83
sim> set rq0 ra81
sim> set rq1 ra82
sim> att rq0 rt56b.dsk
sim> att rq1 rt11_83_RA82.dsk
sim> boot rq0

RT-11FB V05.07

.TYPE V5USER.TXT

RT-11 V5.7

Installation of RT-11 Version 5.7 is complete and you are now running
RT-11 from your system volume.

Your system volume is your working volume if you have used the Automatic
Installation (AI) procedure. If you have installed RT-11 using that
procedure, Mentec recommends you verify the correct operation of your
system's software using the VERIFY verification procedure. You can only
perform VERIFY on the valid target (output) media you used for the AI
procedure. Run VERIFY before you run CONFIG. To run VERIFY, enter the
command:
IND VERIFY

Mentec recommends you read the file V5NOTE.TXT, which you can TYPE or
PRINT. Also, read the Introduction to RT-11, rewritten for V5.7, which
contains much of the information you need to use RT-11 Version 5.7.


.R MSCPCK
?MSCPCK-I-MU0-TK50 FW Rev Level is 005/HW Rev Level is 001
?MSCPCK-W-TQK50 controller below FW Rev 4/HW Rev 6

.initialize/badblocks du1:
DU1:/Initialize; Are you sure? Y
?DUP-I-No bad blocks detected DU1:

.dir du1:


0 Files, 0 Blocks
65467 Free blocks

.squeeze/output:du1: du0:

You can select one of several RT11 Monitors. Refer to page 1-2
and 1-3 of the RT-11 Installation Guide.

.copy/boot du1:RT11ZM.SYS du1:

.squeeze du1:
DU1:/Squeeze; Are you sure? Y

.dir du1:

SWAP .SYS 28P 21-Jan-2000 RT11AI.SYS 96P 21-Jan-2000
RT11SB.SYS 97P 21-Jan-2000 RT11FB.SYS 106P 21-Jan-2000
RT11XM.SYS 124P 21-Jan-2000 RT11ZM.SYS 127P 21-Jan-2000
DL .SYS 4P 21-Jan-2000 DM .SYS 5P 21-Jan-2000
DU .SYS 10P 21-Jan-2000 DW .SYS 6P 21-Jan-2000
DX .SYS 4P 21-Jan-2000 DY .SYS 4P 21-Jan-2000
DZ .SYS 4P 21-Jan-2000 RK .SYS 3P 21-Jan-2000
LD .SYS 11P 21-Jan-2000 LP .SYS 2P 21-Jan-2000
LS .SYS 5P 21-Jan-2000 MM .SYS 10P 21-Jan-2000
.
.
.
CT .MAC 101P 21-Jan-2000 DD .MAC 66P 21-Jan-2000
DP .MAC 24P 21-Jan-2000 DS .MAC 20P 21-Jan-2000
DT .MAC 18P 21-Jan-2000 PC .MAC 11P 21-Jan-2000
PD .MAC 31P 21-Jan-2000 RF .MAC 15P 21-Jan-2000
224 Files, 7178 Blocks
58289 Free blocks

.<CNTL> e to end emulation

Simulation stopped, PC: 147700 (MOV R4,130054)
sim> exit
Goodbye

Now use dd to copy your newly created image to your SCSI2SD card.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
MAKE SURE YOUR SELECT THE CORRECT DESTINATION DRIVE FOR YOUR
SYSTEM. /dev/sbd is correct for mine. IF YOU DO THIS WRONG
YOU CAN WIPE OUT YOUR LINUX OPPERATING SYSTEM!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

root@pdpe:~/SIMH# dd bs=512 if=rt11_83_RA82.dsk of=/dev/sdb
1216665+0 records in
1216665+0 records out
622932480 bytes (623 MB) copied, 433.032 s, 1.4 MB/s

Next shut down your system and move the SD card or the SCSI2SD
card to your PDP11.


################################################################################

With the newly installed RT11 system dvive connected, power up and boot your
PDP11:



Testing in progress - Please wait
Memory Size is 4088 K Bytes
9 Step memory test
Step 1 2 3 4 5 6 7 8 9


Message 04 Entering Dialog mode

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B DU


Trying DU0

Starting system from DU0


RT-11ZM V05.07

.TYPE V5USER.TXT

RT-11 V5.7

Installation of RT-11 Version 5.7 is complete and you are now running
RT-11 from your system volume.

Your system volume is your working volume if you have used the Automatic
Installation (AI) procedure. If you have installed RT-11 using that
procedure, Mentec recommends you verify the correct operation of your
system's software using the VERIFY verification procedure. You can only
perform VERIFY on the valid target (output) media you used for the AI
procedure. Run VERIFY before you run CONFIG. To run VERIFY, enter the
command:
IND VERIFY

Mentec recommends you read the file V5NOTE.TXT, which you can TYPE or
PRINT. Also, read the Introduction to RT-11, rewritten for V5.7, which
contains much of the information you need to use RT-11 Version 5.7.


.R MSCPCK

.dir

SWAP .SYS 28P 21-Jan-2000 RT11AI.SYS 96P 21-Jan-2000
RT11SB.SYS 97P 21-Jan-2000 RT11FB.SYS 106P 21-Jan-2000
RT11XM.SYS 124P 21-Jan-2000 RT11ZM.SYS 127P 21-Jan-2000
DL .SYS 4P 21-Jan-2000 DM .SYS 5P 21-Jan-2000
DU .SYS 10P 21-Jan-2000 DW .SYS 6P 21-Jan-2000
DX .SYS 4P 21-Jan-2000 DY .SYS 4P 21-Jan-2000
DZ .SYS 4P 21-Jan-2000 RK .SYS 3P 21-Jan-2000
LD .SYS 11P 21-Jan-2000 LP .SYS 2P 21-Jan-2000
LS .SYS 5P 21-Jan-2000 MM .SYS 10P 21-Jan-2000
MS .SYS 11P 21-Jan-2000 MT .SYS 9P 21-Jan-2000
MU .SYS 14P 21-Jan-2000 NL .SYS 2P 21-Jan-2000
PI .SYS 60P 21-Jan-2000 SL .SYS 17P 21-Jan-2000
SLMIN .SYS 12P 21-Jan-2000 SP .SYS 7P 21-Jan-2000
VM .SYS 3P 21-Jan-2000 XC .SYS 4P 21-Jan-2000
XL .SYS 4P 21-Jan-2000 DLX .SYS 5P 21-Jan-2000
DMX .SYS 5P 21-Jan-2000 DUX .SYS 13P 21-Jan-2000
DWX .SYS 6P 21-Jan-2000 DXX .SYS 4P 21-Jan-2000
DYX .SYS 4P 21-Jan-2000 DZX .SYS 4P 21-Jan-2000
LDX .SYS 11P 21-Jan-2000 LPX .SYS 2P 21-Jan-2000
LSX .SYS 5P 21-Jan-2000 MMX .SYS 11P 21-Jan-2000
MSX .SYS 12P 21-Jan-2000 MTX .SYS 10P 21-Jan-2000
MUX .SYS 19P 21-Jan-2000 NCX .SYS 10P 21-Jan-2000
NLX .SYS 2P 21-Jan-2000 NQX .SYS 10P 21-Jan-2000
NUX .SYS 10P 21-Jan-2000 PIX .SYS 68P 21-Jan-2000
RKX .SYS 3P 21-Jan-2000 SLX .SYS 20P 21-Jan-2000
SPX .SYS 11P 21-Jan-2000 UBX .SYS 13P 21-Jan-2000
VMX .SYS 3P 21-Jan-2000 XCX .SYS 4P 21-Jan-2000
XLX .SYS 4P 21-Jan-2000 STRTAI.COM 46P 21-Jan-2000
STRTFB.COM 5P 21-Jan-2000 STRTSB.COM 1P 21-Jan-2000
STRTXM.COM 8P 21-Jan-2000 STRTXB.COM 5P 21-Jan-2000
STRTZM.COM 8P 21-Jan-2000 STRTZB.COM 5P 21-Jan-2000
PIP .SAV 30P 21-Jan-2000 DUP .SAV 52P 21-Jan-2000
DIR .SAV 20P 21-Jan-2000 IND .SAV 58P 21-Jan-2000
RESORC.SAV 35P 21-Jan-2000 EDIT .SAV 19P 21-Jan-2000
KED .SAV 85P 21-Jan-2000 KEX .SAV 72P 21-Jan-2000
MACRO .SAV 63P 21-Jan-2000 CREF .SAV 6P 21-Jan-2000
LINK .SAV 59P 21-Jan-2000 MONMRG.SAV 14P 21-Jan-2000
LIBR .SAV 24P 21-Jan-2000 FILEX .SAV 22P 21-Jan-2000
SRCCOM.SAV 26P 21-Jan-2000 BINCOM.SAV 25P 21-Jan-2000
SLP .SAV 13P 21-Jan-2000 DUMP .SAV 10P 21-Jan-2000
SIPP .SAV 21P 21-Jan-2000 BUP .SAV 68P 21-Jan-2000
PAT .SAV 11P 21-Jan-2000 HELP .SAV 161P 21-Jan-2000
SYSMAC.SML 92P 21-Jan-2000 SYSLIB.OBJ 84P 21-Jan-2000
BATCH .SAV 26P 21-Jan-2000 QUEMAN.SAV 16P 21-Jan-2000
FORMAT.SAV 28P 21-Jan-2000 SETUP .SAV 43P 21-Jan-2000
VTCOM .SAV 24P 21-Jan-2000 DATIME.SAV 4P 21-Jan-2000
DATIME.MAC 23P 21-Jan-2000 DATIME.COM 3P 21-Jan-2000
LET .SAV 6P 21-Jan-2000 SPLIT .SAV 3P 21-Jan-2000
UCL .SAV 16P 21-Jan-2000 VBGEXE.SAV 18P 21-Jan-2000
TERMID.SAV 4P 21-Jan-2000 QUEUE .REL 14P 21-Jan-2000
RTMON .REL 8P 21-Jan-2000 SPOOL .REL 12P 21-Jan-2000
SPOOL .SAV 22P 21-Jan-2000 VTCOM .REL 27P 21-Jan-2000
TRANSF.SAV 16P 21-Jan-2000 TRANSF.TSK 76P 21-Jan-2000
TRANSF.EXE 45P 21-Jan-2000 GIDIS .SAV 72P 21-Jan-2000
ALPH00.FNT 9P 21-Jan-2000 ODT .OBJ 8P 21-Jan-2000
VDT .OBJ 8P 21-Jan-2000 MDUP .SAV 22P 21-Jan-2000
MBOOT .BOT 1P 21-Jan-2000 MBOT16.BOT 1P 21-Jan-2000
MSBOOT.BOT 4P 21-Jan-2000 MDUP .AI 72P 21-Jan-2000
MDUP .MM 72P 21-Jan-2000 MDUP .MS 72P 21-Jan-2000
MDUP .MT 72P 21-Jan-2000 MDUP .MU 72P 21-Jan-2000
DEMOBG.MAC 2P 21-Jan-2000 DEMOFG.MAC 3P 21-Jan-2000
DEMOF1.FOR 1P 21-Jan-2000 DEMOF2.FOR 1P 21-Jan-2000
DEMOF3.FOR 3P 21-Jan-2000 DEMOB1.BAS 3P 21-Jan-2000
DEMOM1.MAC 4P 21-Jan-2000 DEMOKD.TXT 4P 21-Jan-2000
VERIFY.COM 2P 21-Jan-2000 IVP .COM 16P 21-Jan-2000
IVP .MAC 33P 21-Jan-2000 MTB .COM 16P 21-Jan-2000
MSB .COM 16P 21-Jan-2000 MS1B .COM 16P 21-Jan-2000
MUB .COM 16P 21-Jan-2000 FB .MAC 1P 21-Jan-2000
SB .MAC 1P 21-Jan-2000 XB .MAC 1P 21-Jan-2000
XM .MAC 1P 21-Jan-2000 ZB .MAC 1P 21-Jan-2000
ZM .MAC 1P 21-Jan-2000 SYSTEM.MLB 148P 21-Jan-2000
EDTL .MLB 11P 21-Jan-2000 BSTRAP.MAC 108P 21-Jan-2000
EDTG .MAC 29P 21-Jan-2000 KMON .MAC 147P 21-Jan-2000
KMOVLY.MAC 265P 21-Jan-2000 MTTEMT.MAC 24P 21-Jan-2000
MTTINT.MAC 72P 21-Jan-2000 RMON .MAC 215P 21-Jan-2000
TRMTBL.MAC 26P 21-Jan-2000 USR .MAC 92P 21-Jan-2000
XMSUBS.MAC 74P 21-Jan-2000 BA .MAC 22P 21-Jan-2000
DL .MAC 42P 21-Jan-2000 DM .MAC 32P 21-Jan-2000
DU .MAC 101P 21-Jan-2000 DW .MAC 46P 21-Jan-2000
DX .MAC 21P 21-Jan-2000 DY .MAC 27P 21-Jan-2000
DZ .MAC 18P 21-Jan-2000 LD .MAC 76P 21-Jan-2000
LP .MAC 14P 21-Jan-2000 LS .MAC 47P 21-Jan-2000
NC .MAC 45P 21-Jan-2000 NI .MAC 27P 21-Jan-2000
NL .MAC 12P 21-Jan-2000 NQ .MAC 31P 21-Jan-2000
NU .MAC 40P 21-Jan-2000 RK .MAC 13P 21-Jan-2000
SP .MAC 87P 21-Jan-2000 TJ .MAC 39P 21-Jan-2000
TM .MAC 31P 21-Jan-2000 TS .MAC 55P 21-Jan-2000
TU .MAC 41P 21-Jan-2000 UM .MAC 112P 21-Jan-2000
VM .MAC 36P 21-Jan-2000 XC .MAC 3P 21-Jan-2000
XL .MAC 42P 21-Jan-2000 FSM .MAC 38P 21-Jan-2000
EL .MAC 26P 21-Jan-2000 ERROUT.SAV 37P 21-Jan-2000
ELCOPY.MAC 18P 21-Jan-2000 ELINIT.MAC 17P 21-Jan-2000
ELTASK.MAC 13P 21-Jan-2000 ERRTXT.MAC 7P 21-Jan-2000
ERROUT.OBJ 36P 21-Jan-2000 RTSB .MAP 33P 21-Jan-2000
RTFB .MAP 35P 21-Jan-2000 RTXM .MAP 37P 21-Jan-2000
RTZM .MAP 38P 21-Jan-2000 SYSGEN.COM 286P 21-Jan-2000
SBFB .ANS 11P 21-Jan-2000 XBXM .ANS 12P 21-Jan-2000
XMEL .ANS 12P 21-Jan-2000 ZBZM .ANS 12P 21-Jan-2000
CONFIG.COM 29P 21-Jan-2000 CONFIG.SAV 10P 21-Jan-2000
V5USER.TXT 2P 21-Jan-2000 V5NOTE.TXT 49P 21-Jan-2000
CUSTOM.TXT 14P 21-Jan-2000 CONSOL.MAC 6P 21-Jan-2000
NITEST.MAC 24P 21-Jan-2000 MSCPCK.SAV 4P 21-Jan-2000
DBGSYM.SAV 10P 21-Jan-2000 SDS .SYS 23P 21-Jan-2000
SDH .SYS 24P 21-Jan-2000 SDSX .SYS 26P 21-Jan-2000
SDHX .SYS 26P 21-Jan-2000 INDEX .SAV 11P 21-Jan-2000
INDEXX.SAV 14P 21-Jan-2000 INDEXA.IMG 164P 21-Jan-2000
INDEXB.IMG 165P 21-Jan-2000 INDEX .IDX 7P 21-Jan-2000
TECO .SAV 50P 21-Jan-2000 CR .MAC 28P 21-Jan-2000
CT .MAC 101P 21-Jan-2000 DD .MAC 66P 21-Jan-2000
DP .MAC 24P 21-Jan-2000 DS .MAC 20P 21-Jan-2000
DT .MAC 18P 21-Jan-2000 PC .MAC 11P 21-Jan-2000
PD .MAC 31P 21-Jan-2000 RF .MAC 15P 21-Jan-2000
224 Files, 7178 Blocks
58289 Free blocks

.time
00:02:52

.time
00:02:57

.


################################################################################


################################################################################
 
RT11 on SCSI2SD

RT11 on SCSI2SD

Len,
Thanks for the detailed post. I think that the documentation we can provide one another through this forum is invaluable. After reading through your post I am very interested in building a micro SD card with RT11 V5.7 that I could stick in my PDP-11/83 to experiment with RT11. My experience has primarily been with RSX11M and M+ which I used 30 years ago and have really enjoyed becoming re-united with in the last couple years. Being able to use both Simh to bring down distributions and the transfer them onto SD cards is an idea way to explore this old technology. Then to boot the SD card up with SCSI2SD on original hardware is quite a thrill!

I remember driving a couple hundred miles to the Chicago Area Real Time Society meetings in Chicago and trading blank 9 track tapes for tapes with the latest RSX Sig tape with all kinds of new public domain software. Now all those tapes are available as down loads from trailing-edge ftp sites. My next big project is to load all those tapes as virtual disks onto one big RA92 disk emulation on a microSD card so I can access them all on one volume.

Len, thanks again for your detailed post as we all learn from one another.

Matlock
 
Last edited:
Matlock,

I really appreciate your write up on the Emulex config, that saved me TONS of time.

I soldered together both of my SCSI2SD cards. I get a kick out of conquering a surface mount board. I think the most difficult part was trying to solder on the SD socket with the pins tucked inside the socket. In either case they are fantastic drives. If you go that route I would suggest getting two. That way one can stay in your PDP and the other in the emulator. It saves a bunch of time swapping it around.

Next I'm going for BSD 2.11, hopefully that goes as well. I picked the RA82 as a mid point. My first install used a RA92, which was overkill, and made really big image files to deal with. The RA92 worked fine, it will give you plenty of space for tape.

On a different topic... I need to get back to my TU58 Pi. I have ltu58 compiled and working on a raspberry pi. I have the pi interfaced to a touch screen and a usb serial port. The were a few changes I documented to get the ltu58 code to work with the extra NULLs the 11/83 sends. In any case it will make a really nice stand alone TU58 emulator. All the parts are less than $100. I need to work on the code so you can select the tape from a menu on the touch screen. I also need to play with larger tapes, 10 and 32M. If anyone is interested, let me know. And if someone who is an Xwindows programmer wants to join in, all the better.

len
 
Len,
I bought my two SCSI2SD boards assembled. You are much more ambitious than I, soldering the surface mount parts and sockets. I do agree that they are fantastic drives. I did buy two SCSI2SD boards but I have them both installed on my PDP-11/83 as DU0: and DU1: The way that I move images from Simh to the micro sd cards is via the dd utility on Linux and USB to micro SD adapters. The Linux I use is Ubuntu under VMware on an iMac. The RA92 is the size of the DU1 drive but I do use a smaller RD54 sized drive for the system disk which is much easier to update and move around.

I am very interested in your Raspberry Pi based TU58 emulator. I have a DLV-11J card configured for TU58 and would love to have a standalone TU58 emulator. Please do post more information on your work on this.

I have been working with BeagleBone computers running Simh to emulate PDP-11a but because they can not do promiscuous ethernet, it is not possible to get them to run DECnet. I would love to find a small Raspberry Pi or BeagleBone type system that could do DECnet on ethernet. My PDP-11/83 has a DELQA ethernet board and it is great to move tape images to the RA92 via DECnet. I also used Johnny Billquist's RSX TCP/IP FTP to move files from Linux on occasion.

Thanks again for your posts and I look forward to learning more about your TU58 emulator in the future.

Matlock
 
Hi Matlock,

That's good to know that you can dd directly to a mounted SD card. It never occurred to me to try that. I like the idea of having multiple drives on my 11/83. That actually makes more sense than letting the other SCSI2SD site idle on my Linux box.

I'll have to look and see if I have the branch that works on the PI tar'd up. There were a few little tweaks to get it to compile, nothing big tho. I'm using the model B+ Pi. The fixed a bunch of the deficiencies that came along with the original Pi's. (Physical mounting, lousy SD card, and too few USB ports. They also expanded the I/O) I'll power up the Pi and tar up my source tree. It will work fine command line on the Pi for now if you are interested. To "change" tapes you just stop and start the program. In the future I though it would be nice to just have a wrapper that would allow you to select a tape and start the emulator. The menu would have a DB listing what's on the tape, or at least a title. It would also be nice to have the emulator be able to mount multiple tapes so you could specify the drive #. (0 or 1 if I remember correctly)

When I have the Pi up I'll see if I have tcpdump loaded and can get it to go into promiscuous mode.

I also have an ethernet card for the 11/83. I figured I would test it out when I get BSD going. Although... if I get some time I could try the tcp for RT11.

len


Len,
I bought my two SCSI2SD boards assembled. You are much more ambitious than I, soldering the surface mount parts and sockets. I do agree that they are fantastic drives. I did buy two SCSI2SD boards but I have them both installed on my PDP-11/83 as DU0: and DU1: The way that I move images from Simh to the micro sd cards is via the dd utility on Linux and USB to micro SD adapters. The Linux I use is Ubuntu under VMware on an iMac. The RA92 is the size of the DU1 drive but I do use a smaller RD54 sized drive for the system disk which is much easier to update and move around.

I am very interested in your Raspberry Pi based TU58 emulator. I have a DLV-11J card configured for TU58 and would love to have a standalone TU58 emulator. Please do post more information on your work on this.

I have been working with BeagleBone computers running Simh to emulate PDP-11a but because they can not do promiscuous ethernet, it is not possible to get them to run DECnet. I would love to find a small Raspberry Pi or BeagleBone type system that could do DECnet on ethernet. My PDP-11/83 has a DELQA ethernet board and it is great to move tape images to the RA92 via DECnet. I also used Johnny Billquist's RSX TCP/IP FTP to move files from Linux on occasion.

Thanks again for your posts and I look forward to learning more about your TU58 emulator in the future.

Matlock
 
Hi Don

I saw that a while ago and didn't find it very interesting, at least for my needs. With the pi you get a much more interesting interface, networking, and lots of storage. In addition you can use it as an emulator. At 35 bucks it's hard to beat.

Len



You don't need anything as powerful as an RPI/BBB to be a standalone TU58 emulator. Arduino will do it just fine:

http://www.torok.info/computing/pdp11/tu58/index.htm

Personally I don't find much utility in having a standalone TU58 emulator box, I use a PC hosted version as it is much more flexible. But to each their own.

Don
 
Hi Don

I saw that a while ago and didn't find it very interesting, at least for my needs. With the pi you get a much more interesting interface, networking, and lots of storage. In addition you can use it as an emulator. At 35 bucks it's hard to beat.

Len

Len,
I saw the link for the TU58 Emulator software, but wasn't clear if you needed any extra hard ware to connect to RS232? I have not worked with the Raspberry Pi but this might be a good excuse to get one. As you say you can't beat the price.

Thanks,
Matlock
 
Sorry, I just use a USB serial cable. I have had good luck with the ftdi compatable chips.

Len

Len,
I saw the link for the TU58 Emulator software, but wasn't clear if you needed any extra hard ware to connect to RS232? I have not worked with the Raspberry Pi but this might be a good excuse to get one. As you say you can't beat the price.

Thanks,
Matlock
 
Len,
Ok, that makes sense. I use a cable with the FTDI chips to connect my IMac to the PDP-11/83. I found a particular cable with RS-232 indicator lights that help when diagnosing RS-232 hand shake signals. If I did the image upload correctly there should be an picture of the cable connected with this post. As far as terminal emulation on OSX I have had good luck with Ericom's PowerTerm. It does a nice job of mapping a MAC keyboard with number pad to the VT220 keyboard to the extent that EDT is very useable.

Thanks for all the info,

Matlock

GearMo USB RS-232.jpg
 
len (or any one else using an Emulex UC07),
I have been busy the last day or two working with Johnny Billquist's new TCP/IP for RSX11M+. Today when I went to boot the PDP-11/83 I got a

Message 07
None of the Selected devices were bootable

First, I thought I wiped the boot block on the DU0: sd card, but when I tried to activate the F.R.D. firmware in the UC07 card, the procedure did not work. I read the diagnostic pages of the Emulex manual and found that the LED error codes on the 3 LEDs of the UC07 could be read by switching SW1-4 ON on the DIP switch accessable from the back of the board. When I powered up then the message on the console screen was the same, but LEDS 2 & 3 stayed lit and that indicates:

Emulation EPROM Checksum Test Failed

so I thought the EPROM could have lost some bits or it could be a loose connection on the EPROM socket. I chose to work on the later possibility because I had no way to re-program the EPROM easily. So I pulled the board, and loosen the EPROM slightly with a screw driver. Then I sprayed some tuner cleaner on the EPROM pins and socket and securely re-seated the EPROM. Then I spent some time cleaning excess tuner cleaner off everything. When I reseated the UC07 in the Qbus...

SUCCESS! It booted perfectly. I did some work rebooting several times during the evening and that appears to have fixed it.

Matlock
 
Nice work - next time, try DeOxit!

Matlock,

The tuner cleaner will help fix the problem now, but will not prevent if from reoccurring.

I use DeOxit! cleaner and then the DeOxit! treatment on all of the DEC equipment that I work on. When reviving my PDP-8/e it cleaned an amazing amount of oxidation from the Omnibus connectors. It also reduced the insertion force of the boards by about 1/2. This is really great stuff.
 
Jack, M_Thompson,
Thanks for the recommendation on DeOxit. I had not heard of it before but between your recommendations and the reviews on Amazon and have already ordered a can. Thanks for your posts on this topic!

Matlock
 
"almost" means "not"

"almost" means "not"

I have put a UC07 on my 11/73 [and also moved the UC07 setup to a 23+ with the same results].

I have SCSI2SD set-up as set out above (that is nice documentation - it works a treat)
RT11 on an RA82 etc
BUT
It only almost works.

The disk image boots OK on SIMH.
The disk image has been DDed to the SD card OK since a unix byte-by-byte read-back-and-compare "cmp -l /dev/sdd <rt11.dsk>" gives no differences.

Now the fun. The UC07 wont boot the image - or rather nothing visible happens on screen when I boot off DU0.
Enter one of [Boot, Diagnose, Help, List, Map]:b

Type ? for a list of devices
Enter device name:?

Bootable devices
Device Max
Name Type Units
DU DSA 8
DL RL01/02 4
DX RX01 2
DY RX02 2
DD TU58 2
XH QNA 2
MS TQK25/TS05 1
MU TK50 1
Enter device name:du0
TRYING UNIT DU0



Not to be outdone I typed in the ODT UC07 "special" UC07 boot (section 7.5 of the UC07 manual) progran and that loaded the boot block into block 0.
The first block of bytes compare exactly to an octal dump of the SD card (od -o /dev/sdd). So, I believe I have read in the first
block of the disk correctly.
@777772150/000000
17772152/005400 30003
@/000400 40000
17772152/2000
So, It has read in data from the SCSI2SD "disk":

@0/000240
00000002/000415
00000004/000000
00000006/000000
00000010/000000
00000012/000000
00000014/006303
00000016/006303
00000020/062703
00000022/000526
00000024/000407
00000026/000000
00000030/000000
00000032/054020
00000034/103420
00000036/000400
00000040/000137



But, 0G does nothing obvious on the terminal.

I have kind of reached an impassssss. I can footer around for a bit longer, but I cant phathom why RT11 wont start.
Any nice kind people who can share insight?
 
Sorry. Cannot give you the answer since I have a Viking QD0 and a real SCSI disk (and that works fine), but only what I would have done if I ended up in the same situation:

  • Check if there is a difference when using a standard SCSI drive rather than the SCSI2SD.
  • Use PDP11GUI to read off the disk into a PC via the PDP11-console serial line. Probably incredibly slow but at least a check that the controller and SCSI2SD works together.
  • When you do 0G where does it end up when you press HALT on the machine? In the wilderness or looping in the boot block code?
  • When halted, can you recognize that it has read some more into memory? You need to understand the boot block I assume to understand where to it will store the rest.
  • Does the UC07 has some kind of utility to do diagnostics on the drive? Is there any configuration to be done in the UC07?

Good luck!
 
I have put a UC07 on my 11/73 [and also moved the UC07 setup to a 23+ with the same results].

I have SCSI2SD set-up as set out above (that is nice documentation - it works a treat)
RT11 on an RA82 etc
BUT
It only almost works.

The disk image boots OK on SIMH.
The disk image has been DDed to the SD card OK since a unix byte-by-byte read-back-and-compare "cmp -l /dev/sdd <rt11.dsk>" gives no differences.

Now the fun. The UC07 wont boot the image - or rather nothing visible happens on screen when I boot off DU0.
Enter one of [Boot, Diagnose, Help, List, Map]:b

Type ? for a list of devices
Enter device name:?

Bootable devices
Device Max
Name Type Units
DU DSA 8
DL RL01/02 4
DX RX01 2
DY RX02 2
DD TU58 2
XH QNA 2
MS TQK25/TS05 1
MU TK50 1
Enter device name:du0
TRYING UNIT DU0



Not to be outdone I typed in the ODT UC07 "special" UC07 boot (section 7.5 of the UC07 manual) progran and that loaded the boot block into block 0.
The first block of bytes compare exactly to an octal dump of the SD card (od -o /dev/sdd). So, I believe I have read in the first
block of the disk correctly.
@777772150/000000
17772152/005400 30003
@/000400 40000
17772152/2000
So, It has read in data from the SCSI2SD "disk":

@0/000240
00000002/000415
00000004/000000
00000006/000000
00000010/000000
00000012/000000
00000014/006303
00000016/006303
00000020/062703
00000022/000526
00000024/000407
00000026/000000
00000030/000000
00000032/054020
00000034/103420
00000036/000400
00000040/000137



But, 0G does nothing obvious on the terminal.

I have kind of reached an impassssss. I can footer around for a bit longer, but I cant phathom why RT11 wont start.
Any nice kind people who can share insight?

Does the UC07 require you to to run the FRD to define the disk? My UC17 does. I don't know about a UC07.
This is a utility in the UC ROM and how it knows what disks it has connected.
 
Sorry. Cannot give you the answer since I have a Viking QD0 and a real SCSI disk (and that works fine), but only what I would have done if I ended up in the same situation:

  • Check if there is a difference when using a standard SCSI drive rather than the SCSI2SD.
  • Use PDP11GUI to read off the disk into a PC via the PDP11-console serial line. Probably incredibly slow but at least a check that the controller and SCSI2SD works together.
  • When you do 0G where does it end up when you press HALT on the machine? In the wilderness or looping in the boot block code?
  • When halted, can you recognize that it has read some more into memory? You need to understand the boot block I assume to understand where to it will store the rest.
  • Does the UC07 has some kind of utility to do diagnostics on the drive? Is there any configuration to be done in the UC07?

Good luck!
ok I see your list and will try PDP11GUI tonight.
Yes, the first 512 bytes in RAM are exactly what was on disk. After that I have no idea!
The UC07 FRD does have a disk verify command, and it ran OK (before I copied the OS to it)
I did not note where I ended up when I halted. See below about 23+ and 73 information.
 
I agree with the post above that you should run FRD on the UC07 controller and look carefully at the various settings.
You could have the drive configured as a RA82 ok, but some other setting (SCSI parity, lun, etc) is not quite right. You might
be bypassing some setting with the direct read via the CSRs that you tried?

By the way, Len, I bought a Raspberry Pi B+, and set up the TU58 emulator with the software you referenced earlier in this topic
and it worked very well. I was able to run XXDP+ fine, and also was able to access the TU58 from RSX as well. Thanks!

Matlock
 
Back
Top