[Simh] pdp11 - console input with high bit set

[Paul Moore]

I am running it in the windows console.

I can see that setting TTU_KSR on the mode flags passed to sim_tt_impcvt will do the job. The pdp-8 console hard code this bit on

else uptr->buf = sim_tt_inpcvt (c, TT_GET_MODE (uptr->flags) | TTUF_KSR);

the is also a KSR mode switch

MTAB tti_mod[] = {
    { TT_MODE, TT_MODE_KSR, "KSR", "KSR", &tty_set_mode },

But this only forces UC (sim_console.h)

#define  TT_MODE_KSR    (TT_MODE_UC)

So basically pdp8 is always doing KSR. I assume that I don’t want that for pdp11. 

I tried naively adding the same mode flag but of course that did nothing since is not a mode it’s a modifier of a mode (an 'ored' in flag) so I am not sure what to do. I mean I can hack that flag into a temp build but it seems like this is a useful thing to have

Not helped by not knowing what KSR really means.

-----Original Message-----
From: Ethan Dicks <ethan.dicks at gmail.com> 
Sent: Friday, July 24, 2020 10:53 AM
To: Paul Moore <paulmoore100 at hotmail.com>
Cc: Simh at trailing-edge.com; Johnny Billquist <bqt at softjar.se>
Subject: Re: [Simh] pdp11 - console input with high bit set

On Fri, Jul 24, 2020 at 1:13 PM Paul Moore <paulmoore100 at hotmail.com> wrote:
> Johnny, I don't know what that means for simh

On an xterm session, there may not be a way to do it.  If you were running simh from a dumb terminal on a serial port, you could set your terminal to do 7E1 (even parity), and possibly a matching  "stty parenb -parodd" , but the arg 'parenb' appears not to be valid from a window session.

> From: Johnny Billquist <bqt at softjar.se>
> Sent: Friday, July 24, 2020 1:37:27 AM
> To: Paul Moore <paulmoore100 at hotmail.com>; Simh at trailing-edge.com 
> <Simh at trailing-edge.com>
>
> You need to have your terminal set to MARK parity.
>
> On 2020-07-24 01:56, Paul Moore wrote:
> > I am trying to run an RK11 diagnostic and am stuck.
> >
> > Looking at the code, it is looking for digits and then cr.
> >
> > But it is actually looking for  #215, which is 0x8d. Which is CR 
> > with the high bit set. (It also looks for #377 del with HB set)
> >
> > So what happens is that it just keeps reprompting
> >
> > I don’t see how that character ever gets into the system. I did ‘set 
> > tti 8b’ but it made no difference. I can post the relevant code if needed.

Does "set tti 7p" work for this?

-ethan