|
|
Post by michelb on Jun 3, 2018 16:34:43 GMT
Yes, the jpeg files open in the Editor using File>Open.
I have to admit I am baffled and running out of options. You had said earlier, . . .
FYI: I deleted both the Preferences files before reinstalling PSE5 originally. This is a very long shot in the dark. Delete the Organizer Preferences file.
I am going to bring this thread to the attention of Michel B, an Elements guru. Hang in there!
Well, I don't have any useful idea either... Since my PSE5 is no longer installed in my present Win 10, I can only rely on vague memories from the times of Elements Village.
What is still no clear is about the 'version sets' of jpegs and .psd. If you turn your version sets back to individual items, would you be able to open the files from the organizer?
|
|
|
|
Post by Sepiana on Jun 3, 2018 17:58:48 GMT
I have to admit I am baffled and running out of options . . .
This is a very long shot in the dark. Delete the Organizer Preferences file.
I am going to bring this thread to the attention of Michel B, an Elements guru. Hang in there!
Well, I don't have any useful idea either... Since my PSE5 is no longer installed in my present Win 10, I can only rely on vague memories from the times of Elements Village. What is still no clear is about the 'version sets' of jpegs and .psd. If you turn your version sets back to individual items, would you be able to open the files from the organizer?
Michel, thanks for coming to the rescue!
I believe you got something here. We have tested several variables (with no successful results) but we haven't brought the version sets into the troubleshooting. The "nature" of these version sets may indeed explain this scenario.
. . . getting the older files (before 2015) to load into the Editor is still not working. Why would newer photos (2015 and later) open from the Organizer to the Editor, but not the older photos. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 3, 2018 20:27:09 GMT
I'm sorry, I really am. But expecting a roughly 12 year old application to continue to work on a computer is not practical. The ways that things can be broken is off the scale. If newer versions were not available, and this was a critical application, MAYBE it would be worth trouble shooting. In this case, no. Step number one will ALWAYS, ALWAYS, ALWAYS be upgrade to at least a more current version application, if not the MOST current. I hate to be harsh, but sometimes reality bites
|
|
dano
New Forum Member
Posts: 45
|
Post by dano on Jun 4, 2018 0:20:11 GMT
Thank you for trying. In answer to your earlier question, if I separate the version sets neither the jpeg nor the psd will load into the Editor from the Organizer.
Thanks again.
|
|
|
|
Post by BuckSkin on Jun 4, 2018 8:10:44 GMT
I'm sorry, I really am. But expecting a roughly 12 year old application to continue to work on a computer is not practical. The ways that things can be broken is off the scale. If newer versions were not available, and this was a critical application, MAYBE it would be worth trouble shooting. In this case, no. Step number one will ALWAYS, ALWAYS, ALWAYS be upgrade to at least a more current version application, if not the MOST current. I hate to be harsh, but sometimes reality bites In my own experience, it is the "new and improved" stuff that causes all the problems. He is using Windows 7; there is no reason Elements 5 should not work fine so long as he remains with W-7. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 4, 2018 10:17:44 GMT
"He is using Windows 7; there is no reason Elements 5 should not work fine so long as he remains with W-7" This statement is factually wrong
You have a 12 year old program that gets no updates of any kind. You have an operating system that is in extended support. Which means it gets security updates only because it is old and obsolete. Should Microsoft release a patch that replaces lets say a run time library or DLL of some type that breaks a function, you will not get any support from either MS or Adobe. Now, I don't know if anything like that has happened in this case, but I can tell you flat out, no support organization on the planet would waste 5 seconds trying to figure this scenario out. Running applications this old is a recipe for disaster
|
|
|
|
Post by Bailey on Jun 4, 2018 10:48:50 GMT
Hi dano, You have done a number of uninstalls/re-installs of PSE5. Quite often when you unistall an application, references to it might still remain in your OS's registry. Given you can open a psd or jpg in PSE5 directly from your folder by right-clicking the file and then "Open" or "Open with..." but not from the Organiser, suggests there is a miscommunication between the Organiser and the Editor. I'm not an expert on the innards of the Organiser but this miscommunication could be caused by an anomaly in your registry. So as a close to last resort attempt I would suggest you try the following: 1. Backup your PSE catalogue if you haven't got a current backup atm. 2. Unistall PSE from your computer. 3. Create a Windows System Restore Point 4. Use something like Ccleaner to clean your registry 5. Re-install PSE Good luck  ps.......fwiw, I totally agree with swilliams284 regarding the reasons for updating your PSE in the absence of any budgetary constraints. |
|
|
|
Post by Sepiana on Jun 4, 2018 13:34:20 GMT
Before this troubleshooting changes direction into old program vs newer OS, I would like to bring this to the attention of anyone following this thread. It is indeed possible that the OS (Windows 7) is the culprit here; I am not ruling out this possibility. However, we need to keep the following in mind.
- There is plenty of evidence on the Adobe forums of older versions of PSE (all the way back to version 2) working fine on Windows 7 and even Windows 10. - Adobe has provisions in place to address possible compatibility issues when running older versions of PSE on a newer OP. - Users of older PSE versions are not ignored. If you go to the Adobe forums, you will see these users being helped - We have at least one member using a "very old" version of PSE (version 2) on Windows 7. As far as I know, there have been no problems. - We also have members running PSE 6 on Windows 7 and 10. There doesn't seem to be a problem. - I myself have two copies of PSE 7 (Windows 7 and Windows 10). No problems whatsoever!
Therefore, BuckSkin made a valid point.
He is using Windows 7; there is no reason Elements 5 should not work fine
This seems to be also confirmed by Michel. He has hands-on experience of PSE 5 running on a newer Windows version. I believe he can further elaborate on this. Also, he is an ACP on the Adobe forums.
Since my PSE5 is no longer installed in my present Win 10, I can only rely on vague memories from the times of Elements Village.
As a side note -- There are many reports of the problem dano describes, i.e, some files not opening in the Editor when going Organizer>Editor. This is not unheard of. It has been reported on the Adobe forums and I remember it being reported on the now-closed Elements Village forum (in which dano was a member). Most of the time the problem was with PSE itself and was not directly related to the OS.
|
|
|
|
Post by Sepiana on Jun 4, 2018 14:54:30 GMT
. . . getting the older files (before 2015) to load into the Editor is still not working. Why would newer photos (2015 and later) open from the Organizer to the Editor, but not the older photos jpegs with psd version sets - same as the newer files. What is still no clear is about the 'version sets' of jpegs and .psd. If you turn your version sets back to individual items, would you be able to open the files from the organizer? Michel, thanks for coming to the rescue!
I believe you got something here. We have tested several variables (with no successful results) but we haven't brought the version sets into the troubleshooting. The "nature" of these version sets may indeed explain this scenario.
Thank you for trying. In answer to your earlier question, if I separate the version sets neither the jpeg nor the psd will load into the Editor from the Organizer. Thanks again.
dano,
Thanks for reporting the results! One more variable tested. It really helps our troubleshooting.
I am going to ask you to try something else. This may help clarify if the problem is with the Organizer>Editor connection or with the file itself.
1. Open the jpeg file in Microsoft Paint (or in another program). 2. Save your file as jpeg. 3. Next, try opening the file in PSE by doing Organizer>Editor.
Let's see that happens! Post back with the results.
|
|
|
|
Post by Bailey on Jun 4, 2018 23:22:37 GMT
I would have thought that a common sense approach to solving this issue is to first make sure the OS, including the registry, are clean.
Since the OP has said that multiple uninstalls/re-installs have been done it is very probable that references to PSE have remained in the registry. But we don't know for sure until the registry has been cleaned.
I assume that PSE has worked fine after previous re-installs. The fact it isn't now suggests that either something went wrong during the latest re-install or there is a problem with the OS and/or Registry.
It's common sense and something that should be done after every uninstall of any application - to clean and make sure the registry is purged of all references to the uninstalled application. I am not convinced the OP's registry is clean.
If the registry and OS are clean and up to date, as far as possible, then PSE5 should install on Windows 7 without any problems.
So as I mentioned in my previous post, uninstalling PSE and cleaning the registry following the steps I listed should be the next step before re-installing PSE5. If issues persist after the re-install, then you can proceed with troubleshooting knowing that the registry and OS are clean.
At the moment it appears to me this thread is using a scatter gun approach to try to solve the OP's issue with out first establishing a clean registry and OS.
|
|
|
|
Post by Sepiana on Jun 4, 2018 23:55:54 GMT
Just adding a little clarification for the benefit of anyone following this thread.
My previous post was not about uninstalling/cleaning the Registry/reinstalling PSE 5. It directly addressed the issue that was brought up of older PSE versions vs newer OS along with suggestions that dano should upgrade. As you can see, there is plenty of evidence that older PSE versions will work on newer versions of Windows.
www.photoshopelementsandmore.com/post/45629
|
|
|
|
Post by Bailey on Jun 5, 2018 0:19:54 GMT
... Most of the time the problem was with PSE itself and was not directly related to the OS. ... This might be true, but you are then also saying that sometimes it was related to the OS. So I agree 100% with "He is using Windows 7; there is no reason Elements 5 should not work fine so long as he remains with W-7" This statement is factually wrong You have a 12 year old program that gets no updates of any kind. You have an operating system that is in extended support. Which means it gets security updates only because it is old and obsolete. Should Microsoft release a patch that replaces lets say a run time library or DLL of some type that breaks a function, you will not get any support from either MS or Adobe. Now, I don't know if anything like that has happened in this case, but I can tell you flat out, no support organization on the planet would waste 5 seconds trying to figure this scenario out. Running applications this old is a recipe for disaster The next logical step imho is to uninstall PSE, clean the registry, and then re-install PSE using the steps I posted earlier. At the moment, from what I have seen in this thread, the possibility that the problem is with the OS and/or Registry have not been eliminated. This is simple to do, then if issues persist you can proceed with trouble shooting PSE. But, in the absence of budgetary constraints, upgrading PSE is the quickest and easiest solution. |
|
|
|
Post by BuckSkin on Jun 5, 2018 3:53:49 GMT
For what it's worth, for quite some time, I have been using GEEK Uninstaller instead of the Windows tool; GEEK has a step after initial uninstall where it seeks out and cleans up all left-over traces of the uninstalled application.
|
|
|
|
Post by Bailey on Jun 5, 2018 6:29:59 GMT
Hi Buckskin,
Personally, I would not use a 3rd party uninstaller. The reason being is that it might not be up to date with all the Windows Updates that have been released since the last time the 3rd party uninstaller was updated. I doubt any 3rd party uninstaller makers would update their software immediately after each Windows Update is released.
Best practice is to use the Windows Uninstaller since I would think Microsoft would know the structure of its own OS and how works better than any 3rd party software maker.
|
|
|
|
Post by michelb on Jun 5, 2018 7:47:17 GMT
Hi Buckskin,
Personally, I would not use a 3rd party uninstaller. The reason being is that it might not be up to date with all the Windows Updates that have been released since the last time the 3rd party uninstaller was updated. I doubt any 3rd party uninstaller makers would update their software immediately after each Windows Update is released.
Best practice is to use the Windows Uninstaller since I would think Microsoft would know the structure of its own OS and how works better than any 3rd party software maker.
Hi Buckskin and Bailey:
Don't forget that Adobe provides their own uninstaller: It alswo works for Elements as mentioned in 'getting started'. While it is always a good choice to use the Windows uninstaller, there are a number of cases when the Adobe solution is the only one to be effective. And I have seen that several times. The reason is that it will wipe data which are common to other Adobe softwares, not only the one you are targeting.
I also have other ways to uninstall: Ccleaner (not from Adobe), Avast premium... but if they mostly call the Windows uninstalling routines, the result may be just the same.
|
|
