Ackwell Posted February 1, 2010 Share Posted February 1, 2010 Hi, On X64 systems the @SystemDir macro delivers C:\Windows\system32 instead of C:\Windows\SysVow64 when compiled in 64-bit mode. I tried it both with AutoIt 3.3.4.0 and 3.3.5.1 beta. Regards, Ackwell Link to comment Share on other sites More sharing options...
Yashied Posted February 1, 2010 Share Posted February 1, 2010 (edited) Try using the following code.#Include <WinAPIEx.au3> $SystemDir = _WinAPI_ShellGetSpecialFolderPath($CSIDL_SYSTEMX86) ConsoleWrite($SystemDir & @CR)WinAPIEx.au3 Edited February 1, 2010 by Yashied My UDFs: iKey | FTP Uploader | Battery Checker | Boot Manager | Font Viewer | UDF Keyword Manager | Run Dialog Replacement | USBProtect | 3D Axis | Calculator | Sleep | iSwitcher | TM | NetHelper | File Types Manager | Control Viewer | SynFolders | DLL Helper Animated Tray Icons UDF Library | Hotkeys UDF Library | Hotkeys Input Control UDF Library | Caret Shape UDF Library | Context Help UDF Library | Most Recently Used List UDF Library | Icons UDF Library | FTP UDF Library | Script Communications UDF Library | Color Chooser UDF Library | Color Picker Control UDF Library | IPHelper (Vista/7) UDF Library | WinAPI Extended UDF Library | WinAPIVhd UDF Library | Icon Chooser UDF Library | Copy UDF Library | Restart UDF Library | Event Log UDF Library | NotifyBox UDF Library | Pop-up Windows UDF Library | TVExplorer UDF Library | GuiHotKey UDF Library | GuiSysLink UDF Library | Package UDF Library | Skin UDF Library | AITray UDF Library | RDC UDF Library Appropriate path | Button text color | Gaussian random numbers | Header's styles (Vista/7) | ICON resource enumeration | Menu & INI | Tabbed string size | Tab's skin | Pop-up circular menu | Progress Bar without animation (Vista/7) | Registry export | Registry path jumping | Unique hardware ID | Windows alignment More... Link to comment Share on other sites More sharing options...
KaFu Posted February 1, 2010 Share Posted February 1, 2010 I guess the macro result is correct:http://msdn.microsoft.com/en-us/library/aa384187%28VS.85%29.aspx"The %windir%\System32 directory is reserved for 64-bit applications. Most DLL file names were not changed when 64-bit versions of the DLLs were created, so 32-bit versions of the DLLs are stored in a different directory. WOW64 hides this difference using a file system redirector."As I understand system32 contains 64bit dlls and 32bit calls are redirected to SYSWOW64... but sounds strange to me too ... OS: Win10-22H2 - 64bit - German, AutoIt Version: 3.3.16.1, AutoIt Editor: SciTE, Website: https://funk.eu AMT - Auto-Movie-Thumbnailer (2022-Nov-26) BIC - Batch-Image-Cropper (2023-Apr-01) COP - Color Picker (2009-May-21) DCS - Dynamic Cursor Selector (2024-Feb-16) HMW - Hide my Windows (2018-Sep-16) HRC - HotKey Resolution Changer (2012-May-16) ICU - Icon Configuration Utility (2018-Sep-16) SMF - Search my Files (2023-Jun-03) - THE file info and duplicates search tool SSD - Set Sound Device (2017-Sep-16) Link to comment Share on other sites More sharing options...
Ackwell Posted February 2, 2010 Author Share Posted February 2, 2010 OK, thanks a lot for your quick and friendly replies. I really didn't know that and yes, it appears quite strange to me, too. Regards Ackwell Link to comment Share on other sites More sharing options...
Richard Robertson Posted February 2, 2010 Share Posted February 2, 2010 The reason the redirection is in place is that for years people have been using dlls with 32 in the name. For whatever reason Microsoft added these, it has now become a problem because everyone needs to use things like shell32 or kernel32. By making it automatically jump to the new files, that provides a cushion for the old programs to still run. Link to comment Share on other sites More sharing options...
KaFu Posted February 2, 2010 Share Posted February 2, 2010 (edited) Of course I see the necessity for the redirection… but why not just create a sytem64 directory for 64bit and let 32bit stay in system32? If the redirection mechanism can capture the calls by process architecture, sure that would’ve been a more logical way then putting 32bit dlls in a dir called SysWOW64 and 64bit dlls in the system32. Edit: Hmmm, one reason might be that the redirection has an impact on the overall performance and MS thinks most programs run on 64bit machines are 64bit... but I fear that's not nearly true looking on the processes in my taskmanager ... Edited February 2, 2010 by KaFu OS: Win10-22H2 - 64bit - German, AutoIt Version: 3.3.16.1, AutoIt Editor: SciTE, Website: https://funk.eu AMT - Auto-Movie-Thumbnailer (2022-Nov-26) BIC - Batch-Image-Cropper (2023-Apr-01) COP - Color Picker (2009-May-21) DCS - Dynamic Cursor Selector (2024-Feb-16) HMW - Hide my Windows (2018-Sep-16) HRC - HotKey Resolution Changer (2012-May-16) ICU - Icon Configuration Utility (2018-Sep-16) SMF - Search my Files (2023-Jun-03) - THE file info and duplicates search tool SSD - Set Sound Device (2017-Sep-16) Link to comment Share on other sites More sharing options...
Richard Robertson Posted February 2, 2010 Share Posted February 2, 2010 The real problem is that there is no easy bridge between 32 bit and 64 bit applications. If everything were compiled to match the OS, there wouldn't be any need for redirection. That's what I like about being able to compile programs from source... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now