Kurt, Ah I misunderstood. I thought the injected version had the delay. I'll check my cables and try that this week some time.
Thanks, GregS <>< Feb 7, 2021 4:50:00 PM Kurt McCullum <[email protected]>: > Greg, > > The DOS injector puts a normal RAM version of TS-DOS without the delays that > are needed for BT. The error you are having is due to TS-DOS expecting a > response in 3ms and a BT connection cannot respond that fast. The ROM > versions I made with delays address this problem. Most of the testing I did > with this is a few years old but I do know that Gary Weber was able to get it > working on his NEC 8201 using the delay verison. > > Another thought would be to use TEENY since that doesn't have the delay issue. > > Kurt > > On Sun, Feb 7, 2021, at 7:23 AM, Greg Swallow wrote: >> Kurt, >> >> Updated mComm vs BT. >> >> Have been working on this on my days off F-S-S. Setup a P4 with XP to >> dedicate to M100 task as the MB has serial. Parallel et al. >> >> Have been able to inject TS-DOS via cable with mComm 2.5. It works in that I >> can see files on Disk [F4]. Loading [F1] is not happening. I am able to use >> Term between XP and the M100, but sending a file to the M100 is not working >> using modem, kermit or modem (default). >> >> BT has at least given some new messages. When connecting to the M100 via BT >> and mComm 2.5 TS-DOS gives a “Disk not ready” message after pressing Disk >> [F4]. mComm 1.8.x on the w/ A9 has progressed in that it gets to Connection >> Successful before giving a message of “No Com Ports Found.” >> >> Please let me know and hints or thoughts you might have. >> >> Thanks, >> >> GregS <>< >> >>> On Jan 2, 2021, at 4:54 PM, Greg Swallow <[email protected]> wrote: >>> >>> Kurt, >>> >>> Cool. I've had other apps (Music Folder Player) that had/have issues w/ A9. >>> >>> Take your time. I was hoping to get more done over the holidays myself. My >>> keyboard drawer project got delayed two days. I moved a fan after brushing >>> on a second coat of stain and it blew particals on to the surface. >>> >>> God Bless, >>> >>> GregS <>< >>> >>> >>> Jan 2, 2021 4:35:11 PM Kurt McCullum <[email protected]>: >>> >>>> Greg, >>>> >>>> I've been moving into my new home these past few days. Finding a new place >>>> took far longer than I anticipated. I'll take a look at the Bluetooth >>>> connection in v1.81 when I find my Retro computer boxes. I suspect that >>>> your problem has something to do with Android 9 and above not playing nice >>>> with mComm. Google made some big changes with either version 8 or 9 and I >>>> may end up having to get a newer Android device to test out my code >>>> against. >>>> >>>> Kurt >>>> >>>> On Sat, Jan 2, 2021, at 1:17 PM, Greg Swallow wrote: >>>>> All: >>>>> >>>>> Didn't want to get a handful of BlueSMirF Gold boards and put one in each >>>>> of my M100/T102 computers. Picked up this ioGear GBC232A (seller posted >>>>> it on eBay as a GBS301). Anyway, I'm hoping to get it working and connect >>>>> to my motoG6 (Android 9) using mComm. >>>>> >>>>> I've been able to verify connection between an M100/GBC232A and my >>>>> MacbookPro through TERM @ 98N1E. So forgot the device on the MBP and >>>>> paired to motoG6 but mComm v1.81 exits with a message about no COM ports >>>>> found after selecting to connect to the GBC232A from the device list. >>>>> >>>>> Any suggestions? Or, is there an update to mComm? Would need a link as I >>>>> lost whatever link I had to Club100 user files et al. >>>>> >>>>> Thanks, >>>>> >>>>> GregS <>< >>>> >
