Bug 15572 – Windows installer leaves "sc.ini" inaccessible
Status
RESOLVED
Resolution
FIXED
Severity
major
Priority
P1
Component
installer
Product
D
Version
D2
Platform
x86
OS
Windows
Creation time
2016-01-16T21:35:00Z
Last change time
2016-01-18T17:24:19Z
Assigned to
nobody
Creator
bugzilla
Comments
Comment #0 by bugzilla — 2016-01-16T21:35:25Z
As I received in an email:
I downloaded the file dmd-2.069.2.exe and parked it in C:\D.
That self-installing file was then run in command line mode. Success was declared. However, file “sc.ini” was still declared inaccessible to “TYPE” its contents or to “REN” its name, or “COPY” to copy it to another folder BUT Windows Explorer was happy enough to move it. It was then possible to copy back the saved file as “sc.ini” and this time all the necessary permissions were available. In this newly extracted downloaded file, according to the script, Windows has amended several lines, and with file “sc.ini” now accessible, the DFLAGS line is now operable and the earlier flag lines (see earlier messages below) for accessing files “import.d” and “std\stdio” are no longer needed. My guess is that the Windows installation program – or even Windows itself - is varying the file permissions of “sc.ini” (and some other files) but it leaves behind a slightly smaller file “sc.ini.old” with the same inaccessibility permissions. Has “sc.ini” been sourced from a Linux or other platform?
on a 64K Windows 7 Pro platform
Comment #1 by r.sagitario — 2016-01-17T22:17:30Z
Very likely a duplicate of issue 15456.
Comment #2 by github-bugzilla — 2016-01-18T17:22:05Z