|
|
#1 |
|
Junior Member
Join Date: Aug 2007
Posts: 3
|
Bug report in Vista64
Hi!
On Windows XP64, the dlls are correctly copied \SysWOW64 instead to \System32, but on Vista 64, they again land in \System32. Consequently the apps can not find them because System32 is not in the path. Is there any update in sight that will fix this? Thanks! Atmapuri |
|
|
|
|
|
#2 |
|
M.I.A.
[NSIS Dev, Mod] Join Date: Oct 2001
Location: Israel
Posts: 11,343
|
Use ${DisableX64FSRedirection} from x64.nsh.
NSIS FAQ | NSIS Home Page | Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius |
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Aug 2007
Posts: 3
|
Hi!
That is the problem. The redirection is not working on Vista 64. It only works on XP 64. I dont want to disable the redirection. I would like to have it working ![]() Thanks! Atmapuri ; SetOutPath $SYSDIR ; ${DisableX64FSRedirection} ; File some.dll # extracts to C:\Windows\System32 ; ${EnableX64FSRedirection} ; File some.dll # extracts to C:\Windows\SysWOW64 |
|
|
|
|
|
#4 |
|
M.I.A.
[NSIS Dev, Mod] Join Date: Oct 2001
Location: Israel
Posts: 11,343
|
That's not documented anywhere. Redirection to SysWOW64 should still be available on Vista x64 and there shouldn't be anything NSIS can do about it. Are you sure you're not registering some DLL that disables it for the process? Can you post the minimal script that reproduces this issue?
NSIS FAQ | NSIS Home Page | Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|