On 18/7/03 13:53, "Laurie Solomon" <LAURIE@ADVANCENET.NET> wrote:
>> Maybe not impossible, just difficult and time consuming.
>
> I do not know what planet you live on or in what universe you operate;
> but here on planet Earth in this universe it is still impossible to
> assign 120 thousand MB of physical RAM to Photoshop on a system that
> only has 304MB of physical RAM.
Naw, Laurie,I just accepted your supposition that the number as given was in
error - intended to be 120 meg - (indeed, you can't assign 120,000 meg from
a system with 304 meg - didn't know that this would arose an attack cat. The
universe is the same, and I wonder why you felt the need to jump me. I
stopped doing flame wars long ago, but if you wish...
>
> filmscanners_owner@halftone.co.uk <> wrote:
>> On 17/7/03 10:34, "LAURIE SOLOMON" <laurie@advancenet.net> wrote:
>>
>>> I believe that your so-called clue is a normal condition and one of
>>> the reasons why one requires a large scratch disk of unfragmented
>>> contiguous space usually 3-5 times the size of one's actual file
>>> size.
>> You do need to
>>> turn virtual memory on so as to use the scratch disks. The 120MB of
>>> physical RAM is really very little in the scheme of things with
>>> contemporary machines having up to 3GB of physical RAM with as much
>>> as 1GB asigned to Photoshop. However, unless you are working with 3
>>> or 4 100MB plus files during a session, it should not cause the
>>> Photoshop to freeze once you turn the virtual memory back on and
>>> assign Photoshop a sccratch disk space one a hard drive with some
>>> free contiguous unfragmented space of around 100MB or more ( better
>>> yet assign the scratch disk itsown dedicated hard drive or, at least
>>> a dedicated partition on a hard drive).
>>>
>>>> There is 304MB installed RAM of which 120,000MB are assigned to
>>>> Photoshop.
>>>
>>> I assume that the 120,000MB iws an error and should read 120MB;
>>> otherwise that is your problem, you are trying to do the impossible.
>>> :-)
>>
>> Maybe not impossible, just difficult and time consuming. I recently
>> tried to do some work on a PC with 256 RAM, and after scanning a 100
>> Meg file, any attempt to work with it was very slow (as in many
>> minutes) as photoshop was paging material out to the disk at a
>> frightening rate. It took minutes to do the simplest thing. If
>> there is only 120 Meg available to photoshop, it will page (and tell
>> you if you don't have enough disk space - er, I think it is the OS
>> that tells you... I normally use a G$ with dual processors and 512
>> meg of RAM and it is very fast (I made 80% of the RAM available to
>> Photoshop. I can get it to page too, but I have to work at it, and I
>> prefer not. The point is that photoshop isn't necessarily "freezing,
>> it is just busy with the writes to and reads from the disk.
>>
>> As Laurie implied, *give it more RAM*!
>> Brad
>>
>>>
>>> You also might check to see if the files which are to be saved are
>>> flattened files since sometimes undesr some settings one cannot save
>>> unflattened files; files that are 42 bit as oppposed to 24 bit also
>>> cannot be saved to a TIFF format.
>>>
>>>
>>> -----Original Message-----
>>> From: filmscanners_owner@halftone.co.uk
>>> [mailto:filmscanners_owner@halftone.co.uk]On Behalf Of Maaki
>>> Sent: Thursday, July 17, 2003 4:24 AM
>>> To: laurie@advancenet.net
>>> Subject: [filmscanners] Photoshop freezing
>>>
>>>
>>> I've hired a graphic designer to scan and colour correct some
>>> transparencies using Photoshop, and I have set her up on a new Epson
>>> 3200 scanner, and a PowerMac 9500 upgraded with a G3/400/1MB card,
>>> and running Mac OS 9.1. (I had never used Photoshop myself, but I
>>> seem to be the tech support person for all the Macs around here).
>>> There is 304MB installed RAM of which 120,000MB are assigned to
>>> Photoshop. Virtual Memory is off.
>>>
>>> Today Photoshop kept freezing. It seemed to work fine for the first
>>> file opened and adjusted, but it always froze during the "Save As"
>>> of the second file. The files are in the range of 20 to 40 MB in
>>> size.
>>>
>>> Following is what happens. Open a Photoshop TIFF file, make some
>>> adjustments and save it as under a new title and then close it. Then
>>> when another TIFF file is opened, everything is the same up until the
>>> "Save As" operation. When the dialog appears asking whether to save
>>> as a "PC" or "Macintosh" file, the program freezes as soon as
>>> "Macintosh' is clicked leaving a white space where the dialog had
>>> been.
>>>
>>> Any ideas?
>>>
>>> CLUE
>>> (A) I've checked with Memory Mapper, and find that Photoshop does
>>> not release the extra memory a file used when that file is closed. It
>>> hass to be quit and re-launched in order to release the memory.
>>>
>>> Maaki
>>>
>>>
>> --------------------------------------------------------------
>> --------------
>>> ------------
>>> Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe
>>> filmscanners' or 'unsubscribe filmscanners_digest' (as appropriate)
>>> in the message title or body
>>>
>>>
>>>
>> --------------------------------------------------------------
>> ----------------
>>> ----------
>>> Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe
>>> filmscanners' or 'unsubscribe filmscanners_digest' (as appropriate)
>>> in the message title or body
>>
>> --------------------------------------------------------------
>> --------------------------
>> Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe
>> filmscanners' or 'unsubscribe filmscanners_digest' (as appropriate)
>> in the message title or body
>>
>>
>> ---
>> Incoming mail is certified Virus Free.
>> Checked by AVG anti-virus system ().
>> Version: 6.0.500 / Virus Database: 298 - Release Date: 7/10/2003
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system ().
> Version: 6.0.500 / Virus Database: 298 - Release Date: 7/10/2003
>
> ------------------------------------------------------------------------------
> ----------
> Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe
> filmscanners'
> or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or
> body
----------------------------------------------------------------------------------------
Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe
filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or
body
