-
-
2. Re: Windows 7 64bit Encore Issues
LeBozo Nov 23, 2009 9:44 AM (in response to jkb242)All of my problems with Windows 7 64-bit lockups were related to the Roxio PX Engine, which Encore uses under the hood.
This patch fixed all of my issues:
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
-
3. Re: Windows 7 64bit Encore Issues
jkb242 Nov 23, 2009 10:04 AM (in response to LeBozo)Most interesting indeed. How in the world did you determine this. I will try and leave feedback as to how this solves my one and only issue---that I know about thus far.
Thanks again!!
-
4. Re: Windows 7 64bit Encore Issues
jkb242 Nov 23, 2009 10:10 AM (in response to LeBozo)Did you have failures when opening a project in Encore which is the root of what is being reported here or other issues may be related to DVD burning? I did not see any mention to Adobe in the compatibility listings. I just want to be careful I do not install a driver or fix that doesn't pertain to the only issue that I am aware of with my installation of Win7 and Encore CS4.
-
5. Re: Windows 7 64bit Encore Issues
LeBozo Nov 23, 2009 10:19 AM (in response to jkb242)It manifested itself in several ways:
1) Opening a project that contained HD assets
2) Importing HD assets
3) Clicking on Sys Info
The patch fixed all of these crashes.
There are several postings in the forums about the PX engine. It is used by Encore, which seems to be why it is the only CS4 app having the crash issues.
-
6. Re: Windows 7 64bit Encore Issues
jkb242 Nov 23, 2009 10:22 AM (in response to LeBozo)The help remains valuable as it might also manifest itself more widely, over the ones you have mentioned here.
My projects have had nothing in common with the items below.
-
7. Re: Windows 7 64bit Encore Issues
LeBozo Nov 23, 2009 10:31 AM (in response to jkb242)The way I came across this solution was reading a post that stated it fixed the 32 bit version. Out of desperation I gave it a try. My machine is a brand new build so I could afford to reinstall everything if it failed.
BTW I think because it is a new build is why they problem isn't as widespread as it should be. I develop software and it's very common to have software get through the QC process and fail when distributed to the public because developers has so much crap on their machines. It's really hard to have a dedicated clean environment for testing. If you have any software on your machine for Roxio or PX licensed products, you might already have the correct patch so the program doesn't crash.
My theory on the cause of the problem is in the way it is retrieving system info, since that crashes every time. Win 7 probably made a change or the PX engine was using an undocumented or unsupported call to retrieve the info.


