reinstall the app. sounds like a problem with the scripting plugin…
We’ve already tried that…it didn’t work. We still get the error. One thing that I forgot to mention is that the program actually seems to run just fine. We just clear the error message when it appears, and PS runs.
That sounds like you’ve got the wrong version of the scripting components, or they’ve become damaged.
Chris,
Thanks for your reply.
Wouldn’t reinstalling fix those issues?
We reinstalled the app and updated…still no luck!
How do I repair/replace the "scripting components" (where are they on the computer, how do I find current versions, etc)?
For PS 7 you re-download the scripting plugin.
I don’t recall where the components are located on disk.
I hadn’t thought of that…but it didn’t work either. The user is now telling me that he DID NOT get the error UNTIL he installed the scripting feature update to PS7 (the plot thickens). I have an image of this machine BEFORE any of that was on it, so I could just re-image and get on with my life…but why would the update be the cause of this? Uninstalling the feature doesn’t remove the error either. Is there something that can be changed in the .dll that it refers to?
Well, of course – because the error is IN the scripting plugin for PS 7.
I’m sorry…I must be missing the point here. How did the error get in the plugin? Did it happen (corruption) during the install or is it just something that doesn’t run well on w2k? Can I get rid of the error in the plugin by downloading a different one, or a fix for it…or is this a problem that can’t be worked around in W2k?
The error is that you misinstalled the plugin, or removed some needed component installed by the plugin.
If you remove the plugin, then it won’t complain about missing it’s needed component.
It works fine on Win2K – but you need to make sure it is installed correctly and you aren’t removing parts that it needs.
The fix is to install it correctly.
How much simpler can this explanation get?
Uninstalling doesn’t completely remove everything that it installed in the first place…which is why we continued to get the errors after uninstalling.
However, the user did discover this:
C:\Program Files\Adobe\Photoshop 7.0\Plug-Ins\Adobe Photoshop Only\Automate\ScriptingSupport.8li Anything in this "Automate" directory gets run when you fire up Photoshop. It was pointing to the ExtendScriptIDE.dll
and ExtendScript.dll. The .dll’s must be bad or corrupted because even when they are found it cannot find the entry
point. So all I did was put a tilde after the extension so it would not be run and fired up Photoshop all works well,
now I will remove it, the .8li file that is. For your info these little files with the .8li and similar extensions are like .dll’s
in themselves because they set Photoshop up to use all kinds of filters and features that Photoshop has, so evidently
when you do an uninstall of "Photoshop 7.0 Scripting plug-in v.1.0.2a" it does not remove the "ScriptingSupport.8li" entry.
Now we don’t get the error anymore.
Now…how SIMPLE would I like an explanation to get? I just don’t see how it can be installed incorrectly when the only step in the installation process is clicking on the .EXE file. You click the icon, the installation runs with no user intervention…done. That IS about as simple as it gets! I agree that your explanation is simple…but to a fault…you are not answering my QUESTION in Post #4, which was "How do I repair/replace the scripting components?"
In your Post #7: Well, of course – because the error is IN the scripting plugin for PS 7. Fine, we’ve confirmed that uninstallation does not fix the problem, and that uninstallation/re-installation does not change it either. If the problem is IN the plugin…how do I REPAIR that? Why do we continue to get the message after uninstall?
Hey Chris…My arm hurts when I do this!
Chris says: "Don’t do that!"
Thanks, buddy!!!!
To anybody out there that has seen this before (Photoshop, not arm/pain): Can I find copies of those DLLs and compare them with what is there now? I’m just asking for help! And Chris, if you don’t have an answer to the question…lighten up, take a Midol and don’t bother replying…I wasn’t looking at getting or giving a tongue-lashing when I posted in here.
Greg,
Chris told you how to fix it in Post#5:
"For PS 7 you re-download the scripting plugin."
An uninstall CANNOT remove the scripting plugin as it wasn’t installed by installing Photoshop in the first place, but was installed subsequently. Therefore Photoshop’s uninstall file knows knothing about it.
Len,
In Windows 2000, you can go to Control Panel, and click opn the Add Reomove Programs icon. In that window, it displays all of the programs that you have installed on the machine (including Photoshop plugins). That is where you can uninstall specific plugins,as well as complete programs.
My post explains that we tried uninstalling the plugin…we still got the error…after that, we re-installed the plugin…still got the error…uninstalled the plugin AND PS7, reinstalled PS7 and the plugin…and still got the error AGAIN.
The error message that pops up on the screen explains that the problem is in the entry point in a specific DLL.
How does one repair the entry point problem in the DLL? Does anybody in here have experience with hex editors or the like? We remmed out an 8li file so that it could not be accessed, and the error box stopped. That must be the problem.
If telling me to download and install a file and then telling me that the error is IN the file that I downloaded (back-to-back replies from Chris)…
For PS 7 you re-download the scripting plugin.
Well, of course – because the error is IN the scripting plugin for PS 7.
….that’s not telling me how to fix my problem
Apparently, the answer in here is, download a file that has an error IN it that will not run on your workstation.
If we want to use the scripting component, we need to fix the error, and when I say error…I don’t mean the dialog box that pops up and tells me where the problem is…when I say error, I mean a line of code in the DLL or 8li file where the "error in the entry point" is.
THAT is why I am confused! I ask how to fix it…and we go around in circles. The plugin installs itself…how can I install it incorrectly if it requires no user intervention? We’ve isolated the line of code with the problem, and established the reinstalling doesn’t work. What next? How do I repair the error IN the scripting component? Does this require a registry hack?
This isn’t a forum for calling users "simpletons", it is a place to come for help. If I were really smart, I could figure this one out by myself, but I am a novice at code debugging. I didn’t intend to draw anybody’s ire, and I’m sorry if I offended anybody in the process of asking questions.
Greg,
Something (probably the dll) has become corrupt ON YOUR MACHINE, or DURING the download process. Re-downloading the scripting plugin will get you a GOOD copy of the plugin.
It is NOT a case that the file on the Adobe site is corrupt…
Len,
I have EGG ON MY FACE!!!!
One thousand apologies.
It appears that we did not install the plugin correct from the get-go. Once I read the directions (this is SOOO EMBARASSING!!) I realized that we only ran the original EXE but not the EXE that it had created in another folder.
ALSO, we had saved the download to the server and ran it from there…that causes some problems too.
I will humbly post a copy of this in Chris’s last post.
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." — Rich Cook
Greg <—The bane of Rich Cook’s existence
Chris,
I have EGG ON MY FACE!!!!
One thousand apologies.
It appears that we did not install the plugin correct from the get-go. Once I read the directions (this is SOOO EMBARASSING!!) I realized that we only ran the original EXE but not the EXE that it had created in another folder.
ALSO, we had saved the download to the server and ran it from there…that causes some problems too.
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." — Rich Cook
Greg <—The bane of Rich Cook’s existence
Greg,
I’m just pleased to hear that you have finally got it sorted out…
