When I try to open the find window from within a lister, either from the menu or using ctrl-f, the window takes 20 seconds to open. The CPU usage goes up to 100% usage for the whole time. Does anyone know how to solve this?
I've defragged, checked for registry errors, cleaned up all temp files and even tried disabling the indexing service to no avail.
I've checked the FAQs and tried searching the forums but couldn't find anything so I hope I haven't missed the answer to this problem somewhere.
Win XP Professional
AMD Athlon Processor 3000+
2gb Ram
Seems weird as it's just opening a window and loading some resources out of the language DLL. It might be worth a try to disable any real-time anti-virus/malware scanners or software firewalls (if it's one like Zone Alarm which does a lot more than just acting as a firewall) in case loading the resources out of the language DLL is causing a lengthy scan of the DLL for some reason.
It may also be worth using Process Monitor to see what the Opus process is doing during that delay. That could point us to what's behind the delay.
I'm using DOpus 9.5.1.0 I've tried disabling the firewall and anti-virus with no luck - same results. Process Monitor shows that the time spent is searching through the registry with a mixture of 'Name not found' and 'Success'.
Lots of registry access is usually fine/normal as the registry tends to be very fast, so don't worry about that.
Just had a thought, do you have any unreachable network drives mapped?
The find window and panel may enumerate the list of drive letters when they open and an unreachable drive could cause that kind of delay (as well as delays in other places, sometimes that have no obvious connection to the drive).
Another though: Type /dopuslocaldata into the Opus location field, then rename (or move to a temp folder) find.osd and MRU\find_name.osd and MRU\find_path.osd.
(If that fixes it, please attach the original files to a private message so someone can work out what was causing the slow-down.)
I don't think I have any mapped drives. How can I check this 
It's a bit of a mystery. Thanks for the suggestions anyway.