How to Fix Terminal Refusal to Copy Tiff Files, shows error 36 on MacBook Air

Question

Level 1

15 points

How to Fix Terminal Refusal to Copy Tiff Files, shows error 36 on MacBook Air

I'm trying to copy 12 Tiff files from a cd rom: some went across OK, others I managed to fix with dot_clean. but 3 others Terminal refuses. When I copied the files singly they gave an error message (36) but in the destination folder there was a title and a the correct file size.

The reply from terminal when I put the folder in the terminal window was

zsh: permission denied: /Users/mymachine/Desktop/Folder Name /Tiff files/Unreadable(error36)

[ Unreadable(error36) is the name of the folder with the 3 problem files ]

They have previews, but all blank—white or black

I've checked the permissions of the folder—they are read and write: me, staff, everybody

Any advice would be very welcome.

[Re-Titled by Moderator]

MacBook Air 13″

Posted on Feb 12, 2024 2:56 AM

Reply

Answer 1

BDAqua

Level 10

251,131 points

Feb 12, 2024 3:44 AM in response to gilcs

Is it a minus 36?

Well, in pure Apple File System talk... -36 ioErr I/O error (bummers)

Not very helpful, but generally means a Drive quit being Readable or Writable since starting the operation...

http://fuzzy.wordpress.com/2006/12/10/ioerror-36/

I doubt the files are good on the CD, but you might try Gisk Utility>File>New Image from Folder,as it tries several Reads in an attempt to get the info.

Reply

Answer 2

gilcs Author

Level 1

15 points

Feb 12, 2024 10:01 AM in response to gilcs

Sorry, I didn't make myself clear. I managed to copy the files over from CD to computer, despite an error message saying some files were unreadable, error -36. Some I cleaned with dot_clean in the terminal but for others Terminal gave an error message: zsh: permission denied: /Users/mymachine/Desktop/Top Folder Name /Tiff files/Folderwithproblemfiles.

Reply

Answer 3

BDAqua

Level 10

251,131 points

Feb 12, 2024 10:47 AM in response to gilcs

Well, I think it read how big the files were & their names, reserved space on the destination drive, then failed when reading the actual data for the files... unless you can provide more info. :)

Reply