IPP 5.3.4 doesn't install on E5200 processors

[gast128]

Dear all,

We use the IPP libraries to speed up image processing. The IPP libraries are linked with the dynamic link option. Some of our customers use a E5200 processor which already has resulted in some crashes of our application. It is located in illegal instruction which is a SSE 4.x instruction not supported by the E5200. Intel recommends to upgrade to 5.3.4, see:

http://software.intel.com/en-us/forums/showthread.php?t=62088

However IPP 5.3.4 doesn't let itself install on these PC's. One get a 'No DLLs were found in the Waterfall procedure' error. In control panel one can see that the install is only 2 MB big, while on my PC its more than 100MB. All the processor specific dll's seems not be present (resulting in the dreaded waterfall error message). Does the installer work correctly on this processor? Can anyone help?


 

[Ying_H_Intel]

Quoting - gast128

Dear all,

We use the IPP libraries to speed up image processing. The IPP libraries are linked with the dynamic link option. Some of our customers use a E5200 processor which already has resulted in some crashes of our application. It is located in illegal instruction which is a SSE 4.x instruction not supported by the E5200. Intel recommends to upgrade to 5.3.4, see:

http://software.intel.com/en-us/forums/showthread.php?t=62088

However IPP 5.3.4 doesn't let itself install on these PC's. One get a 'No DLLs were found in the Waterfall procedure' error. In control panel one can see that the install is only 2 MB big, while on my PC its more than 100MB. All the processor specific dll's seems not be present (resulting in the dreaded waterfall error message). Does the installer work correctly on this processor? Can anyone help?

Hello,

right, about the crashed on E5200(http://ark.intel.com/Product.aspx?id=37212), itisour known issue, please see the KBat: http://software.intel.com/en-us/articles/intel-integrated-performance-primitives-intel-ipp-intel-ipp-53-dispatches-wrong-cpu-type-for-intel-core2-duo-mobile-processors/.It should befixed in IPP 5.3.4 and higher version.

About the installer, do you mean the installer under IPP install directory toolsruntime?Itlooks ainstaller error with IPP 5.3.4. could you ask the customer provide the OS information and the installer directory size?

For quick workaround, you may send a package which include all ipp*v8.dll to customer and let them copy the dlls todirectoryWINDOWSsystem32 manually.

On the other hand, is it ok for your application to latest IPP version, like IPP 6.1.1 andcopy the required dlls tosystem pathinstead of installer?
because you may know that the IPP install installer is removed since IPP 6.x. Please see http://software.intel.com/en-us/articles/intel-ipp-rti-tool-is-obsolete/ for details.

Regards,
Ying

[gast128]

Hello Mr. Ying,

thanx for your answer. The link doesn't work somehow, but what I can do is sending manually the ipp*v8*.dll.

We had 2 customers with this problem, one Acer PC and one DELL pc. I have here Aida log files, but they are quite large (2 MB). If u are interested I can send them to u personally. The only thing in common is that they have the E5200 processor. One can clearly see that IPP hadn't installed itself correcly, looking at the size (only 2MB) and the missing specific processor DLL's in system32.

Switching to 6.x is an option, but this should be tested first. Unfortunately Intel removed the installer, so we must do that now manually which requires some research. It would be nicer if Intel had made an installer, preferably one whichinstalls side by side (in the WinSxS directory).

In the mean time we followed advise (copying IPP Dll's by hand) and it seems to work @ customer. So for now I conclude that IPP 5.3.4 may solve the problem but still wouldn't let itself installed on a E5200 processor.

wkr
me

Edit 11-03-2010: problem also manifests itself on E6300 processors.

Edit 22-03-2010:Article mentioned by Mr Ying is'Intel IPP 5.3 dispatches wrong CPU type for Intel Core2 Duo mobile processors' (somehow his link does not work).

Edit 25-03-2010: same problem on Core i5.