arri
Registered
ok, this is not really a question,
i was wondering about your opinion,
and maybe solutions/workarounds for this ever returning problem;
you mount volume of some remote computer,
but this machine gets disconnected..
result is that the finder will hang for some minutes,
and sometimes other apps..
i noticed this also happens when trying to access a 'recent folder'
(from go > recent folders-menu) when the remote machine is disconected..
i found that relaunching the finder often takes as much time,
as waiting for the finder to finally get out of it's coma..
anyway, already since pre-osx systems this was happening,
i hoped for osx to have solved this problem..
why is apple unable to solve this in an elegant way?
or am i doing things wrong?
is there a solution?
(appart from this apple-script i once downloaded,
which would only run after the finder finally gave the
"server doconnected" popup)
i think this is one of the greatest design-flaws in osx
\
i was wondering about your opinion,
and maybe solutions/workarounds for this ever returning problem;
you mount volume of some remote computer,
but this machine gets disconnected..
result is that the finder will hang for some minutes,
and sometimes other apps..
i noticed this also happens when trying to access a 'recent folder'
(from go > recent folders-menu) when the remote machine is disconected..
i found that relaunching the finder often takes as much time,
as waiting for the finder to finally get out of it's coma..
anyway, already since pre-osx systems this was happening,
i hoped for osx to have solved this problem..
why is apple unable to solve this in an elegant way?
or am i doing things wrong?
is there a solution?
(appart from this apple-script i once downloaded,
which would only run after the finder finally gave the
"server doconnected" popup)
i think this is one of the greatest design-flaws in osx
\