Possible bug in Connect X7 on local drives.
One of the first things I noticed with connect is the huge performance improvements, looks as though they are relying on Microsoft indexing more heavily compared to X6, this is good.
However, I am seeing a huge lag in new files being displayed in connect; this is because it is not displaying files unless they are indexed.
To duplicate, simply create a new .cdr or .cpt file in a folder and see if it appears in connect right after saving. Then wait awhile and you will see it appear after windows updates the indexes.
Also, I noticed a sizable increase in CPU utilization compared to X6 that is not released when closing connect, requiring a restart of the search process.
Can someone verify this?
You are correct about Windows indexing...CONNECT won't show results unit the location is indexed.
Can you give me more details on the CPU issue? Which locations were you searching? How many searches had you preformed? What kind of content (jpg, png...) were you searching for? Any info you can share with us would help us track this one down.