The DAM Forum
Welcome, Guest. Please login or register.
September 21, 2017, 04:04:53 PM

Login with username, password and session length
Search:     Advanced search
28031 Posts in 5146 Topics by 2907 Members
Latest Member: kbroch
* Home Help Search Login Register
+  The DAM Forum
|-+  DAM Stuff
| |-+  Scans and Camera Scans
| | |-+  scanned tif files will not open up on all hard drives
« previous next »
Pages: [1] Print
Author Topic: scanned tif files will not open up on all hard drives  (Read 3179 times)
Sossity Corby
Full Member
***
Posts: 247


View Profile
« on: May 29, 2014, 04:11:12 AM »

I recently scanned my college diploma, using my epson perfection scanner, at 600 dpi, with both Adobe RGB 48 bit and sRGB 24 bit, and scanned it as tif files. These raw scans were scanned to my macs internal rotational 500 gb standard hard drive. Both quick look and preview have no problems viewing these files.

I then copied these onto my macs internal 240 gb solid state hard drive and a thumb drive, and tried to view the files with quick look, and preview, and both had trouble opening them, saying the file extension is not supported or the file might be damaged. I have tried changing the file extension name, but this does not help.

my mac has dual solid state and rotational hard drive, running 10.8.5.

I am totally baffled as to what the problem might be, I have scanned a few other certificates like this in the past, with no problems, now suddenly there is. It is frustrating, I do not want to have to rescan but if that is what is needed, I will.

anybody have any idea what might be wrong? I dont want to continue scanning other content if my scanner is bad, but it seems I am facing a time consuming process of trying to find the problem, be it the files themselves or hardware problems.

Sossity
Logged
BeckyMalaria
Jr. Member
**
Posts: 58


View Profile
« Reply #1 on: June 03, 2014, 08:40:29 AM »

Hi,

Can you open the damaged file with another program like Photoshop?

Before assuming the problem is with my scanner, I would test if it might be something about the transfer operation from drive to drive.

Since the problem occurred after copying the file, try running a file-verification tool on it (I use ImageVerifier) before and after copying the file. Or try doing a validated transfer in the first place. What results do you get? Does the problem re-occur?

-Becky
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!