Date: Sun, 26 Dec 1999 11:08:31 -0400
From: RUBEN FIGUEROA
To: SHANE CARAVEO
Subject: wcNav & Win95
Newsgroups: win.navigator
Message-ID: <1036425011.34.945879041@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 34

Shane,

Does the Navigator initialize a modem in a different way then another application (like Hyperterminal?).

The reason I ask is that when calling out with the Navigator, it doesn't
seem to use the extra initialization parameters (under Control Panel ->
Modems -> Properties -> Advanced).

The modems in question are USR and they can only connect to my system if
you disable v.90 (which I have the users setup in the Advanced
properties tab), otherwise they only connect at 1200 baud instead of
33.6k.

When they first boot, if the first program they use is Navigator, it
apppears the extra init string is not sent to the modem because it will
not connect at 33.6, only 1200. But if they call out with Hyperterminal
first, and then use the Navigator, the modem is properly initialized
(from the previous Hyperterminal session) and it connects fine a 33.6k.

Any ideas? I'm going to try this with a few other modems to see if its
just the modem, or an actual Navigator issue.

Thanks!

Chris Ross
chris.ross@eshade.com






--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Sun, 26 Dec 1999 19:04:00 -0400
From: RUBEN FIGUEROA
To: CHRIS ROSS
Subject: wcNav & Win95
Newsgroups: win.navigator
Message-ID: <1036425013.34.946224511@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 22

Does the Navigator initialize a modem in a different way then another CR>application (like Hyperterminal?).

Hello Chris. May be wrong about this, but I think that wcNav talks
directly to the modem rather than through Windows like Hyperterminal
does. You can set any special connection strings you need to set inside
wcNav when it initializes the modem.

Go to "View/Options/Devices" Then select which com port your device is
on. Highlight that com port and click on EDIT. Then click on the
Connections Tab. Input any special strings items you need and say OK
back out to the dialing icons. That should have the modems call out
however your special settings are set.

Rick





--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Sun, 26 Dec 1999 19:39:22 -0400
From: RUBEN FIGUEROA
To: CHRIS ROSS
Subject: wcNav & Win95
Newsgroups: win.navigator
Message-ID: <1036425015.34.946224511@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 13

Does the Navigator initialize a modem in a different way then another application (like Hyperterminal?).

The reason I ask is that when calling out with the Navigator, it doesn't seem to use the extra initialization parameters (under Control Panel -> Modems -> Properties -> Advanced).

Since wcNav is a 16-bit application, it doesn't know how to see or use
the settings in your control panel. You can configure the modem in wcNav
by using the configuration settings within wcNav -- it includes a line
for a modem init string (under View, Options, COMx, Edit).
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Wed, 29 Dec 1999 09:21:19 -0400
From: RUBEN FIGUEROA
To: EARL BORAH
Subject: wcNav & Win95
Newsgroups: win.navigator
Message-ID: <1036425025.34.946255162@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 19

Since wcNav is a 16-bit application, it doesn't know how to see or use
the settings in your control panel. You can configure the modem in wcNav
by using the configuration settings within wcNav -- it includes a line
for a modem init string (under View, Options, COMx, Edit).

Somehow managed to miss that, thanks again Earl. Often its the things
that are right in front of your eyes that you can't find :).

Added, it and it works fine now.

For anyone else having troubles getting USR v.90 modems to connect to
your V.34 modem pool, the USR init string to use is: at&fs32=98

Chris


--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Wed, 29 Dec 1999 13:45:10 -0400
From: RUBEN FIGUEROA
To: ALL
Subject: wcNav & Win95
Newsgroups: win.navigator
Message-ID: <1036425029.34.0@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 19

Since wcNav is a 16-bit application, it doesn't know how to see or use the settings in your control panel. You can configure the modem in wcNav by using the configuration settings within wcNav -- it includes a line for a modem init string (under View, Options, COMx, Edit).

Somehow managed to miss that, thanks again Earl. Often its the things
that are right in front of your eyes that you can't find :).

Added, it and it works fine now.

For anyone else having troubles getting USR v.90 modems to connect to
your V.34 modem pool, the USR init string to use is: at&fs32=98

FYI,
ATS32=66 disables v90
ATS32=98 disables x2 & v90

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Thu, 30 Dec 1999 06:37:16 -0400
From: RUBEN FIGUEROA
To: ALL
Subject: wcNav & Win95
Newsgroups: win.navigator
Message-ID: <1036425031.34.0@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 30

FYI,
ATS32=66 disables v90
ATS32=98 disables x2 & v90

Lee,

I finally figured that out. I had a lot of Navigator users with v90
modems that could not get a clean connect over 1200 to our v.34 modem
pool. I was never able to get a straight answer on why, yet a lot of
people were posting they had the same problem.

Everyone blamed it on my Motorola v34 modems.

I whent out and purchased several of the modems that my users had
problems with, in about an hour, I had all the init strings figured out.

For K56flex modems, the string would be:

at&f+ms=11,1

Thanks,

Chris Ross




--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)