For what it is worth.
Yes, the same Injoy can be used to dial your ISP, for
email and web browsing, and
even a manual run of Irex while you are there. :)
Again, I'd have to look at it, but I think all you
need to do is leave off
that command line param, and it will simply load up and wait for you to choose a connection and tell it to dial. This is how it behaves when I want to use it.
Be assured that one installation of Injoy can be used
by both bbs events for
Irex, and manually by you.
The version of Injoy I have aguments my broadband cable connection. In fact, before I got the cable modem, Injoy was a far better deal than Dial Other Internet Providers, (DOIP) that came with OS/2. Once connected, Injoy will provide all the port service, at least mine wiil, for everthing else I toss against it. For example, the in-town site has all the nailed up operations against the cable modem, including TelNet BBS, FTP server and so on, as and when I need them.
However, cable service is not available at a remote site that I also need linked to things. So .. in the rural location Injoy comes back as a dial-in to
the same I/P provider I host from - you're given the dial up access with the Cable service for one dial-in as well.
Getting Injoy to do that does require some thinking about the setup routine. For example, as part of the setup routine, you can prepare an on-board slaved list of applications that you wish Injoy to fire off after it connects! More than one, as needed. That's similar to what you find with the command line deal being espoused here. You'll likely find that there is a learning script needed or you have to fool with for your provider. PPP,CHAP chalenges, all that stuff. However, Injoy creates a debugging log for your use in discussing what is going wrong if it is.
As well, Injoy has a number of options to optimize the achieved connection as to I/O. It's set up as a wizard sort of deal for two basi formats, as I recall
from memory. You may find, for example, that changing the defauit MRU setting Injoy starts with may be required to work best with your provider - I think mine is still set on 1492 .. Whatever. There are tools and output data to let
you watch the connect rates and transfers to let you fiddle with stuff until you get it just right as needed.
There is a way, if my memory is correct, to fudge with Injoy and let it issue traffic requests in an oblique fashion at timed intervals. That will keep you connected as long as they will let you hold the connection. In my case, during
some contest work to proof things, I've been hard against the I/P for 12 hours at a crack - no problems.
From that point, it's down hill. At the remote site, via both TC/PIP and TELNET, over the one line in use, I wind up able to monitor, on a contiuous basis, the Finland DX cluster on TCPIP, as well as FTP whatever in and out of the site. At the same time ZOC via the Injoy game will let me have access to the TelNet side of the DX spotting cluster spotting game, as well as TelNet access back in town to my cable hosted interface too.
I do not call my own BBS system POTS any longer if connected to an IP somehow.
No LD anywhere with Injoy to an IP that is local. And by the way,ZOC is a JEWEL of a program. Its scripting language can let you do a number of interesting things with it that can be merged with other server-side hosts. For example, cluster spots it simultaneously logs to a disk file can be snifffed, autospoken by a speech talker directly over the air as a repeater operation! Service! Service! Grin...
Of course it is all limited to what the phone line will carry at a given site, but it is darned reliable. I've paid for Injoy and also the so-called professional version which costs a few bucks more. Renewals are freer for longer, plus that version, if my memory is correct, lets you use Injoy for more
than just POTS phone connects. It can do the job via other interfaces as well.
My notes on Fixpack faiiures indicate that this is an ongoing spat between Injoy and the IBM crew past Fixpack 12 for Warp 4.0. It results in corruption problems of the system on the second dial-in and connect from a given session if I am correct. Injoy has posted a version of the product that attempts to fix it, per the notes. However, they claim solidly that the problem is in IBM's camp and TC/PIP 4.3 that is involved with Warp 4.5 in the upgrade version.. Per the posts I have, I haven't confirmed whether this hassel is resolved or not. I think it requires careful coordination with a non-regular TC/PIP fix for 4.3 and all this, somehow. Maybe most folks aren't getting all the exact version number files together to get rid of the problem.
I was happy enough with Injoy to go ahead and pay for the Injoy Firewall as well... Little by little I'm learning .. This game is far bigger than I am!
Mike @ 117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)