This question may sound ridiculous (and it may be) but I am having a heck of
a time making a connection with Reflection (either the old DOS version or
the newer (5.21) Windows version with a modem and the DTC. I tried using the
HP Supportlink modem -- the 19.2 kbs modem - and now I'm trying a Practical
Peripherals 14.4 modem which I set into non volatile RAM 9600 kbs  which is
the port speed.

All I get is garbage - the DOS version of Reflection seems to be limited in
how I can change the settings - seems to be limited to stop bit - but on the
Windows version I've tried everything - 7bit, 8 bit, even, odd , non
parity - all I get is garbage.

The Tech guy at the vender I bought it from -Genisys -  who incidentally has
really helped me  with other things - said that it can sometimes take hours
getting a modem to work and some - despite being Hayes and Bell compatible -
just don't talk to each other.

That makes no sense but based on my experience so far seems to ring true.

A CE gave me some manuals they were going to throw away so I will slowly but
surely learn MPE/ix - next on my list is boosting the DTC to 19.2 for the
terminals - and I know you use nmnmgr - that's about as far as I've gone ;-)

Anyone have some modem hints for this beast? I'll be glad to buy some other
modem if it'll work. Next I may try the ancient 2400 baud support modem that
we have had for years. It belongs to HP but they don't seem to anxious to
reclaim it ;-) Like most things HP it looks like it is built like a tank -
and to last -

Sorry I can't help others more on this list but I seem to be on a steep
learning curve myself...

BTW for you  Reflection users here's a weird problem that seemed to solve
itself with the newer computer. For some reason with our Win95 version we
could not get returned characters on the View screen - it **would** work
with the DOS version but **not** on the Win95 version. As an aside we handle
View a bit differently since we use BASIC 3000 and are limited to 255 byte
strings. Instead of calling the VIEW intrinsic to display the retrieved
data, we simply do a BASIC formatted print to STDOUT which is the screen.

Anyway the Tech at WRQ did isolate the problem to the fact that we weren't
getting a control character back on my Win95 screen, and it was coming back
on the DOS screen. He was trying to tell me that there was something in the
serial line between the HP and the PC that was preventing this character
from coming back. All my lines are straight serial 4 pin (1,2,3,7) connected
(past tense of course) to an ADCC.

I was going to swap computers to the lines to prove or disprove him but
installation issues with the 917 came up. Anyway with the 917 the screen
looks fine.
Same lines now plugged to the DTC.

That falls into one of those "Twilight Zone" phenonomon...Interesting and
unexplainable...

Bill