3 Dec
1997
3 Dec
'97
3:04 p.m.
On Wed, 3 Dec 1997, Tim Shoppa wrote:
Who told you that KERMIT (Billy Yodelman's KRT,
I'm assuming here)
doesn't work under SJ? If they told you that you need
XM, they were lying. Just SYSGEN a 5.0 or later SJ system with TIMER
support and you're set.
Because when I type "kermit" is says
KERMIT.SAV Requires an Extended Memory monitor.
The way you keep the buffer from being overrun is to
slow the rate
at which you're blasting data to the PDP. As usual, you've neglected
to tell us what command you are using and the error message (or
symptoms) that it produces when it fails, but I'm going
to assume that you are actually following the instructions in KRTHEX.MAC.
Pay particular attention to the following section:
The terminal is the nameserver at school, it runs Linux.
The configuration is the COM2 port is plugged into the PC, and I run
minicom there, (Telix-type comm program) and talk to the PDP.
I was trying to send KSERVE, but I'll follow this.
The error message was dropped every time the ASCII upload gave up, I only
got to see it for a second. It said something about stack overflow.
; 3. Run PIP on the PDP-11, then give it a file name
to create and tell
; it to take its input from the terminal. Example:
; .PIP
; *KRT.HEX=TT: ! or file name of your choice
; ^ ! PIP prints a ^ when it's ready for input
;
That's what I did. But I did it on one line.
; You then use the comm program's ASCII transfer
function to simply send
; the file across. Note that you may have to insert delays between chars
; or lines (or both) to avoid overrunning the PDP-11, which will return a
; bell for each char thus lost. When done, reconnect to the PDP-11 and
; type a control-Z to close the file:
;
; ^Z
This is happening at 9600 baud. How do I slow it to 1200 or something?
The serial in question is the console on M8189 (11/23+ Single-board
hex-height CPU)
If you're using MS-DOS Kermit or C-Kermit, the
commands to insert
delays in the blasting process are "SET TRANSMIT PAUSE nnn" where
"nnn" is the number of milliseconds to pause between lines. A
very conservative starting value would be 300 ms. Don't get too
greedy - take it slowly and carefully, and it will work! Get impatient
and set the delays too small, and you'll drop characters and have to
do it all over again! (I speak from long experience...)