home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
dialp132.zip
/
dialup132.doc
< prev
next >
Wrap
Text File
|
2000-06-18
|
10KB
|
215 lines
DialUp: v1.32
DialUp is a package of REXX routines designed to interface with the InJoy
dialer from F/X Communications and/or the AT&T Global Network TCP/IP
Dialer. Its functions are:
1. Start the dialer if not already started.
2. Dial a predetermined host.
3. Disconnect from the host.
4. Launch an object after connection (ala LINKUP.EXE)
5. Create a launch object
DialUp is no-charge shareware, copyrighted 1999, 2000 by Charles H.
McKinnis and can be registered with an e-mail to mckinnis@attglobal.net.
If you don't register, don't expect me to reply to any queries.
DialUp Installation:
1. Install the WPTools package from Hank Kelder or use the required
module packaged with DialUp. You can find the package on Hobbes
(ftp://hobbes.nmsu.edu/pub/os2/util/system/wptool29.zip). If
wptools.dll is not in your LIBPATH, the install.exe will unzip the
wptools.zip file that contains only the wptools.dll.
2. Install the VRexx package from IBM Employee written software or use
the required modules packaged with DialUp. You can find the package
on Hobbes (ftp://hobbes.nmsu.edu/pub/os2/dev/rexx/vrexx.zip). If
vrexx.exe is not in your PATH, or if vrexx.dll or devbase.dll are
not in your LIBPATH, the install.exe will unzip the missing modules
from the vrexx.zip file that contains the required VRexx modules.
3. Install the FM/2 Utilities package from Mark Kimes or use the
required module (killpid.exe) packaged with DialUp. You can find the
package on Hobbes (ftp://hobbes.nmsu.edu/pub/os2/util/browser/fm2utils.zip).
4. Unzip dialup132.zip to a desired directory (recomment x:\dialup).
There is no requirement that this directory be referenced in any
path definition in config.sys. There are no changes required to
any system configuration files.
5. Go to the installation directory and run install.exe.
The install will create a DialUp folder on your desktop that contains
DialUp Utility object, the DialUp Launch Object folder, and the DialUp
Target Object folder.
The VRexx files will be unzipped into the DialUp directory if
required. If all of the VRexx modules are already present, the
install.exe will delete the vrexx.zip file.
The wptools.dll will be unzipped into the DialUp directory if
required. If WPTools is already installed and wptools.dll is in
your LIBPATH, the install.exe will delete the wptools.zip file.
At the completion of the install, the DialUp Utility will start.
Select the "Setup all parameters" option. You will be asked to
navigate to the InJoy object. You will then be asked to pick the
configuration file to be used. You are now ready to set up the
InJoy exits required to keep track of the status of the InJoy dialer.
InJoy Setup:
1. Now you need to set up InJoy to notify DialUp of its status. Open
the InJoy dialer. Select "Misc. opt.".
Select "Autostarting modules". Set the following:
a. Path and filename - drive:\path\dialup.exe
b. Parameters - /online
c. Working directory - drive:\path
d. Start at - host connect
e. Stop at - discon.(after) and InJoy exit
f. Start minimized - on
g. Select "Add"
h. Path and filename - drive:\path\dialup.exe
i. Parameters - /offline
j. Working directory - drive:\path
k. Start at - discon.(after) and InJoy exit
l. Select "Add"
You should now have dialup.exe set up to be called twice, after
connect and after hangup. Select "Ok". Select "ESC=Go back".
2. Using the AT&T Global Network TCP/IP Dialer requires no special
setup procedures in the dialer properties.
Setting up launch objects:
1. Now you are ready to set up whatever applications you want to use
with DialUp.
Some e-mail clients have a dialer exit that can be used. If this is
your case, you can set that exit to "x:\path\dialup.exe /dial". If
your mailer client provides an exit for hanging up, you can set it
to "x:\path\dialup.exe /disc" to trigger a disconnect.
I have found that some e-mail clients, even though they provide a
dialer exit, do not wait for the connection properly and will post
an error message concerning a bad POP server connection. If that is
your case, I suggest that you use the /CREATE function described
below to get the connection made before invoking the e-mail client.
2. DialUp can be used in a similar manner to that of the "LINKUP.EXE"
furnished with Warp 4. However, LINKUP.EXE always expected to be
passed the program name to be started and the working directory for
that program. DialUp wants the actual object name (in the form
"<object>"). No parameters or working directory are accepted
because they wil be the parameters currently associated with the
object.
3. You can run the DialUp Utility and select the 'Create an object to
connect and launch an object id' parameter to build launch objects.
The launch object will always be created in the "DialUp Launch
Objects" sub-folder of the "DialUp" folder.
Because IBM has managed to completely screw up the Object Rexx WPS
interface, the process of setting an icon for the DialUp launch
object is rather crude. URL launch objects will have the standard
URL icon. If an icon can be extracted for the target, it will be
used. Otherwise, the folder containing the target object and the
settings for the launch object will be opened so that you can drag
and drop the target object icon to the icon page of the launch object.
If the object you select to launch does not have a proper object id,
it will be assigned a unique id. You will find another folder,
"DialUp Target Objects" inside of the "DialUp" folder. This is where
I deposit my real URL objects (see note).
Note: If you use the AWGet package for retrieving URL files, make
sure to stop the AWGet dameon before creating an object of a
bookmark. Otherwise, AWGet will grab it and run off and hide.
4. Changes
1999.09.02 - JoyUp098.Zip
1) Initial posting to Hobbes
1999.09.04 - JoyUp099.Zip
1) Added icon capability for URL objects
1999.09.09 - JoyUp100.Zip
1) Quit trying to work with the icons for abstract objects. May try
again when the Object Rexx WPS interface gets fixed.
2) All objects will now be given proper object ids before JoyUp
uses them.
3) Added tests to make sure that RxExtras and WPTools are installed
and usable.
1999.09.11 - JoyUp101.Zip
1) Simplified setup and initialization by basing the InJoy
information on the information in the InJoy object rather than
storing it in JOYUP.INI.
1999.09.30 - JoyUp110.Zip
1) The application has been redesigned.
2) The setup, create, and query functions have been re-written in
VRexx to provide a graphical interface and moved into a separate
routine called JoyUpU.Cmd. The VRexx modules (from IBM Employee
written software) are included.
3) The status of the InJoy dialer connection is now maintained via a
Rexx queue and the logic for setting, deleting and querying the
queue has been moved into a separate routine called JoyUpQ.Cmd
(which is why the InJoy dialer autostart functions have been
changed).
4) Added a routine called JoyUpK.Cmd to kill the VRexx functions if
they should become "stuck".
1999.12.20 - JoyUp111.Zip
1) The install.exe will selectively install the tools necessary for
its own operation.
2) The joyupq.cmd has been incorporated back into joyup.cmd.
3) The install.cmd, joyup.cmd, and joyupu.cmd are now install.exe,
joyup.exe, and joyupu.exe. They were converted using the
REXX2EXE tool. There are still 2 routines called joyup.cmd
and joyupu.cmd that will call the new executables.
2000.02.03 - JoyUp111.Zip
1) Removed the joyup.cmd and joyupu.cmd routines. Some mailers,
like Polarbar, do not handle anything except exe modules.
2) Updated the documentation.
2000.02.11 - JoyUp12.Zip
1) Removed the generated exe files. All code now runs as Rexx
command routines. See "Setting up launch objects:" if your
application only supports exe files.
2) Added the optional "/Wait" parameter to the joyup.exe. This will
cause joyup.cmd to wait for the InJoy dialer to connect before
launching the application object. Useful when an application is
set up to communicate with the Internet when it is opened.
3) Modified code to eliminate the propagation of queues. Moved the
InJoy interface code to get quicker response to InJoy calls made
to JoyUp.
4) Removed the usage of RxExtras.
5) Added killpid.exe from FM/2 Utilities package.
2000.03.16 - JoyUp121.Zip
1) All routines have been converted to exe files using REXX2EXE.
2) Add the /H:injoy_host parameter to eliminate retaining the InJoy
host name in the joyup.ini file.
3) Fixed a minor bug that prevented object ids with spaces or
forward slashes from processing properly.
4) Added the rxslibp.cmd routine to the package. This Rexx routine
will determine if a module is in your libpath and return the fully
qualified name of the module if found or a blank if not.
2000.05.01 - DialUp13.Zip
1) JoyUp became DialUp and now supports the AT&T Global Network
TCP/IP Dialer as well as the InJoy Dialer.
2000.06.03 - DialUp131.Zip
1) Corrected an error in assigning object ids to objects in dialupu.
2000.06.21 - DialUp132.Zip
1) The /WAIT parameter is now the standard behavior. A target object
will not be launched until the dialer has connected.