MBrand

I have a similar problem now. Did you find a solution? Thanks in advance.

In order to have a proper solution I tried DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1) at the top of the code but it didn't work...

Hi, thanks for the fast reply. I found a solution for the same issue in a python Forum. It's probably a Windows problem. It wont't work even with the proper & full path. So I copied defrag.exe from system32 to the sysWOW64 directory and it worked immediately. Added a hint for the user: If @OSArch = "x64" Then $szMsg = $szMsg & " ggfls. defrag.exe ins DIR sysWOW64 kopieren" EndIf

Hi there since hours I can't find the solution to this problem: I try to check with defrag c: -a if defragmentation is necessary. $str_l = "C:\" Local $RunCMD = @ComSpec & " /c " & @SystemDir & "\defrag.exe " & $str_l & " -a" Local $f01 = Run($RunCMD, @SystemDir, @SW_MINIMIZE, $STDERR_MERGED + $STDOUT_CHILD) That works fine with XP and Server 2003 32bit. When I start it on a 2003 64 bit machine, I always get the following error: 'C:\WINDOWS\SysWOW64\defrag.exe' is not recognized as an internal or external command,operable program or batch file. So I tried several different ways to give the correct path with the run command, like @WindowsDir & "\system32\defrag.exe", also in the Run-Workingdir Parameter without any success: (and C:\WINDOWS\system32\defrag.exe is definitely the correct path!) 'C:\WINDOWS\system32\defrag.exe' is not recognized as an internal or external command,operable program or batch file. The Example code works, when I compile the script for x64, but then it won't work on x32 machines. But I need ONE script for both systems.... Any suggestions? Thanks a lot!

Thanks for the fast answer. I'm going to test your dll as soon as possible. In the meantime changing the default printer will do...(I hope) Michael

Thank You for this handy udf & dll. I only have this one problem with them: It all works fine with the DefaultPrinter under W2K and also with _PrintSelectPrinter under WXPProf. But _PrintSelectPrinter with W2K doesn't work: the Printer receives the job but goes into some strange paper-out-error. I think this has to do with either _PrintSelectPrinter or with W2K , for the print (contents, size) is always the same. Any idea? Thanks Michael

I solved the Problem with If Not IsAdmin() Then RunAsSet($AdminName, $DomainName, $AdminPWD) EndIf

I checked RunAsSet: the "Secondary Logon service" or "RunAs service" is running. Also I'm logged on with administrative rights....

Thank you very much for all the ideas. I just got closer to the solution now. In my AutoIT Code I had this line a few lines above the RunWait command: RunAsSet($AdminName, $DomainName, $AdminPWD) Disabling this line makes the whole thing work fine. Now I only have to find out why. The idea of my AutoIT script is to have a tool for us few Admins in our company that centralizes softwareinstallation (and more) and that is easy to configure (I don't want to compile the Script each time I add or change an installation, until today it worked fine for nearly 2 years). So my "AutoAdmin" manages from a simple config file all our batches (and e.g. command-lines you need twice a year an then you have forgotten what it was). Changes in the config-file are easy to be done with an editor and then it works immediately. That's the reason for splitting it into AutoIt and Batches or whatever. Also it puts all this seperate commands into one GUI. A few lines from the Config file: [Prog24] Name=FoxITReader CMD=$INSTSERVER\REMINST\AutoInst\FoxIt\Foxit.bat $INSTSERVER\REMINST\AutoInst\FoxIt LongText=Schneller, kleiner PDF Reader - Freeware

Hi, I have a (tested & working) batch that installs Foxit reader 2.2. When I call this Batch from AutoIT, it doesn't work - but only the msiexec-line does not work properly. The msiexec-installation starts an does something (Progressbar), but for example the shortcuts in the Program-menue are missing. The (proper working) Batch is: msiexec.exe /i \\AUR-S-FS002\REMINST\AutoInst\FoxIt\foxitreader22.msi /passive <--This line is not proper working copy \\AUR-S-FS002\REMINST\AutoInst\FoxIt\lang_de_de.xml "%PROGRAMFILES%\Foxit Software\Foxit Reader" "%PROGRAMFILES%\Foxit Software\Foxit Reader\Foxit Reader.exe" -register regedit /s \\AUR-S-FS002\REMINST\AutoInst\FoxIt\Foxit.reg The code in AutoIT3 is: $val = RunWait(@ComSpec & " /c " & $cmd,@TempDir,@SW_MINIMIZE) where $cmd gets replaced by the name of the Batchfile Has anyone an idea? Thanks a lot Michael

Hi amel27, I managed to integrate your _Filopen function successfully into my autoit-scripts and they worked fine with WXP. But today I tried them on 2 W2K machines and the $ret, $ret[0] and $ret[1] is always empty. W2K uses an older version of the comdlg32.dll. So is there a chance to get the filname someway by changing the script? Michael