Error EACCESSVIOLATION upon startup attempt for FindANDRun ???

[JamesUSA]

After enjoying good use of FIND AND RUN for several months, I am now unable to start the program. Every time that I click to start it, I receive the message "EACCESSVIOLATION".

I don't know where to begin to sort this out or understand it. Can anyone help?

I have done an uninstall and new install, and have downloaded the most recent version July 15.

Thank you!

James

[mouser]

that is really strange.. i've never heard of it.
i can think of 2 things to try:

1) move or rename the findandrunrobot.ini file to see if maybe there is something in your ini file making it crash.  if so, dont delete that file, but save it so you can help me figure out what about it it doesnt like.
2) if that files, try launching F&R through the start menu with the different techniques and see if some work and others dont.

has anything else changes on your pc?

[JamesUSA]

Mouser,

HAPPY CAMPER HERE!!

I renamed the INI file and it then started up. I will now test it after configuration.

Before that, I tried all starting methods via the Start Menu and none worked.

Yes, many things have changed on my system and do frequently. I try lots of different software. However, I didn't note at what specific time Find and Run developed the problem.

I still have the renamed INI file. Is there some email address to which I could send it to you?

Thanks!!

James

[mouser]

yes please: mouser@donationcoder.com

its a text file, so please do open it and view it in any text editor just to make sure that for whatever reason it doesnt have any info or files that you wouldnt want to send before you do send it.  it shouldnt but never hurts to check.

seeing it might help me reproduce the problem and figure out what's wrong for the future, thanks!

[mouser]

james, don't forget to send me that config file if you get a chance.

[jballi]

Found this thread after I experienced this problem again.  I hate to admit it (since I like the program a lot) but I experience this problem a lot more often than I would like.

For me, the EAccessViolation error is an indication of a corrupted configuration file.  I detest doing it but I make a copy of a valid configuration file so that I can quickly recover from this error.  I've found that the more often the configuration is updated, the more likely it will become corrupted.  For this reason, I've stopped adding launched files to the launch history, don't maintain a launch history, don't use aliases, and any time I make major changes to the configuration, I make a copy.  Since I've changes, the configuration file becomes corrupted much less frequently.

Currently using v1.05.21.  I also experienced the problem with an earlier version, I forget which one.

One thing that I do that others may not...  I launch F&R from a hotkey (AutoHotkey script).  I don't use the F&R System Tray Trigger.

[mouser]

if its being caused by a bad configuration file that becomes corrupted then that is great news - if you can share with me the configuration file.  it's just a text file, so you can edit it yourself and make sure it doesn't have anything sensitive before you send it to me.

and if you are keeping a backup to recorder, even better because youll have a recent example of a working version vs a newer version that causes a crash.

will you please suffer through and keep using the program until it happens again so that you can send me the example of a broken configuration file that causes the crash? it would let me solve the problem so it never happens again.

[jballi]

Files sent.  Let me know if you need any additional information.

Thanks for your assistance.

[mouser]

got it, thanks you -
the problem is that the configuration file did not save completely, as if the program crashed while it was exiting and saving it's configuration.  now the question is why..  do you remember what you did between the saving of the good and bad configurations?
maybe a good safety mechanism would be for me to always save the new config file as a temporary and then replace only after successful save.  this would be useful also as a kind of backup system.

[mouser]

new version should fix this i think and prevent it from happening again.
let me know if you do encounter it again after version 1.07.03