In general I have discovered that if the machine is working fine before you
install your filter and only
Falls over when your filter is in the chain then the big finger normally
points at you!
If it is a commercial product is causing a problem then you generally have
no alternative but to work
Around the problem if possible.
When you say “causes network operation problems”, what exactly do you mean
by this?
Ben Curley
Data Encryption Systems Ltd
-----Original Message-----
From: Ratmil Torres [mailto:xxxxx@seg.inf.cu]
Sent: 06 March 2003 13:47
To: File Systems Developers
Subject: [ntfsd] Re: How to hook to LanmanRedirector before Norton SymEvent
You have to be sure your driver loads before Norton’s. But if there is a
compatibiliy problem either you or Norton are doing something wrong.
----- Original Message -----
From: “Philip Hong”
To: “File Systems Developers”
Sent: Thursday, March 06, 2003 8:07 AM
Subject: [ntfsd] How to hook to LanmanRedirector before Norton SymEvent
> Hi all,
>
> I have a driver that must hook to “\Device\LanmanRedirector” after
> running an driver loading application. However, after installing
> Norton AntiVirus, I found that my driver no longer can attach to
> LanmanRedirector directly. Instead, it attaches to SymEvent, which
> causes network operation problems.
>
> Since all drivers, i.e. my driver and SymEvent are essential and must
> be servicing. Would anybody tells me the way to ensure the following
> order ?
>
> \Device\LanmanRedirector
> |
> Attached: \FileSystem\My Driver
> |
> Attached: \Driver\SymEvent
>
> Thanks in advance.
>
> – Philip
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@seg.inf.cu To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
—
You are currently subscribed to ntfsd as: xxxxx@des.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com