Slow file open dialogue box

Sorry for the dead end if it didn't work for you, brilor. So far, my system is still in good shape and displaying files in the Open or Save dialog with no delay.

I did submit feedback to Apple. In my feedback, I linked a couple of forum threads like this one.

TextEdit can't do it because it won't unlock the file. Use the free TextWrangler instead. It will ask if you want to unlock the file. Do so, and you can save the change (which is just adding one # symbol to the beginning of the /net line).

OK, I opened private/etc/auto_master in Text Wrangler, I put a # in front of /net and saved it.

Now what do I do? Close Text Wrangler? OR...

Where do i type --- sudo automount -vc? At the bottom of the file in Text Wrangler

OR in Terminal? If in termina... from what directory, the root? Home?

Thank You

This is what I did in Terminal (with results) after saving the Text Wrangler file:

Last login: Wed Jan 29 04:55:39 on ttys000

joe's-imac:~ Myusename$ sudo automount -vc

Password:

automount: /home updated

automount: /net unmounted

JOE'S-imac:~ MYUSERNAME$

babylonslim wrote:

Where do i type --- sudo automount -vc?

When you see 'sudo' it mostly( commands can be put in scripts but there is no script building required here ) means a command to type in to the Terminal.app. 'sudo' requests temporary root authority which is required to execute the command ( which is the 'automount -vc' ).

btw: IMO older age doesn't necessarily imply computer ignorance; if it did I'd be really stupid. I agree the original post could have been clearer about where to use the editor vs. where to use the command.

So... This is what I typed in Terminal (with results) after saving the Text Wrangler file:

Last login: Wed Jan 29 04:55:39 on ttys000

joe's-imac:~ Myusename$

sudo automount -vc

Password:xxxxxxxx

automount: /home updated

automount: /net unmounted

JOE'S-imac:~ MYUSERNAME$

Is that the correct revisions to expect in terminal?

Am I done?

Thanks

Sorry for the long delay. I had left for the day shortly after posting.

OK, I opened private/etc/auto_master in Text Wrangler, I put a # in front of /net and saved it.

That is correct. It's all you needed to do to that file. If you view the file again in TextEdit, it should look basically like this:

#

# Automounter master map

#

+auto_master # Use directory service

#/net -hosts -nobrowse,hidefromfinder,nosuid

/home auto_home -nobrowse,hidefromfinder

/Network/Servers -fstab

/- -static

So you're done with that file. Your last post is also correct. The automount command briefly notes the current home and net settings (after updating them as necessary). That's all it does and goes back to the prompt.

Close the Terminal app and you're done. You may not even have to restart to see windows and dialogue boxes opening now without the delay.

Okay, not quite like the above. The lines wrapped funny in the forums. More like this:

#

# Automounter master map

#

+auto_master # Use directory service

#/net -hosts -nobrowse,hidefromfinder,nosuid

/home auto_home -nobrowse,hidefromfinder

/Network/Servers -fstab

/- -static

I made the auto-master change and rebooted, which I guess should do the automount part. It did nothing for me.

And even worse, my Parallels Windows 8.1 VM now has disk access errors (to my SSD).

Some were from Norton on the Mac interpreting them as ARP cache attacks. I turned off detecting them in Norton. Now I get other disk busy errors.

Disk utility says all disks are fine, as does SMART.

I'm having this problem on a brand new, late-2013 15" Retina MBP with quad core i7 and 16GB RAM, 512GB SSD, set up as new machine, not restored from Time Machine backup.

Can someone tell me exactly what the terminal workaround does and what (if any) negative effects it has?

Give me an example?

I've applied the workaround. On my MBP if I click "Mac Mini" under "Shared" in Finder, all my drives on the Mac Mini show up in the Finder window. If I double click one, it mounts on my MBP dekstop just fine.

Unless I'm completely missing the point here...

Specific to what you comment out with this workaround: Not a big deal for the vast majority of users, and, for those that it may impact, there may be some level of inconvenience that is not as annoying as the problem being addressed.

I'll go ahead and assume you'll be fine with this workaround in place, markmc78. I hope it works for you as it has fore most of those that have tried it and after seeing no reports of anyone's world coming to an end :)

Yup, but the Mavericks issue seems to be that the OS gets hung up looking for a network drive that may not be mounted. And that's about the extent of what I know. 🙂

I did look at the auto_master file in Snow Leopard and Mountain Lion. It's basically identical, but works correctly without having to comment out the /net ... line. So it appears some other bug related to the contents of the auto_master file is the problem.

I'll go ahead and assume you'll be fine with this workaround in place, markmc78.

We've seen no problems with it here. All Macs running Mavericks with the modified file can still access all networked drives the same as always. The only thing that changes is the annoying delay in every single save or open dialogue box is gone. The delay even affected opening your own local partitions. All fixed now.

In October I was in the states for a week. So I installed a large SSD and mavericks. Thought I'd do it in case there were any issues. Although that breaks the "only one change at a time" rule, I felt that it would be OK. since they were quite disparate items. oops...

After that, I found this "hang" on save (and on open from an app). It was killing me. since I made 2 major changes, I suspected that it was the SSD, that was having trouble.

However, after (just now) finding this thread, I implemented it and Voila! it works!

So, this is a REALLY??? for Apple OSX designers: At what point did it become ok to go and check drive availability in the entire known universe just to open or save a file, especially when the destination/source of the file is local? And what was it in Mavericks that you changed to make that happen?

I'm guessing that some genius made the assumption that once you've connected your computer to a network, you would always have that network and those connections available. What part of "laptop" or "portable" don't they get?

Well, a workaround that deletes some system functionality is really not acceptable from a design perspective. I hope this is on a bug report somewhere...

But big kudos to the guy who figured this out. you are my hero for the week!