HAs been running the RC on XP on my T60p with 4Gb and 200 GB 7200 disk. compared to the previous version I have a couple of things you may want to check before final release.

1) X1 appear often unresponsive when hitting Ctrl-Alt-L. Even when clicking on the icon, X1 takes MUCH longer before the window pops up. Its is NOT disk I/o that appears to block but CPU. As a side issue, that must be a weakness compared to Vista's responsivenes.

2) DAte/Time title in right side header field for file searching appears to long and makes the header field look unaligned.

3) Should be minor - but actually is not. the choice of fionts in the search result window may appear too large to some. I do not know if there is some ressource that can be set to change this, but it is difficult to get the overview when the window is full. Great for us who wo not have the eyes

4) It appears that X1 sporadically misses indexing certain mails in the inbox (Office 2007) even when it has been activated permanently

I have now been running the RC for a longer period and it is markedly slower than its predecessors. This occurs especially when you are working on something else, and then activates X1. Even after the main window is back again - which takes considerable time for a desktop product, it does not echo back what you are typing into the "From" field (or other fields) in email. This markedsly improves when it has been active for some longer time. Apparently it is related to paging, whcih could be explained if it uses more storage than previously due to .net or if it has some debug features in it still. Or is the size related to the index size (I am indexing a lot of documents).

There has been little feedback on this. Could someone at X1 please comment if this is a known issue that is being acted upon, or if this came as a surprise when swithcing to .net and we will have to live with it?

giuse wrote:Also at boot startup, it is launched as a window and not just as a tray icon, also when that option is checked.Did you see the same thing?cheers

Giuse

Thank you for reporting this. I brought it up in an earlier beta. It still has not been fixed.

I find that it isn't just a case of not minimising to the Notification Area. I have to wake up X1 and then dismiss it again to make it go to the tray.

My hope is that the large gaps between beta versions is a sign that someone is working on these issues, especially the speed, which is not good.

I can see very little in the way of new features in the RC. So if someone asks me if I would advise upgrading from the previous version to 6.5, my answer would be a firm No.

I really don't think most users care about using .Net framework. Actually, some will not upgrade because their IT folks do not allow this technology. At least, that is what they have said here.

By the way, there was a significant update to .Net this week. I have no idea if this will deal with the crashes I get in X1. Every few days it just pops up and says that the UI has stopped working and sends an error report.

Anyone else seen this?

MKX1 Search 8.5.2 - Build 6001si (64-bit)Windows 10 Pro 64-bit | Windows 10 Home 32-bitNo, I have nothing to do with X1, just a user since 2004.

I installed the RC for a little while to give it a test. I must say I was less than impressed though, no new features, I didn't like the font and it seemed slower overall. I went back to 6.2.3 and I've been much happier.

I'm sure that there's a lot that's gone on under the hood I can't see, but from my point of view it wasn't worth the upgrade.

I had problems with it not minimising on startup as you've mentioned and also very long times waking up from the tray. Though I also have this with 6.2.3 as well.

Glad to see that I am not the only one thinking about going back. I have been trying, faithfully, to use it for the past period since I started the thread, but it has not helped.

Interestingly, I have noted a "hesitance" when I want to search. I tend to feel a negative reaction - prior to starting up X1. I find myself resolving to other search mechanisms (outlook, explorer) not because it is faster in total (of which I have no opinion) but because it is more responsive in the initial phase. There are lots of cognitive reasons for that, and a successful product must take this into consideration.

I started using the quick launch bar, but its erratic behaviour in connection with its informational box that overlays the input field, makes me just using Ctrl-Alt-L. But it is so slooooooooow. I can accept, to a certain degree, that the search takes time, but getting up a user interface should be instantaniously. Unfortunately - as we have found out - .NET is slow by nature. Too much code to execute.

I expect that X1 has discovered the same, since neither the product has been announced nor have we seen any bug fixes for a long time. My guess is that a major rewrite is in process - but it is only a guess.

bk3 wrote:I expect that X1 has discovered the same, since neither the product has been announced nor have we seen any bug fixes for a long time. My guess is that a major rewrite is in process - but it is only a guess.

I had exactly the same guess.

Two months and counting?

This was never an "RC".

More like alpha.

MKX1 Search 8.5.2 - Build 6001si (64-bit)Windows 10 Pro 64-bit | Windows 10 Home 32-bitNo, I have nothing to do with X1, just a user since 2004.