Justin,
Did you by chance add a plug-ins path to your preferences, pointing it to a path shared with an earlier PS version? If so, and particularly if that was a plug-ins path within an older PS installation directory, you may be inadvertently loading incompatible plug-ins. The MMXCore.8bx file is native to whatever version of PS it was provided with and should not be used with later versions. I suggest you try launching PS CS3 with a reset of the prerferences (Ctrl+Alt+Shift while launching PS) to see if that clears out the problem and allows CS3 to load. If so, then explore your preference settings again and ensure the secondary plug-ins path is empty or else pointing to a path only containing 3rd-party plug-ins.
Regards,
Daryl
I had Virtual Photographer installed for CS2 and I copied and pasted that folder to the CS3 directory(last week). Today I deleted both directories and installed Virtual Photographer again and dragged the folder to the Plugins>Filters area of CS3 within Windows Explorer.
CS3 starts, but I still can’t use motion blur, and I’m not sure if any other plugins are effected. I can click on motion blur, it pops up, and it crashes when I try to adjust anything. I deleted the CS3 preferences files and after that motion blue would work, slowly, and the preview screen wouldn’t update. I clicked the preview checkbox on and off and then it crashed again telling me "Adobe Photoshop CS3 has encountered a problem and needs to close". This is the error signature:
AppName: photoshop.exe AppVer: 10.0.0.0 ModName: mmxcore.8bx ModVer: 10.0.0.0 Offset: 0000c02e
I had the same problem with the demo. Other than that the interface is terribly slow. And we’re not alone:
<
http://mattwilcox.net/archive/entry/id/894/>
Seems like the code hasn’t been optimized for ‘old’ CPUs like the Athlon XPs. I got an Athlon XP 3200 Barton. Oh well, no upgrade then for me. Hopefully there’ll be a fix one day.
You don’t happen to have the Additional Plug-Ins directory set to your plug-ins directory for an earlier version of Photoshop, do you? This often results in errors similar to yours, because Photoshop tries to load the plug-ins found there that were part of the earlier version (such as MMXCore.8bi) that aren’t designed for the version you are running.
Hello and thanks for the tip Michael, but that’s not the case. =)
If the cpu is part of the problem, it’s not necessarily because it is "old". Silicon does not operate in a vacuum. Mobo, I/O bridges etc all operate together such that, individual board/silicon (including Bridges) combinations may cause crashes, as they have reached some margin limit due to stressing beyond the known limits from the testing at the time.
You may run off and replace the system, and that’s ok. But maybe, if it is a H/W problem, maybe simply replacing th cpu with another will ameliorate the problem.
But then again, maybe not!
No, I didn’t mean that the CPU is part of the problem because it’s not functioning properly. What I meant was, that Adobe hasn’t optimized the code for older processors. From the problems I encountered with Lightroom I’ve learned, that it is seemingly normal, that new software only works properly on recent hardware, as Lightroom can’t render some colours properly on machines that don’t have SSE2 (the so called ‘highlight bug’).
Lightroom and PS3 are also very slow on my machines…the menus are laggy and the sliders unresponsive.
As Adobe is a smart company, so these ‘bugs’ must be part of the cost-benefit analysis. The majority of professionals seem to have the needed hardware and additional sales to small companies who can’t upgrade their hardware every year don’t seem to make up the additional costs for development. They probably also think they can force customers to upgrade and sell their products anyway, as the lack of competition doesn’t allow us to go elsewhere. But my situation is rather simple and so is the analysis on my side: I would buy new licenses for Adobe products, but I won’t upgrade all my hardware to run them at the same time. The new features aren’t worth the costs this would bring for me. But probably I’m dispensable…
It would be intersting to validate that. For openers, i would be interested in whether Athlon 32 is indicated as suspect over Athlon 64, and if single core processors are indicated over dual core.
too much to ask, I suppose.
Hey Lawrence, nice idea. For starters it would be nice if you could post your type of CPU and if these crashes occur on your system(s) or not. The original poster had an Athlon XP, the person in the link I posted has one and I have one. So there’s three so far with Athlon XPs (non SSE2) CPUs. Anyone else?
The topic name is probably not right to ask for much feedback though. It should be more specific…
Mine is an Athlon 64 3200+, AM2 socket at 2GHz, 2G RAM. I have not experienced any crashes in PSCS3, but I am having hangups in Bridge. After opening and closing a number of times, Bridge will not open unless i first kill it in the process tab in Task Manager.
Also I would like to know if any Core 2 Duo Intel processors are crashing.
