Ron:
Based on problems similar to yours that I’ve read about, this may help.
If you upgraded to CS from PS6 or PS7, I’ve read where others were able to restore CS droplet functionality by reinstalling the old version. When you get to the point where the install asks about file associations, choose "no change" since CS associations are in place. Apparently when the old version of PS is uninstalled, something in the registry and/or a needed file or two gets whacked. (I dunno.)
If you installed CS (full version) and did not upgrade, then let’s hope for reinforcements soon.
Hope this helps.
~Danny~
To add to Danny’s sage advice, consider this. I have yet to encounter a situation that would require a droplet, action, or batch operation include File|Open. It adds more opportunity for error than by simply omitting the step. That may have a bearing on what you are experiencing.
When you have a droplet or a batch operation, the droplet and batch dialogs take control, in a sense, of what files the specific action affect. The files that are acted upon and where they are placed after being acted upon is automatically included in the functionality of the Droplet and Batch dialogs.
Therefore, including Open and Close commands in the action itself needs to be carefully controlled for to avoid conflict with what the Droplet or Batch dialog boxes are affecting.
I have always found it much easier to create an action that performs editing operations, without any Open commands, and then letting the Batch or Droplet dialog drive what files are affected. That said, I often include a Save As step because I intend on changing the file format from PSD to say, Tiff.
So in your case, the first steps *I* would perform, is to trim your action to include your editing steps, and maybe a Save As step, if you intend on renaming and/or changing file types. If you include a Save As step, make sure and toggle the dialog to OFF for that particular step in the actions palette. Then create your droplet based on that action.
In the Droplet dialog, it knows that you are going to drop files on it, that’s why there’s no "source" box, like in the Batch dialog. So, simply tell that dialog to run your action, and where to put the files, and optionally if you want a specific naming convention other than the default.
When you drop files on it, the files you chose in explorer (and ONLY those files) should then open in PS, be edited, saved, then close; one by one.
Peace,
Tony
Thanks for responding. My next question. Is this a bug or an expected method?
RSR
In the two other situations I’m aware of where the user was able to use droplets in PS CS prior to removing previous version (PS7) and CS droplet functionality ceased after removing PS7, it’s my opinion the "solution" of having to reinstall a previous version to get the new version to work (again) adds up to a bug.
The circumstances must be unique since this problem hasn’t hit everyone.
Pls. post results of further troubleshooting. It would be great to nail this one down. Include what version of Windows you’re using + any other details you might feel relevant.
~Danny~
Danny,
Thanks for responding. FWIW, I am rebuilding one of my two machines that has CS on it this comming weekend. That will allow for a fresh install of CS without any prior involvement on any past versions, typically 7.0 which was on this machine.
If I’m successful in getting the droplets to run on a virgin installation of CS without the upgrade path, I’ll post it to you.
The new machine will be a P4 3.2 2G RAM, Gigabyte 865PE-8PENXP Mobo. All my other devices will remain the same. 2 ATA-100 80G HDD, 2 Plextor 48X R/RW CDRs
I’ll keep you posted.
Thanks again.
RSR
Is this a bug or an expected method?
Impossible to tell with the information we have atm. Again, if you removed your OPEN commands and it worked, would that equal a bug or a logic conflict? <shrug>
Well here is what I now know. My suspicions are confirmed. There must be a bug in PS/CS droplets when using CS from an upgrade path as opposed to a virgin install.
I rebuilt my office computer this weekend and found that when I installed PS/CS as a fresh install and used an old version only for media verification the droplets worked perfectly.
However, as an upgrade path using PS and only upgrading, droplets will complain and not run.
My guess is that it is a registry problem.
Adobe needs to acknowledge it and fix it.
Ron
Ron:
This is good and bad news… Good in that you confirmed installation of PS CS standard = droplets work OK.
Bad in that we still don’t know the reason "Why," but registry bug would be a good place to look (way beyond me).
On the no-go system:
* You had PS7
* Installed CS upgrade
At that time did droplets not work… or was it after you uninstalled PS7?
Maybe I missed it: What version of Windows are you running?
Thx for the add’l info. I’m guessing Adobe is aware and there’s a fix in the works. Maybe with PS CS SP1 🙂
~Danny~
You are correct. Running XPP, 2GB RAM, yada yada. Had PS7. Did upgrade to CS. Nuked PS7. Droplets stopped. Rebuilt machine w/fresh install of XPP. Installed CS alone. Droplets work.
I never tested droplets before uninstalling PS7, assuming it worked. Silly me!
RSR
Droplets probably worked while PS7 was still installed. In other cases it was the uninstall of PS7 (through Control Panel) that triggered the problems.
XP Pro info helps.
Just to be sure: On the new machine you installed a std. version of CS, right – not the upgrade? (If it was the upgrade, wonder how that worked w/o PS7 installed first.)
~Danny~
Danny,
The install of CS was an upgrade. You don’t need to have a previous version installed when using the upgrade, just the media to verify ownership of a legit version. CS asks for the location of either the program or orginal CD for verification.
RSR
