Taperssection.com
Gear / Technical Help => Recording Gear => Topic started by: reesey on April 25, 2005, 05:13:15 PM
-
any known transfer issues with macs? thanks.
-
http://taperssection.com/index.php?topic=39148.0
-
no problems on a 2005 powerbook here
-
any known transfer issues with macs? thanks.
I've been experiencing a couple issues...
1.) After transfering shows to my '04 powerbook, I will get a message on the 722 that says... "INHDD was not shutdown properly. Would you like to run a repair?" I will then run the repair, but when it's done, it will say it found like 50 errors, but only about half will get fixed. Everything stays connected, so I dont see how or why this keeps happening.
2.) When I try to dither the files down in Spark XL, I get a message saying spark can't dither because "files are marked with error". Does this mean my files are somehow corrupt?
*Edit* My dithering issue was due to a software bug in Spark, which can be fixed by updating to the latest version. I still have'nt figured out why my 722 insists on automatically unmounting/ejecting itself, though.
-
For #1, are you ejecting the 722 drive properly? You should not unplug the 722 unless the normal screen is showing again, not the "connected to computer" screen.
For #2, I've never seen that error from Spark.
What firmware are you running? You should update to 1.32 if you haven't yet.
-
For #1, are you ejecting the 722 drive properly? You should not unplug the 722 unless the normal screen is showing again, not the "connected to computer" screen.
For #2, I've never seen that error from Spark.
What firmware are you running? You should update to 1.32 if you haven't yet.
I'm not ejecting the 722 drive at all (that's the problem). I will get the message as soon as a folder/file is finished transfering. I will also get it when I 'properly' eject the 722 from my laptop. I also get it when nothings going on. The problem is happening with all version of firmware i've used (i think i've been through 3).
-
Have you tried 1.32? They claim to have fixed the repair utility in that version. On my drive, the new version was able to repair detected errors that the previous version detected but failed to repair.
Very often I cannot get the host to unmount the 722 drive. I've had no choice about 50% of the time and have to detach without a managed shutdown. Is this a common problem or just a windows issue? Does it ever happen on the apple machines?
-
Have you tried 1.32? They claim to have fixed the repair utility in that version. On my drive, the new version was able to repair detected errors that the previous version detected but failed to repair.
I just upgraged to the lastest version. We'll see if that helps.
I've had no choice about 50% of the time and have to detach without a managed shutdown. Does it ever happen on the apple machines?
Yes, it's happened to me more than once.
-
I upgraded the firmware and the first transfer I attempted did the same thing. It will still un-mount itself without me doing anything.
-
Is it possible that you have a bad cable? Can you try another machine and cable?
I had some problems with firewire connectivity and I had to send the 722 back to SD for repair of an intermittant solder joint. Except for the MD5 consistancy issues, it has been solid with respect to attaching and transferring since.