Re: [M100] mConm v1.81 vs ioGear GBC232A (BT)
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 : > 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 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 : >>> 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 <>< >
Re: [M100] mConm v1.81 vs ioGear GBC232A (BT)
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 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 : >>> 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 <>< >>>
Re: [M100] mConm v1.81 vs ioGear GBC232A (BT)
A few things: 1: A bluetooth link will not work for TPDD, or at least not consistently, because of the unexpected delays in the connection. Kurt does have a specially modified copy of TS-DOS but I don't know if it actually fully solves the problem or if it was just an attempt that helps somewhat. At the very least you need to be using that specific copy of TS-DOS, and even then maybe it will and maybe it won't be 100%. I don't know if the loader in mcomm provides that version. Maybe it does, and so maybe you're already doing this part. 2: "Disk not ready" usually means the 100 is not seeing DSR. Does the BT device provide the DSR & DTR lines? If not, you need to short DSR to DTR on the 100 side of the connection. I would get this working perfectly with a normal serial connection before even thinking about bluetooth. If you fail to get a regular serial connection working, the next steps will not be to try BT instead, but to figure out why the normal serial isn't working. Almost always it's simply getting the serial wiring correct. Have you verified the serial port is good in the 100 with a loopback plug? I can't quite make sense of the last part of your post. It seems like maybe you're talking about an Android device. No com port found means the app needs a serial port, and you don't have one plugged in (or the os doesn't have a driver for it, or there is some setting in the os that must be switched to enable usb otg devices) . I don't know if mcomm for android supports using bluetooth directly, but I do know it normally expects to use a usb-serial adapter connected by an "OTG" cable. If it does support bt directly, I imagine there must be directions and settings somewhere in the app to pair the phone with the other device and then select that device in the app. Again I would start with a usb-serial adapter and a serial cable and get that working 100% before moving to bluetooth. For reference, here is an off-the-shelf serial cable (a few actually but the first one is cheapest) with fully correct wiring to go from a 100 to a pc com port or a usb-serial adapter, and on the bottom of the page is a few known-good usb-serial adapters. With those, all doubts have been removed. The cable is good and the usb-serial is good. You can get just the serial cable and use that with your old full pc with a real comm port. For use with an Android device, get the serial cable, the Sabrent usb-serial adapter, and a usb OTG cable. I don't have a link for one there but just go on ebay or amazon and search "otg cable" and get one that has the right connector for your phone or tablet. Most likely you need micro-usb, but new devices are now using usb-c so at least those two types will turn up and you need to watch out to get the kind that fits your device. http://tandy.wiki/Model_T_Serial_Cable -- bkw On Sun, Feb 7, 2021, 10: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 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 : > > 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 v
Re: [M100] mConm v1.81 vs ioGear GBC232A (BT)
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 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 : > > 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 <>< >
Re: [M100] mConm v1.81 vs ioGear GBC232A (BT)
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 : > 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 <>< >
Re: [M100] mConm v1.81 vs ioGear GBC232A (BT)
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 <><
Re: [M100] mConm v1.81 vs ioGear GBC232A (BT)
(con't) Was able find a VT100/Terminal emulator for the phone and connected M100 as I did with the MBP. Typing in both directions correct at full/half duplex (echo) working fine. Thanks in advance for any help. GregS <>< Jan 2, 2021 2:18:22 PM Greg Swallow : > 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 <><
[M100] mConm v1.81 vs ioGear GBC232A (BT)
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 <><
