Nope... I used other Xmodem programs and they work fine except that they
are not designed to transfer .CO or .BA. Indeed, only *one* xmodem
program gets errors... only one.
So I have been able to transfer with Xmodem just fine with no checksum
errors. One and only one Xmodem program gives me checksum errors and
that is on *every* file it transfers! I think with that program, I have
flow control wrong or I am not invoking the M/L file correctly.
Additionally, I am able to transfer very large .DO files containing
BASIC programs. They have all transferred just fine with paste on the
host PC. I have sent over 50 files so far this way and have not lost a
single character than I know of.
I am aware that .DO files that create the .CO files might get an error
somewhere in them and that worries me about sending in this fashion.
Hence, I am trying to get a stable Xmodem capable of .CO and .DO.
In regards to Teeny's documentation. I have gone through it at least 7
times from what I believe is a clean restarted M102. The first couple of
times, I did not understand CLEAR usage. Some things I do not know are:
- In future calls of Teeny, should I be CLEARing the same way each
- When does CLEAR get reset (ie reset button, etc)
- How long should I wait for Teeny to sit until I consider it locked?
Perhaps I have not been patient enough?
- How do I hard reset the M102 and how do I warm reset?
From the archives, I just learned how to make sure an M/L program is
gone. I did not do this stuff before so I might have been loading a
bunch of .CO files in and they could have been fighting.
As far as why make my own Xmodem server. Many reasons; some the same as
why I wrote in the 1980's
- I like my own interfaces
- I can
- I like to know intimately how it works so I can change it to suit my
- I would only be writing it for myself so I am the only one that
needs to prefer it over Teeny :>D
I seriously don't think these old programs are buggy, except DSKMGR on
the M102(which is the one I asked people about and the M102). I am sure
it is some of my inexperience with the way the M102 handles M/L coupled
with other factors. I am narrowing down both the former and the latter.
What I have been asking for is program recommendations and in the one
case, where to find the program. As far as troubleshooting the serial
connection, I really don't need help there as I have done that for most
of my life.
Now, if I can find a good diagnostic program, it would be nice to test
the M102 or at least the RAM.
Thanks for trying to help John.
From: John R. Hogerhuis [mailto:email@example.com]
Sent: Saturday, September 11, 2004 11:28 AM
Subject: RE: How to transfer BA and CO with Xmodem?
Hardware is A-OK. I can send, receive, and execute programs A-OK.
How do you know that? From what I understand every program you have
tried that does a checksum has proven unstable.
As far as TEENY, I may just be missing some basic Model T skills when
executing ML programs. I could be loading up RAM and mis-executing
stuff. Or maybe I have too many files in C:\ROOT????
Well Ron's docs are nothing if not complete... I'd say teeny is your
best option until you get through the learning curve, if that is indeed
BTW, if you are creating an "xmodem server" and adding an "xmodem
client" how is that better than a "desklink server" and a "laptop dos"
combo? At least the latter is in wide use. They both do checksums.
Xmodem is probably more efficient but I doubt by an amount you would
Even if you do choose to start out with xmodem, I would just pick one
and figure out the exact problem, since I think you would agree it is
unlikely that all of these old standby programs are seriously buggy.