PhotoImpact 11 fails to load under Vista when not C:

[reinders]

I installed PHotoImpact 11 under Microsoft Vista, which I have installed from my F: drive -
(I did this because Windows XP on C: - and I wanted to migrate a step at a time)

and like others (I learned from this forum) -
I found PhotoImpact would not finish initializing.

According the screen - it stopped while loading u32Ico.fio...

The solution (other than redoing the system to have a C: drive operating system) - is as follows:

MOVE
f:\Program Files\Ulead Systems\Ulead PhotoImpact11\Fio\FIORC.dll
to
f:\Windows\System32\FIORC.dll

You *must* delete the file from the Fio directory - if you leave a copy there - it still finds it in the Fio directory it fails to loads.

If you do not put a copy in the system32 directory - you'll find PhotoImpact loads but will not open photos any more.

I hope ULead will consider fixing whatever error is in there code - this has been mentioned on this forum for past versions.
A great piece of software - a minor bug once you know how to work around it -

I hope this helps others.

[Ron P.]

Nice advise, thank you for providing it. However I would not consider it a bug, since Intervideo/Ulead has not released a patch yet for PI to work on Vista. It's like expecting software that was designed to work on Win 3.1 to work on WinXP...

[reinders]

It's not a Vista specific bug - it has been noted on Windows XP but the fixes I found reported in this forum were to reinstall XP on C: instead of a non-C: drive. I think a lot of people might install Vista on non-C: - so I hope this patch helps them... should help XP users too.

[Raptor8]

Thanks, that was an easy and great fix. When I replaced my C: drive due to failure and reloaded XP it assigned it F:, seems pretty lame but once it does that it can't be changed. My P11 also wouldn't boot until I moved the FIOC.DLL file after which it worked fine.
Thanks!

[staycool]

Thank you very much!
I spent a lot of time installing - reinstalling PI 11 on XP prof. It freezed every time, nothing helped, but your tipp.

yours sincerely

Carlo from Germany

[heinz-oz]

Well, on this PC my XP just happens to be located on D: drive, I don't have and never had this problem. Neither with PI 10 nor PI 11 and certainly not with PI 12. Go figure.

[sjj1805]

The problem here is that Windows did not update the PATH statement to include the current location of FIOC.DLL.
There could be a dozen reasons why the PATH statement was not updated and could vary from one users machine to another.

Useful link:
How to set the path in Windows 2000 / Windows XP.