avatar image

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

Login with username, password and session length
  • Sunday October 25, 2020, 8:35 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 - ghfhhghdfghghghsa [ switch to compact view ]

Pages: [1]
I did a bit more testing. It happens even if the file exists on the file system, but only when the option in FARR is disabled. It doesn't appear to actually log anything on exit, which is when the issue seems to occur. It has also started happening on my Windows 8.1 system, which makes me think something in my environment has changed, but nothing has really changed recently. Here is everything logged on my system while the log is enabled for a start then exit (which is all I need to do to reproduce the issue with the log disabled):

::: [ Starting Find and Run Robot v2.226.01 on Friday October 30, 2015 at 03:32:31 PM ] :::
*Loading plugin: FCalc\FCalc.dll
::: [ Program ends on Friday October 30, 2015 at 03:32:54 PM ] :::

Exiting the application seems to be a good trigger, I'd say 95% of the time when right clicking the tray icon and selecting "Exit Find and Run Robot" I get the exception, but only when FCalc is installed and the troubleshooting log is disabled. The exception pops up 6 times - always the same addresses, then a popup saying "Abnormal program termination". It could actually be 100% of the time, but I'm not certain of that. I'm running portable off a USB stick. The very same stick works without issue on Windows 8, I switch between a few different systems, it's only the Windows 10 installs that are a problem. It does the same thing when run elevated.

It's probably not a big deal, the primary reason it annoys me is because I run off a USB stick. I exit FARR when I need to eject the stick (usually in a hurry), and it crashes almost every time. I disable the troubleshooting log because I sync the USB stick, and I like to keep the list of files that have to be synced every time to a minimum.

Anyone else having issues with FARR crashing on Windows 10 with FCalc installed? Still works fine on Win8. On Win10, intermittently I get "Access violation at address 63278250. Read of address 63278250.", most often when closing FARR. HOWEVER, this only appears to occur when the troubleshooting log is disabled, which is very frustrating as I don't want to leave the troubleshooting log enabled and also means when it crashes there is no log. Any ideas?

Find And Run Robot / Re: Custom Document Opener
« on: October 19, 2015, 04:15 PM »
Awesome, thanks mouser. Excellent support, time for me to send you some money, your apps are awesome and have been very helpful. Sorry on the delay getting back to this post, but I think using the syntax "\fullpathwithoutdrive" works if you want it relative to the drive FARR is on, but allowing the use variables would be a very nice addition, also in the "override default browser" and "default file explorer" would be good too, the same workaround seems to work there too. I've not had a chance to pull down the latest update to check out if this works, I'll have a crack at it over the next week or so.

Find And Run Robot / Re: Compatibility with Windows 10
« on: August 17, 2015, 05:15 PM »
Works on Windows 10 for me too, however, I had to disable the FCalc plugin as it was crashing. Anyone else having problems with FCalc?

Find And Run Robot / Re: Custom Document Opener
« on: July 31, 2015, 05:17 AM »
Sorry to drag up an old post, but this doesn't seem to be answered and I'm having the same problem. Anyone have an answer on this? Thanks.

Pages: [1]