Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

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

    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/vcfo...2SD-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_d...ists/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

    .


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


    ################################################## ##############################
    Spread the joy of Vintage Addiction

    -->www.chronworks.com/<--->www.i8008.net/<--

    #2
    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 by Matlock; January 8, 2015, 05:34 PM.

    Comment


      #3
      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
      Spread the joy of Vintage Addiction

      -->www.chronworks.com/<--->www.i8008.net/<--

      Comment


        #4
        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

        Comment


          #5
          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


          Originally posted by Matlock View Post
          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
          Spread the joy of Vintage Addiction

          -->www.chronworks.com/<--->www.i8008.net/<--

          Comment


            #6
            Here is the link to ltu58 that I have compiling on the Raspberry PI. There are warnings on the compile tho it still works fine. I am running the current version of Rasbian.

            http://isdi.com/PDP/ltu58_lb_bootFixPi.tar.gz
            Spread the joy of Vintage Addiction

            -->www.chronworks.com/<--->www.i8008.net/<--

            Comment


              #7
              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

              Comment


                #8
                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



                Originally posted by AK6DN View Post
                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
                Spread the joy of Vintage Addiction

                -->www.chronworks.com/<--->www.i8008.net/<--

                Comment


                  #9
                  Originally posted by 8008guy View Post
                  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

                  Comment


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

                    Len

                    Originally posted by Matlock View Post
                    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
                    Spread the joy of Vintage Addiction

                    -->www.chronworks.com/<--->www.i8008.net/<--

                    Comment


                      #11
                      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

                      Comment


                        #12
                        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

                        Comment


                          #13
                          Nice work - next time, try DeOxit!

                          Jack
                          Jack
                          www.computerarium.org

                          Comment


                            #14
                            Originally posted by jackrubin View Post
                            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.
                            Member of the Rhode Island Computer Museum
                            http://www.ricomputermuseum.org

                            Comment


                              #15
                              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

                              Comment

                              Working...
                              X