G
Guest
Guest
Archived from groups: microsoft.public.windowsxp.basics,microsoft.public.windowsxp.customize,microsoft.public.windowsxp.general (More info?)
There's a 'feature' of the common dialogue open and save windows that remembers the last path you used even after re-starting the
parent application, I need to be able to disable this feature.
Whilst this is a quite handy feature most of the time, we tend to open a lot of files over many networked machines that don't stay
on the network for very long (they get built and tested here then shipped off after a few days) so it's quite often the case that
the previous path is on a machine that's not even plugged in any more. In these cases Windows still tries to contact these machines
and can take anywhere between 1 and 3 minutes to eventually time out and bring up the dialogue with a default path.
These machines are all on the local area network so even setting the timeout to something quite small, say 10 seconds, would be
better than nothing but ideally I'd just like to disable this feature altogether, any ideas?
Cheers,
Mike
P.s. Sorry if this is on the wrong group(s), if there's a more appropriate group then please let me know.
- Microsoft Visual Basic MVP -
E-Mail: EDais@mvps.org
WWW: Http://www.mvps.org/EDais/
There's a 'feature' of the common dialogue open and save windows that remembers the last path you used even after re-starting the
parent application, I need to be able to disable this feature.
Whilst this is a quite handy feature most of the time, we tend to open a lot of files over many networked machines that don't stay
on the network for very long (they get built and tested here then shipped off after a few days) so it's quite often the case that
the previous path is on a machine that's not even plugged in any more. In these cases Windows still tries to contact these machines
and can take anywhere between 1 and 3 minutes to eventually time out and bring up the dialogue with a default path.
These machines are all on the local area network so even setting the timeout to something quite small, say 10 seconds, would be
better than nothing but ideally I'd just like to disable this feature altogether, any ideas?
Cheers,
Mike
P.s. Sorry if this is on the wrong group(s), if there's a more appropriate group then please let me know.
- Microsoft Visual Basic MVP -
E-Mail: EDais@mvps.org
WWW: Http://www.mvps.org/EDais/