| From: | Andrew Bell |
| Date: | 7 Oct 99 at 14:15:34 |
| Subject: | Re: That Enforcer/Cyberguard Tute :) |
From: Andrew Bell <andrew.ab2000@bigfoot.com>
Hi Dave,
On 05-Oct-99, you wrote:
> Remember that suggestion I had for running a tutorial in CU on how
> to setup Enforcer, Cyberguard and all those other wonderfull tools,
> so that us everyday users could provide the software authors with as
> much helpfull info as possible ?
If you're interested, here's a quick a dirty way to start it up:
run <>nil: ENFORCER DATESTAMP SHOWPC FILE=CON:0/11/640/100/Enforcer_Hits/CLOSE/AUTO
This will make Enforcer sit in the background. When a hit happens,
it'll open up a console window and list the details of each hit. From
there, you can cut and paste the information into an email and send
your bug report to the author.
It might also be a good idea to start SegTracker too (it comes as part
of the Enforcer package). I have the following line in my startup-sequence:
run <>nil: segtracker
SegTracker allows Enforcer to trace and display the name of the executable (or library, device, mcc, etc.) that caused the hit (or more specifically, the segment list of the offending load object).
Regards, Andrew Bell.
+----------------------------------------+
email: mailto:andrew.ab2000@bigfoot.com or
mailto:andrew@ab2000.prestel.co.uk
web: http://www2.prestel.co.uk/ab2000
+----------------------------------------+
My wife said she was going to the gym, or was that to Jim?
--------------------------- ONElist Sponsor ----------------------------
Does Windows keep ""bugging"" you? Can't get that PowerPoint slide to fit?
Get FREE real-time live expert support over the Internet at expertcity.com.
<a href=" http://clickme.onelist.com/ad/expertcity7 ">Click Here</a>
------------------------------------------------------------------------
Quote carefully and read all ADMIN:README mails