Okay, I don't see any extraneous (leftover) junk in that /Volumes listing.

You should do a quantitative test to see if the problem is related to Finder's search or to networking. One way to do this would be to time how long it takes to find a specific file by using the 'find' command in a Terminal window and compare that to the time for the Find in Finder. Try these tests several times, alternating between the Terminal and Finder methods. Report the average time for each method.

I think you know how to do the 'find' in Terminal from instructions in a previous thread by here it is again.
Suppose the file is called "myfile.txt" and is in the folder "mystuff/myfolder" on the drive "mydrive" that is mounted under /Volumes. You could search for this file using 'find' in Terminal by running the following command:

find /Volumes/mydrive -name myfile.txt

That would start the search at the top level of the "mydrive" volume. It should print out the result as:
/Volumes/mydrive/mystuff/myfolder/myfile.txt

Do the same search in Finder by telling it to search in "Specific Places" and chooing the "mydrive" volume, and specifying to look for a file whose name "is" (not "contains") myfile.txt.
Time each search with a stopwatch, repeat several times and show us the results.

ok will give that a try
 

should I also use the finder window 'query'?

Sorry - I don't know what you mean by that. I see no such term in my Finder.

I was talking about using File/Find in Finder. I assumed that was what your original speed complaint was about.

Ok here are some results...
 

But first let me explain..

I did the search based upon how we performed our searches in OS 9, for example; file " SV123456 THIS IS A TEST " is the file I need to find, we would search by either the number or the possible description ( if whoever saved it assigned an appropriate name).

So when doing the test through terminal for an existing file I ask to find ie SV123456, although searching was quick it never found that file because it never exists ( at least not completely) I wouldn't remember the whole exact name of the file I need to find. And the same problem arises with the command F using 'is' rather than 'contains' -- I'm searching for part of the name structure.

So I did the search with contains--- it took over four minutes, did the same search with starts with 'SV123456' a little better
about 2. 20 secs but still nothing in comparison to OS 9 speed results, which was almost instant. And this is what baffles us, we have a supposed better OS but the find/search is painfully slow.

I hope this is offers a better understanding.



Thanks

Ok, it's good to have some quantitative results to compare to.
To summarize, a Finder search for:
contains SV123456
took 240 seconds, while a Finder search for:
starts with SV123456
took 140 seconds.
Is that correct? And what did you specify as to where the Finder should search? (the top part of the Find dialog)

Please try the 'find' in Terminal again using this command
(or the analog for some other file):

find /Volumes/mydrive -name 'SV123456*'

where of course you would replace the 'mydrive' with the actual name of your mounted drive.

The * at the end of the SV123456 makes it do a search like the Finder's "starts with". Please note the single quotes around the specification of the name in that command - they are necessary. It is probably best if you copy & paste the last part of the command from above after typing the beginning part.
How long does the 'find' command take to find the file?

s that correct?- YES
And what did you specify as to where the Finder should search? (the top part of the Find dialog) THE VOLUME NAME

ok terminal took-- over four minutes and still did not list the files --I stopped it. ( visually it went past where the file resides).

Find window specific places - volume selected took approx. 130 secs, but narrowing the search to a specific folder took even longer..over 2 mins.


Now I don't know if this may be result that I am now connected to the server via SMB rather that AFP, I can no longer connect this way for some odd reason.

Just for curiousity I did the same test on another unit that is able to connect via AFP, the results were very different.

terminal still couldn't find the file but it's search was extremely fast.

Find window- with volume selected took one min,
and with narrowing down to a specific folder took 30 secs,

so it seems something is weird with my setup.. I even did repair permissions but no luck.

You are likely making a mistake when you do the 'find' in Terminal. Please show us the full name of the file that you are searching for and show us (copy & paste) the 'find' command that you are using in Terminal.

But it seems that you have figured out the difference between your fast searches and your slow ones - it seems (from what you have said) to be related to the protocol (SMB versus AFP) used to mount the remote volume.

It seems likely that when you are in OS 9, the remote volume is mounted via AFP, but in OS X, you are mounting the volume via SMB.
You don't usually want to use SMB to mount volumes containing Macintosh files. It is usually used for mounting volumes with Windows files. SMB does not support type & creator info, so your files will not show up with the correct icons, will not open with the correct application, etc.

You should unmount the remote volume and then remount it using AFP. You could ask your system administrator about how to do this, but the usual way is to use Finder's "Connect to server" and type in a URL starting with "afp://" and followed by teh IP address of the remote machine.

Ok
 

the file is F527835 Full Sail pin.ai,
terminal: find /Volumes/vol2 'F527835*'

I know I should be using AFP but I get this: ( wish I could paste the window)

Connecting to afp:///at/artcom:upstairs...
Could not connect to the server because the name or password is not correct.

Try Again Cancel.

No matter what I try this is what the result is, the IT guy assumes that for some reason OSX switched from logining as clear text to encrypted and I can't figure out how to remove this problem and start fresh

Re: Ok
 

You forgot the "-name" part of the command. Try again with this command:

find /Volumes/vol2 -name 'F527835*'

I seem to recall this issue being discussed a few places a while ago. You should search on the main macosxhints site as well as on these forums for discussions of problems with passwords and file sharing.

Ahhhh...
 

very nice, a slight pause but within 10 secs voila...
just as quick as OS 9 used to be..

but to clairfy I was doing the test on the other machine that was running OSX, NOT OS9.. but using AFP connect.


thanks will do a search and see if I can fix my connection and run the test again through AFP.