Everything-1.2.1.451a: Monitor changes doesn't take effect.

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
zhaohs
Posts: 30
Joined: Sun May 03, 2009 9:56 am

Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by zhaohs »

Hi David,

I use the latest Everything-1.2.1.451a, and I find that sometimes the function of Monitor changes doesn't take effect. In my case, when I newly build a file on Desktop, Everything will not find it. If I restart Everything, then the file will be found within Everything. I've the option Monitor changes and Include in database enabled.

Why should this happen?
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by void »

Please try running "Everything" in debug mode.

To run "Everything" in debug mode:
  • Run Everything.exe with the -debug command line option:

    Code: Select all

    Everything.exe -debug
Are there any errors reported in the debug console?
Look for the follow error messages in red:
DeviceIoControl failed xxxxxxxx, retrying in 30 seconds...
GetOverlappedResult failed xxxxxxxx, retrying in 30 seconds...

If the monitors are not starting at all you should find an error in the Errorlog.txt file in your "Everything" installation folder?
zhaohs
Posts: 30
Joined: Sun May 03, 2009 9:56 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by zhaohs »

Everything-1.2.1.451a.exe -debug will give messages like the following:

--------------------------------
WM_ACTIVATE 00000001 00000000
search edit focus 2
db::load
db::destroy
load db...
excludes 0
verified folder offsets 0.014235 seconds
verified folder FRN order 0.010662 seconds
verified file name order and check for circular references 0.122996 seconds
0 updates in 0.079328 seconds
16 updates in 0.000656 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003977 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.004011 seconds
11156 updates in 0.144898 seconds
0 updates in 0.000481 seconds
0 updates in 0.000808 seconds
0 updates in 0.000359 seconds
6 updates in 0.020785 seconds
6 updates in 0.034883 seconds
loaded run history in 0.000776 seconds
start all monitors
_load_db_querier
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
term 11111111111111
0016ddc0: 1 11111111111111, matchnext: 00000000, nomatchnext: 00000000
first t 1495840
query
found 0 folders, size 0, db search time taken: 0.000455 seconds
clear results
requery
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
term 11111111111111
0016ddc0: 1 11111111111111, matchnext: 00000000, nomatchnext: 00000000
first t 1495840
found 0 folders, size 0, db search time taken: 0.001219 seconds
found 1 files, size 65540, db search time taken: 0.017293 seconds
waiting for 9 monitors, isdelay 0...
GetOverlappedResult failed 00000057, retrying in 30 seconds...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
WM_ACTIVATE 00000000 00000000
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
Updating \\?\Volume{x} (F:):
waiting for 7 monitors, isdelay 1...
waiting for 7 monitors, isdelay 1...
1 updates in 0.000045 seconds
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
WM_ACTIVATE 00000002 00000000
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
Updating \\?\Volume{x} (F:):
waiting for 7 monitors, isdelay 1...
1 updates in 0.000045 seconds
waiting for 7 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
WM_ACTIVATE 00000000 00000000
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
GetOverlappedResult failed 00000057, retrying in 30 seconds...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
WM_ACTIVATE 00000001 00000000
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
WM_ACTIVATE 00000000 00000000
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
GetOverlappedResult failed 00000057, retrying in 30 seconds...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
Updating \\?\Volume{x} (F:):
waiting for 7 monitors, isdelay 1...
waiting for 7 monitors, isdelay 1...
2 updates in 0.000142 seconds
waiting for 8 monitors, isdelay 1...
Updating \\?\Volume{x} (F:):
waiting for 7 monitors, isdelay 1...
waiting for 7 monitors, isdelay 1...
5 updates in 0.000077 seconds
waiting for 8 monitors, isdelay 1...
waiting for 8 monitors, isdelay 1...
--------------------------------

Best regards.
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by void »

Looks like this could be a memory alignment issue..

Does the problem occur with http://www.voidtools.com/Everything-1.2.1.452a.zip ?
zhaohs
Posts: 30
Joined: Sun May 03, 2009 9:56 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by zhaohs »

I've tried the Everything-1.2.1.452a but the issues is still the same, i.e., it cann't find the newly generated file till I restart the Everything.

The following is the debug output:

-------------------------------------
WM_ACTIVATE 00000001 00000000
search edit focus 2
db::load
db::destroy
load db...
excludes 0
verified folder offsets 0.014203 seconds
verified folder FRN order 0.010652 seconds
verified file name order and check for circular references 0.123290 seconds
0 updates in 0.326376 seconds
0 updates in 0.000581 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.004004 seconds
1492 updates in 0.299017 seconds
0 updates in 0.000471 seconds
0 updates in 0.001325 seconds
0 updates in 0.000369 seconds
0 updates in 0.027294 seconds
0 updates in 0.003380 seconds
loaded run history in 0.000678 seconds
start all monitors
_load_db_querier
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
0016d048: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1498800
query
found 0 folders, size 0, db search time taken: 0.000308 seconds
clear results
requery
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
0016deb0: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1495112
found 0 folders, size 0, db search time taken: 0.005479 seconds
found 1 files, size 65540, db search time taken: 0.081497 seconds
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000047 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000050 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000050 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000076 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
WM_ACTIVATE 00000000 00000000
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000054 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
WM_ACTIVATE 00000002 00000000
WM_ACTIVATE 00000000 00000000
-------------------------------------

Thanks again.
zhaohs
Posts: 30
Joined: Sun May 03, 2009 9:56 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by zhaohs »

Let me desribe this issue in more detail:

Firstly, I set my Everything on system startup.
When I start my system, and new build a file on desktop, then Everything will not find this file. In this case, the "Everything-1.2.1.452a.exe -debug" command without restarting Everything will give the following messages:

------------------------
WM_ACTIVATE 00000001 00000000
search edit focus 2
_load_db_querier
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
04b12d00: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1494840
found 0 folders, size 0, db search time taken: 0.005979 seconds
found 0 files, size 0, db search time taken: 0.081461 seconds
WM_ACTIVATE 00000000 00000000
WM_ACTIVATE 00000002 00000000
WM_ACTIVATE 00000000 00000000
WM_ACTIVATE 00000002 00000000
WM_ACTIVATE 00000000 00000000
------------------------------

Then, I exit the Everything, and restart it by "Everything-1.2.1.452a.exe -debug". In this case, Everything will find the newly gererated file and give the following messages:

-------------------------
WM_ACTIVATE 00000001 00000000
search edit focus 2
db::load
db::destroy
load db...
excludes 0
verified folder offsets 0.014152 seconds
verified folder FRN order 0.010611 seconds
verified file name order and check for circular references 0.122308 seconds
0 updates in 0.077872 seconds
0 updates in 0.000458 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003984 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003974 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003986 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003969 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003977 seconds
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003971 seconds
12333 updates in 0.133718 seconds
0 updates in 0.000466 seconds
0 updates in 0.002244 seconds
0 updates in 0.000144 seconds
0 updates in 0.001731 seconds
0 updates in 0.001891 seconds
loaded run history in 0.000836 seconds
start all monitors
_load_db_querier
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
0016cb88: 94, matchnext: 00000000, nomatchnext: 00000000
first t 2366528
query
found 0 folders, size 0, db search time taken: 0.000419 seconds
clear results
requery
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
00241c40: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1493896
found 0 folders, size 0, db search time taken: 0.005680 seconds
waiting for 9 monitors, isdelay 0...
found 1 files, size 65540, db search time taken: 0.081507 seconds
WM_ACTIVATE 00000000 00000000
Updating \\?\Volume{9976b96f-41a0-11dd-b6e0-00016c2e5cb5} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000049 seconds
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{9976b96f-41a0-11dd-b6e0-00016c2e5cb5} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000048 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{9976b96f-41a0-11dd-b6e0-00016c2e5cb5} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000107 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{9976b96f-41a0-11dd-b6e0-00016c2e5cb5} (F:):
waiting for 8 monitors, isdelay 0...
4 updates in 0.000046 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
-------------------------

Best regards.
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by void »

It is hard to tell if the monitors are running on the "Everything" started on system startup..

Does "Everything" correctly monitor file changes after you run it a second time?

Does "Everything" correctly monitor file changes on a different folder or volume on your system? (ie the root directory c:\)
zhaohs
Posts: 30
Joined: Sun May 03, 2009 9:56 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by zhaohs »

void wrote:It is hard to tell if the monitors are running on the "Everything" started on system startup..

Does "Everything" correctly monitor file changes after you run it a second time?

Does "Everything" correctly monitor file changes on a different folder or volume on your system? (ie the root directory c:\)

1- It is hard to tell if the monitors are running on the "Everything" started on system startup..

If so, what's function of the following combinations:

General | Start Everything on system startup;
Volumes | Monitor changes.

2- Does "Everything" correctly monitor file changes after you run it a second time?
Yes.

3- Does "Everything" correctly monitor file changes on a different folder or volume on your system?
yes.

Best regards.
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by void »

1- It is hard to tell if the monitors are running on the "Everything" started on system startup...
Please try the following:
  • Run regedit.
  • Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Run
  • Add -debug to the Everything value, it should now look something like this:

    Code: Select all

    "C:\Program Files\Everything\everything.exe" -startup -debug
  • What is displayed in the debug console after a restart?
Thanks for your support.
zhaohs
Posts: 30
Joined: Sun May 03, 2009 9:56 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by zhaohs »

void wrote:
1- It is hard to tell if the monitors are running on the "Everything" started on system startup...
Please try the following:
  • Run regedit.
  • Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Run
  • Add -debug to the Everything value, it should now look something like this:

    Code: Select all

    "C:\Program Files\Everything\everything.exe" -startup -debug
  • What is displayed in the debug console after a restart?
Thanks for your support.
I've revise the regedit entry according to your above instructions. But start Everything doesn't start the debug console together.

In my case, in order to invoke the debug console for Everything, I must run the the command "Everything-1.2.1.452a.exe -debug" under the dos terminal.

The following is the debut information I've seen:

---------------------------
WM_ACTIVATE 00000001 00000000
search edit focus 2
_load_db_querier
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
00154458: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1393792
found 0 folders, size 0, db search time taken: 0.005593 seconds
found 1 files, size 65540, db search time taken: 0.083152 seconds
WM_ACTIVATE 00000000 00000000
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000052 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
3 updates in 0.000052 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000051 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000045 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000045 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000046 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{x} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000045 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
---------------------------

Best regards.
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by void »

It looks like the monitor on the F: drive is running..
Does "Everything" detect changes to the F: when "Everything" runs for the first time?
zhaohs
Posts: 30
Joined: Sun May 03, 2009 9:56 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by zhaohs »

Sometimes yes, sometimes no. It seems all at random.

But, if the "Everything" doesn't detect the changes to the F:, I firstly disable the Monitor changes option on F:, then reenable it by toggle and untoggle this option on the Volumes panel manually. After the above operation, the "Everything" will be able to detect the changes to the F: again.

The following is the whole debug messgage in the above operation process:


--------------------------------
WM_ACTIVATE 00000001 00000000
search edit focus 2
_load_db_querier
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
04940a18: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1500776
found 0 folders, size 0, db search time taken: 0.006321 seconds
found 1 files, size 65540, db search time taken: 0.081647 seconds
WM_ACTIVATE 00000000 00000000
WM_ACTIVATE 00000002 00000000
query
found 0 search history results in 0.000005 seconds
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
0016e668: 94, matchnext: 00000000, nomatchnext: 00000000
first t 76810776
found 0 folders, size 0, db search time taken: 0.005448 seconds
found 1 files, size 65540, db search time taken: 0.082506 seconds
query
found 0 search history results in 0.000004 seconds
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
04940a18: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1500776
found 0 folders, size 0, db search time taken: 0.005475 seconds
found 0 files, size 0, db search time taken: 0.081645 seconds
query
found 0 search history results in 0.000005 seconds
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
0016e668: 94, matchnext: 00000000, nomatchnext: 00000000
first t 76810776
found 0 folders, size 0, db search time taken: 0.005472 seconds
found 0 files, size 0, db search time taken: 0.081626 seconds
query
found 0 search history results in 0.000004 seconds
query
restore selection (proir count 0 folders, 0 files, 0 special)
clear results
04940a18: 94, matchnext: 00000000, nomatchnext: 00000000
first t 1500776
found 0 folders, size 0, db search time taken: 0.005473 seconds
found 0 files, size 0, db search time taken: 0.081588 seconds
WM_ACTIVATE 00000000 00000000
WM_ACTIVATE 00000002 00000000
WM_SELECT 80900003 001408f3
WM_INITMENUPOP 005d083f 00000003
no command 0 to settings key
no command 0 to settings key
no command 41601 to settings key
no command 0 to settings key
no command 0 to settings key
WM_SELECT 80809c7c 005d083f
WM_SELECT 80819c7d 005d083f
WM_SELECT 80809c7e 005d083f
WM_SELECT 88030000 005d083f
WM_SELECT 80889c7f 005d083f
WM_SELECT 88030000 005d083f
WM_SELECT 80900006 005d083f
WM_SELECT 88030000 005d083f
WM_SELECT 80809c80 005d083f
WM_SELECT 80900009 005d083f
WM_INITMENUPOP 006f08eb 00000009
WM_SELECT 80809c80 005d083f
WM_SELECT 88030000 005d083f
WM_SELECT 80900006 005d083f
WM_SELECT 88030000 005d083f
WM_SELECT 80889c7f 005d083f
WM_SELECT 88030000 005d083f
WM_SELECT 80809c7e 005d083f
WM_SELECT 80819c7d 005d083f
WM_SELECT 80809c7c 005d083f
WM_SELECT 80900003 001408f3
WM_SELECT 80900003 001408f3
WM_SELECT 80900004 001408f3
WM_INITMENUPOP 000208fd 00000004
no command 0 to settings key
WM_SELECT 80809c86 000208fd
WM_SELECT 80809c87 000208fd
WM_SELECT 80809c88 000208fd
WM_SELECT 80819c89 000208fd
WM_SELECT 88030000 000208fd
WM_SELECT 80809c8a 000208fd
WM_SELECT ffff0000 00000000
enter mu options dialog...
WM_ACTIVATE 00000000 000606c6
start all monitors
disabling the focused item!
waiting for 8 monitors, isdelay 0...
start all monitors
disabling the focused item!
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{9976b96f-41a0-11dd-b6e0-00016c2e5cb5} (F:):
waiting for 8 monitors, isdelay 0...
remove: old name folder: \
allocate folder indexes: total folder count 1
sorted folder indexes in 0.000000 seconds
found 0 files in 0.003992 seconds
892 updates in 0.007145 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
Updating \\?\Volume{9976b96f-41a0-11dd-b6e0-00016c2e5cb5} (F:):
waiting for 8 monitors, isdelay 0...
1 updates in 0.000047 seconds
waiting for 8 monitors, isdelay 1...
waiting for 9 monitors, isdelay 0...
WM_ACTIVATE 00000001 000606c6
exit dialog model 0 79519984
WM_ACTIVATE 00000000 00000000
WM_ACTIVATE 00000002 00000000
WM_ACTIVATE 00000000 00000000
--------------------------------

Best regards.
skuzzlebutt
Posts: 1
Joined: Tue Feb 09, 2010 10:48 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by skuzzlebutt »

Same problem here :( (Windows SBS 2003)

is there any solution by now?

* It's a Raid1 System
jpbanks
Posts: 1
Joined: Tue Mar 09, 2010 7:11 pm

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by jpbanks »

First off, thank you, this is a great utility. I am, however, having the same problem as described above. New or moved files and folders are not found on my monitored drives. Re-starting Everything fixes the problem. I was looking for a "force sync" option but obviously there is none (having read this thread). I am willing to trouble shoot on my end if that helps. I have quickly come to rely on this utility for initial file/information management.
I am currently running version 1.2.1.371 and will upgrade to Everything-1.2.1.452a today.
kookaburra2
Posts: 7
Joined: Sat Mar 27, 2010 2:27 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by kookaburra2 »

I too have this problem. Also had it or similar in v1.2.1.371 (at times not showing new files, nor renamed ones).
I've been using 1.2.1.451a for a few days and not seen this issue, so I was thinking it was no longer, sadly not so. At least seems less prevalent.

Very hard to pin down, seems intermittent, selective, but I've never been able to pin down a pattern to the circumstances. In any moderately active day on the pc, I would get it 5-10 times a day maybe more (v1.2.1.371); but *only* maybe 10-30% of certain types of ops [so it feels], but really hard to gauge. Seems like conditions and actions that are the same (except for when and perhaps filenames/folders) work sometimes not others. When it's having the problem it is repeatable, to a degree.

My specific situation, this time...
Vista Business. FireFox 3.6.2
A print button in a webpage contains "javascript: form_submit('0')", it says in the status line.
Click on the print button gives Windows Print dialog.
My default printer is CutePDF Writer.
OK on Print dialog gives CutePDF Save As dialog.
Choose a filename, say XYZ.pdf, optionally navigate to another folder, Save.
Expect to see XYZ.pdf appear in already open (for a some hours but not much action) "Everything" window containing search spec XYZ pdf (other files matching this spec are showing beforehand). But the new one doesn't appear.
Starting a new instance (not new search window) of "Everything", either with or without closing down the first one that's not behaving, *does* now find the new XYZ.pdf.
Repeated this a few times from the point of clicking on the Print button on the webpage. None worked.

Sometime later I started over from the point of fetching the initial webpage (with -debug on "Everything", having found this thread) and now the new XYZ pdf *does* show straight away. Seeing it worked, I discarded the console log.

Just found this in errorlog.txt; around about the time of the malfunction, a bit vague but I *think* the malfunction was about 10 mins Before the timestamp in the errorlog...
29-03-10 23:41:22: Everything 1.2.1.451a: .\src\mu.cpp(2699): mu_RenameFileUTF8(): MoveFileExW(): GetLastError(): 2: Failed to move file from C:\Users\XXX\Documents\INSTALLED\UnPlugged\Everything.YYY.XXX.db.tmp to C:\Users\XXX\Documents\INSTALLED\UnPlugged\Everything.YYY.XXX.db


What to do next to help get this sorted?
therube
Posts: 4580
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by therube »

If I had to guess ...

Permissions issue?
Or some other program (anti-virus perhaps) has the database (.db) locked at the time that it wants to (re)write itself?
kookaburra2
Posts: 7
Joined: Sat Mar 27, 2010 2:27 am

Re: Everything-1.2.1.451a: Monitor changes doesn't take effect.

Post by kookaburra2 »

The fail-to-move db in the errorlog came, about 10 minutes after I saved the (print) file that wasn't showing up in the search. So, the fail-to-move db is of lesser importance (to me, now), unless it somehow is related.
Post Reply