avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Friday July 19, 2024, 8:21 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - SaschaM [ switch to compact view ]

Pages: [1]
Hi jesse,

thanks a lot for the wonderful software, it's a total time saver *thumbsup*.

I'll untick the box and will see if that changes anything. If not I will try the latest beta.

Have a great weekend!

Best, Sascha

I am using the most recent version of FARR and so far have only one thing to complain about:

my laptop is connected to two external displays, totalling in 3 used displays. When I disconnect the screens so that only the laptop display remains, FARR will no longer show up. The display settings of Windows 10 show that it properly disconnected the devices, there is only the remaining internal screen being shown. You can see that something is happening when using the FARR toggle key combination as the focus moves away from the currently active application when first toggling FARR and is being returned on the second toggling.
Problem also persists when I restart FARR. I have not tried if the error goes away if I restart Windows with no screens attached but that wouldn't be a working workaround as I don't want to restart my PC just to re-enable FARR.

Thanks a lot for any pointers :)

Thanks again for the continuous support! After the lunch break I booted into BIOS and changed my graphics card settings to use "Hybrid" rather than "Discrete graphics". I then configured Nvidia drivers to always use the Nvidia card in combination with FARR. Now it no longer pops up when locking up and logging in again.

I also tried your recommendation but this still shows FARR after the above lock/log in.

Thanks anyway, my problem is now solved :-). Have a great weekend!

Just checked your recommendations:

- when the external monitors are connected, FARR will pop up after logging in again
- when the external monitors are not connected, no window will pop up

So I think it has to be connected to the two different graphic adapters, one being the Intel HD graphics, the other is a Nvidia Quadro that is being used fornal monitors. I am just updating the drivers and will check if I can tell the PC to always use the internal graphics card to run FARR. Perhaps that'll fix things.

I'll definitely check this tomorrow when I'm back in the office. I kind of suspect our IT to have installed some software messing up FARR but we'll see about that. Will keep you posted and thanks for the feedback!

Hi mouser,

thanks a lot for the feedback :Thmbsup:. I can't remember if and which settings I had changed but please find attached the screenshots of the two asked windows. My laptop is connected totwo external monitors, one of the two is configured as Windows' Main Monitor.

Should I perhaps uninstall, remove the configuration files (in case they are preserved and not removed) and reinstall?


2019-06-13 17_55_29-Options.png
2019-06-13 17_55_45-Options.png


on my work laptop running Windows 10 x64 I experience a strange behavior with FARR:

if my computer was either locked or in sleep mode (which also causes locking up) after I log in the FARR search window is shown and can't be closed using the X button. If I use the hotkey to bring up FARR the window gains the focus and when hitting the hotkey again it is hidden again. I changed the memory usage setting from Average to "stay in memory" today and after logging out and in again the Settings dialog was shown instead of the FARR search window, the behavior was the same and the window couldn't be closed using either the OK button nor the window's X button.
It is not a big bug as I know how to handle it but a fix would still be nice, though :-)


in my case I had to force FARR to run on the Nvidia graphics card rather than using the internal Intel graphics card.

Pages: [1]