I noticed today that, when using the INLIN routine at 47AA, that it does not return with B holding the # of bytes in the response.
Recall that INLIN is meant to capture keyboard input like a file name etc. I could not find anywhere in RAM where the input # of characters was stored, so I had to write a loop to discover the value. Did I miss something? (not fun when published routines are different between M100, NEC and T200!!!!) thx Steve
