I checked and have Code: :OriginalRunOnceSync=Yes Strange, the setting has been always like that, and it worked fine until a few builds ago (no idea if Windows or MRP, as I update them together). Would No be better here? Remember, once all MRP windows have passed, next reboots work correctly for all autorun. Also note that when it worked earlier, Explorer would load, including Taskbar and background+icons, and MRP windows would run to completion inside of Explorer shell. Now, the MRP windows run to completion on a blank desktop with no Taskbar, background, or icons. Only after they close, Explorer loads, and none of the other startup tasks execute. Next thing, the config creator v62 does not work for me, errors as follows:
From the ini file: Code: # This switches RunOnce mode to asynchronous or in sequence from the newer synchronous or all at once. # Hopefully should reduce failures of 3rd party files/scripts that normally be run all at once and cause # timing issues due to them being run out of order in which you want them to be run etc. # This may cause setup to take longer or shorter to complete depending on your programs etc being run/installed. # When MRP's Addon Manager is running the Desktop, Start Menu and Taskbar will not be shown until MRP has completed. # The TitleBar/Highlight colors and some theme elements may not be active until a reboot/signout-in cycle is performed. # Default is No. :OriginalRunOnceSync=No With w7 you would get that little box appear where it listed all your runonce lines/programs as they was being run or installed with a non shown desktop until it finished the list of tasks. If i remember there was a possible timing issue before so i added in that option to help with the way w10+ runs things at final oobe stage. Maybe m$ messing about with that again -- anything to get to desktop faster in their eyes! Will look into that variable error, thought i had caught all them
Alienware has reasonable desktop images and logos The User810 is transparent(ish) looked ok on a test install when i selected Alienware in the creator to be used instead of automatic as the pc i tested on was a asus. Click and drag the picture above around to see how it looks
Hmm in the creator, for that error, cant find that line reference i think it because the release version's internal .au script was shorter so the lines was moved up.. But it seems to be in the DPI Aware function(s) area as they are the last sections in the .au3 script, odd as those functions have been tested by the person who created them... Will investigate but it harder when you not wrote the code and have to work out how it works first before 'fixing' If you have more than 1 monitor connected setup then that may be the problem as i only look at the first, or the desktop that the program is run on.
OK, Scaling is greyed out, need to check ... BUT: I changed one FHD to 720p and fastly moved the GUI - no hickups. Looks as expected. You can check yourself .
I can decompile the creator's exe with all #includes in it so it should be in alignment, but i had made some slight changes to the creator before i released in the MRP archive, must of been enough to throw the calculation out a bit but its certainly in that dpi function(s) area at the end.
Just installed AHK , however with autoit i got some example scripts but with AHK sod all there is a template thing but that's empty too I did have a quick play and got a simple input thing to work but will take me a while to work things out plus try and convert over using the new syntax...
Sent you App-Pass and link for my Nextcloud in our convo, Total Commanders (Desk/Android) have a WebDAV AddIns, needs the link and the app-pass. Folders are under Tools MRP.Project, you will see.
Good call! Didn't even notice the lines had changed. New error message: Only one monitor, 31.5", UHD, DPI 100%.
Strange But it certainly in the dpi aware section... (line number's code in red below) Code: Func _GETDPISCALE() Local $AMONITORS = _WinAPI_EnumDisplayMonitors() If Not IsArray($AMONITORS) Then Exit MsgBox(0x0, "", "EnumDisplayMonitors error") Local $ADPI, $_FAKE For $I = 0x1 To $AMONITORS[0x0][0x0] $ADPI = _WINAPI_GETDPIFORMONITOR($AMONITORS[$I][0x0], $MDT_DEFAULT) $_FAKE = IsArray($ADPI) Next #forceref $_FAKE Return $ADPI[0x0] EndFunc ;==>_GETDPISCALE Func _WINAPI_SETPROCESSDPIAWARENESS($DPIAWARE) DllCall("Shcore.dll", "long", "SetProcessDpiAwareness", "int", $DPIAWARE) If @error Then Return SetError(0x1, 0x0, 0x0) EndFunc ;==>_WINAPI_SETPROCESSDPIAWARENESS Func _WINAPI_GETDPIFORMONITOR($HMONITOR, $DPITYPE) Local $X, $Y Local $ARET = DllCall("Shcore.dll", "long", "GetDpiForMonitor", "long", $HMONITOR, "int", $DPITYPE, "uint*", $X, "uint*", $Y) If @error Or Not IsArray($ARET) Then Return SetError(0x1, 0x0, 0x0) Local $ADPI[0x2] = [$ARET[0x3], $ARET[0x4]] Return $ADPI EndFunc ;==>_WINAPI_GETDPIFORMONITOR Damn arrays