Kurt McCullum wrote:
> Teeny can also be injected from mComm. It's quite a bit smaller too
> so it loads faster. I'm not sure why that error would be coming up
> with TS-DOS. Did you use the command "RUN COM:98N1E" from Basic? The
> dos injector uses xon/xoff so the flow control lines don't matter
> when loading.

Kurt, I didn't asked about it yet because my M100 is having a lot of
other issues and I didn't want to flood the list with too many
different topics but if I did manage to get mComm 2.5 running, the
"inject TS-DOS" feature never worked for me (and yes, I have
eventually tested every single pin of my DB9 to DB25 adapter and it is
totally matching the cable described in mComm documentation).

I'm pretty sure the issue is my dodgy cheap USB to RS232 interface
having issues with xon/xoff, but here is how I managed to get TS-DOS
on the M100:

- I opened the file dos100.do from the mComm directory in a text
editor and copied it in the clipboard
- I opened a 1200 bauds serial connection with even parity and
xon/xoff using Putty on the PC
- I typed LOAD "com:58e1e in the basic prompt
- I pasted the clipboard content into putty
- I pressed CTRL+Z in putty (that sends the EOF to the M100)
- After one eternity (3-4 minutes) the loading completed, I typed RUN
and it did the trick

Note that using TS-DOS, I can transfer files at at full speed and I
got no error so far so the problem only occurs at the initial step.

Also to be transparent I had to try 3 times before getting TS-DOS
transferred without any corrupted content so perhaps you may try an
even slower speed (it usually works fine at 1200 bauds but I've never
transferred a file that big before). Note that if you're using 600
bauds you'll have to wait for 6-8 minutes to get the file.

Perhaps in the next revision of mComm you could add an option to
reduce the speed for TS-DOS injection? (and if possible some kind of
progress indicator because it's a little nerve breaking to look at the
M100 for 3+ minutes while nothing changes at all :o) )

Greg Swallow wrote:
> Yeup, using RUN"COM:98N1E" alright. Have tried to inject TEENY, but it stalls.
> I RESET, go to BASIC, and RUN and gives a Checksum error. Am beginning to
> wonder about my RS-232 port.

Is it one of those $4 USB to RS232C interfaces from eBay? That's what
I'm using and I'm pretty sure that's where the problem comes from...

Eric

Reply via email to