Problem with scanning in PS CS6 - scanning process crashes

Question

Hi.
Here is my hardware:
   Macbook pro 4 GB DDR3 core i5 with plenty of HD space
   Epson V700 scanner (6400 dpi scanning capability)
My Software:
   Adobe CS6 trial
What I want to do:
   Scan a typical photo that is 6 by 6 inches at 6400 dpi as a bitmap, for utmost quality
What I tried:
   File -> Import -> Images from device -> then selected my scanner, set it to scan at 6400 dpi and save as a bitmap
My problem:
    When the scanner head is done scanning and the progress bar for scanning the image completes and moves to the next step (presumably writing the image to the file), PS crashes and gives me an error log. It is far too detailed for me. I have no problem scanning images at lower resolutions like 1200 dpi. But this scanner is capable of 6400 dpi and I want to take full advantage of it. I cannot use the scanner software that came with teh scanner because tech support told me the scanner software has a 1.something GB file limit size. They told me 3rd party software like PS should be able to scan unlimited file sizes.
   I suspect the file size migh be too large (16 GB)
My question:
   Is this a bug in the trial or something? Should PS be able to scan a 6 by 6 inch photo at 6400 dpi and save it as a bitmap?
Any 1st thoughts? I imagine it would be useful to upload the error log. I can do that if it is ok to do so
Thanks, your help is appreciated since I would lik eto scan this image at 6400 dpi. If I am given a solution, I will probably buy the full version

Answer 1

I downloaded and placed the new Mac plugin that PDFerguson was talking about. I also made sure I had the latest drivers from EPson. I have the same problem. I tried a couple of different file formats, like TIFF (at 6400 dpi and billions of colors) and while "reading the TIFF file" it stops and tells me : "Could not complete your request because of a problem parsing the TIFF file.". Just to note, I scan to a new PS document, so it seems like it has scanned the image, but after a certain file size the driver/PS messes up the creation of the file. Then when PS reads that image data that it just made in some temporary location (which I am presuming is an improper image) into a new document (I say this because when PS opens a file it says "reading blah blah"), the parser (JPG, TIFF, etc....) crashes somewhere in the process of reading the file that it just wrote to temporary disk space into a new PS document.
Because of these facts, I am led to believe that there seems to be some size limit after which PS or whatever is writing the temporarily scanned file where this file becomes corrupt. My suspicion of this as the cause of the problem is made darker from this experience: when I use the Apple OS scanning utility, and scan it at the dpi and color depth at which PS crashes, the apple utility does not crash, but instead produces a corrupt file on my disk. I say it is corrupt becasue the file is all black or white and has no scanned information. Likewise, when PS tries to open up those images, its parser for a particular file type fails, probably because it encounters an error.
That sounds confusing so here is a diagram:
Scanner invoked in PS => scans successfully at 6400 dpi and writes image data to scratch disk space (but this data is corrupt) =>PS tries to make a new document by reading this image data like it would open up a file from disk, using the appropriate format parser => because the iage data on scratch disk has been corrupted, the parser crashes as it encounters bad format data.
When I ask PS to scan into BMP files, I get a vague error, which I presume is becasue the parser for BMP is quite primitive and will cast bad data as pixels anyways?
From all this experimentation this is what I have concluded. The problem doesnt seem to be with how much RAM I have, or teh scanner driver itself, but the step where the software writes the scanned image data temporarily to disk (and messes up in doing so), causing any further image saving steps to fail, because the parser encounters an exception.
Any thoughts from the engineers?