Yeah, let's assume that Apple is turning its back, whistling thru lunch and doing nothing.

Fer chrissake, there is one demo'd bug in the finder, it's been less than 24 hours in getting this news out, and Apple needs to fix a bug in something as complex as the Finder.

As for the drive, it's not confirmed, if it is it's Seagate's problem, and as soon as they confirm it and get a fix in place, I'm sure Apple will be on board with it.

I don't know if this is a new problem, but it was potentially dangerous in my case.

I have a lot of log files with a specific extension in a folder mixed with a lot of other files. For examples sake, lets say .storage is the extension.

The folder that all of those files are in is also called Storage.

Well, I did a Finder search in the folder "Storage" for all the files in that folder with the .storage extension that I wanted to delete, and the top level folder "Storage" was mixed in with the search results. When I selected Command + A to selected them and delete them, the folder "Storage" was also deleted. The is dangerous because that also deleted all the other files in that folder.

Fortunately I caught that the folder was missing before I emptied the Trash! I think this needs to be fixed?

Seagate should definitely have a recall.

And Apple should definitely issue a Leopard patch.

Here's hoping both companies do what is needed!

Meanwhile, I'd like to see some AP articles about how PC laptops are better because "Apple hard drives" are unreliable

Same thing happened to me... sort of. When I was installing I chose the "archive and install" option. It was about 90+% done and was in the process of moving my user folder and settings over, when the install failed.

I had to reinstall the OS, and chose to use the 'upgrade' method instead - which worked flawlessly.

On the first boot up, I noticed that it had toasted nearly all of the information in my home directory. My desktop was gone (which contained a number of files, Documents -- gone (containing archived work history for billing, and my Microsoft User Data), and a ton of other stuff.

Luckily, I had moved from Entourage over to Mail a few months ago, so my mail was still intact in the library.

At any rate -- ouch. It was a nasty couple of days recreating what was lost. Made me realize I had gotten sloppy in my weekly backups to the server. :-/

Actually this news has been out for a week.

I never move files from one place to another. As a matter of fact I think it should be removed from the operating system. I spend the extra 3 seconds and copy the files and manually delete the original files when the copying is done.

Quote:

Originally Posted by jpellino

Fer chrissake, there is one demo'd bug in the finder, it's been less than 24 hours in getting this news out.

I believe Windows XP has similar behavior. It can be called a bug, but it can also be called a feature. The default behavior for dragging to another volume is copy, so one has to actively choose move.

How many have had my experience of downloading a large file, and suddenly realizing there is not enough space, so then quickly starting a "move" of files to another volume to immediately free up space?

The moving bug is something Apple should address, and I'm sure they will. Although I'm with others that moving is generally a bad thing.

The Seagate bug isn't directly Apple's fault. If it can be fixed by Firmware, Apple should make that available in Software Update for those affected. Otherwise it's really a matter of identifying the true likelihood of failure and doing preventative repairs if needed. There have been many "bad drives" over the years (Maxtor had a big problem years back) and I never remember anyone doing an actual recall. This would be extremely costly for Seagate as they'd have to pay for tens or hundreds of thousands of repairs by authorized repair centers - not just for Macs, but every OEM that's put their drives into laptops. Apple won't do anything unless Seagate is footing the bill.

I use the move all the time. Scary that I was at risk for data loss. I've read the move does not exhibit this problem with OS 10.4 and the "mv" UNIX command does not exhibit this problem either. Seeing that it works with the underlying UNIX file system, how difficult would this be to fix?