PI 12 unexpected shutdown

trueblue · Post by **trueblue** » Fri Feb 02, 2007 11:26 am

When I do some big tasks in PI, it could be a photograph or graphic or digital painting, PI shutsdown without warning.

Sometimes I get this warning:

followed by this:

It does not happen in any other graphics programs I use, only PI. It's as if PI is unable to complete a task sometimes.

I'd appreciate your help with this.

htchien · Post by **htchien** » Fri Feb 02, 2007 12:08 pm

PhotoImpact version?

What's the format and how large is the file you edit in PI?

H.T.

trueblue · Post by **trueblue** » Fri Feb 02, 2007 10:38 pm

Hi htchien,

Thanks for your reply.

I stated in the subject window PI 12!

The file size varies. For instance, I was making a reflet picture a composite of 5 pictures saved as a .jpg. 352px x 197px -
Each time I tried to open the file in PI it would shut down.

Sometimes when digitally painting - 600px x 450px....... I reach for a brush tool and mostly eraser, sometimes PI shutsdown, either without a warning or the messages as given per above.
This can be extremely annoying when trying to paint fine work.

I try to complete a task, adding presets to EP sometimes the same thing happens.

So you see, it varies. It's like PI is unable to complete a particular task at times. This doesn't happen always, but it's unpredictablity is causing me frustration in working.

I would have put this to Ulead Technical Support, but it's impossible to give them visual proof of a problem and often the reply given is unsatisfactory, like reinstall PI. How many times must one install/uninstall/reinstall. Just having to do this is time consuming as I have to reload all my EP again, and often adding the .smp to EP they don't work properly - keep getting message box requesting to browse for the file.

I do hope Ulead/Corel can fix these problems and provide us with a necessary 'fix' and not ask us to purchase yet another version with fixes as they did from v. 11 to v. 12.

heinz-oz · Post by **heinz-oz** » Sat Feb 03, 2007 1:03 am

I had similar problems when I rebuilt my machine last time. Turned out to be a faulty RAM memory module. The error that you get when it states that it could not write to memory can mean two thinks, as I understand it, either WIN XP has protected that memory area or the stick is faulty.

You can get a memory checking utility at the MS website.

trueblue · Post by **trueblue** » Sat Feb 03, 2007 9:02 am

Hi Heinz, if it is a hardware problem it would affect other programs, as I said in my previous post it's ONLY happening with PhotoImpact 12...

This is a new PC ... just over a month old and everything else is running very well.... except PI 12.

It would be good if the image examples were given to Ulead Technician for their appraisal, however I would not like someone to return and say uninstall/reinstall, as that often seems to be their stock answer.

Thanks for any help you can provide, as it's frustrating when it closes down in the middle of working. There's only a limited number of times one can save, also with auto save too.

njdowding · Post by **njdowding** » Sat Feb 03, 2007 9:29 am

Maureen its not always enough to say all my other software is running ok so it must be PI that is causing the problem. When you think about it if it were that simple then the problem would exist for every user which clearly it doesnt. There is clearly a clash between PI and your machine.

It would do no harm to test your RAM to discount it as a problem. All programs handle the computer resources a little differently depending on how they are written.

As we have discussed many times before a bug is a universal problem directly attributable to the software. We should expect and have a right to have this fixed through a patch.

However your sort of problem is never going to be fixed by a patch. If the software does not run in a stable way on a few users machine how can you realistically expect the software vendor to fix it. They wouldnt know where to start unless they attempted to reproduce every ones machine in their labs. Even then whats the betting it would still be restircted to one machine. I am not defending Ulead here just saying you have to be a little realistic in what you expect them to be able to do.

Your screen shots are only showing that an area of memory is not accessable and sadly would not help any one to really diagnose why.

Nick

dafalias · Post by **dafalias** » Sat Feb 03, 2007 12:15 pm

Nick,

your answer is totally unacceptable.
If you read this forum, you see that a number of people are having massive problems with PI 12.
Your statement is pure arrogance.
If ANY other software works perfectly on a machine except Photo Impact, then there IS a problem with Photo Impact.
Well written software does not have to be patched by renaming DLLs (like uipl.dll).
We all know that photo editing software is very performance critical thus has to make use of every multimedia extension a processor can offer.
There are vast differences though, sloppy processor detection may try to use non existing extensions and crash.
That is what I suspect with PI 12, since the problems seem to be all on Athlon systems;
if Your arrogance reflects the position of Ulead towards their customers, then that's it for me. I have been a PI user from version 3, but if Ulead is not willing to provide software that has been properly tested then I will go and spend my money elsewhere.

htchien · Post by **htchien** » Sat Feb 03, 2007 12:20 pm

Please report your issues to Ulead Tech Support.

http://www.ulead.com/tech/techsupport.htm

I hope they can help you.

H.T.

njdowding · Post by **njdowding** » Sat Feb 03, 2007 12:29 pm

Not arrogance but realism. I have no axe to grind either way. As I clearly stated this was in no way a defence of Ulead or sloppy programing or anything else. You use as an example something that clearly IS a bug as I would define it. As you quite rightly mention having to rename a dll and noting that it applies widly to AMD processor driven systems in my book makes it a bug.

However the OP was not discussing this bug but something else all together. My answer was neither acceptable or unacceptable it was simply a suggestion that to cure the problem the OP would probably have to track down the problem themselves since even a perfectly working support department will have a problem diagnosing something like this unless they can reproduce the exact set up. Ulead certainly does not have a perfectly working support department.

I would like you to reread my post and I think you will see I did not say or infer what you suggest. Please read it in context of the post and not in the context of some other unrelated problems.

Nick

htchien · Post by **htchien** » Sat Feb 03, 2007 12:38 pm

Hi,

dafalias wrote:if Your arrogance reflects the position of Ulead towards their customers, then that's it for me. I have been a PI user from version 3, but if Ulead is not willing to provide software that has been properly tested then I will go and spend my money elsewhere.

Please stop using arrogance to attack people here. Please, offensive posts are not allowed.

Nick is just a user like you and me here. He is not a Ulead people and does not represent Ulead here.

Since it's getting OT, I will lock this thread.

To the original OP, please consider the suggestion to do a memory check. If that does not help, contact Ulead Tech Support.

For the Athlon compatible issue, please contact Ulead Tech Support for that also.

If you think it's not proper to lock this thread, send me a PM to tell me the reason.

H.T.

Moderator: thread reopened due to the request from the original OP.

trueblue · Post by **trueblue** » Fri Feb 09, 2007 7:40 am

Thank you HTChein.

As for my problem, I think it's now fixed.

It definitely was not RAM as that's ok/stable. This is a brand new PC, but I know with technology, things can go wrong, even with new PCs.

I already have the Virtual Memory in XP increased, what I didn't have was extra temporary folders for PhotoImpact to use.
I made 3 folders in my C: drive and allocated them to PI from Preferences, General, System. Along with the normal C: Temp folder, I entered the 3 new folders in the relevant window bars. I rebooted my PC.

I also shut down my internet, turned off all security software and any other programs that may take up any resources.

I reopened PI and have been working on it now for several hours doing some high res graphics and digital artwork. It never shut down once. yippeeeee!!

Normally by now I'd be tearing my hair out because PI would have shut down numerous times.

If anyone else is having a similar problem, this is definitely worth a try.