Large file printing errors with Epson 4800/9800

[Greg Miller]

As for freeing the largest amount of memory I've contemplated the possibilty of running CS2 as a 32 bit process in XP64 in which case it should be possible to allocate a full 4GBs to PS. However, I don't know of anyone who's tried this and I haven't worked up the nerve myself.

This will only work when Phosotshop is also updated with the code to address that much memory (I may be worng but I don't think this has happened yet). Under 64 bit, both Windows and Photoshop will have the theoretical capability of addressing quite a bit more than 4GB.

[Greg Miller]

This will only work when Phosotshop is also updated with the code to address that much memory (I may be worng but I don't think this has happened yet). Under 64 bit, both Windows and Photoshop will have the theoretical capability of addressing quite a bit more than 4GB.

According to Adobe (http://www.adobe.com/support/techdocs/320005.html), Photoshop CS2 can currently only address up to 3GB with 64 bit. If you have more than 4GB total then it will use RAM above 4 GB for the swap disk when it can.

[ben-passiontolive]

I've come up with another work around to the "program error" issue for large prints with Photoshop 9.0.1 and the Epson 9800 on a Mac. The workaround came out of a phone call with the Adobe techs. Essentially save the image as a tiff and then open with Apple's Preview app and print from within it.

Using this approach I have a 44" x 66" print at 360 resolution (1.15GB file) on its way out now. So far it's working.

I'm going to do additional testing with trying to print from Aperture and also with using Adobe's psb format. I'll update here.

-Ben

___________________
passiontolive
ben@passiontolive.com
http://www.passiontolive.com

[QT Luong]

Yes, I also have this problem with my G5/2.0 (OS 10.3.9, 4.5GB memory) and 9800. My solution has been to just print at 240dpi for the larger print sizes.

[MJSfoto1956]

Anecdotal at best: I have a dedicated RAID 0 swap disk dedicated to Photoshop. Every once and a while with Photoshop I will get the dreaded "spinning wheel of death" doing basic things like opening, saving, printing, etc. (however, it eventually gets around to doing what it was supposed to do, only it takes much longer than any mere mortal should have to endure)

By chance during one of these spinning wheel moments I chanced to copy a small file to the swap drive and instantaneously the spinning wheel of death disappeared. Since then I have validated that this simple procedure "fixes" 90% of my spinning wheel of death moments. Not sure exactly what it means but is suggests that at the core of the problem, Adobe has their way of doing virtual memory (read, swapping) and Apple has their way of doing swapping and the two techniques simply ain't happy living together. Thus, every once in a while you need to "kick it in the ass" to get things moving again!

Just my two cents.

[jim kitchen]

Periodically and although somewhat related to the issue at hand, I work with files that approach 3.5gb in Photoshop on my Mac, and the spinning wheel of death can surface for several minutes...

I discovered, quite by accident, a method that seems to relieve that issue. I touch the finder, and I start up another program, such as my email program. These two actions seem to interrupt Photoshop's absolute control of my computer's memory. Touching the finder allows Photoshop to complete the task at hand at some point in time, and allows my email program to gain access the usurped memory. I have 8GB of Ram, and I find it annoying that this known memory leak, impacts my computer the way it does...

Photoshop's memory leak can interrupt the allocated memory, required by the operating system, and it will eventually totally consume this allocated memory. This imperfection will introduce a number of side effects. The side effects are not limited too printing commands, but can include the interruption of a number of Photoshop actions, such as implementing a filtering action, and even interrupt the simple action of saving a file to disk.

Activating the "Force Quit" window, while only highlighting the action but not implementing the action, seems to work too. I also discovered, that if I "Force Quit" Photoshop, after the application consumes my allocated operating system memory, I can experience a few issues upon a restart.

Since I know this memory leak condition exists and surfaces, I restart my computer after Photoshop relinquishes the memory, and after I save my file in Photoshop. Placing more Ram into a computer allows the imperfection to hide for a while, but the memory leak will eventually act upon the operating system. This Photoshop memory leak forces me to save my files frequently and restart my computer frequently, which seems to be for the moment, a good habit.

jim k

[studio 58]

this is a late reply to an old thread. I have been dealing with the same issue & other crazy crap from my 4800. Solution found !!!!! I am printing through Lightroom 2 & everything is beautiful.