From: theguitarmanSPAM@charter.net
Thanks Doug!
That was a big help. I'll tinker around with it & check out the manual to
help fill in the gaps.
I sure appreciate you taking the time to help like this.
:-)
-Chris
"Doug_M" wrote in message
news:u6Xsg.9276$pu3.209551@ursa-nb00s0.nbnet.nb.ca...
> Chris Young wrote:
>> Hey thanks Doug, that's more of what I was looking for was the "idiots
>> guide to using a modem with the TRS-80" lol!!
>> ;-)
>> I did see the programs "COM/DVR" & "COMM", but I'm not familiar with the
>> parameters I need to use.
>> For example with COMM it gives the message "Comm line driver not
>> specified"
>> And with COM/DVR, it says "Must install via set".
>> Could you give me a crash course, step-wise, on what I need to do, all
>> the way up to the point of dialing up a BBS?
>>
>> Also, a big thanks for the BBS listings. :-)
>> Is there a way to determine what BBS's will work with the TRS-80? Or is
>> it basically "dial & trial"?
>> ;-)
>> I'm going to download "FastTerm" today and get that on a disk.
>>
>> Many Thanks Doug!!!!
>> -Chris
>>
> Hi Chris,
>
> I can't remember the specific commands for COM/DVR and COMM off the top of
> my head, but you know where to get the manuals. On a more general level,
> first you SET the COM driver (which makes it resident), then use SETCOM to
> set the communications parameters (1200 baud, 8 bit, no parity, etc.),
> then you use COMM as the actual communications program. Something like:
>
> SET *CL COM/DVR
> SETCOM (1200,8,N,1)
>
> Don't quote me on the syntax (try HELP DOS). I can't remember how to use
> COMM.
>
> As for BBSes, you're right, it will be trial and error. You may run into
> some that want your terminal program to be ANSI which you can't do without
> a hi-res graphics board. But most should have VT100 support.
>
> Regards,
> --
> Doug McComber
> http://www.VintageComputing.net/
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
