• via Digitalmars-d-bugs (31/31) Jan 16 2016 https://issues.dlang.org/show_bug.cgi?id=15572

via Digitalmars-d-bugs <digitalmars-d-bugs puremagic.com> writes:

https://issues.dlang.org/show_bug.cgi?id=15572

          Issue ID: 15572
           Summary: Windows installer leaves "sc.ini" inaccessible
           Product: D
           Version: D2
          Hardware: x86
                OS: Windows
            Status: NEW
          Severity: major
          Priority: P1
         Component: installer
          Assignee: nobody puremagic.com
          Reporter: bugzilla digitalmars.com

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

--