topbanner_forum
  *

avatar image

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

Login with username, password and session length
  • Sunday April 5, 2020, 12:10 am
  • 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 - rustymonkey [ switch to compact view ]

Pages: [1]
1
Find And Run Robot / Re: Aliases don't appear in History
« on: July 11, 2019, 09:10 PM »
Thanks for considering this feature, and for the tips!

-Rusty

2
Find And Run Robot / Aliases don't appear in History
« on: April 14, 2019, 11:51 AM »
Hi,
I'm been using farr as a portable app for years--and love it, but I have one longstanding annoyance that I was hoping someone can help with. When I set up an alias (e.g. for 'capture' to  %APPDRIVE%\PortableApps\FSCapture\FSCapture.exe or to D:\PortableApps\FSCapture\FSCapture.exe ) and then use the alias, no entry for FSCapture.exe appears in the History list. The History list works as expected for non-aliased entries.

The following are enabled in History options (these are the defaults afaik):
-Add launched file to launch history
-Blank search shows files from launch history in initial results
-Ignore History Scores on Blank Display
-Keep track of search string history

Any ideas how to solve this?

Thanks!

-Rusty

3
Hi,

I just tried updating to FARR Portable 2.223.01 (on Win 8 ), but when I attempt to run the .exe, I get a windows error:

Windows smartscreen prevented an unrecognized app from starting. Running this app might put your PC at risk.
Publisher: Unknown Publisher
App: FindAndRunRobot.exe

Upon examining the certificate associated with the .exe it seems that Windows considers that "One of the countersignatures is not valid. The file may have been altered". See images re. the cert below.

FARR_cert1.jpgFarr_cert2.jpg

Any idea what the problem might be? I've reverted to my previous version for now (it doesn't exhibit this issue).

Thanks for a great app!

-Rusty

4
Find And Run Robot / Re: Drive gets lost / disappears
« on: October 01, 2013, 08:48 AM »
OK--thanks for confirming that it's a software issue.  I'll give the beta a try as soon as I see it.

Please keep in mind that the solution should hopefully still support a portable drive. i.e. The K: drive is portable, and the Q: drive is also portable in the sense that it is a truecrypt drive on K:

Anyhow, thanks again for all your efforts.

-Rusty

5
Find And Run Robot / Drive gets lost / disappears
« on: September 02, 2013, 11:44 AM »
Hi,

First of all, I just want to say that I love FARR, have been using it for a couple of years, and want to congratulate mouser and any other contributors on a great piece of software.

I'm having a problem with FARR (in fact I've always had this problem), and it was kind of bugging me today, so I figured I'd ask--I'm not sure if it's a bug or user issue.  Some background: I have farr installed as a portable app.  My machines typically have a K: drive that's unencrypted, and a Q: drive that's encryped (it's a Truecrypt drive).  My FARR search folders contain both K:/Apps and Q:/Apps.  My problem is that each time I restart my machine (and hence FARR) the Q:/Apps gets changed to K:/Apps (so that there are 2 K:/Apps entries in the search folders).

All other search folders (on both the K and Q drives) are correctly saved--the only problem occurs with the folders described above.  Is there an issue in which FARR gets confused by identically named directories that are on different drives?

My workaround is to edit that particular search folder entry each time I restart, but that's a bit of a pita, and I'm hoping that someone has a more permanent solution.

Thanks.

Pages: [1]