Hi,

We have WINDOWS XP OS on my system. We have a problem with auto refresh in
windows explorer.

We have a folder that is mapped to network location. We have this problem
only with the network mapped drive.

As soon as we rename any file, the file is moved to the last in the folder.
We do not want this behavior. The file

should be in the same place where it was before renaming.


For example,

we have the following files in the folder in the same order

abc.pdf
fgh.pdf
zyx.pdf



if we rename the file 'fgh.pdf' as 'fghxyz.pdf' then the order will be

abc.pdf
zyx.pdf
fghxyz.pdf

we do not want this type of behavior. The file should be at the same place
where it was before renaming.

Any ideas to disable this behavior?


Thank you in advance,
Raheem MA

Raheem MA wrote:

> We have WINDOWS XP OS on my system. We have a problem with auto
> refresh in windows explorer. We have a folder that is mapped to
> network location. We have this problem only with the network mapped
> drive. As soon as we rename any file, the file is moved to the last
> in the folder. We do not want this behavior. The file should be in
> the same place where it was before renaming. ... Any ideas to disable
> this behavior?

I suspect the reason for refreshing the file list to show the updated
file but not to refresh the entire list's order as that it would make it
completely impossible for you to select a file if that network resource
was continually getting updated. This list would continuously bounce
around as you and others were creating or renaming files in the same
shared folder. A constantly refreshed list would make it impossible for
you to get the mouse on the filename before it happened to move from an
update (yours or someone else's). Even the auto-refresh that you note
to show the new file can become a problem with the constant refreshes.
Lots of users updating the same shared folder can result in a severe
slowdown of Windows responsiveness (it keeps updating the list for the
file changes in which you may not even be involved).

Mapped drives are fraught with problems, like them getting disconnected
(by the server after an idle timeout and not on your end). I've seen
users write scripts that relied on the connected state of the mapped
drive only to have those scripts fail because the server decided to
disconnect their connection (timeout, priority connects, whatever).
Perhaps you should consider using a UNC path to the networked host's
shared folder. Mapped drives is an old kludge from long ago. It's been
so many years since I bothered with mapped drives that I can't remember
back that many years.

See if editing the following registry key gets rid of the auto-refresh
(net crawling) in Windows Explorer:

Key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
Data item: NoNetCrawling
Data value: 0 for off, 1 for on

Disabling no net crawling means net crawling is enabled (because of the
negative-oriented option). To enable no net crawling (i.e., disable net
crawling), set this to 1.

After finding this registry key and data item in searches at Microsoft
and Google, I also found it at:

http://news.softpedia.com/news/Regis...II-94583.shtml