cfillion
commented
8 years ago Thanks for the nice report!
XP support was only theoretical as I was unable to find a version of Windows XP to test with... But I got lucky today and finally found this VM image from Microsoft, so I was able to make it (almost) work (yay!). However...
- Windows XP's implementation of SSL is utterly obsolete and cannot connect to any server using modern security settings (such as GitHub where all of ReaPack's default set of repositories are hosted). The solution is to use an alternate SSL implementation (namely, OpenSSL), adding 1–2 MB to the ReaPack builds
- I must also either manually bundle and maintain a set of current CA certificates or disable remote server authentication altogether (meaning lessened security) to make it work
- XP itself and Microsoft's C runtime on XP have bugs which cause crashes and bad behavior
- + a few other glitches I haven't tried to track down...
In short: workarounds are possible but I'll pass and focus on Vista and newer. I'll still keep a partial fix for XP around just in case...
(related issue #4)
uncleswede
I've downloaded Reapack onto my studio PC but get the error "The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.DLL" when starting Reaper v5.211.
On investigation, it seems that the Windows XP version of Kernel32.dll does not have the GetTickCount64 function (this was introduced from Windows Vista onwards).
I installed Reapack on my mobile recording laptop (running Windows 8.1) and it worked fine with Reaper v5.211
So it appears that Reapack is not compatible with Windows XP :-(