When I did a search I initially seen it as a 2MB drive, then someone claimed it was 8MB. Different website says different things, and I don't recall Seagate's site actually giving a number. But when you look at the data sheet, it says 2MB.
AFAIK, it's a ST94011A not ST94011. The ST94011A has the 8MB cache.
deathkoba: not seeing files in a samba share is always a permissions problem. I've found that if even only one file doesn't have sharing read permissions for your user, none of the files in that share show up. Simply fix the problem by setting up inherit permissions in the sharing tab (I can't remember exactly where, because my PC is off atm - but it's much easier to do this in OS X with that Apply to Enclosed items button
). Note that in Windows, the actual file permissions are separate to the sharing permissions.
deathkoba: not seeing files in a samba share is always a permissions problem. I've found that if even only one file doesn't have sharing read permissions for your user, none of the files in that share show up. Simply fix the problem by setting up inherit permissions in the sharing tab (I can't remember exactly where, because my PC is off atm - but it's much easier to do this in OS X with that Apply to Enclosed items button
). Note that in Windows, the actual file permissions are separate to the sharing permissions.Originally posted by: hopejr
AFAIK, it's a ST94011A not ST94011. The ST94011A has the 8MB cache.
deathkoba: not seeing files in a samba share is always a permissions problem. I've found that if even only one file doesn't have sharing read permissions for your user, none of the files in that share show up. Simply fix the problem by setting up inherit permissions in the sharing tab (I can't remember exactly where, because my PC is off atm - but it's much easier to do this in OS X with that Apply to Enclosed items button
Not according to the Data Sheet linked above.
Originally posted by: hopejr
AFAIK, it's a ST94011A not ST94011. The ST94011A has the 8MB cache.
deathkoba: not seeing files in a samba share is always a permissions problem. I've found that if even only one file doesn't have sharing read permissions for your user, none of the files in that share show up. Simply fix the problem by setting up inherit permissions in the sharing tab (I can't remember exactly where, because my PC is off atm - but it's much easier to do this in OS X with that Apply to Enclosed items button
Yea I know that and already did that on the PC. All users have read/write access on the NTFS partition and the entire enclosing folder has been granted access to that particular user. It's definitely a bug in Apple's implementation of Samba as it is not consistant.
I have never with OSX, had a Blank Windows share come up and I network sometimes with 15 plus machines at the same time. All are windows XP or 2k. Every computer I repair is plugged into my network after all Virus and Spyware are zapped, and I have never had a problem with either of my OSX machines accessing the shares or their contents.
A close friend of mine recently went Mac and has many windows systems. I set it all up for him and all shares worked 100% there also. Something is wrong somewhere.
A close friend of mine recently went Mac and has many windows systems. I set it all up for him and all shares worked 100% there also. Something is wrong somewhere.
Did the freeze happen during filesharing? Could be a Samba related kernel panic?
I've used my PowerBook hard for the past 13 months starting with 10.3.1 and now up to 10.3.7 and I have never once had a crash or freeze. Maybe your Mini has a hardware defect? I'll put my Mini into some sort of a intensive loop of tasks overnight and see if it's still running fine in the morning. I hope the problem you describe isn't an epidemic!
I think you're still getting it confused. The share permissions have nothing to do with the NTFS permissions. Someone may not have NTFS permissions so will be unable to access the directory locally, but given permission on the share can access that directory through the network.Originally posted by: deathkoba
Originally posted by: hopejr
AFAIK, it's a ST94011A not ST94011. The ST94011A has the 8MB cache.
deathkoba: not seeing files in a samba share is always a permissions problem. I've found that if even only one file doesn't have sharing read permissions for your user, none of the files in that share show up. Simply fix the problem by setting up inherit permissions in the sharing tab (I can't remember exactly where, because my PC is off atm - but it's much easier to do this in OS X with that Apply to Enclosed items button
Yea I know that and already did that on the PC. All users have read/write access on the NTFS partition and the entire enclosing folder has been granted access to that particular user. It's definitely a bug in Apple's implementation of Samba as it is not consistant.
0roo0roo
No Lifer
- Sep 21, 2002
- 64,795
- 84
- 91
For someone to access a file remotely they must have both share (to be able to get to the shared file) and NTFS permissions (to be able to actually read the file).
BTO takes 4 weeks anyway, so who knows what they'll ship. Apparently, Apple doesn't know either.Originally posted by: Eug
WTF?
Today the SuperDrive is 4X again.
I think they seriously underestimated demand. Now they are just trying to fill orders with anything they have in stock. They probably have some guy in China ripping superdrives and hard drives out of Powerbooks!
- Mar 11, 2000
- 24,169
- 1,812
- 126
Mac Mini overclocking
Keep in mind that this voids your warranty, and you must have skills using the soldering iron.
Keep in mind that this voids your warranty, and you must have skills using the soldering iron.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter