Leaderboard

The back story: I've got a Dell XPS w/ i7-8700K. The fastest, by single core, I could get, by well known PC maker. The problem is that the fan can get so loud, like, REALLY LOUD, I can not use the CPU at its max. clock speed. I could leave it at 90% all the time and not use this but I want to have the full 4.x Ghz and no parked cores, at all times, if I can. But as room temperature and CPU load changes, a set throttle, may still make fan noise. The solution: To avoid the fan from going "airplane turbine mode", the utility gets the temp. from "Core Temp" ( you can google it ) It has a"plug-in" called "Core Temp Remote Server". The utility gets the values via TCP. When it "feels" it's gonna get hot, drops the CPU throttle to a selected value, lets say 99% ( where is quieter ) and back up to 100% when it "feels" is ok to go back. Now temperature can creep up to higher than expected if load is sustained or room temperature changes. So there is an "anti creep up" feature, to temporarily set the throttle even lower, 5% at a time, until the known quiet temperature is achieved. If don't know how to find the temperature you should use, check out these videos. They will tell you how. https://www.youtube.com/watch?v=p3B5WCJZTuw&ab_channel=SergeantPope-KomadaComputerRepair https://www.youtube.com/watch?v=VuP6I0mOb1s&ab_channel=Techquickie https://www.google.com/search?q=find+max+cpu+temperature The end result: Any thermal problem, is a hardware problem. No way around that, other than attending to the CPU cooling and case ventilation. Software can not fix that. But without this utility, the PC would slow down the CPU anyway, to keep it from melting. This software preemptively slow down the CPU, keeping the CPU related fan speeds from going to maximum RPM. Hence having a slower, but a quieter box. The files are in the download section of the forum.

Activate("Title of your app")  WinWaitActive("Title of your app")  Send("^{F2}") ; Ctrl+F2 Send("{Enter}") Sleep(7000) ; 7 seconds Send("{Enter}") Sleep(7000) Send("{Enter}") Sleep(3000) Send("{Enter}") Sleep(3000) ; ...

you can also introduce a "watchdog" service - a script scheduled to run at startup under the local SYSTEM account, constantly running in the background, monitoring the active processes. it it finds that your app is running only one time, under the dedicated user account - this is OK. if your app is not running (closed by the user, or the user has logged off) - start the app under the local SYSTEM account, so even though it is not accessible to users, it is still functional. if it is running under the local SYSTEM account, and another instance is detected under the dedicated user account - let it run and close the instance running under the local SYSTEM account. this way, at all times, there is only one instance of your app running, and is accessible to users.

I can't imagine that the problem gets caused by the AutoIt script as it does not automate the GUI (and hence might interfere with other programs). Can you test with another Excel workbook that dos not run a macro?

As you use AutoIt to open the Excel workbook you could use the returned object to wait for the close event (untested): #include <Excel.au3> $sFileName = @TempDir & "\[UPDATED]Standard Stock Requistion 06122018 - 06152018.xlsm" FileInstall("C:\Documents and Settings\MPC\Desktop\[UPDATED]Standard Stock Requistion 06122018 - 06152018.xlsm", $sFileName, 1) $oExcel = _Excel_Open(False) ; Open Excel invisible $oExcel.AutomationSecurity = 1 $oWorkbook = _Excel_BookOpen($oExcel, $sFileName) ObjEvent($oWorkbook, "Workbook_") $bExit = False While 1 ; Wait until the workbook gets closed Sleep(10) If $bExit Then Sleep(500) ; Make sure that Excel has closed FileDelete($sFileName) Exit EndIf WEnd Func WorkBook_BeforeClose($bCancel) $bExit = True EndFunc

You could use the AutoIt script to wait for this event and then delete the Excel file.

Look at FileInstall to include the excel file with the script. When the script runs you can output to a temp directory, then delete when finished.

I have worked with applications that use Thunder Forms. You can use ControlCommand to work with them. Give this code sample a try. Global Const $sDialogTitle = "[CLASS:ThunderRT6MDIForm]" Global Const $sDialogText = "" Global Const $sControlUseBillTemplate = "[CLASS:ThunderRT6CheckBox; TEXT:Use Bill Template]" If ControlCommand($sDialogTitle, $sDialogText, $sControlUseBillTemplate, "IsChecked", "") Then ControlCommand($sDialogTitle, $sDialogText, $sControlUseBillTemplate, "UnCheck", "") MsgBox(0, "Test", ControlCommand($sDialogTitle, $sDialogText, $sControlUseBillTemplate, "IsChecked", "")) EndIf Adam

Func OverlayWindow($hwndParent, $rectToHighlight, $rectForText, $textToWrite) $style = $WS_POPUP $exstyle = BitOR($WS_EX_TOPMOST, $WS_EX_TRANSPARENT, $WS_EX_LAYERED) $hGUI = GUICreate("transparent overlay", 420, 420, 0, 0, $style, $exstyle) GUISetBkColor(0x112233) _WinAPI_SetLayeredWindowAttributes($hGUI, 0x112233, 0, $LWA_COLORKEY) ConsoleWrite("**** $hGUI: " & $hGUI & @CRLF) ...

if you want something fun to work on - Look at the Vollatran project and see if you can contribute to it. Things you could do: Add language support for your language and other languages like French, Spanish, and so forth. Add Windows 8 and Windows 10 support Add uninstall app support Make the GUI tool to edit INI files that Vollatran uses. Link is in my signature.

@jaberwacky: your script has a memory leak in function _draw_circle. Must be Func _draw_circle(Const $hGraphic, Const $x, Const $y, Const $diameter, Const $color) Local Const $hPen = _GDIPlus_PenCreate($color, 3) _GDIPlus_GraphicsDrawArc($hGraphic, $x - ($diameter / 2), $y - ($diameter / 2), $diameter, $diameter, 180, 360, $hPen) _GDIPlus_PenDispose($hPen) ;add this line otherwise memory leak because pen handle will be created everytime when function is called with disposing it! EndFunc