| Alfred,
You can try the following. No guarantees though:
SETHOST.PIF can be modified to launch any DOS application or batch file.
Hubwatch assumes it is invoking SETHOST.EXE, which it passes the following
command string:
telnet: <ip address>
where the ip address is determined by the Hubwatch management code.
If SETHOST.PIF is set up to invoke a different terminal application, the app
will likely want only the ip address, so the trick lies in stripping off
the "telnet:" argument. This can be done by indirectly launching the terminal
app via a batch file. Here's how:
1) Make a backup of SETHOST.PIF. Modifications described below must be made
on the "live" version.
2) Create a batch file (e.g. LAUNCHER.BAT) which invokes your terminal app
as follows:
MYAPP.EXE %2
where MYAPP.EXE is a DOS terminal application. (The app must be a DOS app;
Windows apps cannot be launched via a PIF file.) The %2 argument will be
replaced by the ip address passed by Hubwatch. You should provide any
additional arguments required by the terminal app. If necessary, provide
the full path to the terminal app. You may want to directly invoke the
batch file from the command line to see if it works. Pass a dummy value
for argument 1.
3) Use the Windows PIF editor (PIFEDIT.EXE) to change the program filename
in SETHOST.PIF from SETHOST.EXE to the name of your batch file, e.g.:
Program filename: LAUNCHER.BAT
4) Save the modified SETHOST.PIF file.
The SETHOST.PIF and LAUNCHER.BAT files should both reside in the same
directory as Hubwatch.
Note that the DOS box window title will still say "telnet". Hubwatch uses
this window title to keep track of the DOS box.
Steve
HUBwatch
|