This is great, Oz! Can I post it to Tips & Tricks?
So long as it can be still discussed there, sure - it would be good to hear of any problems with it when anyone interested has had a chance to use it and report back in this thread. Maybe leave it here for a week or so, then move it? I leave it to your inestimable judgement!
Will do. Again, thanks, Oz.
Thanks for the utility. I have downloaded it, but have not unzipped the folder.
Is the utility specific for Premiere Elements 8? Any comments about it's action on other versions of Premiere Elements also installed on the same computer?
Great work Ozpeter! Thanks for taking the time to put together PrE 8 Runner and for posting it. I vote with Steve, that this should be in the Tips & Tricks area, so it will remaine for perpetuity - or until the next forum change!
Just downloaded this little gem, unzipped it, held my breath - and EXEc it! .. Runs like a dream. Im using VISTA Home Premium, and the proglet runs just as Ozpeter explained. It will certainly do the trick until (hopefully!) Adobe comes up with an official solution. BTW, I still havn't heard anything from Adobe, and I'm certainly not holding my breath! Many thanks Ozpeter.
Oz, I've taken the liberty of adding a copy of your post to our FAQs -- crediting you, of course.
I'm also downloading your program for my computer. If this does everything it apparently does, it is too good not to share!
Thanks for letting me know it works for you Kermit-999 - I couldn't test it under Vista so I'm glad to hear that it does.
ATR, the little program will only work in relation to PE8 and other versions will be completely unaffected by it (on the assumption that you don't have multiple versions actually open and running at the same time, which is unlikely!).
Works great for me under XP too. Thanks again, Oz!
Thanks for the follow up.
I will give it a try later this evening and will report back.
That's a nice utility but it's just masking a larger problem. I can always go into the task manager and end the process before I start it up again, but that's not the major issue.
Will Adobe address the real problem? Why won't Premiere Elements 8.0 exit properly on my machine, and many others?
If that's not a rhetorical question, you should ask Adobe directly. There's no one from Adobe on this forum.
You can contact Adobe by clicking on the Contact link at the very top of this page.
I have tried contacting Adobe, and I still am trying to get some sense out of them concerning PrE8. It's a lot of money to pay out for a broken program!
The only response I have had so far is an incident number and being referred to document cpsid_51427 (which deals with freezes etc) - Still waiting for some kind of response spacifically regarding the failure to close cleanly
Hi, Here's an update of replies I have received from Adobe Support regarding this problem PrE8 has EXITing cleanly..
The first response was to follow the instructions on Doc cpsid_51427 .. This doc refers to installation problems, so not really relevant
Second response was to follow these steps:-
1 Remove the Application
2 Run CS4 CLEAN SCRIPT, use doc kb406241
3 Restart and reinstall.
Tried this, but the application never found anything amiss, and being it is used for CS4, and PREMIER is not even mentioned, I'm not surprised !
Third response, and I quote:-
"Contact Microsoft, because if it is still showing in Task Manager then it is an operating system issue, because the Task Manager is related to the OS, so please contact Microsoft"
Now tell me if I'm wrong, but to me, that reply smacks of "Tough Luck, go annoy someone else with your woes, we've got yer money - not interested anymore !!!"
Yes that's the moronic response I got when I did an customer portal bug report on it. This is a microsoft issue, we can't fix it. I assume they have contacted microsoft and eventually it will be addressed, but my confidence in Adobe is further weakened by this issue.
The program does not work on my Vista 64-bit machine, because Premiere Elements 8 installs itself to the "Program Files (x86)" directory, not to the regular "Program Files" directory as this program looks for. Fix?
Why does yours do this, Jim? It doesn't do this by default, and it does give you the option of choosing where it installs.
Not sure. I am attaching a screen shot of the warning..
Almost all 32 bit apps, which means almost every app you install, place themselves in the Program Files(x86) directory by default, including Adobe. It has no effect on it running or not. I use Adobe 8 with Vista 64 and it works fine out of that directory, except for the no exit issue which would happen regardless of the install directory.
There are virtually no apps that don't install themselves in Program Files(x86) by default on 64 bit systems.
The shortcuts Adobe creates also have Program Files(x86) as the path they point to. Are you sure the install completed and how are you trying to start up the program?
Thanks for the tip. I read it only after I sent along the link to the file.
Have you found a fix for PE8 shutting down shortly after it opens? It's driving me crazy. Thanks for the runner exe.
I really can not understand their logic. It is showing in Task Manager because the process (Adobe's exe) is still running and using the CPU. I know this because it causes a slowdown on my system as well. They are either assuming that Task Manager is reporting a ghost so it is an OS system, or they are claiming that they are making a call to a Microsoft function in a redistributable .dll or a function in a compile time library written by Microsoft, and that function is not operating as specified by Microsoft.
I know that it isn't a ghost report; the process is running. If it is a failure in a .dll or library, Adobe will still have to issue an update to us after reporting it to Microsoft and MS putting out a developer's update. We can not report it to Microsoft because we do not know what functions they are calling.
It really sounds like their application is not distributing the exit call to all of its processes. Without a design map and the code, it is all conjecture and I really shouldn't be guessing at what I really don't know.
Based on how many folks all see this, I can't imagine how this slipped through testing. Oh well, it did and most organizations have one slip through every now and then. The real important thing is how Adobe responds to the discovery. I personally would be happier with a "We have been notified of this issue and our developers are working to recreate it and then correct any problems we identify." It sounds like tech support has been outsourced and is too far removed from the situation to really respond with anything more than deflection. I have run into this with Digital River and their overseas call center. They could answer by the script, but they really could not get to the folks who could provide answers or solutions. This kind of support is what turned me away from a large scale installation of Adobe consumer applications. I have found better stability and support with the professional line of products.
I am looking forward to fix for this and any other issues. PE is fun to play with.
I have posted this on another thread aswell today. Thought of just checking if this helps.
Do you guys all have something in common here ? Because it seems that the NVIDIA cards and PREE does not gel well.
Have you guys checked disabling one of the display drivers (preferably the NVIDIA ones) and check if this problem vanishes.
Offcourse, this is not a fix, because there could be other display related downgrading of the whole system, but aleast it would be good to learn that the problem is common only for guys who have NVIDIA sitting on the system
I played with my NVIDIA drivers a bit, to no avail. Really, I don't
even want to go there. We shouldn't have to. This is just poor code
and a lousy, buggy program by Adobe, and they need to fix it and not
throw out 'ideas' to try. It is well documented that the previous
version of the program had none of these bugs.
Its really frustating when you are using a tool and are unable to achieve the results that you expect from that tool. Its perfectly normal to let your anger out and express them on the forum, so that the guys from the development or tech support team alteast know about the issue.
This issue is reported many times and people have tried different worarounds to this and I am sure that they must be looking at this.
In the forum, we try to help each other by trying out different 'ideas' that other experienced members of the forum have. You said you played with the NVIDIA drivers, but didnt mention that if disabling the drivers help?
If you say that it does NOT help - it becomes easy for others to understand that this has got nothin to do with disabling the NVIDIA drivers - so that we dont waste further time in this direction.
Hello guys. From the desktop I right clicked and opened properties/settings tab/advanced/troubleshoot and slid the Hardware Acceleration leftwards to NONE; and the PE8 editor no longer shuts down. In fact, I am now able to import movie clips with no problem. I may slide the bar one or two steps back to the right in order to see what my max acceleration is while maintaining the functionality of PE8.
Thanks for the suggestion EMI.
Jack G. Stevenson
I'm new here and I have nothing to say but thank you to everyone for your contributions. This forum has done more for me to get PE8 working than anything adobe has done. I can't wait to download Runner...Oz..brilliant...seriously, thank you so much!
I loaded Runner and it works perfectly to start PE8 but I didn't get the message after close that it would shut down the processes. I didn't open a project though, just started and closed.
If anyone is still using the little utility I provided, do check out this link
where you'll find the proper fix for the problem.
Meanwhile, I see there were a couple of questions about my utility in this thread but I'm afraid I'm not able to provide any useful suggestions in response - but hopefully the proper fix will work for you.
Hello Everyone! My CPU was pegged at 50 and my memory was stuck well above 400,000k every time I exited. I found that the PE8 Runner utility worked well for me, but I also stumbled upon a solution that seems to fix the issue. It seems that the Welcome Screen may be causing the program to hang in memory upon exit, at least on my installation.
If I run "Adobe Premiere Elements.exe" rather than"Adobe Premiere Elements 8.0.exe" it will bypass the Welcome Screen and shut down properly, utilizing the expected few seconds to clean up files. I went through and changed all my shortcuts to use the new path. Both .exe files are found in the same program directory. For me it's "C:\Program Files\Adobe\Adobe Premiere Elements 8.0".
Does anyone see any problems with this method?
Thank you for the input. My mind is a bit cloudy, but it seems that many wanted to bypass the Splash/Welcome Screen in PrE 7 also, though for different reasons. IIRC, their method was almost identical to yours. Going back, I do not recall any issues with that method.
Now, it seems that PrE 8's Welcome Screen has taken on some additional duties and responsibilites, and maybe these changes are causing issues?
Again, thank you for reporting, and good luck,
As reported some time ago first by Ozpeter and elaborated on myself and others, the Adobe Premiere Elements 8.0 shortcut that is placed on the Desktop as part of the program's installation process targets the Adobe Premiere Elements 8.0.exe which has the program opening with the Welcome Screen. However, if you create a Desktop shortcut that targets the Adobe Premiere Elements.exe (which sits right next to the Adobe Premiere Element 8.0.exe in the Premiere Elements 8.0 program files), you can bypass the Welcome Screen. I have been running my Premiere Elements 8.0 successfully via the bypassing the Welcome Screen route for quite some time now.
I suspect that Adobe designers had a "method behind the madness" for directing us to the Welcome screen route. Check out the Premiere Elements 8.0 Help PDF accessed under the program's Help Menu:
Adobe Premiere Elements Workspace
About the Workspace
"DISABLE TRACKING OF INFORMATION
The Welcome screen by default records and relays some usage information to Adobe to assist in the improvement of the Welcome screen experience".
The writeup goes on to describe how to disable the "tracking of information" via Run/regedit.exe. I have done that as well as use the Adobe Premiere Elements.exe as the target for the Premiere Elements 8.0 Desktop shortcut.
Therefore, based on my experiences, so far I do not see any problems with the choice that both of us has made in setting up our workflow.
Thanks for "reporting from the trenches." Many should benefit from this knowledge.
So, PrE 8 really does "call home," and in a bigger way? Guess that if ET can do it, so can PrE 8.
I recall the furor, when Adobe CS introduced Activation, and the program wanted to connect with Adobe to verify the validity of the Activation. Wow, were those ever heated days? This was also about the time that Adobe put in code that would prevent anyone from scanning and opening an image of any US currency. One would get an error screen telling them that this was illegal and would not be allowed. I had to do all sorts of workarounds for a client, who had a purchased (full repro-rights) image of a $1,000,000 bill. Though it was not real, of course, PS wanted to keep us from doing any work on this image. Seems that she was putting her corporate logo around the seal, or similar. Whew, I expected the FBI to knock on my door any day. Maybe that was what all of the black helicopters over my house were all about... ?
Is there a version oft PE8 Runner
for Windows 7?