Wayne,
This can be caused by corrupt plug-ins, or by other files (not plug-ins) that reside in the plug-ins path.
These can even be pdf manuals etc. PS may have to chew them a lot before it realises they’re not plug-ins.
It can also be caused by proper plug-ins that have links to corrupt plug-in presets/templates.
Rob
Okay, you have me on the right path. I’ve swapped plug-ins in and out and found that two plugins dealing with scanner input are slowing the system. I’ve installed scanner software but have not connected the devices yet so there may be some initialization that needs to be run that will hopefully clear up the problem.
Will post my results.
Thank you,
Wayne
Update: Connecting the scanners to complete driver initialization did not resolve the problem. Even rolling back my changes and removing the Nikon Scan and Epson Scan software did not resolve the slowdown at the PS plugin scan.
I noticed that the Epson software took 4 minutes to load when I ran the app (Epson Control Panel or something like that). This is really strange. I removed the scanner software but that has not resolved the problem. I do have a network HP all-in-one. (OfficeJet 7310xi). Does that have twain drivers? Nothing shows up under scannners in control panel.
This is really weird. My system has a dual-core processor and 4 gig of memory.
Wayne,
Start eliminating by first removing all 3rd party plug-ins to see if it’s a plug-in at all.
Change the printer to some generic thing or a PDF file.
Rob
The specific Plug-ins that cause this are the Automate and the Import/Export.
The Twain Menu build lags when the Import/Export plugin is in the plugins directory.
Any ideas how to resolve this??
AMD Dual Core, WinXP, 4gig ram
Thanks,
Wayne
Change the printer to some generic thing or a PDF file.
Like Rob said, change the default printer to a generic one.
I didn’t see his post when I created my last message.
I’ve eliminated all plugins and found that the Twain and the WIA plugins are the culprits.
I set up a generic printer, set it to default and that doesn’t resolve the issue. The only thing that works is to remove those two adobe plugins.
