Hi Willard, and thanks a million for letting me know this! I’ve been pulling my hair out, trying to figure out what I was missing. Why in the world did it end up this way? Why would folks make an XMODEM program and advertise it as a way to handle .CO files, but then they don’t? Too weird for me! I am so glad to know that I am not totally incompetent!
Thanks! smp - - - Stephen Pereira Bedford, NH 03110 KB1SXE > On Jan 27, 2019, at 3:47 PM, Willard Goosey <[email protected]> wrote: > > >> FYI, the two programs I pulled from the Club 100 Library were: >> XMODEM.BA <http://xmodem.ba/> and XMDPW5.BA <http://xmdpw5.ba/>. I >> was able to transfer each of them into my system, and then run >> the .BA program to create the .CO program. then running the .CO >> program was wht gave me the problem in both cases. > > Sorry,but the available m100 xmodem programs are all limited to ASCII > files only. > > (modem.200 doesn't explicitly admit to being so limited, but it's m200 > only. The commercial X/TEL *might* have been able to transfer binaries > but it's not available anywhere I know of.) > > My advice is to give up on xmodem, and get the appropriate TPDD server > and a m100 client running. It makes life much simpler! > > Willard > -- > Willard Goosey [email protected] > Socorro, New Mexico, USA > I search my heart and find Cimmeria, land of Darkness and the Night. > -- R.E. Howard
