fileman
21st September 2002, 20:37
Hallo,
did anybody notice this problem, or is it my machine/installation?
When handling big files (for example VOBs or 1.4 gb-AVIs) with the explorer, the machine behaves like a 386. Always when it fetches the file information (size, ...) which is shown in the status bar, as done every time you select a file, there is some time you have to wait (the bigger the file, the longer the waiting).
Also, when you try to rename/move/... the file, and you start this task during this waiting time, explorer reports that the file is in use by another program. If you wait until the information is shown in the status bar after selecting the file, renaming/moving/... can be done without any problem. So I guess the explorer itself opens the file and blocks it for any other access while fetching the file information.
Why does this info fetching take so long? What's responsible for this? Is it NTFS, any drivers or what? I can't remember this has always been the case, but perhaps I didn't notice it, because I never dealt with such huge files in the past.
My system configuration is as follows:
Athlon XP 1800+, 512 MB DDR-RAM, 45+123 GB HDD (other components don't matter, I think... (but who knows, I'm using windows) ;-)
Regards, fileman.
did anybody notice this problem, or is it my machine/installation?
When handling big files (for example VOBs or 1.4 gb-AVIs) with the explorer, the machine behaves like a 386. Always when it fetches the file information (size, ...) which is shown in the status bar, as done every time you select a file, there is some time you have to wait (the bigger the file, the longer the waiting).
Also, when you try to rename/move/... the file, and you start this task during this waiting time, explorer reports that the file is in use by another program. If you wait until the information is shown in the status bar after selecting the file, renaming/moving/... can be done without any problem. So I guess the explorer itself opens the file and blocks it for any other access while fetching the file information.
Why does this info fetching take so long? What's responsible for this? Is it NTFS, any drivers or what? I can't remember this has always been the case, but perhaps I didn't notice it, because I never dealt with such huge files in the past.
My system configuration is as follows:
Athlon XP 1800+, 512 MB DDR-RAM, 45+123 GB HDD (other components don't matter, I think... (but who knows, I'm using windows) ;-)
Regards, fileman.