valentina icu*.dlls

[Andreas Mellin]

  Hi Tom,

using Sysinternals ProcessMonitor, I've found a task named tcpsvcs.exe, 
that also tries to access icu*.dll in severe windows system directories 
during startup of your application.

BR
Andreas



Am 19.12.2010 13:05, schrieb Thomas Flemming:
> Hi,
>
> we recently had a customer, where our software based on VNet didn't 
> start.
>
> After investigation we found out, that the problem was these dlls, 
> which the customer had in his windows\system32 - folder, which are 
> from a different version, then vnet 4.6 needs:
>
> 05.12.2009 11:53 8.572.928 icudt30.dll
> 05.12.2009 11:52 733.184 icuin30.dll
> 05.12.2009 11:51 614.400 icuuc30.dll
>
> Our software of course comes with the vnet.dll and all necessary 
> valentina-dlls, including these icu*.dll, but they are all installed 
> in the applications-directory.
>
> After deleting the icu*.dll in windows\system32 our software was using 
> the correct dlls from the applications-directory and was working again.
>
> So, how could this happen?
> If the vnet.dll is in the applications-directory and the icu*.dll 
> also, why are the wrong icu*.dlls from windows\system32 used?
>
> Regards
> Tom
>
>