find the application killer

When my 30-day trial of Injoy Firewall 3.0 ended, the firewall ceased to 
work.  That's fair, but whatever FX Communications put on my system to 
stop 3.0 also prevents 1.4, which I licensed in 2001, from working.  I've 
searched os2.sys and os2ini.sys with Unimaint, the registry with regedit2, 
and the directories with dir /a:s and dir /a:h, but I haven't found 
anything with "injoy" or "fx" in the name. 

Does anyone know how FX is killing my application?

(FX Communications ignored emails, didn't have its chat room up, and 
hasn't had a post on its email forum in years, so I asked BMT Micro, the 
retailer, for help.  BMT promptly emailed FX but without response.)

On Mon, 13 Aug 2007 16:40:38 GMT, Craig Colby <lawcolby@ipns.com> wrote:

> When my 30-day trial of Injoy Firewall 3.0 ended, the firewall ceased to 
> work.  That's fair, but whatever FX Communications put on my system to 
> stop 3.0 also prevents 1.4, which I licensed in 2001, from working.  I've 
> searched os2.sys and os2ini.sys with Unimaint, the registry with regedit2,

> and the directories with dir /a:s and dir /a:h, but I haven't found 
> anything with "injoy" or "fx" in the name. 

If you were designing a copy protection scheme, would you make it so obvious?
Of course not.
RSJ's copy protection scheme didn't have anything relating to their product

Craig Colby wrote:
> When my 30-day trial of Injoy Firewall 3.0 ended, the firewall ceased to 
> work.  That's fair, but whatever FX Communications put on my system to 
> stop 3.0 also prevents 1.4, which I licensed in 2001, from working.  I've 
> searched os2.sys and os2ini.sys with Unimaint, the registry with regedit2,

> and the directories with dir /a:s and dir /a:h, but I haven't found 
> anything with "injoy" or "fx" in the name. 
> 
> Does anyone know how FX is killing my application?
> 
  The firewall product adds a driver to <config.sys>, fxwrap.sys, that
should be removed. And, IIRC, it does things to the network setup. Run
mpts to check that.

-- 
jmm (hyphen) list (at) sohnen-moe (dot) com

In <c1.2b8.36Lhyc$01A@news.ecomstation.com>, on 08/14/07 
     at 10:31 AM, James Moe <jmm-list.AXSPAMECS@sohnen-moe.com> said: >

The firewall product adds a driver to <config.sys>, fxwrap.sys, that
>should be removed. And, IIRC, it does things to the network setup. Run
>mpts to check that.

You might want to check the documentation.  In addition to the above, I
recall that you must run the In-Joy install program and tell it to
uninstall the program.  Because In-Joy installs a network driver, MPTS
will not correctly write protocol.ini until you uninstall the driver with
the In-Joy install program.  My memory of this is dim.  I stopped using
In-Joy in favor of a D-Link router several years ago.  In-Joy is probably
better for an office with 20 computers, which is where I used it, but
overkill for my home systems.

Mike Snyder

I was so sure I had removed fxwrap from both home and office machines, but 
I hadn't.  So I was, like an idiot, trying to run 1.4 on the machine where 
the 3.0 fxwrap was still installed.  All fixed now.  Thanks for the advice.