SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Wed, 7 Nov 2001 18:30:13 PDT
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Non IBM Internet Dialers

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

OK! Now you've confused me. When Linkup.exe opens, it opens as a small
grey box, or dialog. In that dialog is a small rectangular section
entitled, "Dialer". And in that section are 2 option buttons, one for
"IBM Internet" and the other for "Alternate". Now, I assume that's
exactly what it means: it's an option for using the IBM Internet dialer
(the one that came with Warp and whose path name is
C:\TCPIP\BIN\DIALER.EXE), or for using some other dialer. Am I right
here? If I am wrong in my interpretation, I think the Linkup.exe dialog
is poorly worded!

Well, assuming I'm right, how do you configure Linkup.exe to use
another dialer, different than the IBM dialer? When I select the
"Alternate" option another dialog pops up for me to "add" "modify" or
"delete" a dial up connection, or for me to dial, using an existing
setup there. However, it does not seem to work with any dialer. And OK
I've gotten around this problem by using the "IBM Internet" option and
then fooling Linkup.exe into thinking it's using the IBM dialer. But
still, how do you configure Linkup.exe for another dialer?

Although I have not tried the AT&T dialer with any other IPS, it looks
pretty generic. It allows me to test and/or configure the modem and to
enter the addresses of my Internet servers, etc. I assume that I can use
it with Warp and another other provider, as long as I know the info
specific to that provider.

For right now my IBM dialer still works with the AT&T Internet service.
I switched dialers, because a couple of weeks ago I could not get
connected. While troubleshooting the problem with AT&T, they suggested
that I use their dialer and that it might help. It turns out that they
were upgrading their service and the trouble was elsewhere (not in the
dialer).

I don't think I can use a batch or REXX file, at least in the way that
you suggested, with 2 different versions of Linkup.exe. The problem is
that some Warp Internet applications are "hardwired" to Linkup.exe.
C:\TCPIP\BIN\FTPPM.EXE is one such program. When you double click on an
FTP-PM program object (so that you can connect to a particular FTP site
for downloading/uploading files), Linkup.exe is immediately invoked. You
cannot get around it. Linkup.exe in turn calls up the dialer. After you
enter the password and press the "Connect" botton, the dialer calls up
C:\TCPIP\BIN\SLIP.EXE to make the connection to the Internet. After the
connection is made, Linkup.exe allows the FTP-PM program object to
establish the link to the desired FTP site. Therefore as you can see, if
I have 2 versions of Linkup.exe, I've got to change the name of the one
that I want to use to "Linkup.exe" and place it in "C:\TCPIP\BIN\".

HCM
_______________________________________________________________________________________________

Michael Rakijas wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> ** Reply to message from Harry Chris Motin on Tue, 30
> Oct 2001 05:23:11 PDT
>
> > located. Therefore, now when I double-click on any FTP-PM object, it
> > invokes linkup.exe, which in turn invokes the AT&T dialer (that it thinks
> > is the IBM dialer).
>
> So the AT&T dialer is the one that is invoked when it is set up this way.
>
> > When linkup.exe comes up, it has buttons that allow you to "Connect to
> > the
> > Internet", "Not Connect: or "Cancel". It also has 2 option buttons: one
> > for
> > using the IBM Internet dialer, the other for using "Other Dialer". If I
> > select the option for using the IBM dialer (actually, that's what I have
> > now set it to) and then press the "Connect" button everything works,
> > because
> > I fooled it with the dialer.
>
> So, for the most part you can connect as you want with no problem.
>
> >However, if I select the "Other Dialer"
> > option and then press "Connect", a new dialog comes up, allowing me to
> > dial, or add, modify or remove an entry for logging on. That is the
> > process I cannot get to work correctly on linkup.exe. How do you add an
> > entry to linkup.exe allowing you to use it with a dialer other than the
> > IBM dialer?
>
> I guess this is the question that confuses me. Entries are added to linkup but
> you're still using the dialer with the parameters and login sequence you specify
> - it doesn't use a different dialer. So, I presume you mean to find out how to
> connect to ISPs other than AT&T. Since the AT&T dialer doesn't appear to allow
> connection to other ISPs, you need to know how to get the original linkup.exe,
> not the fooled one, to work with AT&T (if that's not right correct me). First
> off, there are two reasons that AT&T distributes or just made their own dialer.
> One is to simply make it easy for their customers to connect to their service.
> So, they hardwired all the connection info so their customers have it easy and
> are not confused. The other is that they are doing something that is not
> standard and they needed to modify the innards of the connection negotiation to
> accommodate it. If it's the former, you should be able to add a connection to
> IBM's linkup.exe that let's you add the phone number and connection info
> required for AT&T. This by itself is not easy because you may have to reverse
> engineer this negotiation/login procedure. The best hope is to contact AT&T's
> tech support and determine what the sequence (for example, login syntax) and
> parameters (for example, VJ compression) they need. It could be much easier if
> you can find other AT&T - OS/2 users who can help solve the problem (try the
> general OS/2 usenet groups). Now, if the reason they have their own custom
> dialer is because they do something non-standard, then I think you're kinda out
> of luck - you're stuck using the AT&T dialer. I presume you're asking because
> you have two ISPs and you'd like to switch between the two and you'd like to use
> one dialer for both (otherwise you would just be happy with your patched setup)?
> Maybe a scheme can be devised whereby you have both dialups (original and
> fooled) under separate names (like linkup.att and linkup.ibm) in the same
> directory as dialup.exe. A simple batch file should be able to execute the one
> command to copy linkup.xxx to linkup.exe depending on which ISP you want to
> connect to.
>
> I'm sorry if I'm on the wrong track here but I hope this helps.
>
> > The only way I can do it now is to trick it, as explained
> > above.
> >
> > HCM
>
> -Rocky
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 07 | November | 2001 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.