Premiere Elements 2.0 SERIOUS ERROR

I have a 3 minute project that I'm trying to burn to disc. When I hit the burn icon, a msg pops up that there has been a serious error and the program must close and it asks me to report the serious error to microsoft. I've restarted the computer each time and no luck.
What next?!

The first thing to do is to check your Assets. What are they? What is the CODEC used to encode them? (Check with G-Spot, www.headbands.com/gspot). Are there any still images? What is their size?
Message such as this, are usually caused by one of three things:
1.) Assets
2.) System
3.) Operator Error
Besides your Assets, give some information about your system.
Have you tried to Burn to a folder, and then use a program like ImgBurn (freeware CD/DVD burning application)?
The answers to these questions will help other possibly help you. Unfortunately, most error messages are barely helpful, if at all. That is true for most NLEs and most DVD authoring apps.
Hunt

Similar Messages

  • Im using premiere element 9 getting serious error occurred force to close can't open project crashes

    Im using Mac and recently when openning projects in premiere 9 i get serious error occurred force close. It was working and my computer crashed and new hardware was installed. I was able to do one project before this started. I can edit and complete my video but cant burn or reopen the project without get the error message and closes. How do i repair?

    What was it that Meatload said, "two out of three ain't bad... ?"
    Glad that two Projects burned properly.
    Before you trash that one Project, I would do this little exercise:
    Move all of your Assets (your Media files) to another folder, so that PrE cannot find them. That part is much easier, if you set up your Project in its own folder structure, with sub-folders containing all media used.
    Then Open that Project. In the loading process, you should get a dialog screen, asking "Where is file ______?" At that point, navigate to the new location, that you Moved the files to. PrE will then re-link to that first file, and then survey the PREL (Project) file, and re-link to every file used in the Project. If the media is in several sub-folders, you will need to repeat that navigation to the respective sub-folder.
    Then, test the Project to see if that re-linking has "fixed" things.
    If not, then the Project is probably corrupt.
    Good luck, and let us know how it goes.
    Hunt

  • When Exporting "Adobe Premiere Pro sorry, A serious Error has accord that requires....."

    Since the new update when Exporting I get this message ""Adobe Premiere Pro sorry, A serious Error has accord that requires....." I've tried to reinstall the software on both computer without any luck. Please Help!

    Premiere worked before.
    I’m not using any third party effects or codecs.
    MAC
    Processor  3.4 GHz Intel Core i7
    Memory  24 GB 1600 MHz DDR3
    Graphics  NVIDIA GeForce GTX 680MX 2048 MB
    Software  OS X 10.9.1 (13B42)
    Adobe Premiere Pro CC Version 7.2.1(4)
    When I press EXPORT I get this message "Adobe Premiere Pro sorry, A serious Error has accord that requires....."

  • Premiere elements has encountered an error.  [..\..\Src\Core\Preferences.cpp-338] (while launching video editor)

    Getting an error while launching Video Editor (either New project or Existing project). However i can launch "Organizer" with no issue.
    windows 7 -64bit Core i7
    Premiere elements has encountered an error.  [..\..\Src\Core\Preferences.cpp-338]
    then
    -Runtime Error!  Program C:\Program Files|A...  This application has requested the Runtime to terminate it in an unusual way.  Please contact the applications suport team for more information.
    then
    -Adobe Premiere Elements 11 has stopped working  A problem caused the program to stop working correctly, please close the program.

    School Board
    Thanks for the replies.
    I was almost sure the uninstall, ccleaner, reinstall would resolve the problem. But, onward....
    Are you working from a school or company network or from an individual home computer?
    From your ID and some comments, I think school network.
    I suspect the issue is more than resetting the preferences, but let us give that a try to rule it out (or in).
    Local Disk C
    Users
    Owner
    AppData
    Roaming
    Adobe
    Premiere Elements
    11.0
    and in the 11.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then
    you delete the whole 11.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working
    with Folder Option Show Hidden Files, Folders, and Drives enabled so that you can see the complete path cited.
    Is the Owner designation in the above path named correctly?
    Also, look at disabling the SLCache Folder if you find one as described for 12 in the following
    ATR Premiere Elements Troubleshooting: PE12: Premiere Elements 12 Editor Will Not Open
    To be continued....
    ATR

  • Premiere elements has encountered an error (preferences.cpp-353)

    Hi guys, trying to get Adobe premiere elements working on a windows domain, will only run for local administrator, logged onto machine locally, not even a full domain administrator.
    Any ideas?
    Any help would be very very appreciated.

    Hi ATR,
    I really appreciate you taking the time to reply, sorry for the lack of info in my previous message was pulling hairs out when i wrote that!! I really do appreciate any help you could give with this at all.
    Here are the answers to those questions.
    1. What version of Premiere Elements are you using and on what computer operating system is it running?
         It is the latest version of Premiere Elements 13, we are trying to get it to install on Win 7 32bit.
    2. Are you running the program from a User Account with Administrative Privileges and have you applied Run As
    Administrator to the program's desktop icon?
         They are domain based machines, if you log on as local administrator on the machine the software will run, but if you log on as a domain user or even full domain admin it still doesn't load properly we get the error "Premiere Elements has encountered an error. [..\..\Src\Core\Preferences.cpp -353]
    3. Is this a "it worked before but not now" or "it never worked before" issue?
         It is new software we have never ran on our network before.
    4. Have you deleted the Adobe Premiere Elements Prefs file or the whole Folder in which it exists?
         I did a search of the entire C drive of the machines for the preferences file and couldn't find it to try deleting it.    
    5. Do you have the latest version of QuickTime installed on the computer with Premiere Elements?
         Yes i have tried installing the new version of quicktime on the machines, even though the version we already had installed met the recommendations.
    6. Does the problem exist with or without the antivirus and firewall(s) disabled?
         Firewall is disabled across the domain, i've tried disabling the AV and it didn't make any difference.
    7. Are you using the program with a mouse or one of those pen and tablet devices?
         Just a normal mouse and keyboard.

  • Premiere Elements has encountered an error (Preferences.cpp-347)

    Hi all
    System: Windows 7 x64, Adobe Premier Elements 12.0
    We are getting the following error when attempting to start a new project under one specific user.
    Premiere Elements has encountered an error [..\..\Src\Core\Preferences.cpp-347]
    I have read in other threads network installations can cause this.
    This is a network installations and we do redirect my documents to a network drive.
    I have tested this under Administrator and test accounts where my documents were not redirected and it started a new project fine.
    Other threads have mentioned that there is a possible fix and to contact customer support. I have tried to do this by logging in to this Adobe account but the only option was to Ask the Community.
    Has anybody been provided with the solution to this?
    I have tried the following but to no avail:
    -deleting the preferences file
    -deleting the 12.0 folder
    -adding access rights of the user to all adobe premiere related folders
    -looking through the registry for elements related entries and looking for related paths
    Thanks in advance

    I have searched the net for trying to find a solution but cant find any. Im sure Adobe must find a solution to this problem.

  • I have just got this error on my Windows 8.1 PC in Adobe Premiere Elements 13:"Premiere Elements has encountered an error" -- [c:\adobe\pre\main\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]

    I have just got this error on my Windows 8.1 PC in Adobe Premiere Elements 13:"Premiere Elements has encountered an error" --> [c:\adobe\pre\main\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]. I have found different solution on how to fix it, but it's still hard to find where to change "," to ".". When I try to change my .prel file to a .xml it all shows symbols, letters and numbers, not only numbers like a have seen others. I have a LLOOONNNGGG movie to fix. Can anyone help?

    Hoerup
    Thanks for the update. Sorry that the news was not better.
    There are several cases of keyframe error 142 being reporting, some for version 12 and some for version 13.
    In your case, we may be able to get some help from Adobe via its Adobe Chat since you have purchased, registered, latest version
    Premiere Elements.13. Let us see what Adobe Chat can do for us. Please click on the following link
    Contact Customer Care
    Premiere Elements
    Premiere Elements
    Adobe ID, Signing In
    Adobe ID, Sign In, Account Help
    Chat Panel
    If the link does not hold its set, then you will need to navigate to Chat Panel using the above links.
    As of a moment ago, the Chat Panel was seen to be active. The titles are not ideal, but they do lead
    to an active Chat Panel. I am hoping that the representative whom you reach can answer your question more
    fully or transfer you to an Adobe group which can.
    We will be watching for further developments.
    Best wishes
    ATR

  • "Font Capture: Adobe Premiere Elements.exe - Bad Image" error message

    I purchased Premiere Elements 11 last year and it has been working fine.  But just put in a new HDD into my laptop and now I can't open Premiere.  I uninstalled / reinstalled the program a couple times today with no improvement.  The problem is always the same: once I reinstal the program and open it, I get this error message::
    C:\Windows\system32\QUARTZ.dll is either not designed to run on Windows or it contains an error.  Try installing the program again using the original instalation media or contact your system administrator or the software vendor for support
    I tried moving this QUARTZ.dll file, but it says I require permission from TrustedInstaller in order to move this file... whatever that means.
    I am running a Dell Studio XPS 1640.  Windows 7 Ultimate 64-bit.
    Please help because I need to get these videos processed!
    Thanks so much,
    Janeen

    I still have this problem, unfortunately...  I can't open Premiere Elements 11 because this error keeps preventing the program.  The program will start to load in the purple box, and the error box will come up, saying it is a "Bad Image" and there's a problem with the system32\QUARTZ.dll file.  I can't get past that step in opening Premiere Elements 11.
    I have followed most the directions on the above article, and connected articles related to it.
    I installed updated drivers and Bios, even though they were the same as what my laptop already had.  I also downloaded the latest version of DirectX and that didn't change anything either.   I tried to extract just the QUARTZ.dll file from it, but never was given an option to chose where to save the download or pull files out from it. 
    Can someone please share any suggestions to battle this problem?  I can't use my Premiere Elements program, which is so frustrating.  Everything else on the computer is working normally.
    Thanks for your ideas and suggestions.
    Janeen

  • Premiere Elements has encountered an error: MasterClipFactory

    The windows version of my plug-in (developed using AE CS3 SDK) works fine in AE CS4, CS3 7.0, 6.5 and 6.0 as well as Premiere Pro CS4,CS3, 2.0, 1.5 and 1.0 and in Premiere Elements 3 and 4.
    In Premiere Elements 8 I get the error...
    Premiere Elements has encountered an error. [..\..Src\Clip\MasterClipFactory.cpp-361]
    when I move the mouse over my plug-in icon int he Edit panel.
    This happens before my GlobalSetup procedure is called, so I can't debug.
    Is it a PIPL problem? Any ideas?

    This happens with the Skeleton Effect example too. There must be something about After Effect filters that Premiere Elements doesn't like.

  • Premiere Elements has encountered an error - CPP-610

    Hi,
    I have a member of staff using Premiere Elements 8 that crashes the moment they select Timeline within a project.
    The error is as follows;
    Premiere Elements has encountered an error. ..\..\SRC\WIN\WINPATHUTILS.CPP-610
    Once you OK this the program exits.
    Elements is fully updated running on Windows XP SP3
    Could anyone suggest how to decode the error, it seems pretty specific but I can't pin down where/why it is failing.
    Thanks in advance

    Specific error codes mean little in this case. But a good computer tune-up can make a big difference.
    First, manually go to Windows Update and select Custom to ensure you have even the non-critical updates for your operating system. Then go to Apple.com and get the latest version of Quicktime, per the program's requirements.
    After that, I always recommend that you run Advanced System Care to clean up and defrag your system. (The program is free -- but pay attention to the installation screens or you'll also add an annoying toolbar to your browser.)
    http://www.iobit.com/advancedsystemcareper.html
    After that, go to the Help menu on Premiere Elements (or any Adobe program, even Acrobat Reader) and select Check for Updates. This will update all of the Adobe programs on your computer and add the 8.01 update for Premiere Elements.
    If you are still having problems, list your hardware specs, including the speed of your processor, how much RAM you have and how much free space is on your C drive. To run this program you'll need at least 20-30 gigs of free, clean, defragmented space on your C drive as well as additional space on your second or external drive for your media files.
    Also, list the model of camcorder your video is coming from and which project settings you selected when you set up your Premiere Elements project.

  • (..\..\Src\Timecode.ccp-995) Premiere Elements has encountered an error

    When I try to import a DV movie from my camera the Following error occurs: >Premiere Elements has encountered an error: (..\..\Src\Timecode.ccp-995)> I have no idea how to fix it, please help??

    It could be any of a number of things.
    Are you capturing from a miniDV camcorder over a FireWire connection?
    What are your system specs? What operating system are you running? Have you gone to Windows Update and manually downloaded even the non-critical updates? Have you got the latest version of Quicktime?
    Which version of Premiere Elements are you using? If version 8, do you have the latest update, per the announcement at the top of this forum?

  • Premiere Elements 11 start up error - Windows 7, 64 bit

    Premiere Elements 11 was working fine until 1 week ago.  Now I get an error on start up that says "Display Driver Intel HD Graphics is out of date. . . ". Then it loads very slowly. Once loaded, Premiere does not show the video though appears to be running it.  I checked the Display Driver and it is up to date - latest version. I "restored" PC back to a date when Premiere was working well to no avail.  I then unintstalled and re-installed Premiere 11 and still get the error. I have run diagnositics on the PC - no problems reported with display or any other function.  I also have Premiere 9 and tried it - it runs just fine - no display problems at all.  Where should I look next? Any suggestions?

    In cases, such as these, I try to look for variables, in hopes of explaining the changes.
    As most users have their OS Updates set to fully automatic, those are installed, fairly frequently (depending on OS, and version), and usually without any knowledge of the user.
    However, the failures of video drivers seem to come after several OS Updates have been issued. MS just issued many for XP-Pro and Win7 (do not know about Win8), and we then see an increase in video driver issues. For users who employ their particular Adobe programs often, most video driver issues come immediately after Windows Updates (though not ALL Windows Updates).
    I have all of my OS Updates set to notify me of availability, and then I can manually download, and manually install what I want. Taking my nVidia Quadro FX-4500 as one example, the only times that I have needed to update its video driver, have come immediately after Windows Updates - and I mean immediately. As I download and install my Windows Updates manually, I am ready for the possibility of video driver issues - most times, things work just fine afterwards, but not always. When some changes occur with the Windows Updates, a video driver update has, almost always, fixed them.
    Why does this happen? I cannot tell you, but then not all Windows Updates are created equally, such as the recent one, that broke WMV display.
    Do the video card/chip mfgrs. think that there is a need to update the video drivers? Observing AMD/ATI, and especially nVidia, it appears so, with a new driver coming about once per month. There ARE often features that get added, or tweaked, and especially when the card/chip is used in extreme gaming, but why every month? I would assert that it is to accompany changes in the OS with the Windows Updates, but we will need an engineer from nVidia to comment directly. As an aside, Matrox is a great card/chip mfgr. Their cards were cutting edge, and were the first to allow for multiple monitors. However, their concentration was on business machines, and not so much on Adobe products. They were slow to update their drivers, and Adobe users were often left out in the cold, for up to 6 mos. Matrox cards fell out of favor, due to the lack of video driver updates, with Adobe users. Business users, who only needed to use spreadsheets over 4 monitors, or were using software, that did not need to interface so closely with the video driver, were unaffected - not so for those in the 3D, or video-editing community.
    If one were to try to draw coorelations between Windows Updates and video driver compatibility, I think that they could look to this, and a few other Adobe product forums for data. Now, most computer users do not have programs, that interface with the video driver much at all. They would never notice anything amiss. However, if one is an extreme gamer, or they work with programs, such as heavy-duty 3D, CAD *, or several Adobe products, like Premiere Elements & Pro, After Effects, Photoshop (PsE ?) or Encore, they encounter problems with video display, and often immediately after a Windows Update. In nearly every case, updating the video driver fixes things. Circumstantial evidence? Sure, but it is so common, as to almost be a "given."
    Why does one not see so many video driver issues on a Mac? The video drivers, in most cases, ARE updated, when one updates their OS, as the OS updates, also update the video driver. The exceptions come from some of the recent nVidia CUDA cards, for the Mac, that will usually require a CUDA driver update - and that fixes things.
    Just some observations,
    Hunt
    * Most serious CAD applications will require a special CAD video driver, and not the general ones that most folk use. In the CAD community, the CAD drivers are also released quite often, to fix changes in the OS.

  • Adobe Premiere Elements 7 With Worthless Error Messages.

    I have been a programmer since 1984, and if I saw a programmer in my team wrote these worthless error messages, I would go into my office and kill myself.
    I Googled them, and I found them discussed; but the responses were of no use to me, mostly.
    1. The error message I got that brought me to the edge of a cliff is: "Sorry, a serious error has occurred that require Adobe Premiere Elements to shutdown. We will attempt to save your current project."
    Then it crashed.
    When I was taking Operating Systems in my computer science class, a crash means you will get no more than 60 (out of 100). At IBM, a crash is always a SEVerity 1 issue. There is no way around it. Crash means the program is worthless.
    I Googled it, and Adobe suggested it could be some drivers using virtual audio. I uninstalled everything I could find, and this problem is not going away. I looked at the sound device configuration, and it's using physical audio, not virtual audio.
    I uninstalled Premiere Elements 7 five times and reinstalled them. They still failed. Finally, I reinstalled it at a different location, and it managed to "Found default catalog. Trying to open the  default catalog." Then crashed.
    If I wanted to use the default catalog, I would have said so. If I knew where they are, I would have set them on fire.
    Anyway, I have a project due this afternoon, and I am stuck with these worthless Adobe Premiere Elements 7 error messages. No wonder Steve Jobs banned Adobe Flash. They are pretty worthless.
    Sorry I am so upset, because none of you need to read my frustration; but I am up to my neck with Adobe. Once I get my project done, and I am switching to SONY Vegas.
    But, for now, would someone tell me how to get rid of these problems so I can get the video edited? Thank you.

    I noticed these errors were reported years ago, and Adobe has done NOTHING to improve it.
    Go back to my little list of how problems, crashes and errors sort out. That was how it was way back with Premiere programs, and how it still sorts out.
    Even the patch for PrE 8 was mainly to get it functioning with nVidia and ATI graphics cards. Yes, those "fixes" probably straddle the line between Bugs and system, with a nod towards Bugs. I know that Adobe takes their Bugs very seriously, and work overtime trying to find fixes for those, that do exist. Though it took a bit of time, as they gathered info, still Adobe had a patch, and that is rare for PrElements, due to the normal lifespan of that program.
    I provide some of the same answers today, that I did years ago, to fix the problems. In nearly every case, things sort out per that list. As "system" is both #1 and is also by far the largest segment of causes, that is where I begin looking. With PC's, there are myriad configurations, and most are not suited for video editing. Too many load up their e-machine and expect to edit HD material. Obviously, that is not the case here, but there could still be equipment incompatibilities, or just some tweaking needed. I see similar in the PrPro forum, as the Mac-users put the program on their MacBook Pros, with one tiny HDD, and a very weak CPU, and things go horribly wrong. If PrE was ported for the Mac, we'd have the same issues here. Usually, my first question will be about the I/O sub-system, i.e. the HDD's, their size, speed, free space, controller type and how they are allocated. Video editing is highly I/O intensive, and most computers are not even close to being able to efficiently handle it. I recommend a minimum of 3x SATA, physical HDD's, and suggest that they be setup to spread the I/O workload over all three. Some manage with a 2x I/O, but that is below MY minimum, and is the real minimum from Adobe. A single HDD I/O is just going to cause bottlenecks, and there is no way around that.
    Once, it was more the domain of the PC, that one had system issues, as Mac's were so limited and controlled. Now, as they have gained the ability to expand beyond the absolute control of Apple, those users are finding out that systems DO matter.
    Notice #2 - Assets. Not all AV material is meant to be edited. Some, like AVCHD (a consumer format) will require a pro-level computer, just to get smooth playback! The second most common issue is trying to edit material that has something like the Xvid, or DivX CODEC.
    Number 3 - Project, is very important too. One must match their Project Preset to their source footage. If not, then there will be problems. The failure to do this match is one of the biggest causes of issues, though usually not crashes, or hangs.
    Number 4 - OE, is when a user decides to push a button, and expects something else to happen, and often because that's how it worked in another program. Many argue with me that #2 and #3 are OE too, but I am much more lenient, than they are.
    Then, there ARE the Bugs. PrPro CS4 had a bunch. CS4.1 fixed a few, but broke some other things. It was not until CS4.2, that things got corrected, mostly, with that version. Then, CS5 hit, and seems quite good, but has a few Bugs too. Some were left over from CS4. A new update for CS5 is coming, and soon. Will it also fix those lingering Bugs? Only time will tell. Will it be a perfect program? Doubtful, but I'll bet that it'll be a "better" program.
    Think back to when you started programming. You were writing apps. for the majority of the install-base. However, what happened if the user had Extended Memory? What happened if they had Expanded Memory? What happened if they had both, and a software manager to handle those? Most still had 640KB. By that time, I had 2GB, though my MoBo could only handle 1GB with the managers. How could you write for me? I was 1:1000000, or maybe even less. I had to do my programming on the fly, and often had boot discs for different programs. It's not that much different now, except that I would not be such a rarity any more, but hardly mainstream.
    I'll bet that we can sort much out, by tackling the "Big 3," and then working down, if necessary.
    I like doing test Projects, keeping things simple, and testing as we make them more complex. That helps isolate the issues in most cases. In another thread, the poor user says that all Project Presets, all formats and all Export setting yield issues. My first thought is to isolate on one Project Preset, one set of Assets, and see if it's a system issue.
    Sometimes it's easy, and that is good, 'cause the user gets to editing and not fritzing so much. Just nailed one in Encore, but the poster gave me all the data necessary, and my memory did not fail me (maybe it was not "wine-thirty yet?). One post, and one correct answer. Life is good. Sometimes, it takes days, and many posts, to narrow things down. In but a few, there is an answer. In those (like the PGC error in Encore) one never does really solve the issue, and the only hope is to get the OP to start over, do everything by the book, and hope for the best, this time around.
    Good luck, and be assured - I do feel your pain. If I have not had one of THOSE error messages, believe me, I have read of them too many times.
    Hunt

  • Premiere Elements 9 Tryout Serious Display Problem

    I will confine my editorializing to "Deja vu, all over again" and describe the Premiere Elements 9 problem that sounds like I was reliving the release of Premiere Elements 8.
    I downloaded and installed Premiere Elements 9 tryout, and it worked great for about 7 days. With no changes in the computer environment, suddenly when Premiere Elements 9 was loading a new project, it would stop at PlayerMediaCore.prm and pop up a message:
    "We have detected an incompatible driver. To get a better and faster playback performance, please update your display driver. Display driver details: NVIDIA Corporation GeForce....." and it went on to fully name my video card driver. When I clicked on OK, the program continued to load completely and opened to the workspace where the Edit Mode Monitor performance was, best described as, wacky....Timeline content that would not present in the Edit Mode Monitor, Preview Windows that froze in the Edit Mode Monitor, etc. And, Edit Mode Full Screen Previews did not work at all. The technical irony in all this was that I have Premiere Elements 6, 7, and 8/8.0.1 all installed on the same computer, and all were still performing great when I was using them one at a time as a control.
    When I went to Hardware/Device Manager and attempted to "update" my NVIDIA card driver, the "update" that installed automatically was older than what is was replacing. BUT, now Premiere Elements 9 did work as expected. HOWEVER, now my Premiere Elements 6, 7, and 8/8.0.1 were crashing at various times from loading to opening of the workspace. I am still hunting for a replacement NVIDIA driver that will fix the Premiere Elements 9 display issue and not kill my Premiere Elements 6, 7, and 8/8.0.1.
    In investigating this matter, I noticed that the Premiere Elements 8/8.0.1 "Enable GPU Playback" is gone in version 9. And, now, if you right click the Premiere Elements 9 Edit Mode Monitor, you have a Playback Quality option of Automatic or Highest. That tells me that Adobe was at work making changes in the name of better. And, I am wondering if what I am encountering is related to Adobe's attempted improvements in display which was one of the issues in Premiere Elements 8.0 when it was released. Or, could this be related to making AVCHD a native format? Lots of possibilities.
    The above is my long way of saying "Has anyone run into this type of situation with Premiere Elements 9, any workarounds found (other than buying a new video card just for Premiere Elements 9, ???"
    At this point, I know of one other person who got a similar message from Premiere Elements 9 and resolved the problem by updating the NVIDIA card driver. But that still raises the question "Do we need a special video card driver just for Premiere Elements 9?" and "Why?"
    ATR

    To Vijay and A.T. Romano:
    I am happy to help out any way I can. First, I do plan on installing PE9.0 on 2 other computers, both running Windows XP. Currently, both of these computers (Dell desktop and laptop) have PE2.0 running, with no problems. I will try to do these installations later on today.
    The 2 new computers have Windows 7 Ultimate 64 bit. While I have installed PE2.0 on these computers, the program runs slowly. I assume PE2.0 and Windows 7 are not compatible. As I mentioned before, PE 9.0 runs fine on the Dell desktop. It does not play videos on the Sony laptop.
    The contents of the text file are..
    ##FALSE#0#0#0
    The error message when the program is launched is..
    Display driver details :NVIDIA Corporation – GeForce GT 330M/PCI/SSE2 3.0 NVIDIA 188.67
    I do hope this help. I can only guess that the problem is wide spread.
    Thank you again.
    Alan Silberlight

  • Adobe Premiere Elements 9 "No Disk" Error

    Please help! I have used PE9 for several months. I tried to open PE9 and I get an error message in a dialog box titled: Adobe Premiere Elements.exe - No Disk. "There is no disk in the drive. Please insert a disk into drive \Device\Harddisk1\DR3."
    I try clicking on cancel, Try Again, Continue, but the dialog box continues to show after hundreds of clicks. I cannot use my PE9 at all.
    Here are my system details:
    Adobe PE 9.0
    System: HP Pavilion dv6700 Notebook PC, Intel Core 2 Duo, T9300 2.5Ghz, 3 GB, Windows Vista Home Premium SP2 32 bit, Paging file: 3369 MB windows managed on C:\
    NVIDIA GeForce 8400M GS Driver Version: 8.17.12.6658, 1/7/2011,
    Drives: 3ea, FUJITSU MHY2250BH, 220GB, Drive C:\ OS, programs and Windows Virtual Memory with 42GB free, Drive D:\ HP recovery partition, 12GB, 1.2 GB free,
    I-O Data HDCS-U, USB drive, Drive G:\ 1TB, 336 GB free, media files, project files, output files
    CD/DVD: TSSSTcorp CDDVDW TS-L632N ATA device. Drive E:\
    I appreciate your help with this problem.

    Removeable drives do cause problems when the program tries to find files
    That is why I always copy all video files to my data drive before starting a project, so the files stay in one place
    My 3 hard drives are configured as...
    1 - 320Gig Boot for Win7 64bit Pro and all program installs
    2 - 320Gig data for Win7 swap file and video project files
    3 - 1Terabyte data for all video files... input & output files (*)
    (*) for 4 drives, drive 3 all source files & drive 4 all output files
    Search Microsoft to find out how to redirect your Windows swap file
    http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US

Maybe you are looking for

  • How do i change my sign in details on the cloud download

    it tries to sign in with a non excisiting account but cant fnd anywhere to change this

  • Form to PDF form

    Hi ,      I have cretaed a form ( SAP Script) which I want send through email. So I need to convert that form to PDF format. How can I do that ? Thanks, Manas

  • My ipod 2nd generation won't charge.  No status light when conected to computer.

    Recently found an ipod shuffle 2nd generation.  When I tried to charge it there was no status light on it at all.  Thinking it could be beyond use as it hadn't been used for a long time.  Any advice welcome.

  • [915 Series] No async PCIe clock possible

    I have a 915P Neo 2 version 1.0A with latest bios 1.7 Bios offers the possibility to clock PCIe async. Example: FSB 200 shows PCIe of 100 FSB 240 shows PCIe of 114 But changing PCIe setting to anything else and the board does not boot.    Only differ

  • Connect to oracle xe from another machine

    How i can set oracle xe for connect from another machine i can connect with : sqlplus system/pass@xe listener and tnsnames are fine on base machine, but I can't do it from another machine i can't do it with html db (from browser), too ist it possible