Preserved Topic: Could not be completed because of a program error

Any of you gets that error just too often not to be minded? Any solutions?

On 7.01

I get that sometimes if I try to run Lighting Effects. It is usually if my machine has been on for a long time. Restarting the computer usually cures the problem.

I`ve gotten it in Versions 6 and 7 while running Lighting Effects. It`s become habit to save just before going to the Lighting Effects filter as the only cure I know is to close PS and reopen it. Sometimes it won`t let you save after the error.

Never had it...wonder why...maybe because I run RamBooster in the background on a WinME?

*looks at PS fiercely* - don't even think about it...

I never get that either... wonder why... oh yeah... an apple a day keeps the crashes away

First thing I can think of is version. You mentioned 7.01, did you check for the extra little tidbits that Adobe likes to release separately from it's point releases? Usually there is a separate download for MMXCore and PPCCore. These usually involve fixing issues with newer processors and I could easily see that causing the problem.

The second culprit I can think of would be memory getting full. Are you running any other applications while running PS? Maybe one of them is conflicting or has a memory leak... check your system resources.

Next in line, make sure you check for file corruption. Maybe Photoshop is corrupted due to a disk error, or it's trying to write it's swapfile to a bad sector of your hard drive.

Down the list would be thirdparty plugins. Maybe there is a plugin that isn't working correctly and it's causing issues.

Trucking on to a sneaky one that I've seen cause havoc and it's hard to track down... a corrrupted font. This is HARD to track down. Because it could just be one font, or some portion of the font that Photoshop is using or even just one style of the font (bold, italic, etc.). A bad font can bring your system to it's knees and it often looks like other things. Windows is also much harder to track this problem down on as it tries to load fonts at boot time not at application time like mac. Both systems are a bitch to troubleshoot. If you JUST installed a font and this is happening, REMOVE it and see. I had my system working fine for a week after installing a new font... then it just started hanging at boot time... turns out the font was corrupt and had just THEN decided to eat itself.

Along those lines, check for driver issues. Could be your wacom drivers, your video card drivers, you scanner drivers, your printer drivers, you limo driver. Who knows... drivers are low level system files... they can be sneaky.

Reset your preferences lately? Might help... could just be a bad pref file. On mac hold cmd+option+shift while you boot. Should be ctrl+alt+shift on windows, can't remember, but that makes sense (anyone?).

Finally your computer could be possessed. You should call a priest, wash all the componets in holy water, have a spiritual cleansing, eat some gingko biloba, chant and dance around a bonfire, and blame sunspots. Sometimes shit happens, reinstall.

Hope SOMETHING works for you.
$0.02


It's only after we've lost everything...
That we're free to do anything...

I used to run into this often with Win98se and 512M of RAM. Since upgrading to XP Pro and 1G of RAM I haven't once seen the problem.

Thanks Mindbender. Tried all that stuff (except the priest). Started in a 5.0 trial on WIN 98SE, 98MB RAM, and a PIII 450. Also ver 6, 6.01 same box...I`m now using a 2.26 Ghz P4 and 1024 MB RAM on 2K pro. Still happens sometimes.

Yea, I know. It`s still Windows.

You know... you #[]%^!$**(&U!@!!! cursed my machine. I saw that error for the first time yesterday. I was trying to move multiple channels from a Lab document into the layers of an RGB duplicate and it gave me that stupid error. Course I just reopened it and it worked. *shrug* don't know why you're getting it.. computers suck. Let's all take up farming.


It's only after we've lost everything...
That we're free to do anything...

hahaha, suits you right

thanx guys. still, i wish i had an autosave function around sometimes

auto save? a quick ctr+s isn't that much trouble is it?