One thing I always hated about windows was it's need to prompt me over and over again during a very long task. One such long task involves copying folders full of images. I would get prompted hundreds or even thousands of times whether to copy the "read only hidden system file" thumbs.db. I went out of my way to delete it before starting a copy session. OS X on the other hand, looks for hiccups like this and prompts you before the process starts. At least this is what an Apple genius claimed when I asked him about this topic. NOT SO! Last night, I started a copy of 21 gig of music to a 32 gig usb flash drive. It told me I had 10 hours remaining so I went off to bed hoping the estimate was wrong and it would be done when I got up. In the morning, what did I see but a dialog asking me whether to copy ".afpDeleted99999" (It was actually a random string of numbers I didn't bother writing down. This dialog popped up after only 3 gig of the total 21 gig got copied. Did OS X ignore this error which affected only 1024 bytes of my 21 gig task and obediently bring me my results the next morning? No. I'm disappointed. I opened a shell at the root of my music folders and typed: "find . -name ".afp*" -print" to make sure there weren't any more of these slimy little turds standing between me and my usb stick 2/3 full of music. I wish I knew a sure fire way to get this in front of Apple engineering so they could close this loophole. When I start my Mac doing something that involves moving 21 gig of stuff, I don't want it to get snagged over a trivial question regarding 1024 bytes somewhere in the middle. This issue leads me to wonder... As Apple becomes more mainstream and tries to become more complex so it can do more for more people, is Apple starting to lose their "Just Works" mojo?