Opened on Jul 12, 2008 at 10:03:25 PM
Closed on Jul 21, 2008 at 10:00:55 PM
Last modified on Jul 22, 2008 at 12:00:06 AM
#438 closed Bug (Fixed)
Vista 64: ProgramDir
| Reported by: | Marc | Owned by: | |
|---|---|---|---|
| Milestone: | Future Release | Component: | Documentation |
| Version: | 3.2.13.4 | Severity: | None |
| Keywords: | Vista64 | Cc: |
Description
Hi,
under Vista64 we find two Program Files-Folders:
- Program Files
- Program Files (x86)
The help file suggests
@SystemDrive & "\Program Files(x86)"
But: The Macro @SystemDrive does not exist and there is a space missing before the "(x86).
Funny thing: When pressing F5, Scite launches the X86 Version from AutoIt (at least, I think so), because @programdir resolves to the x86 version.
If the .au3 script is started from the explorer, the x64 version is used and fails to find the program the script should launches.
Attachments (0)
Change History (3)
follow-up: 2 comment:1 by , on Jul 13, 2008 at 10:25:27 PM
comment:2 by , on Jul 21, 2008 at 10:00:55 PM
| Resolution: | → Fixed |
|---|---|
| Status: | new → closed |
| Version: | 3.2.12.0 → 3.2.13.4 |
Replying to Valik:
Funny thing: When pressing F5, Scite launches the X86 Version from AutoIt (at least, I think so), because @programdir resolves to the x86 version.
If the .au3 script is started from the explorer, the x64 version is used and fails to find the program the script should launches.
I did complete test under Vista64 and everything works as expected.
The reason why is Scite only launch the X86 version is because Scite is a 32-bit process
Replying to Marc:
You do not state where this is in the documentation but I found it none-the-less. I've fixed what you mention and a couple other issues. It no longer contains the mis-leading non-existent macro.
Hmm, is your Explorer the 64-bit version? If so, it's probably looking in "Program Files" which is where 64-bit binaries go. Since AutoIt installs the 64-bit binaries along-side the 32-bit binaries via a 32-bit installer everything goes into the "Program Files (x86)" folder. This sounds like a problem with how our installer sets things up, however.