Author Topic: FARR plugin: FARR Windows Search 0.3.0 (Read 144434 times)

Armando · « **Reply #100 on:** October 28, 2010, 11:13 AM »

Thanks...

The link seems to fscript.1.16.dll seems to be down though

Apart from that, I tried updating a few fscript just before, and now I have another problem... Some syntax error popup (involving JSON.parse) which I've never seen before. So I reverted to the old fscript, and...the problem is still there. I don't see what I did... Only replaced a few fscript.dll, and then put them back to their original version (I know they're right as I only renamed them to *.bk, and then back to *.dll)

Anyhow, I'll just wipe out my farr directory and reinstall a backup for today.
As for the version 1.16, I might try it, but... Only when I'll find it

Armando · « **Reply #101 on:** October 28, 2010, 11:22 AM »

Wiped out farr... The error is still there (the new one... JSON.parse). This is too weird for me today. I give up.

phitsc · « **Reply #102 on:** October 28, 2010, 01:46 PM »

As for the version 1.16, I might try it, but... Only when I'll find it
-Armando (October 28, 2010, 11:13 AM)

But it's there with the rest of them following the link you've posted (http://e.craft.free.fr/farr/FScript).

Armando · « **Reply #103 on:** October 28, 2010, 02:20 PM »

Ok, I see. But isn't it older than 1.20 ?? Anyhow, I'll try it, thanks a lot phitsc.

Armando · « **Reply #104 on:** November 19, 2010, 04:58 PM »

Wiped out farr... The error is still there (the new one... JSON.parse). This is too weird for me today. I give up.
-Armando (October 28, 2010, 11:22 AM)

Half an hour ago, I got fed up with the JSON.parse error and not being able to use the Timer plugin , so I decided to solve it. Turned out that something messed up my findandrunrobot.ini file and the json there was all messed up. I corrected the code there, and all is fine now.

However -- and I know it has nothing to do with the windows search plugin -- it's weird that the json syntax got messed up. Seems like some regex or json parser somewhere didn't do its job properly... Not sure where I should post that info... if you have an idea...

phitsc · « **Reply #105 on:** November 20, 2010, 02:12 AM »

Strange. But good you've solved your problem!

Armando · « **Reply #106 on:** November 20, 2010, 09:17 AM »

(That said, I still have the windows search problem...

)

phitsc · « **Reply #107 on:** November 20, 2010, 01:26 PM »

(That said, I still have the windows search problem... )
-Armando (November 20, 2010, 09:17 AM)

The crash you mean?

Armando · « **Reply #108 on:** November 20, 2010, 03:20 PM »

sorry... Yes.

CyberEvil · « **Reply #109 on:** January 05, 2011, 10:53 PM »

Hi phitsc, I've tried to make this work and finally worked! was getting the same crash as the one reported. To solve that part, picked up the latest FSbuscript dll from the plugin folder and replaced the rest. Before that, I wasn't able to search anything without crashing.
Now, I cannot bypass the oleaut32.dll error also described on this thread. As soon as I get results, navigating to the second item pops up the the oleaut32.dll error.

Any clue?

Thanks!

phitsc · « **Reply #110 on:** January 06, 2011, 02:10 AM »

I was of the opinion that the oleaut32.dll error was caused by not actually having Windows Search installed.

I think Vista and 7 have Windows Search installed by default. So I guess (hope) you're running XP? If so, make sure to install Windows Search 4.0. You can grab that from here.

A solution for the FSubscript problem is in planning. See here.

CyberEvil · « **Reply #111 on:** January 06, 2011, 06:47 AM »

Sorry, I'm on Seven Ultimate 64bit.

Thanks a lot!

CyberEvil · « **Reply #112 on:** January 06, 2011, 10:36 AM »

Maybe is a problem with 32 bit libraries against 64bit? This is the only plugin so far that is not working for me when scrolling the list (or selecting individual items for that matter).

Thanks for your help!

phitsc · « **Reply #113 on:** January 06, 2011, 10:40 AM »

Yeah, maybe oleaut32.dll isn't called oleaut32.dll in the 64bit version? Can you please check in your equivalent of C:\WINDOWS\system32 if there is an oleaut??.dll.

CyberEvil · « **Reply #114 on:** January 06, 2011, 10:45 AM »

Both, System32 ans SysWOW64 contains oleaut32.dll. Version says:
6.1.7600.16567

Thanks!

CyberEvil · « **Reply #115 on:** January 06, 2011, 01:02 PM »

Please let me know if I can provide any further test

TIA

CyberEvil · « **Reply #116 on:** January 06, 2011, 04:24 PM »

Problems solved!
For those looking for a solution:
http://e.craft.free....r/farr/FScript/1.20/

That's the one is working.

Thanks!

phitsc · « **Reply #117 on:** January 07, 2011, 02:04 AM »

Thanks CyberEvil! Does that mean using the version of FScript also resolve the oleaut32.dll problem?

CyberEvil · « **Reply #118 on:** January 07, 2011, 06:45 AM »

Hi, correct. No more crashing or oleaut32 errors, all working!
(you have to replace all entries on other plugins too)

Armando · « **Reply #119 on:** January 25, 2011, 04:46 PM »

I'm late to this thread. I had a problem with my DC related e-mail address and didn't receive notifications for that thread...

I'm eager to try this fix (thanks CyberEvil!)...

Question : Since this fscript.dll can be found in several places, where do I have to paste the v.1.20 ?

Thanks!

phitsc · « **Reply #120 on:** January 26, 2011, 05:02 AM »

Question : Since this fscript.dll can be found in several places, where do I have to paste the v.1.20 ?
-Armando (January 25, 2011, 04:46 PM)

I think what CyberEvil did was replace the dll in all of the places, i.e. in all Plugin-directories where you find it.

Armando · « **Reply #121 on:** January 26, 2011, 09:02 AM »

Thanks ! I think that's what I also did last time -- without success. But will try once more.

Armando · « **Reply #122 on:** January 27, 2011, 06:31 PM »

Ok, seems to work better, but I got an "EAccess violation" error after a short while.
Reported earlier in the thread :

https://www.donation....msg201385#msg201385

The dialog says to contact mouser...?

Armando · « **Reply #123 on:** January 27, 2011, 06:34 PM »

Here's what I get :

Screenshot - 2011-01-26 , 21_54_27.png

Note that this happened once when I was using Farr Windows Search, and and it also happened rather randomly when I was doing something else (browsing the wen, maybe) : farr crashed with that error. I wonder what that means.

phitsc · « **Reply #124 on:** January 28, 2011, 01:48 AM »

Would you mind disabling all other plugins for a while just to make sure it's not caused by any other plugin?