Page 1 of 1

RegisterShellEvent on network drive problem

Posted: Fri Apr 27, 2007 12:01 pm
by Leander van Eck
Hi,

I'm experiencing some problem when using Registershellevent on a network drive to monitor seItemCreated events (other events may be problematic as well, but i have not tested those).

Sometimes the notifications stop coming through. Resetting the registershellevent seems to be the only solution when this happens.
I've found that the FindFirstChangeNotification API has a similar problem.

When switching to a local drive everything works perfectly.

I'm using MadShell 1.3p from Madcollection 2.5.2.1
OS: Windows XP Professional

Is this a known issue in MadShell. I really need to be able to monitor network folders and the only other solution i have is to check continually using a timer.

Thanks in advance,
Leander

Posted: Wed May 02, 2007 7:40 pm
by madshi
If the FindFirstFileNotification stuff stops working after a while, too, the problem is probably somewhere in the OS itself. So I fear there's not much I can do to fix this.

How often does this problem occur? Would it help if you used a timer not to poll directory changes but to reset the shell event stuff? Maybe once every 10 minutes or something like that?

Posted: Tue May 15, 2007 7:36 am
by Leander van Eck
The problem might occur after the first shell event, or it may not happen for another 100 shell events. Generating network activity after a shell notification seems to reduce the occurence.

I agree that the problem most likely exists within the OS.

A timer that starts after a notification and resets the shell event might be a usefull solution.

Thanks.