Can't run PhotoImpact!!!

[sumner]

I'm really frustrated, I have been using the program for a week since I purchased it working on a big project that is due FEB 1ST!! and now suddenly every time I go to open the program I get an error message:
Error Signature:
AppName: iedit.exe ModName: xulparser.dll

I have windows xp...I did a system store to a time that I was actually using the program and then I ended up with another message:
Error Signature:
AppName: iedit.exe ModName: iedit.dll

Went back....uninstalled the program, reinstalled the program....still same message! HELP! I need to open the files I have already created AND I really liked the program....since I paid for it I would like to continue using it. Thanks.

[yayaya]

I've encountered the same problem

here is the message:

IEDIT caused an invalid page fault in
module XULPARSER.DLL at 0167:029d2aff.
Registers:
EAX=014af8f4 CS=0167 EIP=029d2aff EFLGS=00010202
EBX=bff77e01 SS=016f ESP=014af8cc EBP=014af900
ECX=00000000 DS=016f ESI=02c89e80 FS=6907
EDX=02c89e7c ES=016f EDI=02c85870 GS=0000
Bytes at CS:EIP:
8b 01 ff 50 30 8b 4c 24 08 89 46 04 8b c6 5e 64
Stack dump:
02c89e80 02c89e80 014af8f4 02aaedf8 00000000 02999457 00000000 02c85870 00000000 02c89e80 014af924 02aa9f32 00000000 014af930 02998dca 00000000


What can I do to save the program?

[k9ruby]

Me too!

[Masami]

Alright, first of all, reminding people that restoring your system only restores the SYTEM FILES. Any other files such as the Photo Impact files, will remain the way they are, so it's only got a small chance of fixing problems like this.

Best way to try to fix this is to uninstall it. While it is uninstalled, delete the following locations.
1) c:\program files\Common files\ulead systems
2) c:\documents and settings\all users\application data\ulead systems
3) c:\documents and settings\[your login name]application data\ulead systems

then restart the computer and reinstall.

If you're in XP, try restarting in diagnostic mode before the reinstall.

[keenart]

According to the Ulead Russian Forum, xulparser.dll is a major source of problem for them as well. They say the problem is fixed in the PI 10 patch.

I have the patch installed, but didn't have the problem to begin with.
I went searching for the DLL and it is in the main Ulead Folder. The version number is still 10 and the date is still 2004. I see no change. Microsoft dosen't have aything so assume this is a Ulead only problem.

The crash seems to be more prevelent in the European Versions of Ulead. You are going to have to complain to Ulead about this one to get a Fix in the works. Or if you haven't already install the patch.

[keenart]

I have studied the problem a little more:

The parser is a C/C++ function that parses text according to the rules in your grammar and, as it matches rules, calls your code to deal with them.

The iedit.exe file is calling the xulparser.dll, to parse text, create a set of rules, then relocate, and continue calling other components. I don't have a code breaker any more so I can't open the DLL and find out exactly what it is doing.

In comparing file dates and version numbers, and looking at the Headers of many of the files, I can see they were all created at different dates within the total software package, which means they were making last minute changes. Not a good sign.

The latest P 10 patch updated my IEdit but not the DLL.

As stated in the previous thread this problem is all over the Ulead Forums, English, Russian, Taiwan, etc. So it is a problem gaining ground. I can't find any other solutions to the problem from Ulead, or anywhere on the Web, other than the Russian forum members stating the patch solved the problem for some of them.

[OneCapturedMoment]

sorry, I should have read more before my post on the error message. This seems to be my problem. Thanks everyone who replied.

[davecone]

I have found a copy of xulparser.dll for download from:
http://ftpkbt.ulead.com/pub/Updates/pi10/

I have not tried it yet but I am about to do so. I'll post the results.

*** Update 11:30am ***

Replacing the file had no effect. I restored the original copy on xulparser.dll

The only changes that I'm aware of to my system between when it worked and when it started crashing on start-up is Microsoft Windows Updates.

** Update 12:12pm **

The following are the updates that happened on the day PhotoImpact stopped working... There are 18 total.... Perhaps someone who has 'auto-updates' from Microsoft could post a shorter list of the updates that happened when PhotoImpact stopped working for them.

KB883939, KB888240, KB890046, KB983756, KB894391, KB896344, KB896358, KB896422, KB896423, KB896428, KB896727, KB898485, KB898461, KB899587, KB899588, KB899591, KB900930, KB901214.

Based on the fact that the first post about this problem is dated Jan 26th, I'd guess that it is one of the earlier updates.

--Dave

[LaDair]

Hi guys,

I'm not as technical as you guys are. But I have just spent the last 6 hours trying to get PhotoImpact 10 to open. It crashed with an error last night and it never would open again. I have reintalled seven times. It will install just fine but will not open. Even though the extra programs like Photo Explorer and 360 open just fine.

Then I remembered that this happened when I first bought the program and tech help from Ulead was non existent. They never answered my support ticket. I know this is going to sound simple. They need to tell everyone to turn off their virus software. I have Panda.

I turned it off the first time by accident and totally forgot that was the problem. I did this time reinstalled with it off and it worked fine. After six hours it would seem that someone would post this info on the setup info when you buy the program.

I hope that helps some of you.

LaDair

[mayday]

I've had this issue crop up a couple of times; just to help out anyone else who's having it the problem seems to be with the current.xum file becoming corrupt which is presumably what xulparser.dll is trying to read. You can find it in: C:\Documents and Settings\<username>\Application Data\Ulead Systems\Ulead PhotoImpact\10.0\profiles - if you delete the current.xum file Photoimpact should start fine.

[dejavuguy]

THANK YOU!!! I had this promblem for about a week now, and I'm working on a website so not having PhotoImpact 10, I had to put work on hold.

[jaxdoug]

I had this same problem, purchase 10 on Oct 21, 2005 and it locked me out. I removed this file and now it works again. Thanks very very much. Ulead support sucks, thank God for this board.


Doug

[Joshua Liu]

I registered in order to appreciate comments above.
Killing current.xum does help instead wasting days to try fixing xulparser.dll
It works find now and Ulead tech support sucks.

[trueblue]

Joshua, there is no Ulead any longer. PhotoImpact was bought out by Corel and unfortunately it's been put on the scrap heap! So, you will receive no help with this product.