
      Sysops:  Please feel free to use all or parts of this file as you
wish on your own BBS.  You'll of course need to change references here
to our BBS name, modems, and phone numbers to those appropriate to your
own BBS.

      If you use major portions of this file, I'd sincerely appreciate your
retaining the credit lines at the bottom.

      Thanks so much.
      Jon
      Sysop, GLIB
      (jon@glib.org)


--------------------------------

 
      HOW COME I GET THIS FUNNY-LOOKING GARBAGE (@#**;lj*I#-!)?

      The quality of your communications with the CESF computer can only be as 
good as the telephone lines and modems between there where you are and here 
where we are. 

      Unfortunately, especially with budget-priced long-distance services, 
(and with some cheap modems) "line noise" often creeps in.  If you were 
talking via voice on one of these lines, you'd probably not even notice the 
"static", echoes, or strange sound quality.  But your computer (and ours) are 
not quite so forgiving, and in their dogged efforts to make sense out of this 
noise, they simply produce random characters, which appear on our screens as 
"garbage". 

      What's more, sooner or later, this irritating and inconvenient 
phenomenon most definitely will rear its ugly head during one of your calls to 
a BBS.  Maybe this one, maybe not.  But eventually, it =will= happen.  
Guaranteed.  Even with the finest modems in the world, and the most expensive 
phone line services you and we can buy, such interference is really quite 
common. 

      Every sysop in the world who has operated a BBS for more than a few 
weeks has received a message many times which typically goes something like 
this: 

      "There is something wrong with your BBS.  All of a sudden, I get this 
awful garbage on my screen when I call your BBS, but I can call dozens of 
other ones with no problem.  Why don't you fix this? I know there's nothing 
wrong with my computer or modem, because yours is the only BBS I have this 
problem with". 

      Unfortunately, it's just not that simple.  We'll try to explain how and 
why this happens, and what =you= might do about it: 

      All calls you make go through one or more "switches", electronic devices 
which route your call to its destination.  For a local call, only one such 
switch may be involved, but for a distant call, many switches, as well as one 
or more satellite or fiber optic cable circuits may be involved, all of which 
use electronic analog/digital conversion and transmission devices.  Any ONE of 
those devices, either at the sending or receiving end, could garble your data 
call.  While on a voice call, such defective equipment might produce only 
echoes, or fuzziness, or maybe other conversations in the background.  But for 
a data call, "garbage" is often the result. 


      FIRST TRIES

      There are several possible "fixes" for this problem.  Try these first: 

     1.  Are you sure your own communications program is properly configured? 

     Sometimes when new BBS callers have chosen to have GLIB (or any BBS) 
transmit color graphics menus, but they have not selected the proper "terminal 
emulation" in their own communications program, they see what looks like 
"random garbage" on their screens, when in fact what they're actually seeing 
are the ANSI control codes used to write color graphics BBS menus.  Typically, 
they'd see something like this: 

     ^[[45;32m^[[40HA line of text with garbage in it like this^[[35m 
     ^[[46;34mMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM^[[40;34m

     This is because, unless properly configured, the communications software 
running on their own computer is incapable of properly decoding/displaying the 
ANSI codes used to "write" the color graphics menus on most BBSes (including 
GLIB), and instead simply displays those codes literally. 

     To check, go to the dialing directory section of your communications 
program, and be sure you have chosen a graphics-capable terminal emulation for 
your directory entry for GLIB.  The best choices are "ANSI", "IBM-PC", or 
"VT100" (in that order).  Some comm programs do not offer individual settings 
for each directory entry, but rather merely offer one common setting for all 
entries somewhere in its technical setup section.  (Read The Manual). 

        If your comm program does not offer those options, then it is probably 
quite old, and simply incapable of displaying ANSI color graphics.  In such a 
case, you must turn them off here on GLIB when you call in here with that 
software.  To do that, go to the GLIB Utility Menu (press "#" at any GLIB 
"Command:" prompt to get there), and select "<N>o - don't send me color 
graphics".  Should you call in later with a program capable of displaying ANSI, 
you can always go back there and turn them on again. 

     Note:  Incredibly, the "terminal" program in Windows 3.1 is =NOT= capable 
of displaying color graphics.  If you're trying to use it, we recommend you 
get yourself a "real" communications program ASAP. 


     2.  Call us on a better connection.  Our phone lines are usually as good 
as they can get, and most users rarely complain of garbage.  So if you do get 
it, suspect your long-distance carrier first, and your local lines second.  
And if both of those seem OK, (and especially if you also get garbage when 
you're on-line with other services), check out your modem and connecting 
cables. 


     3.  Go to a lower baud rate.  Generally, the higher the baud rate you're 
using, the more susceptible your communications are to noise. 

     The bandwidth of standard dial-up phone lines is limited to the normal 
range of the human voice.  Dr. Bell and his phone-company pioneers never 
intended for their lines to carry anything but the human voice when they 
established the standards still being used in most areas.  So trying to cram 
14,400 bits or more per second into a line which normally transmits only voice 
is quite a trick, at best.  You'll usually experience cleaner communications 
at 9600 or even 2400 bps, because the entire communications "system" from your 
end to ours isn't working quite so hard. 


      MODEM INCOMPATIBILITY

      Unfortunately, the proliferation of high-speed (14,400 bps and above) 
modems has led some "low-end" manufacturers to cut quality as well as price in 
their products.  If you're using a cheap modem, be aware that a number of them 
appear to be only marginally compatible, and will not reliably connect with 
"standard" high-speed modems.  In such a situation, if you connect at all, 
your session may be very "noisy". 

      As of the time this file was last edited, all GLIB phone lines answer 
with at least Hayes Ultra or Optima 14,400 bps modems.  Hayes brand modems are 
considered the "industry standard" against which all others are compared, so 
if your modem cannot connect with ours, suspect your modem as defective. 

      Most modem connection problems (especially those caused by a temporarily 
bad phone line circuit) are transient, and will usually "go away" of their own 
volition in an hour or so.  By the time your Sysop hears of such problems, 
they've usually either simply disappeared, or a phone technician somewhere 
along the way has already fixed it.  But if your new modem regularly seems to 
exhibit a quirky incompatibility or line noise more often than quite rarely, 
and you can still return it, we strongly suggest you do so.  You'll probably 
eventually have the same problem on other BBS services using industry-standard 
modems too.  Some "bargain" modems are no bargain at all.  And remember ... 
"Hayes Compatible" means only that the modem in question understands the Hayes 
"AT" command set ... nothing more, and a low-priced "Hayes Compatible" modem 
may well be very poor quality.  Generally, you get what you pay for. 


      NEXT, THE PHONE LINES IN YOUR HOME OR APARTMENT

      If your home or apartment telephones and/or phone lines were installed 
more than ten years ago, chances are good that they may be causing noise.  
Wires running outside, between floors, and through humid areas (like laundry 
rooms) should be considered suspect.  The best way to check for that 
possibility is to temporarily disconnect them, and connect your modem as close 
to the incoming terminal box as possible.  If that's the cause, temporarily 
disconnecting all other lines should give you a clear connection.  Often there 
are lots of lines still connected which are no longer being used.  They may 
easily be the culprits.  Disconnect them. 

      One other item:  The surge protectors in your "customer interface" box.  
These are the gadgets inside that box, where the lines enter your home, which 
are designed to protect the phone line and other phone-company equipment (not 
=your= equipment) from high voltage damage.  Older protectors were made of 
carbon rods, and they suffer from a problem called "flaking".  This 
significantly increases line noise, especially data calls during humid 
weather.  The cure for this, if you find you have that kind of protector, is to 
ask your phone company to replace them with the newer "gas tube" protectors.  
These newer ones don't produce noise.  It's difficult to determine for 
yourself which kind you have, and carbon protectors are still being installed 
in some rural areas.  If your installation is more than ten years old, it 
might be smart to ask your phone company to check it out for you.  It's worth 
the one-time service charge. 


      YOU AND YOUR PHONE COMPANY

      Remember ... no telephone company guarantees data communications on 
voice phone lines.  If your phone line was installed for voice communications, 
and you are able to make satisfactory voice calls without any audibly obvious 
problems, most telephone repairman will consider it "just fine, thanks".  Some 
telephone company repair personnel and customer service reps, especially in 
larger urban areas, do understand what data calls are all about and know what 
a "modem" is.  But don't count on it. 

      For most reliable use of your modem, consider installing another phone 
line specifically for data calls.  It can be a voice line too, but order the 
most basic service with no frills, and most definitely without "call waiting".  
Tell the phone company that it is to be used specifically for data calls, and 
make sure they note that fact in your customer records.  Then, should you 
encounter data noise on that line, you'll have some leverage in dealing with 
them, and they'll have a point of reference from which to handle your problem. 

      While it is possible to especially equalize a phone line for data 
transmission, such special treatment is usually not necessary, and is often 
very expensive.  Just having your line listed as a "data line" with your phone 
company will often very effectively get their attention to a problem. 


      LONG-DISTANCE SERVICES

      The quality of data communications via long-distance voice services 
often reflects the price you pay for the call.  In many cases, for data calls, 
"bargain" long-distance services are no bargain at all, because the added time 
necessary for the re-transmissions your computer will automatically make when 
transferring a file on a noisy line will often cost more than a higher priced 
connection would have for a shorter call. 

      If you're repeatedly experiencing line noise on long-distance calls, try 
another long-distance carrier.  You do NOT need an account with the alternate 
company.  The charges for your alternate carrier calls will simply appear 
along with your other calls on your regular phone bill. 

      To use another carrier, just preface the number you're calling with "10" 
followed by the code number which specifies the long-distance carrier you want 
to use, followed by "1", followed by the number you're calling. 

      For example, if you are not using AT&T, but you wish to send your call 
through the AT&T system, simply precede the number you want to call with "10-
288-1-".  GLIB's public number, 703-578-4542, would then become: "10-288-1-
703-578-4542".  It's that easy. 

      For other long distance carriers:

      To specify MCI (code 222), you would dial 10-222-1-703-578-4542. 

      To specify US SPRINT (code 333), you would dial 10-333-1-703-578-4542. 

      To specify ALLNET (code 444), you would dial 10-444-1-703-578-4542. 

      There are literally hundreds of other long-distance carriers having 
access codes from "001" to "999".  Check your local phone book for them. 

      Although long-distance companies sometimes share the same transmission 
equipment, this is not necessarily so.  A bad connection via one carrier 
caused by a noisy switching center or poor lines can often be completed 
perfectly via a different carrier.  What's more, the difference is often 
related to only one specific area code at either end of your call.  Some long 
distance carriers simply have better lines into some areas than others, and 
the "interface" between a long-distance carrier and the local phone exchange 
is often the culprit.  So experiment.  The difference might surprise you. 

      REMEMBER:  This problem with noisy connections can also exist within, 
between, and among local metropolitan calling areas.  There have been, for 
example, several persistent outlying Maryland exchanges from which clean data 
calls typically could not be made into our area.  We regret that, but 
generally there is little to nothing we can do about it from here.  The caller 
must initiate the complaint and be willing to work with his or her local phone 
company to fix it.  


      CESF PHONE LINES

      The CESF computer runs on business-grade Centrex phone lines, the finest 
and "cleanest" lines our phone company offers.  These are checked periodically 
for noise, and we usually pass along problems our members report to our local 
phone company.  They are very responsive, and usually have any problem fixed 
within a few hours of our call.  So ... should you report a persistent noise 
problem to us, we'll take it seriously. 

      NOTE:  If you experience a problem you think may be related to a 
specific phone line, PLEASE make note of the line you're on at the time.  To 
find that out, just press "@" at any GLIB "Command:" prompt.  We cannot check 
out a problem unless we know what specific line you were using at the time it 
occurred.  (It's not the "phone number" you called that we need, it's the line 
number such as "7" or "23" that the "@" command returns to you that counts.) 

      Our experience indicates that most noise problems are usually not here 
at our end, but rather, somewhere between you and us.  In the rare instance 
that our own lines are noisy, many of our members will report similar 
problems.  If yours is the only one, and we tell you it doesn't appear to be 
at our end, believe us.  We really do care. 


      SLOW DATA TRANSFERS

      Newer error-correcting modems (like those GLIB uses), as well as
error-correcting file transfer protocols (such as ZModem), will persistently
try to re-send data packets over a poor phone connection.  That's of course
wonderful, but when using hardware-based error-correction (wired into the
modems), that re-transmission activity is essentially invisible to you.  Thus,
it may occasionally seem to take =forever= for a file (such as a QSO message
data packet) to be transmitted between you and GLIB.  When this occurs, your
first suspicion should be a bad connection (particularly if calling long
distance and/or using very high speeds such as 14,400 bps).  The best way to
"get around" such a problem is to call back at a lower speed.  If that lower
speed works, but the higher one doesn't ... noisy phone lines as outlined
above are your most likely problem.


      IF ALL ELSE FAILS

      If you've checked your phone lines, your modem, your software, you've 
let us know about your problem and we've checked our lines and told you 
they're fine, and there's simply nothing more you can do ... call the phone 
company and ask them to trace your data call to us. 

      You will, of course, probably have to be at home to receive the phone 
technician and demonstrate the problem to him.  If you're lucky, and you can 
simulate the problem while he's there (often impossible to do), he may then 
contact other technicians at various switching centers between you and us, and 
they will try to isolate a defective switch or other electronic device.  It's 
much easier to do if you have two phone lines, so he can talk on one, while 
you're communicating on the other. 

      Your phone company will, of course, expect you to pay for this service 
call.  This is a "last resort" fix, but often, it's the only way to correct 
the problem. 

      Remember, each time you place a call, it usually goes through completely 
different circuit paths, depending upon "system load" (how many others are 
using the phone system at the time you are).  Therefore, the switched circuits 
you get on any given call are often entirely random.  You might get a perfect 
connection 9 out of 10 times, but then again it could be 1 in 10.  Only phone 
company technicians can track down a defective switched circuit. 


      HELPFUL HINT

      As mentioned above, error-correcting modems will essentially "mask" 
phone line noise, in which case you may not even be aware of a bad connection, 
particularly if you're just chatting on-line in real time, or keying in text 
messages.  But if you're not using hardware-based error correction, and you're 
in the process of *entering* a message when garbage creeps in, here's a 
helpful hint ... you may =not= want to backspace over garbage characters. 
Remember, those junk characters usually only go one way ... they are probably 
not appearing here.  That means that when your cursor advances past a junk 
character, it may still be on a valid character at this end.  Thus, should you 
backspace, you may actually backspace over VALID characters which would then 
be missing in your message.  Just try to ignore the junk (if you can), and 
proceed to key in your message.  You'll see that when you <V>iew or <L>ist 
your message, the junk often appears at a different place each time, proving 
that it's "not really there" in your message. 

      Example: If you were planning to type in "Hello there" and what appeared 
on your screen as you were typing was "Hello th*^%%" and you decided to 
backspace over the four garbage characters before entering the last two 
characters, what you would actually enter here at this end would be "Hellre". 

                                  -=0=-

        Copyright (c) 1996, Community Educational Services Foundation,
             Sponsors of the GLIB BBS and ZZAPP! Internet Services.
                 Modem: 703-578-4542  Internet: info@glib.org
                      Portions used with permission.

