ABN.ISCAMS@USC-ISID.ARPA (03/21/84)
Netlandians, I like the "background process" idea of both Word*'s PRINT function and UNSPOOL. However, I have a REAL problem with the keyboard being dead the majority of the time. I've read warnings that in Word* there may be an occasional delay, so "heads-up typing is not recommended" or something to that effect. However, waiting many many seconds for ANY key response/echo at ALL, then maybe entering 3 or 4, and then another LONG delay -- and none of this correlating to disk reads (usually), and with a nice little 1.5 or 2 Kb buffer on my Mannesman Tally -- where's the bloody delay? I have DMA on my Decision I disk controllers, sure, but disk reads don't take THAT long. Any ideas? I've tried my CBIOS patched to both Xon/Xoff and ...forget the alternative .. DTR? -- anyway, no difference there, so the BIOS shouldn't be waiting around for the printer. Both functions are effectively useless for any sort of text input because of this excessive delay (with Word* being the WORST!). Would appreciate some advice from the CP/M wizards... David Kirschbaum Toad Hall ABN.ISCAMS@USC-ISID
w8sdz@Brl.ARPA (03/21/84)
From: Keith Petersen <w8sdz@Brl.ARPA> Make sure your CBIOS LISTSTAT routine is properly configured. Many are not configured at all, returning list device always ready or always not ready. Assuming you have that working right then it may be the way you configured WordStar. If you use the CP/M list device for the printer WS.COM does not check LISTSTAT. There is a patch to add list device status checking inside WS.COM, look in the <CPM.WSTAR> directory at SIMTEL20. Otherwise use WordStar's internal drivers, which will require that you answer certain questions at configuration time about port addresses and status bits. --Keith