| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Max2.02 |
Hi Roy,
RJT> Linda Hargraves wrote in a message to Roy J. Tellason:
LH> I have my modem set for hardware flow control and BNU is
LH> locked at 57.6. Would that be a cause if the caller had
LH> software instead of hardware flow control turned on?
RJT> I don't think it matters what the caller is doing,
RJT> this is pretty much a thing between your software
RJT> configuration and your modem...
RJT> Why not upgrade?
LH> The main reason I haven't, is because I only have a 125 meg
LH> hard drive and can't afford any more.
RJT> Finances are pretty tight here, too, but I saw
RJT> drives in that size range selling for as little as $20
RJT> here not too long ago.
Well, I would prefer a larger hard drive, I have a 125 & 80 now.
LH> Another question I want to ask, is there a way to post a
LH> general message to all users like {at}all? I tried that and it
LH> does not work.
RJT> What didn't work? What did it do?
LH> I tried to use {at}all in a local message base it is said no
LH> user by that name. I usually address a message to one user,
LH> then change to all and it takes it.
RJT> I don't know why you're using the "{at}" there.
RJT> I ran into that real early on, and the solution was
RJT> simple -- just create a user called "All", and set it
RJT> not to show up in the userlist, and it won't complain
RJT> about it after that.
Good Idea, I may do that, otherwise I may try to do the other bulletin idea.
TTYL
Linda
cat.lady{at}cats.gratisnet.com
--- Maximus 2.02
* Origin: Cat House BBS * Tulsa BBS List HQ * (918) 584-3441 (1:170/160)SEEN-BY: 396/1 632/0 371 633/260 267 270 284 371 634/397 635/506 725 728 SEEN-BY: 639/252 670/218 @PATH: 170/160 100 400 396/1 633/260 635/506 728 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.