2009 B2-B4: Address Bar Dosent Update Explorer Pane
-
I have been unable to reproduce this when typing an entry - however, I did get the same result (no update) when choosing Desktop from the address dropdown.
Unfortuantely, like mwb1100, it is not reliably reproducible for me. I get the problem sporadically ( twice in about 15 attempts); also it does not persevere when trying different entries/selections from list :confused:
-
Unfortuantely, like mwb1100, it is not reliably reproducible for me.
If I left the impression that this was difficult to repro, I’m sorry - I have no problems reproducing the problem. It happens for me each and every time, exactly the same as MarcFou describes. My only ‘contribution’ to this thread is that it happens for me on WinXP SP2 so it’s not a Vista specific problem.
-
Sadly I can reproduce this 100 times out of 100. In previous betas it would sometimes work. The only way it will work for me is to do the following…
-Type C:\ (for example)
-Hit Enter key
-Click the address box to select the text C:
-Press Enter again
-Files pane then updatesOtherwise type+enter does nothing. The only other info I can add is settings.
I do see one discrepency here. From the UI on the toolbar, under Folders I have “Explorer Display Style” NOT Explorer with Folders. But in the Preferences, View section it says: Viewing Style = Explorer style (with folders).
Could it be as simple as a conflict of settings? See attached.
Edit: Just realized I am using PC Tools ThreatFire (threatfire.com) and it installs a keyboard driver to monitor/detect key logging. Could the driver be the cause?


-
everything is fine there… can you send us your settings again at support at conexware.com?
thanks
-
(reg file)
-
Done. Hopefully it may provide some clues.
-
The issue remains in Beta 5.
-
I tried PA 2009 Beta 4 on another Win XP SP2 machine, and the problem does not occur on it. I don’t know what might be responsible for the different behavior between the two machines.
-
I mailed spwolf a movie how to reproduce the problem. So I guess this gets fixed.
-
Problem resolved in RC 5 :D





