Kurt - fantastic! let me know if you want some testing on this. I've done my own work on Newdos to improve how it handles latency; I'm ready to assist. Steve
On Wed, Mar 2, 2016 at 2:07 PM, Kurt McCullum <[email protected]> wrote: > For those of you who asked for a bluetooth link between mComm running on > your phone, I've been working on it. As of right now I have my 102 working > with a test version of mComm. There are some issues I'm trying to fix but > most surround the latency of characters. I've taken a RAM version of TS-DOS > and changed the timing. > > Looking through the Kens disassemble of the DOS200.CO there seems to be a > simple way to modify all of the ram versions. > Basically the standard versions of TS-DOS have a High and Low byte used for > the delay. By default the Low byte is 255 and the High byte is 20. That > gives a 3ms timeout. By increasing the High byte, the delay is lengthened. > I've done this for the 100 version and it's working. But the delay is far to > high so I need to tweak it. > > For those using New-DOS, you already have a way to adjust the delay. But if > you are using a 200 or NEC, you are stuck right now. > > I'm going to clean up my test version and release it as a beta when I can > clean up the interface. In the process I am going to include some RAM > versions of TS-DOS that have a longer delay. Since it's only a 1 byte change > to the software it won't be difficult. I just need to figure out what the > best delay is. After that I am going to look into the loaders included in > the Sardine and Ultimate ROM. The delay function on those are different but > it will be a similar change to the ROM image to account for latency. > > Kurt
