ERROR Watching Mapped drive

  • Thread starter Thread starter deepak
  • Start date Start date
D

deepak

Hi There,

i have an application which watches mapped drive events using
FilsSystem Watcher .
the filters i am using are these : NotifyFilters.FileName |
NotifyFilters.Attributes | NotifyFilters.Size |
NotifyFilters.LastWrite

now when there are too many file creation in the mapped drive , i am
getting an error from filesystem watcher
which states like this :"the network bios command limit has been
reached " .

i increased the watcher internal buffer size but ,it did not help .

i searched on the web to find one KB article() but wasn't useful.

everything i am doing is on windows-xp machines .

any help/comments/suggestion are highly appreciated .

Hope am Clear

Regards
Dee
 
Hi Mike ,

Thanks for our response, probably thats the case ,when i host my app
in windows-xp ,i am getting the error("Network bois ......").
i tried hosting my app in windows server 2k3 ,now that error ("Network
bios .. ..") is eliminated. but i am getting one more error now ,it
states "Too many changes to drive V: ". i understand this is because
there is too many file creates and deletes happening .
i have set InternalBufferSize to 64kb and i guess i cannot go beyond
64kb .

could you suggest/comment any ways in which i can go away with this
problem.

Thanks for your time

Cheers
Dee
 
The error "Too many changes to drive V: " is eliminated buy increasing
the buffer size .
increasing buffer only works when the watcher is on win 2k3
machine.

mike ,can you point me to the documentation of win-xp which mentions
about limitation with the network bios command limits.
 
Back
Top