On Fri, 2016-06-03 at 10:51 +0200, rolfm@dds.nl wrote:
Dan Wilcox schreef op 02-06-2016 22:50:
When the app needs a different version of the built in windows libs, that usually means it was build on a different version of Windows.
Sometimes, you have to include a copy of the lib itself with the app and/or the user needs to install it. Hacky I know, but that’s what I’ve done in the past…
IE: https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/7f5a39ee-e089-...
Often times, I’ve quickly had to go to one of these sites that hosts various Windows api dlls just to get something to work. Either that or copy it from another machine with an older OS. Seems like this might be an option for now.
great Dan, MSVCR71.dll was present in my system, but apparently not at the 'right' place for Pd/Gem. copying the file to a 'better' location did the trick.
thanks everybody who contributed in my groping around to get Gem working.
Great to hear about your success.
Would be good though, if other Gem users on Windows 10 wouldn't have go through those hoops in the future. Maybe you report that on the Gem-dev mailing list, hoping that there is solution that will automatically detect the dll at its original location.
Roman