Iosaef the Irascible wrote:
Knut,I have an SSC in a //e enhanced and I have not experienced this problem.What are your DIP switch settings? Like I said, I think this is purely PEBKAC on my part, but I'm having a devil of a time finding out where...
Actually if you read the documentation that come with ADT there is a suggested SSC setting. But I was mistaking I just checked doing as you describe I do receive with the high bit set, receiving the screen output from the //e. I'm sorry if I have confused you.
Reading the other posts in this thread made me suspect that I had somehow avoided to see this and it must be so. It seems it is not PEBKAC...
I started with my //e without any software on floppies so ADT was what I explored first, transferring it as a text file via the IN#2 command.
My dip-switches are set to 0000111 1101010
SW1 0000 = 19200 baud
11 = comm mode
1 = unexplained, set to 1 in comm mode
SW2 1 = 1 stopbit
1 = 8 bit
01 = no parity
0 = no extra LF
1 = enable interrupts *necessary for most terminal emulators
0 = unexplained, set to 0 in comm mode
all except SW2.6 the interrupt are just "soft" switches, the actual
settings are done by the ROM software and these settings are overridden
and ignored by software like ADT. SW2.6 a "hard" switch and enables or
disables the possibility of the SSC to interrupt the CPU.
Knut