Glad its working for you.
KurtOn Jan 3, 2018 8:09 AM, Jonathan Yuen <[email protected]> wrote: > > Hello, > > It was the file names from my linux windows whatever. They've been going back > and forth between different systems, and they had (mostly lower case names) > and none were 6.2 characters. I even tried to rename them when the phone was > mounted in windows but no luck, windows wanted to keep them lower case. And > the TPDD directory was on an emulated card in the phone so I couldn't take > the card out. So I ended up downloading a shell for android and changed the > names with a command line in the phone. I've gotten lazy and don't usually > mount the phone in linux since it is MTP now. > > I've only tested TS-DOS but it seemed OK. > > Thanks for the help!! > > Jonathan > > [email protected] > ________________________________________ > Från: M100 [[email protected]] för Kurt McCullum > [[email protected]] > Skickat: den 2 januari 2018 20:52 > Till: [email protected] > Ämne: 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]<mailto:[email protected]> > >
