Thanks MIke! Your clarifications are most appreciated!

I assume a tokenized .BA file either wont open at all or be "garbled" when
opened in notepad or vi whereas a proper plain-text .DO or .BA will be
readable.

several low-cost methods of putting TS-DOS into a ROM

This is reckon is the "next level" once a new user is familiar enough with
getting files in/out and establishing connectivity to a TPDD "server".

What are the .lst files on the HTERM page? I assume those are assembler
listings? Turbo Assembler? (total guess here).

 - Lee
 - 909.437.0250
 - Destroying technology problems.



On Fri, Apr 28, 2017 at 11:59 AM, Mike Stein <[email protected]> wrote:

> Not to be too pedantic, but putting .BA and .DO files together might be a
> little misleading. A 'real' .BA file can not be successfully transferred
> using terminal programs unless you also load something like xmodem etc.,
> and has to be transferred in the same way as .CO files.
>
> So I would say '...Plain-text .BA and .DO files transfers using Telcom'
> and '...using dlplus to transfer .CO and tokenized .BA files'.
>
> In the old Compuserve etc. days when binary transfers over a modem were
> not available, it was the custom to rename the plaintext <PRGNAM>.DO to
> <PRGNAM>.BA to distinguish it from actual .DO document files; before
> actually loading them into the ModelT they would have to be renamed to
> <PRGNAM>.DO
>
> But a 'real' .BA file such as what you get when you SAVE a program is a
> tokenized binary file which can in fact corrupt the file system if you try
> to load it as a text file.
>
> So, unless you already know, it's a good idea to inspect a .BA file first
> to see if it's plain text or tokenized. If it's plain text it must be
> loaded into the ModelT with a .DO extension; if it's tokenized it (and also
> .CO files) will have to be transferred using a binary-compatible method
> such as TEENY, TS-DOS, XMODEM etc. with a suitable 'server' at the other
> end.
>
> Again, LaddieAlpha handles the conversion if necessary.
>
> Note that there are several low-cost methods of putting TS-DOS into a ROM,
> effectively adding it to the OS.
>
> m
>
> ----- Original Message -----
> *From:* Lee Olivares <[email protected]>
> *To:* Model 100 Discussion <[email protected]>
> *Sent:* Friday, April 28, 2017 1:54 PM
> *Subject:* Re: [M100] Questions regarding Full Null Modem Cables, specif
> Serial to USB
>
> I'd be happy to create a "bootstrap" page on the bitchin100 wiki to go
> into the details I initially got hung up on:
>
>  - Initial serial null modem connection and testing using screen (*nix)
> hyperterminal (win) and telcom.
>  - BA/DO transfers using telcom & screen/minicom.
>  - Loading DOS (TEENY or TSDOS) using above.
>  - Using DOS to access dlplus or laddieconalpha to xfer .CO files.
>
> Logically then it should explain .CO file management, I can summarize the
> excellent guidance provided on the list last week.
>
> And while we're at it some DOS basics like the Load (from),Save (to), and
> "Kill" which wasn't an obvious "delete" command to this novice. :)
>
>  - Lee
>  - 909.437.0250 <(909)%20437-0250>
>  - Destroying technology problems.
>
>
>
> On Fri, Apr 28, 2017 at 10:26 AM, Roger Mullins <[email protected]> wrote:
>
>> I've never played around with HTERM but I think I might after this
>> thread. :-) Maybe fire up Lynx and do some web surfing on my M100.
>>
>> On Fri, Apr 28, 2017 at 1:01 PM, Lee Olivares <[email protected]> wrote:
>>
>>> If using minicom to move over BA/DO files be sure to do ASCII transfers,
>>> unless you've loaded sxm.100 or another XMODEM compatible telcom
>>> enhancement that is.
>>>
>>>  - Lee
>>>  - 909.437.0250 <(909)%20437-0250>
>>>  - Destroying technology problems.
>>>
>>>
>>>
>>> On Fri, Apr 28, 2017 at 8:33 AM, Mike Stein <[email protected]> wrote:
>>>
>>>> I think what we need is a video showing TS-DOS (preferably in ROM) or
>>>> mcomm in action; I don't know why anyone would want to fool with terminal
>>>> programs these days (especially at 300 baud ;-) with so many better
>>>> alternatives around unless there were a special reason.
>>>>
>>>> As John pointed out, LaddieAlpha (the 'server')works with all three
>>>> platforms.
>>>>
>>>> For actually logging into a 'NIX system (as opposed to transferring
>>>> file) HTERM is a Telcom replacement that uses hardware handshaking to get
>>>> around XON/XOFF issues (and run faster).
>>>>
>>>> BTW, AFAIK you can't transfer 'real' .BA files with terminal programs
>>>> or the method below, only plain text .DO versions (although of course they
>>>> may be confusingly mislabelled as .BA) That's caused a lot of confusion and
>>>> crashes if they're not renamed during the transfer (although I believe
>>>> LaddieAlpha also takes care of that issue.)
>>>>
>>>> m
>>>>
>>>> ----- Original Message -----
>>>> *From:* Roger Mullins <[email protected]>
>>>> *To:* Model 100 Discussion <[email protected]>
>>>> *Sent:* Friday, April 28, 2017 10:59 AM
>>>> *Subject:* Re: [M100] Questions regarding Full Null Modem Cables,
>>>> specif Serial to USB
>>>>
>>>> That cable should work fine for you - all I do is go into BASIC on the
>>>> M100 and type
>>>>
>>>> new
>>>> load"com:38n1e"
>>>>
>>>> ...then launch minicom on my Linux box and use 'send file' and select
>>>> the .BA (or whatever) file that I've downloaded.  Actually I just realized
>>>> I've never tried it in reverse but I suppose that would work as well.
>>>>
>>>>
>>>> -Roger
>>>>
>>>> On Fri, Apr 28, 2017 at 7:16 AM, Paul Bucalo <[email protected]> wrote:
>>>>
>>>>> Roger, what I want to accomplish at this time is what you are doing. I
>>>>> download a slew of programs from old archives and I haven't a means of
>>>>> getting them into my M100 with the hardware I have now. Today I will order
>>>>> the Belkin cable. At $2 bucks and shipping it's worth having around.
>>>>>
>>>>> I appreciate all the comments and suggestions offered up here.
>>>>> Resurrecting my M100 is totally about spending time in the past. I don't
>>>>> need this to work for any project or importance. The M100 was my first
>>>>> working computer. It was the late 80s. I was a Property and Casualty
>>>>> Insurance Agent in a small agency, looking for an automated means of
>>>>> contact management. It worked. It worked well. So I look forward to 
>>>>> playing
>>>>> around with the options given. It's not the destination that I look 
>>>>> forward
>>>>> to, but how much I can learn on the way there. Forward to the Past! :)
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Roger Mullins <[email protected]>
>>>>> To: Model 100 Discussion <[email protected]>
>>>>> Sent: Fri, Apr 28, 2017 3:11 am
>>>>> Subject: Re: [M100] Questions regarding Full Null Modem Cables, specif
>>>>> Serial to USB
>>>>>
>>>>> Right, that's what it takes for minicom to work properly. My distro is
>>>>> actually a hard drive install of Puppy - I have an ancient HP laptop and
>>>>> Puppy was the only one that could find my particular Broadcom wireless
>>>>> adapter.
>>>>>
>>>>> Anyhow, that cable works great for no more than I do with it, which is
>>>>> basically transferring downloaded files to my M100.
>>>>>
>>>>>
>>>>> Sent from my T-Mobile 4G LTE Device
>>>>>
>>>>>
>>>>> -------- Original message --------
>>>>> From: Daryl Tester <[email protected]>
>>>>> Date: 04/27/2017 9:06 PM (GMT-05:00)
>>>>> To: [email protected]
>>>>> Subject: Re: [M100] Questions regarding Full Null Modem Cables, specif
>>>>> Serial to USB
>>>>>
>>>>> Roger wrote:
>>>>>
>>>>> >     I also use Linux, running minicom to communicate with my M100 on
>>>>> >  ttyd0.  From the command line:
>>>>> >
>>>>> >     rm /dev/ttyd0
>>>>> >     ln -s ttyUSB0 /dev/ttyd0
>>>>> >     minicom
>>>>>
>>>>> On Thu, 27 Apr 2017 20:33:59 -0400, Paul Bucalo wrote:
>>>>>
>>>>> > You said you are also using Linux. What flavor of Linux are you
>>>>> > running that uses ttyd instead of ttyS for serial devices? I only
>>>>> > know
>>>>> > of BSD/*nix that uses that device designation.
>>>>>
>>>>> I think he's done that for minicom default reasons, not Linux reasons.
>>>>> You can override it (of course) to point at whatever device you like,
>>>>> the caveat being that USB serial devices tend to dynamically jump all
>>>>> over the place (unless there is some udev magic).
>>>>>
>>>>> --
>>>>> Regards,
>>>>>    Daryl Tester
>>>>>    Handcrafted Computers Pty. Ltd.
>>>>>
>>>>
>>>>
>>>
>>
>

Reply via email to