In-Depth Troubleshooting
This collection of documents is where more extensive information can be found to answer, support, or solve problems
you might be experiencing. We intend to add new documents to this collection as time goes on, so keep your eye on
additions or other developments to this "In-Depth Troubleshooting Collection".
We're always open for suggestions, so if you have an idea or question that you think would make a good In-Depth
document, feel free to mail us at support@core.com. In your message, please include mention of the In-Depth
support area.
01: Connecting at Speeds Lower Than the Advertised Speed of the Modem
A common question that CoreComm users have is why their modem doesn't connect at the speed that it
is advertised as. When you buy a 28.8, 33.6 or 56k modem, you expect it to connect at 28.8, 33.6 or 56k, right?
Unfortunately, that's rarely the case and this document explains why.
02: Unexpected Disconnections While Online
Nobody likes to see their Internet connection suddenly disconnect, especially when trying to work. This document
explains the various reasons for disconnection problems, and offers suggestions for minimizing or eliminating them.
Please note that this document covers disconnections that occur -after- you're connected to the service. If you are
getting disconnected immediately after logging in, please see the In-Depth article "How
to Avoid Immediate Disconnections when Dialing In" for more information about that particular problem.
03: Resolving General Protection Fault, Illegal Operation, Invalid Page Fault, and other "Freeze-up" Problems
Nearly any Windows user at one time or another has seen one of the previously mentioned errors. This document explains
the reasons for these errors, and what you can do about them if they appear while you're using your Internet software.
04: How to Avoid Being Disconnected Immediately After Dialing In
Getting disconnected immediately after your modem connects doesn't mean we're busy. This document explains what you
can do to avoid being disconnected immediately after dialing into our service, or how you can accurately report this
problem to us if it continues after troubleshooting. Please note that this document only covers immediate disconnections.
If you're being disconnected after using the Internet for a period of time, please see the
"Unexpected Disconnections While Online" document.
05: No Answer, Busy Signals, or No Dialtone Errors When Dialing In
One would think that a message saying "No answer," "No Dialtone," or "The Line is Busy" would have to indicate that we
(or the phone company) weren't picking up the line when you were dialing in... but that's often not the case. A lot of
the time, the true reason for the above problems are software-related, or have a reason that you wouldn't expect. This
document explains the various causes of the messages listed above.
Other sources for In-Depth Information
- Netscape's Answers to Frequently Asked Questions