Results point to incorrect network path

[ventalator]

I've got Everything running on a XP machine with an ETP server running, when i connect to this from my vista machine i can get results but the paths to the files are incorrect. The path for results is \\server\(real drive name)\file where the "real drive name" should actually be the share name of that drive. Is this a bug or is there something i'm missing?

Thanks for any help you can provide, love this program. And apologies if i'm doing something stupid

[ventalator]

No one has any ideas? Maybe i should put this in the bug section because it seems like it should use the network share names of drives when connected to a etp server than the actual drive names...

[David]

Currently "Everything" does not check for existing share names.

You will need to share the drive as its drive letter.

For example, you will need to share your C: drive as C to view the files on an ETP connection.

It will be possible to customize this in a future release of "Everything".

[ventalator]

Thanks, i'll keep that in mind. Looking forward to the next release!

[digitaldoctorsbag]

Currently "Everything" does not check for existing share names.
You will need to share the drive as its drive letter.
For example, you will need to share your C: drive as C to view the files on an ETP connection.

Oh no.
I got burned by this as well.


This makes Voidtools unusable for me.
Most of my files are on my network and following good network protocols I gave my shares names that reflect what they are.
I thought everyone named their shares.
I also don't think it is that great an idea to share your root directory on a server.

Voidtools is an exceptional program for local searching but needs to be able to search local and networked drives simultaneously to work well in most small business environments.

[userguy]

Solution for those of you using everything and network shares. I, too had a problem with wanting to use this awesome program to index/search ALL of my data. ETP wasn't good enough and FTP was "ok".

What I did was two things.

1) I moved 80% of my data off my windows machine to a "dumb" machine running the open source openfiler program. This allows me to run iSCSI. iSCSI itself shows up as a local disk in your Windows disk manager. Everything also sees it as a local disk, thus it can be indexed! Not to mention, iSCSI is way faster than file transferring over a normal share. I won't go into all the details for Openfiler and iSCSI, but click the name for the links. I am now moving all my data to iSCSI based hosts due to the overall gain in file transfer performance in general.

2) Use a Windows machine as a host AND connect from a Windows machine, all over iSCSI. Unfortunately, there is a cost associated with running say, Windows XP as a host, since iSCSI is not native as a host. There are third party tools that will allow you to do this.

I know everyone isn't comfortable with Linux, or Openfiler per se, but I am no Linux guy either. My real advice is to take an old machine, load it with drives and cheap memory, download openfiler and run the disc (great, step by step) install it and configure it. Then download the free iSCSI initiator from Microsoft (link above) and connect to your openfiler machine. WHAMMO! Everything is running on your client machine and you can find all your data on the host openfiler.

Within this week I intend to have a full write up, how-to and setup of mine on my blog at Tech67.com

**PS, or you can simply download the Virtual Machine of Openfiler here

[adamgreen]

Is this still the case?

I have to use share names on our drives because of company policy.