topbanner_forum
  *

avatar image

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

Login with username, password and session length
  • November 21, 2019, 04:38 AM
  • Proudly celebrating 13 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

Author Topic: error findandrunrobot.ini is not a find and run robot configuration file  (Read 1178 times)

battus

  • Participant
  • Joined in 2016
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
Hallo,

I installed latest version 2.234.01 on windows10
When starting the application:
\\domain.local\homes\...\...\Documenten\Donationcoder\findandrunrobot\findandrunrobot.ini is not a find and run robot configuration file.

This file does not exist in this directory.

Closing the app:
Failed to delete previous temp file \\domain.local\homes\...\...\Documenten\Donationcoder\findandrunrobot\findandrunrobot.ini.tmp and
Error: could not write temporary file \\domain.local\homes\...\...\Documenten\Donationcoder\findandrunrobot\findandrunrobot.ini.tmp for saving

Findandrunrobot works all the same but i cannot save the changed HotKeys,

Any idea?

« Last Edit: May 22, 2019, 09:53 AM by battus »

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 39,528
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
It sounds like its not happy with your config files being on a network location.
If you edit the configdir.ini file in the C:\Program Files x86\FindAndRunRobot you can give it an alternative local drive directory to store all your settings and custom stuff, so it won't need to write to the network drive location.

battus

  • Participant
  • Joined in 2016
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
Hallo Mouser,

You are right.
Thanks a lot.

It's working now!

Regards Battus

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 39,528
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member

chaswill

  • Charter Member
  • Joined in 2005
  • ***
  • Posts: 3
    • View Profile
    • Donate to Member
Thanks, Mouser! I had the same problem, and it was easy to find the solution and apply a fix. I've been using FARR since 2010, and it's worked flawlessly the whole time.

I can only speculate, but I suspect installing the notorious Windows 10 1903 update is what messed things up. Using 1809, perfect, but after the final 1903 installation reboot, the config.ini message appeared when FARR started up.