New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the last compatible version for XP #1332
Labels
Comments
cfillion
added a commit
to cfillion/sws
that referenced
this issue
Apr 11, 2020
This is required for compatibility with Windows XP See https://web.archive.org/web/20151123133638/https://connect.microsoft.com/VisualStudio/feedback/details/1789709/visual-c-2015-runtime-broken-on-windows-server-2003-c-11-magic-statics Fixes reaper-oss#1332
Thanks for the report! These builds should fix the crashes on Windows XP: |
I shall test over next 24hrs. Thanks so much for quick response. |
That seems to work great. XP service pack 2 Reaper 5.9.83. SWS 2.11.0.0. |
cfillion
added a commit
to cfillion/sws
that referenced
this issue
Apr 29, 2020
This is required for compatibility with Windows XP See https://web.archive.org/web/20151123133638/https://connect.microsoft.com/VisualStudio/feedback/details/1789709/visual-c-2015-runtime-broken-on-windows-server-2003-c-11-magic-statics Fixes reaper-oss#1332
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am unable to secure a working version on my XP service pack 2 platform beyond 2.9.8 5mar2018
Invocation of these dialogs from the Extensions item on the main menu bar results in the error reaper has encountered a problem and needs to close which it does when you accept the error dialog.
These dialogs exhibit the problem.
Cycle Action Editor
Find
Notes
Live Configs
Region Playlist
Resources
All on Reaper 5.9.83
I have tried various configurations. I come to the conclusion that changes were made to these dialogs that rendered them XP incompatible. Does anybody have working later version of SWS beyond 2.9.8 on windows XP? Thanks.
The text was updated successfully, but these errors were encountered: