Joseph - Thanks for the info. The program is Norton Personal Firewall
2001 ver 2.5, and the OS is Windows 98, although it is an early
upgrade version to convert 95 to 98. The Norton System Works is also
2001, ver 2001-04 Build 50, and I had run live update on these
programs almost daily. I originally thought that the memwatcher
program was causing the conflict, and even emailed the guy who wrote
the program to see if he had any input on it. (He did not) Anyway, I
have not been using that program since I had the two problems, so
programs. If this is a Symantec problem, they should be made aware of
it, as this type of thing could cause an awful lot of headache to
someone who is not very computer savvy. Until the NPF is removed, you
absolutely cannot get past safe mode in Windows. Again, everything
works fine after you reinstall the firewall, after first deleting it.
A buddy who is much geekier than me told me that the Windows
Protection error indicates that there is a memory problem. I do not
not know much about it myself. I will let you know if I can find out
any more info.
On Wed, 30 Jan 2002 18:36:24 -0500, "Joseph V. Morris"
>Well, I certainly haven't experienced or even heard of anything like this.
>. . . (inline below) . . . .
>| I have run into a Windows boot problem three times in the past 3
>| months which I discovered was being caused by Norton Firewall. The
>| first two times, (2-3 months ago) I was running a small shareware
>| program called memwatcher to free up my ram while burning CDs. Both
>| times, after using this pgrm, I got a "Windows protection error,
>| restart your computer" msg which when rebooting after I was done,
>| would only allow me to go into windows via the safe mode. DELETING
>| Norton Firewall fixed the problem both times. ...
>What's your OS and version of Norton (and is it NPF or NIS)? You don't
>say at the moment. May I suggest you go to www.capimonitor.nl and get
>Albert Janssen's NIS Settings utility? (Works up through NIS/NPF 4.0 and
>all the way back to AG 3.22.xx) This will allow you to document both your
>NIS/NPF settings, your system configuration, and the NIS/NPF files in use.
>Post this and maybe someone can provide some assistance. (You might want
>to do some 'sanitizing' of the output before posting, however, just as a
>generally prudent step.) I used to run some memory clean-up routines, but
>I quit long time ago before I even got to NIS/NPF 3.0/4.0.
>If Brendon doesn't show up on his own in a day or so, I'll point him to
>I assume that, whichever version of NIS/NPF you were running, you'd run
>LiveUpdate (possibly multiple times) and gotten all the relevant updates?
>Have you also done the same thing with Windows Update? (And please tell
>me you're not running Win 9X/ME Lite.)
>| Anyway, upon reinstall, everything worked fine. This morning I
>| them since Cox has switched over to their own servers. Anyway, after
>| taking these programs off, I once again ran into the above mentioned
>| problem. I deleted the Firewall and everything is working fine. Have
>| any of you ever heard of this, or run into it yourself? I have not
>| yet put the firewall back on, and am not sure if I really need it, but
>| I think that something must be amiss in the software for this to keep
>| happening. I also wonder if Symantec would like to know about this.
>Yes, there's obviously some sort of conflict involved here, but I can't
>tell you what it is. Again, I don't use the memory management utilities
>know about it so that Symantec can investigate it.
>[Don't bother trying Symantec tech support; all you'll get from them is
>some non-specific, canned responses that are probably not relevant to your
>problem and that will simply irritate you more.]