RT11 on shared RK05

[wohus...@gmail.com]

Hello Joerg,

I tried RT11V4 and have obviously bad commands in my  .CMD-file.

I send you this .CMD and the session result.

Please reflect 

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

.....................

p image RTRKV4.00

Name   Short  Value      Unit  Access    Info                                                      
-----  -----  ---------  ----  --------  ------------------------------------------------------------------------
image  img    RTRKV4.00        writable  Path to binary image file. Empty to detach. ".gz" archive also searched.

shared_filesystem RT11

Unknown command "shared_filesystem RT11"!

shared_dir RTRKV4_shared_rk0

Unknown command "shared_dir RTRKV4_shared_rk0"!

......................................................................

and so on

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

RTRKV4_shared.cmd

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

# inputfile for demo to select a rl1 device in the "device test" menu.
# Read in with command line option  "demo --cmdfile ..."

# Assume CPU stopped. No DMA until booted!
d            # device menu


# CPU is PDP11/05 with integrated Serial IO
# no emulated extra (DDR) memory from UNIBONE !!!!

# CPU stopped, install M9312 + boot into console emulator

sd m9312        # further commands form M9312
p v 5            # verbosity "debug"
p bl DIAG        # set start label to console emulator entry 765020
p cer 23-248F1.lst    # plug console emulator ROM into socket
p br1 23-756A9.lst    # plug RK BOOT ROM into socket1
p br2 23-751A9.lst    # plug RL BOOT ROM into socket2
p br3 23-767A9.lst    # plug MSCP DU BOOT ROM into socket3
p
en m9312        # online

pwr            # reset, should boot into console emulator now

.print Emulating M9312
.print You should see console emulators "@" prompt now
.input Hit return to autoboot RK0 into RT11 V3B


dis m9312
#p bl rk0n        # set new boot address
p bl dk0n        # set new boot address
en m9312


# pwr            # reboot PDP-11
# .wait 3000        # wait for PDP-11 to reset
# m i            # install max UNIBUS memory

# Deposit bootloader into memory
# m ll dk.lst

en rk            # enable RK11 controller

# mount RT11 v4 in RK #0 and start
en rk0            # enable drive #0
sd rk0            # select
p emulation_speed 10    # 10x speed. Load disk in 5 seconds

p runstopbutton 0    # released: "LOAD"
p powerswitch 1        # power on, now in "load" state
p image RTRKV4.00 # mount image file with test pattern
 shared_filesystem RT11 # now share RT11 image with local Linux directory
 shared_dir RTRKV4_shared_rk0    # relative path of subdir for shared files
p runstopbutton 1    # press RUN/STOP, will start

# mount RT11 BASIC in RK #1 and start
en rk1            # enable drive #1
sd rk1            # select
p emulation_speed 10    # 10x speed. Load disk in 5 seconds
p runstopbutton 0    # released: "LOAD"
p powerswitch 1        # power on, now in "load" state
p image basic.dsk    # mount image file with test pattern
 shared_filesystem RT11 # now share RT11 image with local Linux directory
 shared_dir shared_rk1    # relative path of subdir for shared files
p runstopbutton 1    # press RUN/STOP, will start

.print Disk drive now on track after 5 secs



.wait    4000        # wait until drive spins up
p                       # show all params of RK1

pwr           # reboot  ???

.print RK drives ready.
.print RK0 content accessible in shared Linux directory "shared_rk0"
.print RK1 content in "shared_rk1"
#.print RL11 boot loader installed.
#.print Start 10000 to boot from drive 0, 10010 for drive 1, ...
#.print Reload with "m ll"

###############################################################
session

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

rt11v4.txt

Wolfgang

[Joerg Hoppe]

Hi Wolfgang,

you did

shared_filesystem RT11
shared_dir RTRKV4_shared_rk0

but these are "parameters": try

p shared_filesystem RT11
p shared_dir RTRKV4_shared_rk0

kind regards,
Joerg

[wohus...@gmail.com]

Hello Joerg,

sorry for misleading you!

The bad command was a result of inserting a "#" (comment) character in front of the  "p shared_filesystem RT11" and later removing the "#", falsely together

with the "p".

Here is the real outcome!

I did it twice

First on the READ PDP11/05  ( emulated M9312) and

second on my workbench (REAL M9312 but no bootprom for DK:, hence dk.lst loaded etc, and CPU20)

See also the .CMD for the workbench (CPU20)

The crash is at

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

p image RTRKV4.00

Name   Short  Value      Unit  Access    Info                                  
-----  -----  ---------  ----  --------  ------------------------------------------------------------------------
image  img    RTRKV4.00        writable  Path to binary image file. Empty to detach. ".gz" archive also searched.

p shared_filesystem RT11

Name               Short  Value  Unit  Access    Info                          
-----------------  -----  -----  ----  --------  ----------------------------------------------------------

shared_filesystem  shfs   RT11         writable  Encode shared dir in this file system (empty, RT11, XXDP).

p shared_dir RTRKV4_shared_rk0

[18:03:48.859922 WRN    rk0] TODO: drive size (trunc!) and unitno may change? Propagate to shared image!
demo: /root/10.02_devices/2_src/sharedfilesystem/filesystem_rt11.cpp:325: virtual void sharedfilesystem::filesystem_rt11_c::init(): Assertion `image_partition->size >= layout_info.block_count * layout_info.block_size' failed.
./RTRKV4_shared.sh: line 3:  2212 Aborted                 ~/10.03_app_demo/4_deploy/demo --verbose --cmdfile RTRKV4_shared.cmd $*

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

RT11V4 does start, as long as the "shared_filesystem"-option is omitted.

So the disk images I use are bootable.

Sorry, would have been easier, if the missing "p" had been the problem....

kind regards

Wolfgang

[Joerg Hoppe]

Hi Wolfgang,

can you point me to your problematic RTRKV4.00 image?

kind regards,

Joerg

[wohus...@gmail.com]

It is from here:

http://pdp-11.classiccmp.org/RT-11/dists/

RTRKV4.00.ZIP.

(BTW: I did not receive your copy of RTRKV4.00, so I used the above one)

Wolfgang

[wohus...@gmail.com]

Hello Jörg,

at the same URL, you can find 2 more RT11V4RKs in "RT11DV50.ISO.zip"

if that matters.

I could try these too, if wanted!

Wolfgang

[Joerg Hoppe]

Hi Wolfgang,

Hmmm, I can handle  RTRKV4.00 in "shared mode" without problems.

I suspect an outdated compile, try
    ./update-code.sh beta
again.

My .cmd is

...
en rk

en rk0            # enable drive #0
sd rk0            # select

p image RTRKV4.00 # www.classiccmp.org/PDP-11/RT-11/dists
p shared_filesystem RT11 # now switch to shared
p shared_dir rt11_shared_rk0
...



kind regards,
Jörg

[wohus...@gmail.com]

Hello Jörg,

updating did the trick!

I updated to "beta" 2 weeks ago, but somehow I was not "up to date", how it seems!

Very very nice to copy files between the shared folders of the RK drives (images) with MC (midnight commander) in ONE SSH-connection while

RT11V4 is active in the 2nd SSH together with a serial connection to RT11 with virtual DL11 in a third EXTRA-PUTTY window! WOW.

A that point, I get a glimpse idea of how much work you put into that!!

Thank you very very much!

Wolfgang

[wohus...@gmail.com]

One more thing:

I have RT11V3B running "shared" too!

No problem with the filesystem at that point!

GREAT!

have a nice day!

Wolfgang

[wohus...@gmail.com]

Hello Jörg,

got new problems with RT11V4, RK05, shared:

What I do is:

start RTV4 with 2 RK05, DK0: system, DK1: some basic files and basic.sav- both RK0,RK1 are shared.

have  .CMD-file startup in 1st SSH window,  2nd window is ttyS2 for RT11.

start 3rd window SSH to Unibone and navigate to the shared RK-folders via MC.

RK1 has BASIC.SAV

I copy BASIC.SAV to RK0, using Midnight commander, not via RT11 COPY or PIP.

No problem.

DIR RK0:  confirms visibility of BASIC.SAV under RT11.

Now I try to copy a file from RK0 to RK1 with MC, and crash.

---------------

Redo the same thing several times, there is even one message "DISK FULL" ....please see attachment rt4.txt

-----------------

attachment rt4.txt shows a different situation:

Now I try to copy a file from RK0 to RK1 (using COPY of RT11!) and the system crashes.

No midnight commander or different action on Linux side involved.

-----------------------

One thing I recognized:

while RL02  "p" shows under "capacity" some value #0

RK05 devices show "capacity cap 0".

is this of relevance?

Sorry, but I thought you should know about this 

Wolfgang