Dedar Allen, you wrote: > Since upgrading to MacOS X 10.1, I've been having some annoying problems > accessing network drives (NTFS, NT 4 sp 6). > > The most serious is that after I have been accessing files for a while, I > will get an error message (from the OS) that a file can't be accessed > because the original for the alias can't be found (can't remember the exact > text of the message ... I'll write it down next time). The files and > folders have all changed to look like aliases. It seems to happen beyond a > certain level down in the file system but everything is okay until you get > down to that level. When this happens, there is no way to get around it > other than to re-boot the machine ... then everything is fine again.
That's a problem between the application framework and Sharity's automounter. At least Carbon applications don't go through the automounter after the initial access. This problem can easily be fixed by changing the auto-unmount timeout in the "CIFS Browsers" section of Sharity's GUI to the maximum possible value (you must be in expert mode in order to change the value). The next OS X version of Sharity will ship with this default. > Mounted disks become non-functional after a while ... they still appear on > the desktop or in a finder window but they disappear when you click on them. > It is possible to just use the mounted "CIFS" disk or go through "Network" > in a finder window to get at the disk again. That's the same thing, only viewed from Finder's perspective. Changing the unmount timeout will help here, too. > When editting a file on a remote disk with BBEdit, every once in a while > BBEdit loses it's ability to write to the file and it becomes necessary to > "save as" to overwrite the existing file and "re-connect" BBEdit to the > source file on the disk. I have not heared about this one, but it might be related to the automatic unmount. Please try changing the parameter and see which problems remain and which go away. > These are apparently issues which have been brought on by the 10.1 upgrade. > Will a update to Sharity be made available or is there something I can > configure with the current version which will fix these problems? Both, see above... BTW: since 10.1, you can unmount shares from Sharity's GUI (not with eject from Finder). No more need for a kernel patch. Regards, Christian. -- Dipl.-Ing. Christian Starkjohann Objective Development mailto:[EMAIL PROTECTED] | http://www.obdev.at/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ To unsubscribe send a mail with the words "unsubscribe sharity-talk" in the body to <[EMAIL PROTECTED]>. If you want to reach a human, please write to <[EMAIL PROTECTED]>.
