Hi all,
Well, it was quite a trek, but I got it to work.
Thank you all for the help with this.
To start, I first wrote a small basic program with multi-line statements, then examined it with ODT. (This was a chore.), but I found that the file uses just CR for line endings. No apparent special characters (Null and such). Armed with this, I figured I had to make the file from github match.
So the base problem was that in macOS (probably linux too) the file downloads from git with 0x0a (line feed) line endings. If you are using windows, it becomes 0x0d,0x0a (crlf) line endings. Using the macOS "tr" utility, I ran the command:
tr "\n" "\r" <trek52.bas > trek52cr.bas
to convert the LFs to CR. There may be a way to do this with SED, but macOS sed is not up to snuff. Maybe linux's would do better.
Next, I needed to upload it. This was where I had to play for a long time. I tried a few ways. Here's what worked:
- In Windows, I opened the trek52cr.bas file with notepad++ and showed all characters (to ensure CR was just CR).
- I installed the Windows Telnet client. https://social.technet.microsoft.com/wiki/contents/articles/38433.windows-10-enabling-telnet-client.aspx
- I started pdp11 with a dz set up and started RSTS/E (using 10.1 ... haven't gotten it to work on my PIDP yet.)
- Log in to 1,2 password SYSTEM (on RSTS/E)
- I opened a command line in windows and used the command: telnet
- The prompt is 'Microsoft Telnet>' and enter the command: 'u crlf'
- This shuts off CRLF mode when hitting enter. Enter is just CR now.
- Next, enter 'c <ip of pdp11> 1170' to connect. e.g., c 10.10.10.247 1170
- It will tell you where you connected to. e.g., "Connected to the PDP-11 simulator DZ device, line 4"
- On your simh RSTS/E, enter the command 'SHO DEV'. It will print out the devices. in the list, find the DZ and corresponding line.
- e.g., "Device _KB9: (KBG4:) Control DZ0:4 CSR 760100 Status: Restricted."
- On the PDP console, enter the command: pip trek52.bas=kb9:
- Back in Windows, on the open the trek52cr.bas in notepad++, ctrl-a ctrl-c (select all, copy)
- Paste it into the telnet session. Just point at telnet and right-click.
- When you see the final statement, "32767 end", ctrl-z and pip will close
- To check that the program went in ok, do the following on RSTS/E
- Run the 'command basic/bplus'
- Run the command 'old trek52.bas'
- If there are no errors, the file loaded ok.
- So now, you want to run it? I did this:
- Ran the command: 'git clone https://github.com/kgober/VT52'
- cd to the VT52 director
- Compile it with the command: 'dotnet build'. You'll need the dotnet runtime to do this.
- cd to the bin directory
- Run the command: 'vt52'
- Right click the header line
- In connection enter <ip of your pip11>:1170
- Hit enter a few times to get the User: prompt
- Enter: "1,2" then password SYSTEM
- Get to the "$" prompt and enter the command 'set term/device=vt52'
- Enter the command: 'basic/bplus'
- Enter the command: 'run trek52"

So, what failed?
- Everything when the line feeds were in the file
- Trying to paste it into a macOS terminal ssh'd into the pdp11 (it must convert CR's somehow)
- Trying to paste it into a basic/bplus session directly. (Maybe paste too fast/interpreter too slow?)
- Trying to get it on paper tape using RT11. I think RSTS/E 10.1 doesn't have PT drivers?
- Trying to put it on an RK05 then FIT it into RSTS. (Maybe this would have worked, but I hadn't solved the CR/LF problem yet.)
- Trying to put it on mag tape.
I am using the latest macOS on a 2019 MacBook Pro 15" with 2.6GHz core I7. Windows was running on a separate AMD 5900x machine and connected to the mac using Microsoft Remote Desktop.
The trek52cr,bas file is attached.
Regards,
Bob