What the heck; since the Athlon Xp 1.4 was my 2nd processor and is still my back-up machine, I'll add my 2cents worth; with PS 6 and 7.0 it never had any trouble with 50 MB files. It didn't really choke until it got above 150-200mb. My current processor is an Athlon XP 3000+ and it is doing fine in the 300-500mb range and doesn't really groan until it gets up over a Gig. So I think something is a bit gamey with your system, or maybe you've got too many things running in the background. More memory as Anthony suggests can't hurt, but check your CPU operating temperature also. AMD lists 80 celsius as max, but that's actually a meltdown temp; my impression is that the AMDs slow down to prevent overheating long before that. As for the file-size argument: maybe I missed it, having jumped in rather late, but there's a point that has been implied but not stated clearly enough perhaps: the printer driver throws away (downsamples) data beyond it's stated hardware DPI: 720 for the desktop Epsons, and 360 for the bigger models. Any higher res you may think you're printing at, is actually dithering; the printer lays down several dots for each actual dot of input info. So feeding it a big file to make a small print will produce no better quality than having the correct file size to begin with. I have read that at least in theory scanning at full hardware resolution produces the sharpest scan, but I for one have been unable to see the difference. Hope this helps Steve Karafyllakis --- In DigitalBlackandWhiteThePrint@yahoogroups.com, Matthew Wensing <wensing@s...> wrote: > Thanks, Ken. Your response is, as have been many > others, very helpful. > > Matt > > > --- Ken Carney <kcarney1@c...> wrote: > > ===== > E-mail: wensing@s... > Blog: <http://seaofglass.blogspot.com> > Photography: <http://www.wensing-photo.com>
Message
Re: [Digital BW] Computing power
2004-12-03 by Steven Karafyllakis
Attachments
- No local attachments were found for this message.