J
Jess Morecroft
Hi,
I am having an extremely frustrating and time wasting
problem with Windows Explorer. Often, but not always, when
I click on a mapped network drive or a directory within
that drive, I am forced to wait a full 30-60 seconds for
the drive to expand/display its contents. This problem
NEVER occurs when I access the drive from the command line.
A few things to note:
* My computer is a dual 1000Mhz PIII with 1 GB RAM and
plenty of HD space, so CPU/system speed should not be the
problem.
* I am on a high-speed 100Mbs LAN, so network bandwidth
should not be the problem.
* This didn't always happen...started maybe a month ago. I
have no idea why.
* I want to reiterate, this delay NEVER occurs when
acceessing a mapped drive from the command line.
I can only assume this is a bug with Windows Explorer.
Could anyone with any ideas as to what might be causing
this PLEASE reply. This problem has wasting a great deal
of my time and I am seriously considering ditching Windows
and installing Linux.
Thanks
I am having an extremely frustrating and time wasting
problem with Windows Explorer. Often, but not always, when
I click on a mapped network drive or a directory within
that drive, I am forced to wait a full 30-60 seconds for
the drive to expand/display its contents. This problem
NEVER occurs when I access the drive from the command line.
A few things to note:
* My computer is a dual 1000Mhz PIII with 1 GB RAM and
plenty of HD space, so CPU/system speed should not be the
problem.
* I am on a high-speed 100Mbs LAN, so network bandwidth
should not be the problem.
* This didn't always happen...started maybe a month ago. I
have no idea why.
* I want to reiterate, this delay NEVER occurs when
acceessing a mapped drive from the command line.
I can only assume this is a bug with Windows Explorer.
Could anyone with any ideas as to what might be causing
this PLEASE reply. This problem has wasting a great deal
of my time and I am seriously considering ditching Windows
and installing Linux.
Thanks