Nexus 5 is fine, I've tested on a Nexus 7 and I think someone of the list has
used a 5 so no issues there. If the cable is the same one that you use for the
PC then it sounds like the adapter, but let me check the library I am using for
serial communications to see.
Kurt
On Wednesday, August 31, 2016 11:25 PM, James Zeun <[email protected]>
wrote:
Not sure on the brand, but I've used this adapter for several years to link my
m100 and Acorn BBC Micro to my windows computer, so I know it works.I'm using a
Nexus 5 with android 6.0.1.
On 1 Sep 2016 4:45 a.m., "Kurt McCullum" <[email protected]> wrote:
James, No, you don’t need floppy.co. that’s only needed for systems that don’t
have DOS in rom such as TS-DOS. Dropping the baud rate doesn’t do anything
since TS-DOS will change it to 19200 when you try to go to DISK. Two questions.
What type of phone are you using? And what brand of USB to serial converter are
you using? Also, does the same USB to serial converter and cable work with the
PC version? Kurt From: M100 [mailto:m100-bounces@lists. bitchin100.com] On
Behalf Of James Zeun
Sent: Wednesday, August 31, 2016 5:40 PM
To: Model 100 Discussion <[email protected]>
Subject: Re: [M100] Android mcomm Alright, I tried the cable and at first
nothing. I then dropped baud down to 38n1e, which is 300 kbs unless I'm
mistaken. THEN i got hex appearing on my phone, but when I load TS-DOS and try
to load DISK. It hangs, it does say disk not ready, instead it just sits
there.Do I need the floppy.co file? Where do I find it? On 31 Aug 2016 7:38
a.m., "James Zeun" <[email protected]> wrote:
KurtNope, no data appears on the screen.I'll try a different cable and let you
know On 31 Aug 2016 5:28 a.m., "Kurt McCullum" <[email protected]> wrote:
James, A couple things to try. First, use the full serial cable just to test
the exact same setup that you have working on the PC. If that works, the DB9 to
DB25 adapter has the wrong pinout. Second, Do you see any hexadecimal data
appear on the mComm screen? If not, this could be caused by a bad cable or an
unsupported usb to serial adapter. Do you know the manufacturer of the adapter?
Kurt From: M100 [mailto:m100-bounces@lists. bitchin100.com] On Behalf Of James
Zeun
Sent: Tuesday, August 30, 2016 4:01 PM
To: Model 100 Discussion <[email protected]>
Subject: Re: [M100] Android mcomm Also should point out, I'm using the same USB
to serial adapter that I use on my PC with mcomm.Only difference being that I'm
using a db9 to db25 adapter on the end. Instead of a full serial blown cable.
On 30 Aug 2016 10:42 p.m., "Kurt McCullum" <[email protected]> wrote:
Hi James, There isn't much to using the app. Once it's installed on your
Android device, attach your serial cable and press "Start TPDD Service". Once
that has started, you should be able to use TS-DOS. Keep in mind that TS-DOS
needs the DTR and CTS lines wired to work properly. The Android version is a
bit more forgiving than the PC version as far as a cable goes. If you have a
working cable for your PC, use it with the Android. I've tested the app with
both a FTDI and an old Prolific USB to serial adapter. Kurt On Tuesday, August
30, 2016 12:40 PM, James Zeun <[email protected]> wrote: John, as the title
of my email suggests. was asking about Kurt's Mcomm android app. On 30 Aug 2016
7:52 p.m., "John R. Hogerhuis" <[email protected]> wrote:
On Tue, Aug 30, 2016 at 11:20 AM, James Zeun <[email protected]> wrote:
Hey guysMight sound silly, but could someone walk me through using this app.
I've got the TS-dos rom installed via Rex. But it says disk isn't ready, when I
try to access disk drive.
There's no virtual TPDD drive in CloudT. You can launch TS-DOS but at this
point pretty much TS-DOS is only useful for RAM file management since it's not
connected to any kind of disk drive. So you can use TS-DOS to rename and kill
RAM files. I may eventually add a TPDD emulation that will back to Google Drive
and/or browser local storage. In the meantime, the way to get your files into
and out of CloudT is the "fake cassette" So if you're in TEXT and want to save
a text file, just save it to cassette. Hit LABEL to see your optionsHit F3
which means "Save"Type CAS:FNAMEwhere FNAME is the filename you want to Save-As
Scroll CloudT to bottom of screen, you should see your cassette file pop up
there.From the list you can download to local which should let you "share" the
file with Google drive (assuming you have that App installed).Alternatively, if
you are logged into Google Drive (there's a button right under the main window
for that), once your file pops up in the fake cassette list, you can click the
cloud upload button and that will save directly to your Google Drive. If
you're in BASIC and you want to save a file, you type CSAVE "FNAME"where FNAME
is the name you want to save the BA file as. To load files into CloudT, you
have a few options: a) Add URLIf you are adding a file from Club100's file
archive, it should work.b) Add Plain TextIf you paste text into the Add Plain
Text window and click the button it should appear in your cassette files.c)
Choose FileThis should let you pick a file from your local machine. On Android,
I think it should let you pick from Google Drive by launching the Google Drive
app. Not sure about that. It's system dependent (Android/iOS/OSX/Windows/
Linux) what Choose File does.d) Use Google Drive file picker to stage a file.
This will pop up the Google Drive web interface from which you can select a
file. Whichever method you choose, the file if successfully processed will
appear at the bottom of the page (at present, at least, you will need to scroll
down to view the list). Once it is in the list, you can use CLOAD to load the
file into the Model 100 file system just as if the file were on cassette. The
file at the top of the list will be the next one to load when you type CLOAD.
Most applications can pull files from cassette. If you're not typing
CSAVE/CLOAD from the prompt you generally need to prefix the filename with CAS:
Let me know if any of that doesn't make sense. Probably the next big thing
I'll do on CloudT is to add HTML5 / Angular Material fanciness. And then,
documentation. At this point the UI is rough, undocumented but functional. --
John.
