If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Hello all,
On XPsp3 I would like to be able to re-execute a previous saved search (a ..FND file), but notice that it always forgets the "look in:" (the starting folder) field, and defaults to searching all "the local hardrives" from the root. Further more, it always opens with the "search options - type" subselection - nether of which I normally select. One thing I think I should metion: I've disabled the "indexing service". Two questions: 1) Can I "repair" this ? A registry setting perhaps ? 2) Does anybody have a description of the (possible) contents of such anXP style FND file ? (I already got a W98 version description, but the XP one looks to be different) Regards, Rudy Wieser |
Ads |
#2
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
On 2019-9-29 0:19, R.Wieser wrote:
Hello all, On XPsp3 I would like to be able to re-execute a previous saved search (a .FND file), but notice that it always forgets the "look in:" (the starting folder) field, and defaults to searching all "the local hardrives" from the root. Further more, it always opens with the "search options - type" subselection - nether of which I normally select. One thing I think I should metion: I've disabled the "indexing service". Two questions: 1) Can I "repair" this ? A registry setting perhaps ? 2) Does anybody have a description of the (possible) contents of such anXP style FND file ? (I already got a W98 version description, but the XP one looks to be different) Thanks for mentioning of this feature. I never heard of it. I tried and it works here. Have you tried open the fnd file with a text or hex editor? I see the starting folder string appears in the file twice, first ASCII then Unicode. Then maybe check registry HKEY_Classes_Root\fndfile\shell\open item. -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
#3
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Lu Wei,
Thanks for mentioning of this feature. You're welcome. :-) (Didn't know about it until just a few weeks ago myself). Have you tried open the fnd file with a text or hex editor? I see the starting folder string appears in the file twice, first ASCII then Unicode. Yep, and have already, with the help of that W98 document I menrioned, split the file into its parts. And yes, the XP version contains both the ASCII as well as an Unicode part. /Both/ need to be there, even though the ASCII part isn't used. The problem is that the search-origin path does not seem to be stored in the saves I've created, and adding it as described in the W98 document causes the search to start fully empty. Then maybe check registry HKEY_Classes_Root\fndfile\shell\open item. I just did. I assume that the "ddeexec" entry is used, as the "command" entry does not show any parameters. But, as you now have put my eye on it, do you have any idea what [OpenFindFile("%1", %I)] does ? "%1" is ofcourse the .FND file, but "%I" ? (a quick google didn't turn up anything). Regards, Rudy Wieser |
#4
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
On 2019-10-5 15:12, R.Wieser wrote:
... Then maybe check registry HKEY_Classes_Root\fndfile\shell\open item. I just did. I assume that the "ddeexec" entry is used, as the "command" entry does not show any parameters. But, as you now have put my eye on it, do you have any idea what [OpenFindFile("%1", %I)] does ? "%1" is ofcourse the .FND file, but "%I" ? (a quick google didn't turn up anything). I don't know what "ddeexec" entry is for and its syntax. In my experiment it is necessary for fnd file to function. My "ddeexec" entry is: ------------------------------------------------- Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\fndfile\shell\open\ddeexec] @="[OpenFindFile(\"%1\", %I)]" [HKEY_CLASSES_ROOT\fndfile\shell\open\ddeexec\appli cation] @="Folders" [HKEY_CLASSES_ROOT\fndfile\shell\open\ddeexec\topic] @="AppProperties" ------------------------------------------------- Deleting any sub-entry will cause error. -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
#5
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Lu Wei,
I don't know what "ddeexec" entry is for and its syntax. Bummer. Could perhaps have been a way to circumvent that .FND file My "ddeexec" entry is: [Snip] Yes, thats the same as I have there. Regards, Rudy Wieser |
#6
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
"R.Wieser" wrote:
The problem is that the search-origin path does not seem to be stored in the saves I've created ... Weirdly, if your origin is "My Documents" or anyone else's documents then it will store the path. Then maybe check registry HKEY_Classes_Root\fndfile\shell\open item. I just did. I assume that the "ddeexec" entry is used, as the "command" entry does not show any parameters. Dynamic Data Exchange (DDE) is involved when files pertaining to explorer.exe like ".fnd" are opened. The ddeexec entry is the DDE message. But, as you now have put my eye on it, do you have any idea what [OpenFindFile("%1", %I)] does ? "%1" is ofcourse the .FND file, but "%I" ? (a quick google didn't turn up anything). DDE Spy, a program shipped with Visual Studio 6 can show what's happening but unfortunately truncates the command and callback input data before the full string is revealed. Example monitoring WM_DDE_EXECUTE messages and all callbacks: - - - Task:0x3ec Time:450979814 hwndTo=0x2d0288 Message(Posted)=Execute: hwndFrom=0x480182, Execute command="[" Task:0x2f8 Time:450980125 Callback: Type=Execute, fmt=0x0("?"), hConv=0x36000500, hsz1=0xc002("AppProperties") hsz2=0x0(""), hData=0x37000b00, dwData1=0x0, dwData2=0x0 return=0x8000 Input data= 5b 00 4f 00 70 00 65 00 6e 00 46 00 69 00 6e 00 [.O.p.e.n.F.i.n. 64 00 46 00 69 00 6c 00 65 00 28 00 22 00 46 00 d.F.i.l.e.(.".F. ... - - - |
#7
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Apd,
Weirdly, if your origin is "My Documents" or anyone else's documents then it will store the path. Do you have the "indexing service" enabled ? If so, that might be the difference (I have it disabled). Could you take a look in your .FND file to see if you can recognise the pathname in there ? If-and-when you do, could you post it, or a hexdump of it for me to look at ? Actually, if you can save a reproducable search from within C:\Windows for me I would be able to see if that FND file would work on my machine, and if so perhaps find the difference(s)/problem. Input data= 5b 00 4f 00 70 00 65 00 6e 00 46 00 69 00 6e 00 [.O.p.e.n.F.i.n. 64 00 46 00 69 00 6c 00 65 00 28 00 22 00 46 00 d.F.i.l.e.(.".F. You left the jucy bits out :-( :-) (the part that shows the %I argument) Regards, Rudy Wieser |
#8
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
"R.Wieser" wrote:
Apd, Weirdly, if your origin is "My Documents" or anyone else's documents then it will store the path. Do you have the "indexing service" enabled ? If so, that might be the difference (I have it disabled). No. I never enable it. Could you take a look in your .FND file to see if you can recognise the pathname in there ? C:\Documents and Settings\AllUsers\Documents That's from searching "Shared Documents". If-and-when you do, could you post it, or a hexdump of it for me to look at ? Actually, if you can save a reproducable search from within C:\Windows for me I would be able to see if that FND file would work on my machine, and if so perhaps find the difference(s)/problem. files: *.txt string: test I did both searches with only "search system folders" ticked (no subfolders or any other options) See below for ".fnd" dumps (WinXP SP3). You left the jucy bits out :-( :-) (the part that shows the %I argument) As I said, DDE Spy truncates it. I looked for a better DDE monitor but couldn't find one. Shared Documents: 44 46 04 00 00 00 00 00 00 00 10 00 24 00 00 00 DF..........$... 05 00 00 00 75 00 00 00 FF FF FF FF 04 00 00 00 ....u........... 00 00 00 00 10 37 06 00 2A 2E 74 78 74 00 02 30 .....7..*.txt..0 2E 00 43 3A 5C 44 6F 63 75 6D 65 6E 74 73 20 61 ..C:\Documents a 6E 64 20 53 65 74 74 69 6E 67 73 5C 41 6C 6C 20 nd Settings\All 55 73 65 72 73 5C 44 6F 63 75 6D 65 6E 74 73 00 Users\Documents. 21 37 05 00 74 65 73 74 00 11 37 02 00 31 00 15 !7..test..7..1.. 37 02 00 31 00 00 00 00 00 10 37 0C 00 2A 00 2E 7..1......7..*.. 00 74 00 78 00 74 00 00 00 02 30 5C 00 43 00 3A .t.x.t....0\.C.: 00 5C 00 44 00 6F 00 63 00 75 00 6D 00 65 00 6E .\.D.o.c.u.m.e.n 00 74 00 73 00 20 00 61 00 6E 00 64 00 20 00 53 .t.s. .a.n.d. .S 00 65 00 74 00 74 00 69 00 6E 00 67 00 73 00 5C .e.t.t.i.n.g.s.\ 00 41 00 6C 00 6C 00 20 00 55 00 73 00 65 00 72 .A.l.l. .U.s.e.r 00 73 00 5C 00 44 00 6F 00 63 00 75 00 6D 00 65 .s.\.D.o.c.u.m.e 00 6E 00 74 00 73 00 00 00 21 37 0A 00 74 00 65 .n.t.s...!7..t.e 00 73 00 74 00 00 00 11 37 04 00 31 00 00 00 15 .s.t....7..1.... 37 04 00 31 00 00 00 79 00 00 00 00 00 00 00 4E 7..1...y.......N 54 46 46 35 04 B4 7E TFF5..~ c:\windows: 44 46 04 00 00 00 00 00 00 00 10 00 24 00 00 00 DF..........$... 04 00 00 00 43 00 00 00 FF FF FF FF 04 00 00 00 ....C........... 00 00 00 00 10 37 06 00 2A 2E 74 78 74 00 21 37 .....7..*.txt.!7 05 00 74 65 73 74 00 11 37 02 00 31 00 15 37 02 ..test..7..1..7. 00 31 00 00 00 00 00 10 37 0C 00 2A 00 2E 00 74 .1......7..*...t 00 78 00 74 00 00 00 21 37 0A 00 74 00 65 00 73 .x.t...!7..t.e.s 00 74 00 00 00 11 37 04 00 31 00 00 00 15 37 04 .t....7..1....7. 00 31 00 00 00 47 00 00 00 00 00 00 00 4E 54 46 .1...G.......NTF 46 35 04 B4 7E F5..~ |
#9
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Apd,
Do you have the "indexing service" enabled ? If so, that might be the difference (I have it disabled). No. I never enable it. Ah. On my version of XP its enabled by default. Could you take a look in your .FND file to see if you can recognise \ the pathname in there ? C:\Documents and Settings\AllUsers\Documents Thanks, as that also answers another part of my worries, being that maybe the starting folder would be saved as a(n internally used) GUID, or even just an ID into the "indexing service" database. Luckily it doesn't seem to be. You left the jucy bits out :-( :-) (the part that shows the %I argument) As I said, DDE Spy truncates it. My apologies, I only realized after posting that that might have been the cause. :-\ And many thanks for the two examples. Take a wild guess to what I'm going to do after finishing reading here. :-) Regards, Rudy Wieser |
#10
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
"R.Wieser" wrote:
You left the jucy bits out :-( :-) (the part that shows the %I argument) As I said, DDE Spy truncates it. My apologies, I only realized after posting that that might have been the cause. :-\ I also tried searching for DDE messages used by explorer and of course found nothing useful. Whenever you look for something specific, in this case including terms like "ddeexec" and "AppProperties", all you get are hits about problems with corrupt registries. And many thanks for the two examples. Take a wild guess to what I'm going to do after finishing reading here. :-) Please report back if you get anywhere. |
#11
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Apd,
I also tried searching for DDE messages used by explorer and of course found nothing useful. Whenever you look for something specific, in this case including terms like "ddeexec" and "AppProperties", all you get are hits about problems with corrupt registries. "Welcome to the club" as they say. :-( From time to time I run into that problem myself too. And for some reason it looks like, using Google, to be getting worse. Page-after-page full with links that have got absolutily nothing to do with what I'm searching for. :-( Please report back if you get anywhere. I noticed that your second example ("c:\windows") did not contain a readable path. Did that one still repeat the search from the correct folder for you ? Though executing the first example here showed that it could indeed remember the starting path. Odd though, the "look in" field doesn't show the last folder in that path - which it definitily does when you start a search yourself (before saving). By taking another look into those files (yours as well as mine) I noticed some fields that turned out to be pointers. One to the start of the ASCII section (at 0x0C), one to the four zeroes behind it (at 0x14) and one, oddly enough, at the end of the wide-string section (just before a set of four zeroes) pointing /backwards/ to the start of that section. Not having been aware of that caused my early "lets try to add a path" experiments to fail. At the moment I can create a search defining the path, filemask(s) and/or words. The setting of the different "Search options" currently still evades me though. Like saving a search with the "Search Options" opened or closed doesn't seem to make any difference (even though it shows a tickmark) .... Regards, Rudy Wieser |
#12
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
"R.Wieser" wrote:
I noticed that your second example ("c:\windows") did not contain a readable path. Did that one still repeat the search from the correct folder for you ? No. Only searches from documents roots save the path. Others do not and so don't fill in the "look in" field when loading a saved search. Though executing the first example here showed that it could indeed remember the starting path. Odd though, the "look in" field doesn't show the last folder in that path - which it definitily does when you start a search yourself (before saving). Are you saying when you open the fnd file that "shared documents" is not shown? It is shown on my system. By taking another look into those files (yours as well as mine) I noticed some fields that turned out to be pointers. One to the start of the ASCII section (at 0x0C), one to the four zeroes behind it (at 0x14) and one, oddly enough, at the end of the wide-string section (just before a set of four zeroes) pointing /backwards/ to the start of that section. Not having been aware of that caused my early "lets try to add a path" experiments to fail. Good to know. At the moment I can create a search defining the path, filemask(s) and/or words. Can you now make "c:\windows", for example, show in the "look in" field when opening a saved search? The setting of the different "Search options" currently still evades me though. Like saving a search with the "Search Options" opened or closed doesn't seem to make any difference (even though it shows a tickmark) Perhaps those options are not saved. |
#13
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Apd,
No. Only searches from documents roots save the path. "document roots" ? You mean the "C:\Documents and Settings\xxxx\Documents" paths only ? Odd. And most of my data is /not/ saved in any of those paths (but instead on different partitions), which would make a saved search fully unusable there. :-( Can you now make "c:\windows", for example, show in the "look in" field when opening a saved search? Show ? No. Search ? Yes. Loading your "All documents" saved search did not show anything in the "look in" field either (it still did search from there though). Perhaps those options are not saved. Thats rather possible, yes. But why than display tickmarks for them ? Also, the "Search options" - "type" field is ticked when you load a saved search, even when you had it unticked on search. And there are other oddities: I can set "search in subfolders", but that doesn't unfold the "Advanced options" (which ticking "Search system folders" seems to do). In short: even though I've /not/ ticked anything when doing a search and with the "Search options" closed, on loading that saved search the "Search options" is open, the "type" field is ticked, the "Advanced options" is closed, but the "search in subdirectories" is ticked. .... but as the "Advenced options" are closed it just takes its own defaults for the entries inside, meaning that it doesn't matter if I have "search in subdirectories" ticked or not. Hmmm ... I reloaded a search where I had ticked /all/ the options. The "time" and "search in hidden files and folders" options are now, in a reloaded search, both unticked ... :-( Regards, Rudy Wieser |
#14
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
"R.Wieser" wrote:
Apd, No. Only searches from documents roots save the path. "document roots" ? You mean the "C:\Documents and Settings\xxxx\Documents" paths only ? Odd. Yes and, on 2nd look, individual drive letters. This is my drop-down list from "Look in:" | My Documents | My Pictures | My Music | My Videos | Desktop | My Computer |- Local Hard Drives(C |- My Documents |- test1's Documents |- Shared Documents |- Local Disk(C |- DVD-RW Drive (D | Browse... Anything below "My Computer" apart from "Local Hard Drives" and "Browse" will have the path saved. So if you chose "My Documents" from the top of the list the path won't be saved but if you choose "My Documents" listed under "My Computer" it will be saved. Can you now make "c:\windows", for example, show in the "look in" field when opening a saved search? Show ? No. Search ? Yes. Strange. Loading your "All documents" saved search did not show anything in the "look in" field either (it still did search from there though). Mine does show in "look in". And there are other oddities: Yes it's weirdly inconsistent. I thought it might be to do with XP updates. I have a base XP SP3 system with only a couple of updates installed (not even any version of .NET) and another which is fully up to date as of earlier this year (masquerading as a point of sale system). Both systems show the same behaviour. |
#15
|
|||
|
|||
A saved search (*.FND) - fails to remember the folder :-(
Apd,
Yes and, on 2nd look, individual drive letters. Nope, just getting that "all local drives" selection back. Nothing visible in the file. This is my drop-down list from "Look in:" I've only got drives (hardisk & DVD) under "my computer" there. Show ? No. Search ? Yes. Strange. Indeed. Upto the point that using a saved search becomes an exercise in remembering all the exceptions, and change them back by hand. :-( I thought it might be to do with XP updates. Always possible (its a bit of a catch-all). Mine is a basic XP sp3 installation. Bottom line, if I want to create a repeatable search I might be better of with letting AutoIt fill in everything (and it can even start the search -) ) ... Regards, Rudy Wieser |
|
Thread Tools | |
Display Modes | |
|
|