mikephn

I recently started a topic asking if I can detect a window by class, and I sure can. I want to detect a 'Save As' window when it appears, but I can't do it by name (it will be different in different languages of Windows). The problem is that Save As has a general class of 'dialog box'. There can be many of them already present. How do I differentiate between those I don't care about, and 'Save as'?

Thanks! (Answer was: You can set [CLASS:xyz] as a title)

I'm having trouble making my script work with different versions of Windows. Here's an example: 1. Script clicks on save button in a program, waits until 'Save As' window opens 2. Script clicks 'Save' Now assume the user isn't using English version of Windows. The window title won't be 'Save As', and the button won't say 'Save'. With a button it's ok, I can use ControlClick and pass the ID. But what's the alternative to using WinExists?

Many thanks

I'm automating the execution of a program. When it runs it does its thing, and then presents the results. Unfortunately, the only clear indication that it finished is that a WindowsForm10.STATIC text saying "Scanning" becomes hidden. In Window Info I can see the text moving from Visible Text to Hidden Text. However, I don't know how to tell if the control is hidden or not. How would you do it? Alternatively, I could check if a button that allows to progress further becomes active (it's grayed out when its scanning). Is that any easier?

The line is: DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1) Worked like a charm. Thanks a lot everyone!

The program that needs this .sys needs to have it in System32, and depending on the OS (64/32) I have two versions of the file to copy. I'm checking @OSArch to determine which one to copy, but the script needs to run on both 32 and 64 bit systems. My path actually is based on the Windows directory, because I also noticed that the system directory AutoIt gives is for sysWOW64. So my command is: FileCopy(@WindowsDir & "\System32\drivers\64b.sys", @WorkingDir & "\Win64\64b.sys", 9) FileExists(@WindowsDir & "\System32\drivers\64b.sys") returns 1, but the file is not there. It also doesn't appear in sysWOW64.

I'm trying to automate an installation and I need to copy a new .sys to system32/drivers. FileCopy and FileMove seem to make no changes, the file doesn't appear there after copying. Oddly enough, FileExists will tell me the file is there, when it's clearly not. The program that requires this .sys to be present also doesn't start. I have all files visible, including system, and I'm requesting admin rights at the beginning of the script. I run Win7 64-bit. So far I can only do it with a .bat being run by AutoIt, which is a bit pointless. Can anybody offer a solution and/or explanation? Many thanks Mike