Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Thread

Re: [Digital BW] Re: Premature page eject - what about XP?

Re: [Digital BW] Re: Premature page eject - what about XP?

2002-08-29 by Martin Wesley

Steve,

Two things to try. When this happens save the file under a temporary name.
Close it and then close PS. This is to get PS to release all the memory that
it is hogging. PS doesn't handle the printing. It is an Epson driver/Windows
issue. The printing is spooled form disk and the amount of RAM doesn't seem
to matter. Restart PS and open your file. Try printing it again and make
sure that the "Print Preview" box is checked. This way you should see if a
print will be truncated before you commit paper to the printer.

Other solution. In the Epson driver Properties window under the "Utilities"
tab click on the "Speed & Progress" button. In the window that opens check
the "Always spool RAW datatype" box. This effects the operation of the
Windows print spooler. This seems to have eliminated the problem for me.

Martin Wesley

http://www.borderless-photos.de/guests.html



----- Original Message -----
From: "scrber" <stephen.bate@...>
To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
Sent: Thursday, August 29, 2002 2:59 AM
Subject: [Digital BW] Re: Premature page eject - what about XP?


> --- In DigitalBlackandWhiteThePrint@y..., Jerry Olson
> <jerryolson@r...> wrote:
>
>
> I have the same problem in windows XP, also with 1 GB RAM - prints
> often spit out after a couple of inches.
>
> How do you change the RAM allocation to the Epson driver in Windows???
>
> Thanks
>
> Steve.
>
>
>
>
> > Hi Bob,
> >
> > Well, if anything, you should notice a marked improvement with
> > photoshops speed at doing everyday tasks! Can't understand how you
> could
> > be getting clogs so fast, especially all inks at the same time.
> > Hopefully, somebody else who has experienced the problem will be
> able to
> > chime in here.
> >
> > Jerry
>
>
>
> Please visit the Group Homepage to check the Files, Bookmarks, Polls and
other resources as they are often being updated. The page is at:
>
> http://groups.yahoo.com/group/DigitalBlackandWhiteThePrint
>
> If you wish to receive no emails or just a daily digest, or you wish to
unsubscribe, please edit your Membership preferences by visiting this same
page.
>
> Please follow these basic guidelines:
> - Include your full name with your message.
> - Include the address of your website, if you have one.
> - As threads develop, trim off excess portions of earlier messages to keep
them short.
> - As the topic of a thread changes remember to change the subject header.
> - Good manners are required at all time. No personal attacks or
&amp;amp;quot;flames.&amp;amp;quot;
> - Complete your Yahoo profile.
> - Before posting a question, search the message archives and the various
resources on the homepage.
Show quoted textHide quoted text
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>

Re: [Digital BW] Re: Premature page eject - what about XP?

2002-08-29 by Tim Spragens

When this was happening to me, I found that *something* was needing 
drive space on the OS partition, even though temporary files, scratch 
space, paging files, spool, were all directed to other partitions.

If you still don't have it sorted, try clearing room on your OS 
partition.

> ----- Original Message -----
> From: "scrber" <stephen.bate@...>
> To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
> Sent: Thursday, August 29, 2002 2:59 AM
> Subject: [Digital BW] Re: Premature page eject - what about XP?
> 
> 
> > --- In DigitalBlackandWhiteThePrint@y..., Jerry Olson
> > <jerryolson@r...> wrote:
> >
> >
> > I have the same problem in windows XP, also with 1 GB RAM - prints
> > often spit out after a couple of inches.
> >
> > How do you change the RAM allocation to the Epson driver in Windows???
> >
> > Thanks

-- 
Tim Spragens

http://www.borderless-photos.de
http://www.borderless-photos.com

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.