Opening or saving files causes HANG on newly installed XP

[Guest Gareth]

I recently re-installed while using 'complete format' windows xp pro eng and

my computer. One of the reasons I re-installed was that whenever I used the

standard file dialog box to save or open a file and try to navigate to other

than the default folder, it would often hang with 'not responding' in the

window caption. Eventually, I would get to the required folder.

 

The problem returned after all my applications were installed.

 

The problem is extremely annoying and a friend with similar applications

installed has exactly the same problem.

 

'Total Commander' has no problem navigating the file system. Presumably it

uses other modules to perform the navigations.

 

Does anyone have a solution?

[Guest Pegasus \(MVP\)]

Re: Opening or saving files causes HANG on newly installed XP

 

 

"Gareth" <battygar@gmail.com> wrote in message

news:u3cWd9ygIHA.1184@TK2MSFTNGP04.phx.gbl...

>I recently re-installed while using 'complete format' windows xp pro eng

>and my computer. One of the reasons I re-installed was that whenever I used

>the standard file dialog box to save or open a file and try to navigate to

>other than the default folder, it would often hang with 'not responding' in

>the window caption. Eventually, I would get to the required folder.

>

> The problem returned after all my applications were installed.

>

> The problem is extremely annoying and a friend with similar applications

> installed has exactly the same problem.

>

> 'Total Commander' has no problem navigating the file system. Presumably it

> uses other modules to perform the navigations.

>

> Does anyone have a solution?

 

The answer to your question lies most likely in your remark "The

problem returned after all my applications were installed." One

of your applicatioins is probably misbehaving and you're the best

person to know which one it is. When you installed the applications

one by one, the one you installed before the problem returned

would be the culprit.

 

You could try System Restore to turn the wheel back a few

days.

[Guest Gareth]

Re: Opening or saving files causes HANG on newly installed XP

 

Thank you for the effort Pegasus but it is really not possible to uninstall

all the apps that I have. We are talking about VS 2005 and 2008 etc. Each of

these is a 'really big one'.

 

I simply cannot believe that others do not have the same problem.

 

When I googled the problem, there are lots of links to sites with similar

problems BUT no real solution.

 

I'll be a little more specific. When the 'Save in' combo is activated, it

disappears and returns about 2 mins later and sometimes the 'save'

navigation can proceed quickly and sometimes each navigation is 2 mins long.

 

Garry

 

"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

news:uVh0Sc2gIHA.1208@TK2MSFTNGP05.phx.gbl...

>

> "Gareth" <battygar@gmail.com> wrote in message

> news:u3cWd9ygIHA.1184@TK2MSFTNGP04.phx.gbl...

>>I recently re-installed while using 'complete format' windows xp pro eng

>>and my computer. One of the reasons I re-installed was that whenever I

>>used the standard file dialog box to save or open a file and try to

>>navigate to other than the default folder, it would often hang with 'not

>>responding' in the window caption. Eventually, I would get to the required

>>folder.

>>

>> The problem returned after all my applications were installed.

>>

>> The problem is extremely annoying and a friend with similar applications

>> installed has exactly the same problem.

>>

>> 'Total Commander' has no problem navigating the file system. Presumably

>> it uses other modules to perform the navigations.

>>

>> Does anyone have a solution?

>

> The answer to your question lies most likely in your remark "The

> problem returned after all my applications were installed." One

> of your applicatioins is probably misbehaving and you're the best

> person to know which one it is. When you installed the applications

> one by one, the one you installed before the problem returned

> would be the culprit.

>

> You could try System Restore to turn the wheel back a few

> days.

>