kenrector / sigma-cpv-kit Goto Github PK

Thank you so much for sharing this project.

Using the README, I was able to telnet in, but neither setting DEP 114a 0 or sending a BREAK seems to trigger a login prompt.

It would be really awesome if you were to capture a walkthrough of the set as a text file.

SUPER is the CP-V tool used to create and maintain user account parameters. The SUPER on the cpcp.tap PO tape is a modified version developed by Andrews University.

It appears to me that SUPER requires the subject account being created or modified have C0 privilege for batch mode. Set B$PRIV=C0 before completing the create or modify operation.

Failure to do this will result in the error message

BAD BILLING NUMBER IN RECORD

when leaving the create or modify operation. If you get this message use CTL-Y to exit SUPER.

James Fehlinger has reported a couple of problems attempting to run this package on simh-V3 and open-simh. Here is what he said, beginning with comments concerning V3.

`So the first clue I had that I'd made the wrong choice was that
the '#' comment characters in Rector's sigma.ini file are wrong
for SimH v3.12-2, which wants ';'. No big deal. Next up: Simh v3.12-2
couldn't parse the "att mux line=0,2020,line=2021. . ." commands
(while it would swallow "att mux 4000"). OK, fine, I'll comment those
out for now and do without the privileged terminals and just log in
on the nonprivileged lines. Then I booted from the PO tape, started
the install, and. . . it went right off the rails.

Next up: "Open" SimH. I used a source repository I'd downloaded on Nov. 28.
This got farther -- it could parse the sigma.ini file, install
the PO tape to disk, and boot CP-V from disk. But terminals -- not
so much. I got the acknowledgements from SimH that a line was
connected, but I could not get any response from CP-V on any line (and yes,
I know about "!ON 107", "deposit 114a 0", and "telnet> send brk").
Curiously, when I issued a "!ZAP" from the console to shut down
the system, then I'd get a squirt of "HI, TCP-V HERE. . . LOGON PLEASE:"
messages on a connected serial line.

Last ditch attempt: "SimH SimH", the "troublesome" branch, source repository
downloaded as of today. And this worked as expected.`

Do we have any identification (file name) for PASS2 control statements used to generate C0F system (loaded off cpcp.tap tape image), or should we rather hunt one on original Siggy-format tapes? Want to compare this vs original system images available on bitsavers.org (need to hunt for FRES too) and hopefully bostrap more recent version of CP-V.

System hangs with error message DPBF0 NOT OPERATIONAL or DPBF1 NOT OPERATIONAL from time to time.

I suppose this is a problem in sigma_dp.c handler.the sigma_dp.c handler.

f00/cpf0 gets check-write error during boot from mt. reported after number of patches read message.

Be careful of running more than one session at a time. I had number of batch users set to 5 and starting 5 batch jobs caused the system to hang. Rebooted and set ONB 1 and all the jobs made it through, one at a time.

Today I started EDIT with a paste input on two sessions and the system hung. Had to reboot.

I have successfully built the sigma simulator, used the cpv-kit and logged in on two MacOS desktops (2019 Intel MacPro/big sur and 2009 Intel MacPro/mojave). On my laptop (2019 Intel MacBook Pro/Big Sur), I can boot from tape and the operator console seems to be working. After "!OPEN 107" and (in simh) "dep 114a 0", I can connect to the simulator. I get:

Connected to the XDS Sigma simulator MUX device, line 6

But don't get a login prompt even if I send a BRK signal (telnet SEND BRK)

I am pretty sure I am doing all the same steps on all the systems. Any suggestions?

The sigma.ini file has the line:

att mt0 ../cpcp.tap

which looks for the cpcp.tap file in the parent directory. This can work if the file is copied or linked to the parent, but as pulled from the repo, I have been removing the ../ to make it work. I can imaging there could a reason for this, for example, to preserve the repo version if the tape image is being modified.

Attempting to execute any basic commands (in a program or from the prompt) results in an "unimplemented instruction" trap. I suspect this in an emulation bug, but since you seem to be able to run BASIC programs, I am wondering if it's a simh config setting.

FORT, EDIT, and APL seem to be working fine.

!BASIC
VER. C02
>10 FOR I = 1 TO 10
>20 PRINT I
>30 NEXT I
>40 STOP
>50 END
>RUN
:P6   ^   RUNQAAA...
  A405 UNIMPLEMENTED INSTRUCTION

!