First Use (Win2K):
- Extracted v3 using UniExtract to my Win2K machine with 6GB disk. (I tried my small machine, first, because of the new indexing...)
- As soon as I started the FSeeker.exe, it began indexing my C: and D: drives using FSeekerDBUpdater.exe. C:\ and D:\ were checked by default.
- I waited until FSeekerDBUpdater's CPU usage went to zero before searching for a file in the database.
- When I click "Search", I receive a Warning message: "It is the first time you're using File Seeker. Wait a few moments for the database to be created."
- I can see that a 3MB file, "files.tmp", is created that contains file and path names.
- When I pick "Search", I receive the following error:
---------------------------
File Seeker
---------------------------
Access violation at address 004EC768 in module 'Fseeker.exe'. Read of address 00000004.
---------------------------
OK
--------------------------- - Furthermore, I receive this same error when I try to pick the "Settings" button, with no drives selected.
- Installed v3 to my Hard drive.
- Same Result.
- Uninstalled File Seeker and re-extracted it using UniExtract.
- Allowed it to run for one hour before attempting to use it.
- No change observed to the files.tmp file, entered a filename into the Name dialog, clicked "Search"
- Received the same Warning as above.
- Waited 15 minutes, for good measure...
- Clicked "OK".
- Received same Access Violation error.
- Checked FSeeker.exe with Dependency Walker. Nothing seems to be out of the ordinary.
- System = 1.6GHz P4 / 1 GB RAM / 60 GB HD
- Ran program from USB
- Indexed disk in just a few minutes and created a 25 MB files.qdb file. (This file was never created on the Win2K system)
- Searched for a file without errors.
- Opened Settings without incident.
- Changed a few things.
- Clicked "OK". Received this error:
---------------------------
File Seeker
---------------------------
Failed to set data for "FileSeekerUpdate"
---------------------------
OK
--------------------------- - Can only Cancel out of the File Seeker Options Dialog.
- On both systems, each time I exited File Seeker, FSeekerDBUpdater.exe continued to run. Closing File Seeker doesn't terminate FSeekerDBUpdater.exe. As a result, I cannot unmount my USB drive until I kill FSeekerDBUpdater.exe.
- The orphaned, idle FSeekerDBUpdater.exe process uses 5 MB of RAM.
- Despite selecting to "Seek within:" Compresses files, and Updating the database, the program did not return the filename of a Word document contained within a ZIP archive on my Desktop. Searching the QDB file with Universal Viewer shows the ZIP file name but, not the desired Word document name in question.
- I'm not sure that v3 is ready for prime time...
Dan