Problem with the database

[vsub]

I've always been using the portable version and when I updated Everything,I just delete the old exe and place the new one

1.When I started the latest beta(I was using 1.3.4.686 before that)I notest that I don't get any search results and that my both hdd where not enabled in the Indexes=>NTFS

2.When I enabled both hdds(ssd and hdd),the database was created but when I exit Everything,the database was saved not in the program folder but in adddata(the option to store settings and data to appdata is not enabled and the path to the database is not set(it was not on 1.3.4.686 too but there the database was saved in the program folder)

This is on WinXP(I'll try Win7 x64 when I go home but I think it was fine there(don't remember if I ever set the path to the database there))

[salazor]

That's right, so it was in the first 1.4 beta, David himself said that this is a bug, and fix it in the next version - download 705B and check. Now is OK.

[vsub]

Hmm,yes I didn't notest there is a new beta(the thread title still says 1.4.0.702b) but only the second problem is fixed(at least here on WinXP...can't say about Win7 yet)

When I start 1.3.4.686 and close it(imitating "I didn't update yet")and then start 1.4.0.705b,the checkbox on the hdds is not enabled and everything display nothing in the search result.

Enabling them and the exit=>run 1.3.4.686=>exit=>run 1.4.0.705b,makes them not indexed again.
But I don't think that a big deal if you are not going to use the older version again

[salazor]

1.4 very differently database indexes than 1.3 - if you have both versions in the same folder, and the same database they replace each other. Use of one or second another location. David will explain it better.

[vsub]

I don't really think there is a problem needing a fix but the thing is...you update your beta and then suddenly the search result don't display anything.

[therube]

See, Running 702 & Older Version Concurrently.

[void]

I'm aware of a few issues when running Everything with an old service.

Everything uses the Service name "Everything" for all versions.
I do not want to change this, as it could lead to left over services when upgrading / uninstalling.

For the next beta update, Everything should detect that the current installed service is not compatible and recommend replacing the current service.
Currently this detection is limited, no version checking is done and if the currently installed service Everything is not compatible, Everything will appear to hang for 1 minute.

There's currently (up to and including 705b) a bug when using named instances and running the for the first time, when ask to install the service, run as admin or ignore ntfs volumes, choosing install service doesn't work (installs the service under the wrong instance). This can be rectified by enabling the service from Tools -> Options -> General -> Everything Service.
-this has been fixed for the next beta update.