Windows Explorer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I was wondering if anyone is having a problem with explorer using up alot of
resources? Whenever I am copying or moving files it takes way too long
and no matter what I do it doesn't seem to help the problem
I know its not my computer because I have over a gig of memory
 
I know what you mean - I'm plagued by "are you sure you want to copy this"
and "are you absolutely sure you want to copy this" messages, transferring
takes ages for me too even over a direct LAN connection. The memory shoots
up, and only shoots back down again when you close both Explorer windows.

Sorry Heather - I presume this is just because Vista's not completely
optimised yet for performance :o(

--
Zack Whittaker
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!

--: Original message follows :--
 
I have :o|

--
Zack Whittaker
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!

--: Original message follows :--
 
I disabled that already because i couldnt stand all those messages. What I
need to know is what i can do to stop explorer from freezing all the time
just because i am copying files or moving them its making me crazy.
 
I already disabled the UAC a while ago what i wanted to know was how to stop
explorer from freezing everytime i try to either move or copy files its
making me crazy.
 
What build are you running? There was an earlier build (5381) I think that
had an explorer error that was caused by the indexing service. People
either had to disable indexing or use a US Locale to make it stop.
 
Back
Top