Jim,
Probably because I was working briefly with T-Base when developing the Android
version so I added it. I noticed that T-Base used filenames that were not valid
in modern file systems so I made a tweak. In the end I didn't find T-Base to be
a database I wanted to use so I never made the change to the Windows version.
Purely an oversight.
I'll make a note to put it in the next release of the Windows version. Not hard
to do at all. Plus I can throw the RAM version of Sardine for the 100 into it
at the same time. I'll let you know when I get time to do it.
Speaking of databases, I developed a SQL engine for the Windows version of
mComm using the Microsoft Jet engine. Really cool but I never added it due to
not having a simple way to pass the data back and forth. However, getting the
TPDD2 opened my eyes to a possibility of using the second bank filename feature
of TS-DOS to create a conduit for the data. I'm not sure it's of any use but I
may pick it up again when I have some time.
Kurt
On Tuesday, January 2, 2018 12:30 PM, Jim Anderson <[email protected]>
wrote:
#yiv2779763072 #yiv2779763072 -- _filtered #yiv2779763072
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv2779763072
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv2779763072
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv2779763072
#yiv2779763072 p.yiv2779763072MsoNormal, #yiv2779763072
li.yiv2779763072MsoNormal, #yiv2779763072 div.yiv2779763072MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv2779763072 a:link,
#yiv2779763072 span.yiv2779763072MsoHyperlink
{color:blue;text-decoration:underline;}#yiv2779763072 a:visited, #yiv2779763072
span.yiv2779763072MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv2779763072
span.yiv2779763072EmailStyle17 {color:#1F497D;}#yiv2779763072
.yiv2779763072MsoChpDefault {font-size:10.0pt;} _filtered #yiv2779763072
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv2779763072 div.yiv2779763072WordSection1
{}#yiv2779763072 I was going to add something similar to this conversation, but
Kurt touched on it already so I’ll just re-emphasize – I recently had an issue
where TS-DOS would hang when I tried to load a file from mcomm on my android
device. Drove myself crazy trying to figure out what was going on, and why it
was only that one specific file, until I looked at the file from the CLI in the
android device and noticed something that was not readily apparent when looking
at the folder from my Windows desktop: the filename had a space in it just
before the dot, which made the filename 7.2 characters long. Like this:
ABCABC .DO ABCABC.DO When you’re looking at the side-by-side it’s obvious,
but on its own and in a small non-proportionally-spaced font, not so much…
I’d previously had headaches with this so I am pretty scrupulous about making
sure that everything in my TPDD folder in Dropbox conforms to the 6.2 all-caps
namespace. I also adopted my own convention of saving ASCII versions of BASIC
programs with a .BD extension, which has the upside of allowing for a .DO file
for the program documentation to share the same filename, but has the downside
of requiring you to copy or rename that file to TEMP.DO or something before
loading it into an M100 since TS-DOS won’t let you rename a file extension even
when copying the file. Hey Kurt, while I’m thinking of it, I love that mcomm
for android transparently changes asterisks in filenames on the M100 side into
carats in the android filesystem, and back again. (I’ve been using T-Base,
which insists on names like CUST*S.DO.) I noticed that mcomm for windows
doesn’t, though. Files in the TPDD folder with carats in the name show up in
TS-DOS with carats. It’s workable as long as I remember to rename the file
appropriately while copying it, but I was curious why only the android version
does this filename translation. jim From: M100
[mailto:[email protected]]On Behalf Of Kurt McCullum
Sent: Tuesday, January 02, 2018 11:53
To: [email protected]
Subject: Re: [M100] mcomm difficulties Jonathan, From what you described,
mComm and your cable are working properly. FFFFFF.XX (C=KLSQ) isn't an error
message. Those are the instructions for TEENY. K=Kill, L=Load, S=Save, Q=Quit.
Just the fact that you were able to load both TEENY and TS-DOS indicates the
cable is working. The quickest way to test this is to write a DO file in
TEXT and then go to TS-DOS or TEENY and save it to the Android device. Then
delete it from your m100 and reload it. If that works, then everything is
working properly. If not, then it's something else. I'm not familiar with your
device but double check to see if your have a TPDD folder when you plug it into
your PC. mComm is supposed to create one when it first runs. Also, mComm is
very specific on filenames. They must be FFFFFF.XX format where the filename is
only 6 characters long and an extension 2 characters long. And one last note.
If you are trying to load a basic file from the club 100 site, keep in mind
that they have all been converted to .do (TEXT) files but their extensions were
left as a .ba (BASIC) file. Loading one will fail unless you first change the
extension to .DO. Hope that helps. Kurt On Tuesday, January 2, 2018
8:41 AM, Jonathan Yuen <[email protected]> wrote: Hello, I've been
playing with mcomm, but it seems to give some trouble. There are enough hacked
together pieces in the chain of devices that I am not sure where to start.
I'm running it on a Samsung S4 but the I9502 version (sold only in China) and
Lineage OS (Android 7.1.2) I have a USB on the go adapter and an FTDI USB
adapter, but the latter was bought on ebay from some place in Asia. When I
plug it into my Linux box, lsusb reports this for the adapter: Bus 003
Device 004: ID 0403:6015 Future Technology Devices International, Ltd
Bridge(I2C/SPI/UART/FIFO) The Null modem was made with a soldering iron the
the connections are the ones listed in the mcomm documentation. I have tried
to bootstrap both tiny and ts-dos into a model 100. Both seem to load OK, but
have trouble running. Tiny gives me an error FFFF.XX (C=KLSQ) I have to
use the reset button to get out. TS-DOS gives me a menu that seems OK (it
reports the files in the M100 or in the virtual disk), but it hangs when I try
to download a file. I have 29638 bytes free after a cold boot, 25878 after
loading tiny, and 23733 after loading ts-dos. Not sure where to start. I
thought if I had either tiny or ts-dos in the m100, I could try things like
Laddie Alpha or dlplus, but I'm not sure if the programs are loading OK. I
have run 'LOAD *COM:981E* as well to get the BASIC program for making ts-dos or
tiny but I'm not sure what the listing should be. Jonathan
[email protected]
