Mixing
File/DLL installed to {sys} does not appear in C:Windowssystem32
I don't know why, but when I try to copy a file from my install directory to system32, it fails to do so although it reads as successfully installing in Inno Setup. Here is my code:
[Files]
; specifies what files will be included in the installation
Source: "{src}..elt.properties"; DestDir: "C:elt"; Flags: ignoreversion; BeforeInstall: SetProgressMax(10);
Source: "{src}..msvcr120.dll"; DestDir: {sys}; Flags: onlyifdoesntexist;
I also wanted to include my log output as I thought it was strange that the time was so off for the file, I am writing this around 11 am on July 8 2016
[11:49:36.526] -- File entry --
[11:49:36.528] Dest filename: C:Windowssystem32msvcr120.dll
[11:49:36.529] Time stamp of our file: 2013-10-04 23:58:24.000
[11:49:36.530] Installing the file.
[11:49:36.566] Successfully installed the file.
inno-setup
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
add a comment |
I don't know why, but when I try to copy a file from my install directory to system32, it fails to do so although it reads as successfully installing in Inno Setup. Here is my code:
[Files]
; specifies what files will be included in the installation
Source: "{src}..elt.properties"; DestDir: "C:elt"; Flags: ignoreversion; BeforeInstall: SetProgressMax(10);
Source: "{src}..msvcr120.dll"; DestDir: {sys}; Flags: onlyifdoesntexist;
I also wanted to include my log output as I thought it was strange that the time was so off for the file, I am writing this around 11 am on July 8 2016
[11:49:36.526] -- File entry --
[11:49:36.528] Dest filename: C:Windowssystem32msvcr120.dll
[11:49:36.529] Time stamp of our file: 2013-10-04 23:58:24.000
[11:49:36.530] Installing the file.
[11:49:36.566] Successfully installed the file.
inno-setup
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
add a comment |
I don't know why, but when I try to copy a file from my install directory to system32, it fails to do so although it reads as successfully installing in Inno Setup. Here is my code:
[Files]
; specifies what files will be included in the installation
Source: "{src}..elt.properties"; DestDir: "C:elt"; Flags: ignoreversion; BeforeInstall: SetProgressMax(10);
Source: "{src}..msvcr120.dll"; DestDir: {sys}; Flags: onlyifdoesntexist;
I also wanted to include my log output as I thought it was strange that the time was so off for the file, I am writing this around 11 am on July 8 2016
[11:49:36.526] -- File entry --
[11:49:36.528] Dest filename: C:Windowssystem32msvcr120.dll
[11:49:36.529] Time stamp of our file: 2013-10-04 23:58:24.000
[11:49:36.530] Installing the file.
[11:49:36.566] Successfully installed the file.
inno-setup
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
I don't know why, but when I try to copy a file from my install directory to system32, it fails to do so although it reads as successfully installing in Inno Setup. Here is my code:
[Files]
; specifies what files will be included in the installation
Source: "{src}..elt.properties"; DestDir: "C:elt"; Flags: ignoreversion; BeforeInstall: SetProgressMax(10);
Source: "{src}..msvcr120.dll"; DestDir: {sys}; Flags: onlyifdoesntexist;
I also wanted to include my log output as I thought it was strange that the time was so off for the file, I am writing this around 11 am on July 8 2016
[11:49:36.526] -- File entry --
[11:49:36.528] Dest filename: C:Windowssystem32msvcr120.dll
[11:49:36.529] Time stamp of our file: 2013-10-04 23:58:24.000
[11:49:36.530] Installing the file.
[11:49:36.566] Successfully installed the file.
inno-setup
inno-setup
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
edited Jul 9 '16 at 5:01
Martin Prikryl
91k22180385
91k22180385
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
asked Jul 8 '16 at 15:57
Dant.ADant.A
5213
5213
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
By default the {sys} (system32) is redirected to {win}SysWOW64 by the OS for 32-bit applications (like Inno Setup).
If your DLL is 32-bit, you actually want the redirection. The SysWOW64 is the System32 equivalent for Windows 32-bit emulation on Windows 64-bit. See also Inno Setup install to SysWOW64 in 32Bit mode.
If you do not want the redirection (because your DLL is 64-bit), you can override the redirect using the 64bit flag:
Source: "..."; DestDir: "{sys}"; Flags: 64bit
64bit: Causes the
{sys}constant to map to the 64-bit System directory when used in theSourceandDestDirparameters, .... This is the default behavior in a 64-bit mode install.
Or enable 64-bit mode install.
[Setup]
ArchitecturesInstallIn64BitMode=x64 ia64
In 64-bit mode:
- The System32 path returned by the
{sys}constant maps to the 64-bit System directory by default when used in the [Dirs], [Files], [InstallDelete], [Run], [UninstallDelete], and [UninstallRun] sections. This is because Setup/Uninstall temporarily disables WOW64 file system redirection when files/directories are accessed by those sections. Elsewhere, System32 and{sys}map to the 32-bit System directory, as is normal in a 32-bit process.
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
You should enable 64-bit mode if your application is also 64-bit. Otherwise use one of the other two options.
– Miral
Jul 10 '16 at 9:12
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f38270942%2ffile-dll-installed-to-sys-does-not-appear-in-c-windows-system32%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
By default the {sys} (system32) is redirected to {win}SysWOW64 by the OS for 32-bit applications (like Inno Setup).
If your DLL is 32-bit, you actually want the redirection. The SysWOW64 is the System32 equivalent for Windows 32-bit emulation on Windows 64-bit. See also Inno Setup install to SysWOW64 in 32Bit mode.
If you do not want the redirection (because your DLL is 64-bit), you can override the redirect using the 64bit flag:
Source: "..."; DestDir: "{sys}"; Flags: 64bit
64bit: Causes the
{sys}constant to map to the 64-bit System directory when used in theSourceandDestDirparameters, .... This is the default behavior in a 64-bit mode install.
Or enable 64-bit mode install.
[Setup]
ArchitecturesInstallIn64BitMode=x64 ia64
In 64-bit mode:
- The System32 path returned by the
{sys}constant maps to the 64-bit System directory by default when used in the [Dirs], [Files], [InstallDelete], [Run], [UninstallDelete], and [UninstallRun] sections. This is because Setup/Uninstall temporarily disables WOW64 file system redirection when files/directories are accessed by those sections. Elsewhere, System32 and{sys}map to the 32-bit System directory, as is normal in a 32-bit process.
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
You should enable 64-bit mode if your application is also 64-bit. Otherwise use one of the other two options.
– Miral
Jul 10 '16 at 9:12
add a comment |
By default the {sys} (system32) is redirected to {win}SysWOW64 by the OS for 32-bit applications (like Inno Setup).
If your DLL is 32-bit, you actually want the redirection. The SysWOW64 is the System32 equivalent for Windows 32-bit emulation on Windows 64-bit. See also Inno Setup install to SysWOW64 in 32Bit mode.
If you do not want the redirection (because your DLL is 64-bit), you can override the redirect using the 64bit flag:
Source: "..."; DestDir: "{sys}"; Flags: 64bit
64bit: Causes the
{sys}constant to map to the 64-bit System directory when used in theSourceandDestDirparameters, .... This is the default behavior in a 64-bit mode install.
Or enable 64-bit mode install.
[Setup]
ArchitecturesInstallIn64BitMode=x64 ia64
In 64-bit mode:
- The System32 path returned by the
{sys}constant maps to the 64-bit System directory by default when used in the [Dirs], [Files], [InstallDelete], [Run], [UninstallDelete], and [UninstallRun] sections. This is because Setup/Uninstall temporarily disables WOW64 file system redirection when files/directories are accessed by those sections. Elsewhere, System32 and{sys}map to the 32-bit System directory, as is normal in a 32-bit process.
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
You should enable 64-bit mode if your application is also 64-bit. Otherwise use one of the other two options.
– Miral
Jul 10 '16 at 9:12
add a comment |
By default the {sys} (system32) is redirected to {win}SysWOW64 by the OS for 32-bit applications (like Inno Setup).
If your DLL is 32-bit, you actually want the redirection. The SysWOW64 is the System32 equivalent for Windows 32-bit emulation on Windows 64-bit. See also Inno Setup install to SysWOW64 in 32Bit mode.
If you do not want the redirection (because your DLL is 64-bit), you can override the redirect using the 64bit flag:
Source: "..."; DestDir: "{sys}"; Flags: 64bit
64bit: Causes the
{sys}constant to map to the 64-bit System directory when used in theSourceandDestDirparameters, .... This is the default behavior in a 64-bit mode install.
Or enable 64-bit mode install.
[Setup]
ArchitecturesInstallIn64BitMode=x64 ia64
In 64-bit mode:
- The System32 path returned by the
{sys}constant maps to the 64-bit System directory by default when used in the [Dirs], [Files], [InstallDelete], [Run], [UninstallDelete], and [UninstallRun] sections. This is because Setup/Uninstall temporarily disables WOW64 file system redirection when files/directories are accessed by those sections. Elsewhere, System32 and{sys}map to the 32-bit System directory, as is normal in a 32-bit process.
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
By default the {sys} (system32) is redirected to {win}SysWOW64 by the OS for 32-bit applications (like Inno Setup).
If your DLL is 32-bit, you actually want the redirection. The SysWOW64 is the System32 equivalent for Windows 32-bit emulation on Windows 64-bit. See also Inno Setup install to SysWOW64 in 32Bit mode.
If you do not want the redirection (because your DLL is 64-bit), you can override the redirect using the 64bit flag:
Source: "..."; DestDir: "{sys}"; Flags: 64bit
64bit: Causes the
{sys}constant to map to the 64-bit System directory when used in theSourceandDestDirparameters, .... This is the default behavior in a 64-bit mode install.
Or enable 64-bit mode install.
[Setup]
ArchitecturesInstallIn64BitMode=x64 ia64
In 64-bit mode:
- The System32 path returned by the
{sys}constant maps to the 64-bit System directory by default when used in the [Dirs], [Files], [InstallDelete], [Run], [UninstallDelete], and [UninstallRun] sections. This is because Setup/Uninstall temporarily disables WOW64 file system redirection when files/directories are accessed by those sections. Elsewhere, System32 and{sys}map to the 32-bit System directory, as is normal in a 32-bit process.
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
edited Jul 23 '18 at 9:12
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
answered Jul 8 '16 at 16:35
Martin PrikrylMartin Prikryl
91k22180385
91k22180385
You should enable 64-bit mode if your application is also 64-bit. Otherwise use one of the other two options.
– Miral
Jul 10 '16 at 9:12
add a comment |
You should enable 64-bit mode if your application is also 64-bit. Otherwise use one of the other two options.
– Miral
Jul 10 '16 at 9:12
You should enable 64-bit mode if your application is also 64-bit. Otherwise use one of the other two options.
– Miral
Jul 10 '16 at 9:12
You should enable 64-bit mode if your application is also 64-bit. Otherwise use one of the other two options.
– Miral
Jul 10 '16 at 9:12
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f38270942%2ffile-dll-installed-to-sys-does-not-appear-in-c-windows-system32%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
