-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Error: "It looks like REAPER is currently running..." when attempting to install SWS when it's already installed #2
Comments
That seems to be an issue with conflicting files that are not yet managed by ReaPack. What Rockum means by "It always results in cancellation" is probably the following screenshot (reported by another user): And this means that ReaBoot is simply facing conflicting files from a previous ReaPack-less installation. I think this should be dealt with in multiple ways:
|
@cfillion mentioned that the first ReaPack package to install existing files takes exclusive ownership of them (until uninstalled), overwriting if they already exist |
Rockum reported:
Regarding Installation of SWS (and perhaps other extensions?)
I don't know if it is a bug, but when I try to install SWS on a system that already has it, Reaboot warns:
"It looks like REAPER is currently running. If it is, please close it before pressing "Continue"!"
This happens regardless to whether or not Reaper is actually running. It always results in cancellation. Installing Helgobox does not cause the same issue.
The text was updated successfully, but these errors were encountered: