Carl (et al),Your help with the Dvorak/QWERTY issue has given me the full access I needed. A few tweaks related, I think, to the hardwiring of the keyboard itself remain--some funkiness around the function and shifting keys--but I'm mostly up and running and will figure the rest of it out. The http://startup.int debug is another story. Using the D WA technique causes http://startup.int to hang indefinitely, no matter the numeric parameter. So for now I'm still getting an error message flash by on the prompt (once I go back to D WA=0), though it doesn't seem to impact overall functionality. There's something the system doesn't like, and since this has only shown up since replacing the keyboard . . . I don't know. I've been too lazy to putafter each line, but may resort to it after getting my ambition up. For the nth time, Thank you. FWOn Sat, Sep 1, 2018 at 3:35 PM Carl Distefano mailto:cld@xxxxxxxx wrote:Reply to note from Fred Weiner mailto:fw1948@xxxxxxxx Sat, 1 Sep 2018 15:06:07 -
0700
Fred,
You can do a couple of things. One, before running http://STARTUP.INT, issue a
command like D WA=54. This will execute a pause after an error. (The
length of the pause is 1/18th of a second per unit of value. So, 54 means
pause for 3 seconds.) After you've debugged it, remember to command D WA=0
to eliminate the pause.
The more painstaking (and revealing) way is to insertcommands at the
end of every line. The program stops when it comes to. Thus, you can
run http://STARTUP.INT repeatedly, deleting each succesiveif it runs
successfully up to that point. You will eventually get to the line(s) that
are misbehaving.
Hope this helps.
--
Carl Distefano
mailto:cld@xxxxxxxx