Len,
Thanks for the info but it did not help. I can run a filemon and a regmon and they both do not show any access denied logs, but still it takes a good while to open images.
Joe,
The other thing to try is making sure the default windows printer is a local rather than a network printer
Sorry but none of these help the issue. I think it must have somthing to do with a GPO.
There are a couple of active threads complaining about this same problem. There are two symptoms: One is slow file opening and the other is slow processing to the point of lock-up when you use the "file browser" feature. So some complain about the file browser and some complain about slow file opening, but I think it is the same issue.
It only seems to be a problem with certain network setups, as when I move my laptop from work to home (where I have about 4 computers networked through a simple DSL router with a switch in it) there is no problem. The corporate network environment is somehow setup in a way that makes the issue appear.
It would be nice if Adobe could clarify or fix this one.
Since nobody has provided enough information for Adobe to reproduce the problem – Adobe can’t do anything about it.
That is understandable. My company would only have a few users who consider Photoshop mission critical so it would never be a high enough priority to get their attention to work with Adobe.
I wonder what kind of information Adobe would need and how one would get it to them?
Enough information to reproduce the problem – and post it here or tell it to technical support.
Well, I posted some details on the other thread:
Leland McArthy "Files open very slowly when connected to network" 1/7/04 9:08pm </cgi-bin/webx?13/7>
Seems like if they could intercept the data going out over the network during the processes in question and see what it is, they might be able to figure out what aspect of the code is involved. I am not technical enough to do that, but if hackers can log keystrokes or glean credit card info, it must be possible with the right tools.
Guess they have to reproduce the problem first.
Yes, the problem has to be reproduced first.
And we can’t reproduce it.
Most of these "problems" are configuration issues on the user’s machine or third party software interferring with normal operation.
