Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 




      :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: filmscanners: RE: Custom PC spec

I'm using a PIII 800 with 768 MB and a Matrox G400 Dual Head under Win98SE.  
It's a year and a half or so old now, and I'm still very happy with it.  If I 
was building a new one now, I'd do a gigahertz processor with 1 gig of the 
fastest RAM I could find, a G500 card and maybe one of those new 100 gig Maxtor 
drives, with Win2K.

The only spec you've quoted that I'd change is the amount of RAM.  The more the 
better, and RAM is cheap right now.  Even if you don't get a gig to start with, 
make sure your motherboard can support it, so you can add it later.  I don't 
know much about it, but I've heard that PS6 will support dual-processor 
systems.  That may be more exotic than you really need, though.  I find my 
system is more limited by RAM size and speed, and disk speed, rather than raw 
CPU speed.


-----Original Message-----
From: Cooke, Julie [mailto:CookeJ@logica.com]
Sent: Wednesday, August 01, 2001 1:50 PM
To: 'filmscanners@halftone.co.uk'
Subject: filmscanners: RE: Custom PC spec

I've got a Celeron 466 with 128MB of RAM and recently bought a Nikon
Coolscan LS4000. I think it's time to upgrade my machine! I've concluded
that I need a custom built machine with a graphics card where the look up
table can be calibrated and a high end monitor. 

Can anyone recommend graphics cards that can be calibrated? I was thinking
of Matrox.

I was planning on getting a 1GHz Athlon with 512MB of RAM and running under
Windows 2000. The Nikon Coolscan produces file sizes of around 70MB, so a
lot of fast RAM is important. Can anyone see any problems with this spec. 

Finally if anyone has any recommendations as to companies in the UK that
could build such as machine I would be grateful. So far my research has
turned up these people who build hi end systems but I'm not sure I would
need a dual processor? Isn't RAM more important? 




-----Original Message-----
From: Jawed Ashraf [mailto:Jawed@cupidity.force9.co.uk]
Sent: Sunday, July 29, 2001 1:12 AM
To: filmscanners@halftone.co.uk
Subject: RE: filmscanners: Scanning and memory limits in Windows

I went from a PIII 500MHz to a 1.2GHz Athlon recently and file load times
(16-bit 44MB scans, uncompressed PS file format) went from around 7s to 3s.

A set of nasty PS operations on the same file (RGB->CMYK->LAB->RGB,
Dust'n'Scratches, Auto Levels) went from 105s down to 46s.  This test ran
entirely in RAM (I had 640MB of RAM for the PIII, but only 512MB for the

Very worthwhile.  I hate to think how many moons would pass waiting for a
PIII-500 to process ICE and GEM...

7200 drives kill 5400 drives as soon as lots of random disk access occurs
(i.e. not reading or writing a single file).  This is valuable if you are
trying to scan (using say Nikon Scan or Vuescan) while also editing in PS.
And browsing the web.  And writing emails.  And playing Quake, if you're
really dextrous.

A friend just bought some cute little Promise IDE ATA 100 controller for his
PC.  Win 2K sees it as a SCSI device.  Despite the fact he has a PII-450
(groan, PS really doesn't like that generation of Pentium) files on his
system load very quickly now, around 4s for that file I mentioned above (it
was 6-7s).  OK, some of it is W2K, but it seems to me that a separate
controller will make your life just that little bit sweeter.


> -----Original Message-----
> From: owner-filmscanners@halftone.co.uk
> [mailto:owner-filmscanners@halftone.co.uk]On Behalf Of Dana Trout
> Sent: 28 July 2001 20:49
> To: filmscanners@halftone.co.uk
> Subject: Re: filmscanners: Scanning and memory limits in Windows
> I find that little of the time spent is due to the disk drive, which is
> the reason for my comment that a 7200 rpm drive, even though it is 33%
> faster than a 5400 rpm drive, will not necessarily reduce load times by
> a like percentage.
> As for my times being slow, you're right: I was quoting the performace
> of my "junker" computer which is used only for scanning -- it's a 466
> Celeron with 512MB RAM but Intel's woefully undersized L2 cache.
> However, the times you quote make me wonder if you are loading
> LZW-compressed TIFFs. If so, it is *definitely* time for me to upgrade
> the scanner computer!
> Thanks for your comments,
>   --Dana
> ----------
> From: geoff murray <geoffmurray@primus.com.au>
> To: filmscanners@halftone.co.uk
> Subject: Re: filmscanners: Scanning and memory limits in Windows
> Date: Saturday, July 28, 2001 6:15 AM
> Hi Dana,
>             Gee your times seem very slow. I tried loading a 56mb file
> from
> my scratch disk and it took 3.6 seconds. A 169mb file took 17 seconds.
> This
> on a Win 98SE machine with a 1Ghz Athlon and 512mb of PC133 ram and two
> 7200rpm hard drives. Scratch partition is not on the hard drive which
> has
> PS6. 7200 rpm drives made a significant difference to overall speed.
> Geoff Murray
> www.geoffmurray.com
> ----- Original Message -----
> From: "Dana Trout" <dana@troutcom.com>
> To: <filmscanners@halftone.co.uk>
> Sent: Saturday, July 28, 2001 7:40 AM
> Subject: RE: filmscanners: Scanning and memory limits in Windows
> > A 25% faster drive won't necessarily get you 25% faster load/store
> > times. PhotoShop seems to be inordinately slow in dealing with
> > compressed TIFFs -- I got curious so I set up a cache large enough to
> > hold the whole file (53MB). The first time I loaded it into PhotoShop
> > it took 61 seconds (reading from the disk). I then closed the file
> and
> > reloaded it into PhotoShop (this time from the cache -- the disk
> light
> > never even blinked) and it took 55 seconds. And I'm reasonably sure
> > that a RAM cache is *much* faster than a 7200 rpm drive!
> >
> > BTW, Ed's VueScan takes less than 30 seconds to read the same file.
> >   --Dana
> > ----------
> > From: Rob Geraghty <harper@wordweb.com>
> > To: filmscanners@halftone.co.uk
> > Subject: filmscanners: RE: filmscanners: Scanning and memory limits
> in
> > Windows
> > Date: Friday, July 27, 2001 12:22 AM
> >
> > < snip >
> >
> > On the other hand I'm reasonably sure the main
> > bottleneck in my PC when dealing with large scans is the 5400RPM IDE
> > drive.
> >  A 7200RPM drive would speed up loading and saving files by at least
> > 25%.
> >  Two 7200rpm drives in a RAID array should be significantly better
> > still.
> >  Loading and saving files is the no.1 timewaster for me when working
> > with
> > film scans on my PC.
> >
> > Rob
> >
> >
> > Rob Geraghty harper@wordweb.com
> > http://wordweb.com
> >
> >
> >


Copyright © Lexa Software, 1996-2009.