hi all ive been trying to update Kontakt from 5.3.1 to 5.4.2
i was useing a freinds win 7 to install all the Native Instruments plugins
for the last year or so and eventhing went ok till 5.4.2,

i new about bin iso 7zip to unpack the updates
and this also worked lots of times for me, but the one thing you wont get from this
is the reg key that the R2R installers have.

the only thing i skiped was the 4.1 update because of all the bugs i read eveyone was haveing
and i think now ,that you still have to install/copy all the files from 5.4.1 to get 5.4.2 working on xp and vista,
the file error you get is,

The procudure entry point k32 get module base name A could not be located in the dynamic libary kernel32.dll

if i get it working ill let use know

 

This is not how it works. Actually you could have done it yourself by locating Kontakt 5.dll and Kontakt 5.exe in the CD image file.
But 5.4.2 and 5.4.1 won't work on XP, because it was compiled with VS 2012 without backwards compatibility option checked, which basically rules out XP kernel entirely. I haven't tested XP64, but since it doesn't work on Vista, it's hard to imagine it'd work there.


Solution? Flood NI forum stating what dumb move it was (considering Vista is still supported by Microsoft - so the stereotypical excuse "XP is not supported by MS, so it's not supported by us" BS doesn't apply) and demand properly compiled executable. Another solution is sign a petition, or DDOS their website.

Offtopic:
Want a secure PC? Install Linux Mint and WinXP/7/8/8.1/10.
Use Linux for internet access and Windows for everything else. On Win, completely disable internet access by removing network adapters and shutting down network services (you'll still be able to install MSU updates offline)
It's not always safe to let backdoored proprietary closed-source OS go online and possibly spill all your secrets to 3rd parties, so this solution prevents that. Also you'll learn to spend less time meaninglessly browsing

 

Maybe someone with programming skills can get some informations out of this workaround discription.

http://blogs.msdn.com/b/vcblog/archive/2009/08/27/windows-sdk-v7-0-v7-0a-incompatibility-workaround.aspx

 

To get this workaround into effect, we'd need source code available
K32GetModuleBaseNameA function is located in PSAPI library (psapi.dll) on WinXP (actually only wrapper is present there), while subsequent versions have it integrated in kernel32.dll

This also further explains why there was "CPU performance in certain scenarios further optimized" in the changelog.
Kontakt 5.3.1 called EnumProcesses while 5.4.1 and above use K32EnumProcesses, slightly faster API, but incompatible with XP.

Full thread here

This ultimately means NI won't support XP and there's no known workaround (so far) other than acquiring source code and modifying target platforms and enums.
Upside is that there's slight performance increase, about 10%. *yes*

 

bit of a long shot here but is there anyway to change Kontakt to look for kernel33 and not 32.
i have a copy of kernel32 from win 7 and renamed it to kernel33.dll
but i cant get Kontakt to look for or run kernel33.dll

i see 100s of kernel32 listings when i open Kontakt in pexplorer
but can only find one kernel32 in UltraEdit to change,

im thinking if we can change Kontakt to look for kernel33 from win 7
we can call it plan c,

its sort of the same thing that R2R did with the Arturia plugins.
by making them look for KAWAELIC and not SYNSOACC so it didnt mess with anything,

i read the blog that lukehh posted and the thread that Andrew posted
but it was like looking into a field.