|
What is an init string ?
Different modems can't necessarily talk to each other
as setup right out of the box. Modems use many different
settings and protocols. In order for two modems to communicate,
they must agree on many things such as speed, error
correction, compression algorithms, etc... By sending
a modem init string, you can control some of these parameters
What do I need to put in my init string?
In general, the modems used by paging carriers run at
a speed from 300 to 2400 baud (1200 being the most common).
They don't typically use any form of error correction
or data compression protocols. In many cases,
if your modem tries to use either these protocols, your
modem will be unable to communicate with the paging
terminal's modem. In your init string you should
include settings to lock your modem's baud rate to that
of your carrier's modem, disable error correction protocols,
and disable data compression protocols. In addition
NotePage, Inc.'s software would like your modem to issue
English response codes (rather than numeric response
codes), and issue complete connection information.
Do all modems use the same init string?
No, many different modem manufacturers use their own
set of init strings. Init strings may even be different
between models by the same manufacturer.
My init string works on one carrier but not the
other.
You may need a different init string to connect to each
carrier. In general your init strings will be the same,
but not always.
What do I use for an initialization string ?
There is no easy answer to that question. Some modems
may need initialization strings to connect to some paging
carriers. If the modem keeps dialing and connecting,
but does not send the message, chances are a modem initialization
string is needed. Some common initialization strings
are below. If you have a less well known brand modem,
you may need to use the documentation with your modem
to create an init string.
| AT&FQ0V1X4&D2 |
Minimal settings. Works with most 1200 or 2400
baud modems |
| AT&FQ0V1X4&D2N0S37=5 |
Works with many 14.4 and 28.8 modems. Additional
codes forces a 1200 baud connection. Use S37=6 for
a 2400 baud connection |
| AT&FQ0V1X4&D2N0S37=5\N0%C0 |
Works with many 14.4 and 28.8 modems. Additional
codes turns off error correction and data compression. |
| AT&FQ0V1X4&D2N0+MS=B103 |
Works with some of the
newer winmodems. Set the baud rate to 300 when using
this string. |
| AT&F0Q0V1X4&D2&B1&K0&M0&N2 |
Works with USR 33.6 and 56 K modems. Turns
off error correction and data compression. Forces
a 1200 baud connection. Use &N3 for a 2400 baud
connection. |
Please note all '0' are zeros not "ohs"
I have a US Robotics (3 Com) modem. I have tried
the init string but still get inconsistent results.
Some model US Robotics modems have difficulty communicating
with the computer at low baud rates (i.e. under 9600
baud). Try setting the baud rate on the carrier setup
screen to 19200. Also use the init string given to lock
the baud rate between the modems to a lower rate.
The modem keeps redialing and doesn't send the messages,
with the detailed log option turned on the log reads:
No ID=Received
or
Automatic TAP mode not accepted
or
No '[p' received
This could be one of two things. First the phone number
the program is dialing does not connect to a paging terminal
that accepts the TAP protocol (in some countries TAP is
not the standard paging protocol). Second, your modem
is not communicating with the paging terminal's modem
correctly. An modem initialization string will usually
solve this problem. See the above discussion on initialization
strings.
I have a 56K modem and am unable to connect to the
paging carrier.
Many new 56K modems are 'voice' modems, which means
that they support features such as speakerphone, voice
mail, sound recording, etc. In order for these features
to be supported, the modem locks itself in a high-speed
connection mode which can't be over-ridden using init
strings. To disable the voice capabilities of the modem
follow these instructions:
1. From the Windows start menu choose: 'Start' >
'Settings' > 'Control Panel'
2. From the control panel double-click on the icon labeled
'System'
3. On the 'System Properties' screen click on the tab
labeled 'Device Manager'
4. Find the entry called 'Sound, video and game controllers'
(if there isn't one you don't have a voice modem)
5. Click on the '+' sign next to the entry
6. Select the entry under 'Sound, video and game controllers'
called: 'Wave device for voice modem' (if there isn't
one there, you don't have a voice modem).
7. Click on the 'Properties' button.
8. The properties screen for the device will appear.
Check the box labeled 'Disable this hardware profile'.
9. Click 'OK' and then 'OK' again.
10. Restart your computer.
I receive the error 'Error Talking to Modem...Invalid
Port Number'
1. Go to 'Tools' -> 'Setup' -> 'Engine' (tab) and check
to be sure your modem (engine) com port is set correctly.
2. If you have an external modem, make sure it is connected
and turned on.
3. There may be another program running on your system
that is using the modem. For example, you will get this
error if you have a fax program running in the background
waiting to receive faxes, or you may have a remote control
program such as PC Anywhere running in the background
waiting for a call. PageGate requires exclusive use
of the modem.
I receive the error "excessive database retries
in procedure: "
Due to a bug in Microsoft Jet Database that PageGate
uses this error occurs in certain versions. We have
worked with Microsoft and compensated for the bug, this
error has been corrected in PageGate v2.07.
When I try to install the server portion, I get
a "missing runtime DLL" message.
Clear out files in the Windows temp directory and redownload.
It is unlikely that a full download came down, redownload
and verify the file size.
I receive the error 'Unable to access modem'
This message is given if PageGate is unable to talk
to your modem. Check the port you have set PageGate
to use for the dialer in question. If you have an external
modem, make sure it is connected and turned on. There
may be another program on your system that is using
the modem. For example, you will get this error if you
have a fax program running in the background waiting
to receive faxes, or you may have a remote control program
such as PCAnywhere running in the background waiting
for a call. PageGate requires exclusive use of the modem.
For more information please refer to the manual section
'Connecting to a carrier' in the 'Troubleshooting' chapter
of the PageGate help file.
I receive the message 'Warning unable to access
the database'
This message is warning you that one of PageGate's modules
has temporarily lost contact with the PageGate database.
If PageGate is running on a real busy computer or network,
you may intermittently receive this message. This can
be normal in a busy environment. PageGate is simply
letting you know that it did not get through right away,
and it will keep trying. However, if the module is unable
to reconnect to the database, this error will eventually
lead to the error 'Program halted. Database error...'
(see the information that follows).
I receive the error 'Program halted. Database error...'
This error is the result of one of two different problems.
Either one of PageGate's modules has lost contact with
the PageGate database, or there is some corruption in
the PageGate database. If the PageGate module that reports
this error is running on a different computer than where
the PageGate database file resides, chances are you
have a network connectivity problem (possible an intermittent
one). If the PageGate module that reports this error
is running on the same computer as the PageGate database
file, there is most likely corruption in the PageGate
database. Corruption is caused by one of the following
conditions.
1. Abnormally terminating PageGate
- PageGate should ALWAYS be shut down in an orderly
manner. PageGate's administration program and ALL of
the running NotePager Net (GUI) clients should be exited
before shutting down the computer that PageGate runs
on . Next, each of PageGate's modules should be set
to a 'stopped' state (red in PG Monitor). The PageGate
service manager should be stopped by clicking on the
pager icon in the Windows system tray and then choosing
'Quit' or 'Stop' from the popup menu. All of the above
should be done before shutting down or restarting the
computer that PageGate is running on. Not following
these procedures can in some cases cause database corruption.
-All NotePager Net (GUI) client programs should be closed
by choosing 'File' and then 'Exit' from their menus,
or by clicking on the 'X' control on their windows (Note:
when NotePager Net is minimized, it appears as a pager
icon in the Windows system tray. Be sure not to shut
down or restart with is still there). Not following
this procedure can in some cases cause database corruption.
2. Freezing, locking or abnormal shutting down/rebooting,
or other hardware failures
-If any computer that is running ANY part of PageGate
or its GUI client (NotePager Net) freezes, locks up,
reboots, shuts down, catches on fire, etc. without using
normal shutdown procedures, in some cases can cause
database corruption.
3. Operating system errors
-If computers running ANY part of PageGate receive
errors such as: 'the blue screen of death' , general
exception errors, processor exception errors, illegal
instruction errors, pagefault errors, etc. in some cases
PageGate database can become corrupt.
4. Incorrect or out-of date database support files
-PageGate uses the Microsoft Jet database engine (common
with MS Access 97) for data access. If any of the database
engine files are out of date (older versions are buggy),
corruption can appear in the PageGate database. Please
refer to the section 'File version problems' in the
'Troubleshooting' chapter of the PageGate help file
for more details.
5. Bad or out-of date operating system files.
-If PageGate is running on Windows NT, be sure that
the NT Service Pack 5 or later is installed on all computers
that run ANY part of PageGate or the NotePager Net (GUI)
client.
-If PageGate is running on Windows 95 or 98, make sure
ALL computers that run ANY part of PageGate or the NotePager
Net (GUI) client have the current Windows redirector
and OLE files. In particular, there is a serious problem
with the redirector shipped with some versions of Windows
95 that will almost certainly cause database corruption.
Please refer to the section 'File version problems'
in the 'Troubleshooting' chapter of the PageGate help
file for more details.
When I start the PG Admin program, I get the error
'Error 35602 key is not unique in collection...'
PageGate will never allow two recipients (users) with
the same user name. If you are inserting records directly
into the PageGate database by your own means, be sure
that you don't allow duplicates. This is the message
you will get if there is one.
Messages aren't being acknowledged by either the
scheduler or the dialers (Engine)
The scheduler module and the dialer modules currently
only support US date format (mm/dd/yy). Check your date
format setting in the control panel under 'Regional
Settings' to be sure this is the current format.
PageGate stopped sending messages at the end of
the month
The scheduler module and the dialer modules currently
only support US date format (mm/dd/yy). Check your date
format setting in the control panel under 'Regional
Settings' to be sure this is the current format.
Is there any way to have all the modules come up
in a "running" state or startup without showing the
splash screen?
The registered version has two alternate startup programs
that do this.
I hear my modem dial, but no messages are sent.
The detailed log says 'No Carrier or Canceled by User'
1. Make sure you have included any dialing prefixes
needed to get an outside line and dial long distance
if necessary.
2. You may not have the correct phone number for your
paging carrier's terminal. Try dialing the phone number
with a regular phone. If you don't hear a long high
pitched (computer) tone, you have the wrong number.
3. If #2 above does give you a computer tone, you need
an init string (or a different one) to connect to the
paging terminals.
My modem doesn't dial out
Check the detailed log. If it says 'No Dialtone', then
check your phone line connections. Also be sure you
don't require a dialing prefix to obtain an outside
line. If the log says 'Sending Init String' and the
very next line says 'Resetting Modem', this means your
modem is rejecting the 'Init String' you entered for
the carrier being dialed. Check for typing errors in
the init string, or try another string that may work
with your modem.
My modem does not hang up after sending a message.
You may need to use an init string (or a different one)
with your modem.
I have downloaded PageGate and all the buttons are
grayed out, how do I start the engine?
You must have valid information entered into the setup
screen before the buttons will become active.
When I start PageGate, one (or more) of the modules
says that it is already running, but it is not.
PageGate is capable of running it's modules across several
separate systems for a high end configuration. It keeps
track of each separate module with a series of 'locks'.
If you are positive that another copy of a particular
module isn't running, you can clear the lock from within
the PageGate Admin program. Chose 'Clear Locks' from
the 'Tools' menu. Click on the button corresponding
to the module you are having the problem with. Only
modules with active locks are highlighted. After you
click on a button, it should become disabled (grayed-out).
Will PageGate work with a direct connection to the
paging terminal (a direct serial connection, no modem)
?
Yes, the. direct connect works in conjunction with our
existing dialers to allow pages to be sent externally
too.
Can PageGate be modified to adhere to a different
paging protocol, that requires '>' character before
inputting text ?
Yes, please provide details to products@notepage.com
and a price quote for modifications can be provided.
I'm using commandline/ascii interface and I am trying
to send message from notepad.
The notepad program, always appends a .txt extension
to it's files. PageGate requires .asc as the last extension
on the file. Rename the file manually.
Can PageGate's modules be run on separate machines?
Yes, each of PageGate's modules maybe run on a different
system. They must all be networked together. The pgengine.ini
file must be copied onto each machine into the module's
program directory.
Why do I get the message "another copy of .... is
running"?
The state of PageGate's modules are tracked by a locking
mechanism. If any of the modules are terminated abnormally,
the lock may stay in place. In PGAdmin program, under
tools menu choose 'clear locks'.
I am certain that everything is set correctly, but
PageGate won't dial with my modem.
We have seen problems with some of the new faster modems
communicating with the computer at lower baud rates.
Set the carrier's baud rate 19200 and use a modem initialization
string to lock the modem to modem connection speed to
1200 baud.
General Troubleshooting Techniques
The first step to solving problems in PageGate is to
turn on its logging capability. Go to 'Tools' -> 'Setup'
-> 'Admin' (tab). Check both 'Log to Disk' and 'Detailed
Log'. The 'Log to Disk' option enables PageGate's general
(summary) log. It can be viewed by choosing 'Reports'
-> 'View Log' -> 'General'. This log includes information
about all rejected, successful and failed messages.
A separate detailed log is maintained for each dialer
(if multiple dialers are in use). The 'Engine' is also
known as 'Dialer1'. The log for Dialer2 is 'Dialer2'
etc. The detailed logs maintain detailed information
about the conversation of PageGate with your carrier's
paging terminal.
Analyzing these logs can in most cases point to where
the problem resides. As a last resort, a low level modem
monitor tool is also available for the first dialer
(Engine). It shows the actual data being sent and received
by your modem. This option should be used with the aid
of NotePage, Inc. tech support personnel. The
tool is designed for diagnostics purposes only, and
is not meant to be left active for long periods of time.
The modem monitoring tool can be activated by creating
a file named 'modem.dbg' and putting it in the same
directory as the 'pgengine.exe' (found by default in
the PageGate program directory) executable file. The
content of the file is unimportant.
How do I get technical support ?
PageGate technical support is handled through e-mail.
If you have a question that is not answered here e-mail
tech@notepage.net.
If you have a suggestion for future releases or other
wireless products please submit them to development@notepage.net
|