The 2.066-rc1 Windows installer went wrong on me.
First, it tried to uninstall, it offered to uninstall from 'C:\D'. My DMD install is 'C:\dev\D', so it got the path wrong.
The path was presented in a greyed out textbox that I couldn't type in to correct it, and no button to select the true install location.
The uninstall step failed.
Then when installing, I was given the option where to install, I chose 'C:\dev\D' and it installed over the top of my existing install, and wiped my sc.ini file.
I needed to reconfigure my paths, and the '.old' file that was present beside sc.ini didn't appear to be my version that was just overwritten, since it had none of my configuration in it. It must have been from some previous time.
Comment #1 by eco — 2014-08-06T04:28:02Z
The installer was partially rewritten for 2.066 so the uninstall path issue may no longer be present. You can try uninstalling 2.066-rc1 and seeing if the path is correct now.
The new behavior is to uninstall before installing. This helps eliminate very bad problems we've had with stagnant files staying around and messing things up. This means your sc.ini is getting deleted even if it hadn't be overwritten. If users are going to customize their sc.ini, I think it's reasonable to expect users to have a copy stored somewhere. Saving a backup somewhere would actually be tricky because the files are removed by the previous versions uninstaller before new version's installer can do anything (like backup an old file).
The .old files are from the automatic MSVC detection the installer does. It does a find and replace on the file to replace the environmental variables with the detected paths and part of that is making a backup first. It's not really necessary or helpful though, just the default behavior.
Did you have any changes to sc.ini beyond adding DirectX paths? If that's all you are changing it for we can probably just add the detection you've wanted so you don't have to touch sc.ini. I'd need your help though, I haven't touched DirectX since DirectX 7 so I'm out of touch.
Comment #2 by turkeyman — 2014-08-06T04:48:29Z
Right, I just tried the uninstaller and it got the path correct. It just didn't get the path correct from an older installation.
Yes, it's only the DX path I've ever messed with. It would be great to support automatic detection. Details in other bug report.
Comment #3 by greensunny12 — 2018-03-27T06:15:27Z
It looks like this has been resolved and it's 4 years later without an activity, so I'm closing this.
Please reopen if this issue still exists or simply report a new one. Thanks!