Opening a program on my system takes maybe 0.2 seconds. But then it takes about two more seconds for the "move window to next monitor" button to appear on the titlebar. Is that delay normal? Any way to speed it up? Thanks.

here you go

Just did a test of the delay and got this:
Two second delay
-----------------
lotus 1-2-3
firefox
irfanview

Zero delay (move window to next monitor button appears at the same time as the rest of the titlebar)
-------------
chrome
notepad
explorer
internet explorer
ccleaner
mspaint
microsoft excel
ultraiso

btw - On my system all of these programs load pretty much instantaneously, maybe .1 or .2 seconds

Then I was curious about what made the top three programs unique so I ran a few scenarios using just irfanview. Here is what i found

1) If I load irfanview by going into my start menu and navigating to the shortcut and INSTEAD of hitting left click like I normally would, but instead selected "right click-open" (I made a screenshot of it below to show what I mean), the program load instantly AND the "move window to next monitor button" ALSO loads instantly. Further, going to the actual program file using explorer and clicking on the exe file directly (whether with a left double click OR a right-click-open) ALSO loads both the program and the move window button instantly.

2) But if I load irfanview that way I normally do, by navigating to its shortcut within the start menu and hitting left click, THEN the program loads instantly BUT the move window button appears two seconds later.

So then I wondered if maybe this had something to do with irfanview's need to load its ini file or its plugins, so I deleted both and re-ran items 1 and 2 above, and the result were the same as before.

Edit: One more data point. Disabling my AVG antivirus also had no impact on the results

Edit #2: Everything within 1) & 2) above also applies to lotus 1-2-3. It also applies to firefox IF I use a blank page as my home page. But if I use an internet page as the home page (mine is www.google.com), the move window button appears only after a delay no matter whether I start it from a menu shortcut or even using right-click-open on the exe file. It appears the menu button waits for the page to load no matter what. And yet on chrome and IE, the move window button appears instantaneously, prior to the home page loading, no matter what method I use to start the program.

log attached. By the way the delayed appearance of "move window to next monitor" also occurs when I load the DF settings window itself.

Thanks for the idea. I tried it, rebooted, but the delay is still there.

delay also still there with beta 3

Good call. After making that change and rebooting Firefox now has the button appearing immediately on program load. Irfanview and Lotus 1-2-3 still do have the delay.

still working on this, thanks for the feedback

Thanks for digging into this. I think I have fixed it but have no clue why so if you want to weigh in on why the below works I would be appreciative.

Lotus 1-2-3 has the delay even without the compatibility rule in place. But based on your point that irfanview relies on DF polling since it briefly enters a not responding state upon startup, I tried doing a few things to see if I could get the two programs to load more quickly. Starting them with realtime priority did not make a difference. Then I came across the tweak of appending the shortcut program path and file name with the argument /prefetch:1. That eliminated the delay in lotus BUT also produced an error message of REFETCH:1 file does not exist. It was as though the shortcut was able to digest the /p, but not the refetch:1. So then I tried changing the shortcut to just c:\lotus\123\123w.exe /p. No idea what a /p does, but we're just trying whatever here. Lo and behold lotus then starts with the same instant speed, produces no error message, and the move window to next monitor button appears instantly. Then I changed the irfanview shortcut to also include a /p and it also now has no delay for the button to appear. No idea why this is working, but I will take it.

The image below describes the above. The /p argument does not appear to do anything, other than eliminate the move window button delay!