I have upgraded my pc with new processor and mb an have made a new installation of WinXP afterwards.
Now, I can't no longer getting PI10 to run. Everytime I start the program, shortly after the working area is displayed, iedit is crashing in module uliblzw.dll.
I also downloaded trial of version 11 but there it's exactly the same problem.
Does anybody know about this problem and a possible fix? Does anybody know, for what the library uliblzw.dll is? It seems to be a common file in different ulead products.
Thanks and regards
Renato
PI10 + 11: crash at startup in module uliblzw.dll
-
keenart
-
2log
re: PI10 + 11: crash at startup in module uliblzw.dll
You can try reinstalling the software. Use the clean reinstallation procedure outlined on the Ulead Knowledge Base:
http://www.ulead.com/tech/kb.htm
*Though I personally think the problem lies elsewhere (since you're experiencing it with both versions 10 and 1), it's still worth a try.
http://www.ulead.com/tech/kb.htm
*Though I personally think the problem lies elsewhere (since you're experiencing it with both versions 10 and 1), it's still worth a try.
-
wajdy
Some workaround on this problem
Hii there,
I also have the same problem. Fortunately, after keep restarting the program I found that the error comes from file u32tif.fio from FIO directory. After removing the file I don't have the error anymore. The bad thing is that I am not able to export the file in TIFF format which is very strange for a Standard Graphic Editor software. Any technical guy here can explain the problem in details.
Following the suggested workarounds, (reinstall + clean installation) yielded no solution on the issue.
Bye
I also have the same problem. Fortunately, after keep restarting the program I found that the error comes from file u32tif.fio from FIO directory. After removing the file I don't have the error anymore. The bad thing is that I am not able to export the file in TIFF format which is very strange for a Standard Graphic Editor software. Any technical guy here can explain the problem in details.
Following the suggested workarounds, (reinstall + clean installation) yielded no solution on the issue.
Bye
