|
Hello all,
This is most likely a series of dumb questions, but I'm trying to
implement some policies with my users and am meeting resistance...
(sigh)
Background:
So I have a lot of files in a shared folder on a Windows 2000 Pro
machine (I know- it's not my choice though). My users are connecting
to this folder and mapping the paths via the Set Path gui (File ->
Set Path). Then they run out of change notification handles. But they
don't care, because "the files on the network don't change that
often, so we don't need to know when they change anyway"... Oh! But
now we can't save (delete, load, fwrite, etc) files on the network
share anymore... Or if we do manage to do it, they are corrupted.
(Problem seems to go away when I remove their paths, and re-add them
using addpath and the '-Frozen' option. And thereby gain all of the
change notification handles back.)
Questions:
So first, do the functions that manipulate the files (save, etc) use
change notification handles? It seems like they should... but I can't
find a clear answer.
Is there a way to up (or find) the number of change notification
handles that windows is willing to allocate?
(I know I can change how matlab regards the handles, but that is a
trade-off with speed. My users are adamant about not giving up those
few seconds of speed...)
Is there a way to incorporate something like addpath's '-Frozen'
option into the set path gui? Users are shying away from using the
addpath command when they have this wonderful gui that does
everything for them... (At this point I'm trying to force them to use
a startup.m file that I wrote that adds the paths with the '-Frozen'
option.)
Thanks for the help
-quo
|