Samba Sharing and Folders

[Andrade Nation]

I have done some searching and haven't found this yet, so here's my trouble... but if you do know of this topic exisitng in a nother place, please direct me there...

 

I am running the 10.4.10 install (upgrade from 10.4.8) on my eMachines T3410 (my soldier box that trucks through anything impossible).

 

I am sharing my media out over the network via SMB for access on my laptop and XBMC.

The media folder is on an NTFS drive, 250G, and read-only is perfect.

OS X can see all the files and I can play the media in OSX and over the network fine.

 

Thing is that when I browse to the SMB Shares on the OSX machine, the folders all show up as 0 byte files which cannot be accessed. That is, until I at least access the folder once from OSX.

Once I do that, the folder is ready to go from the Windows machines.

 

It's a strange step to take and by no means stifling, but I havent' found anyone else to be having that problem or if it has been experienced and deemed to be just the way it works for the time being.

 

Could it be the way it is mounted in OSX?

[Andrade Nation]

I have done some searching and haven't found this yet, so here's my trouble... but if you do know of this topic exisitng in a nother place, please direct me there...

 

I am running the 10.4.10 install (upgrade from 10.4.8) on my eMachines T3410 (my soldier box that trucks through anything impossible).

 

I am sharing my media out over the network via SMB for access on my laptop and XBMC.

The media folder is on an NTFS drive, 250G, and read-only is perfect.

OS X can see all the files and I can play the media in OSX and over the network fine.

 

Thing is that when I browse to the SMB Shares on the OSX machine, the folders all show up as 0 byte files which cannot be accessed. That is, until I at least access the folder once from OSX.

Once I do that, the folder is ready to go from the Windows machines.

 

It's a strange step to take and by no means stifling, but I havent' found anyone else to be having that problem or if it has been experienced and deemed to be just the way it works for the time being.

 

Could it be the way it is mounted in OSX?

 

Did some brute force testing and it seems that it is the way the NTFS is mounted in OSX by default.

Tried some different options and settings but to no avail.

Edited /etc/fstab for the entries to prevent the automount of the partitions.

 

Installed the ntfs-3g pacakge and use those to automount in rc.local.

Now that they are mounted with this package and then shared out via SAMBA, all the files and folders are acting as they should, and more responsive as well, over the network.

 

NTFS-3g and SharePoints are too great packages together.