kenwolff,
Is the share mapped as a drive letter?
At any rate editing files across a peer to peer network is not recommended. You should copy the file to your local system first.
All my drives are mapped.
I do not understand how you can sell a product with all the capabilities as CS and expect it to be used in an antiquated stand alone environment. Their is no rocket science about supporting network drives. I can understand remote loading as I would agree that is a very poor way of working but what small business or even a home based operation does not take advantage of resources such as network drives file servers and mapping/mounting. I will copy and conform but as a customer I would like to suggest that you think about your position. Products that cost 1 tenth as much support mapping and network drives. I can only guess that this is on purpose.
As network/product architecture goes this is poor.
Again not supporting running CS remotely make a lot of sense and very obvious. But not supporting remote files makes no sense. Adobe is not in the hard disk reseller business are you?
Also. FYI this works fine with 6.0.1.
kenwolff,
Photoshop CS supports working across the network using Version Cue.
Adobe has no problem allowing network drives. The problem may just be with your network. I can open files across the network fine. It still isn’t a good idea. The problem is most likely with with your hardware or network configuration.
What small business or even a home based operation does not take advantage of resources such as network drives file servers and mapping/mounting.
You are still taking advantage of all those things. I am not suggesting this to you because it doesn’t work with Photoshop. I am suggesting it because of the nature of peer to peer networks. Caution should be used any time you read and write files directly through a network.
OK in all fairness I will shutdown my network purge the DHCP tables and try see if that helps.
OK I reset my DHCP tables done a cold start on the router and brought all systems back on line. At first I thought the problem was fixed. But as I began testing in depth I have determined that CS is unstable in this area. Sometime it works and others don’t. If I have the folder path already set in CS in open file it will work with now problem but if I back out and go to another folder the problems re occurs. I have don the same testing with 601 under the same conditions and have never had a failure.
I run PS CS on Win2K, 1GB RDRAM and store all images on a Linksys NAS and I’ve never had a problem editing large (180 MB images) over the fast Ethernet wire. Files open and save with nary a whimper.
ABC
Photoshop opens files using the standard 2K/XP open dialogs. The only switch we made was to move to the Wide (Unicode) versions of those dialogs. Photoshop isn’t doing *anything* to either enable or disable access to the network. Access to the network is completely provided by the OS at that point. Check to make sure you don’t have bizarre or unexpected characters in the share name. Do you have an earlier version of Photoshop installed? If so, you may want to go hunt down and rename/remove psicon.dll.
Also see if Norton isn’t causing problems (Norton tools are always suspect).
-Scott
Same problem. One thing that maybe a factor to the flakeyness of Photoshop/Windows 2000 combo is the path depth. I have a mapped network drive and we still have to go down 5-6 levels into the folder to save the file. So, depth of file structure?
