I am having all sorts of trouble with my setup - 32bit windows 7 and 32bit CS6. I have a 2TB hard disk (with 1.7 unused) and 8GB Ram installed.
I understand that this setup has a maximum amount of 1.7GB ram available to CS6 and this may possibly be the problem. (see the attachment)
My D800 NEF images are around 40MB each. I get out of ram messages in Photoshop and the same in Bridge. In Bridge the 100% lupe takes forever to activate and eventually after several images it says the 100% lupe is unavailable. If I purge the cache it is OK again for just a few images.
There appears to be no problem with smaller files, jpegs etc.
What I would like to know is anyone out there using a similar setup and having similar or no problems with the large files?
I will change the setup to 64bit CS6 on Win7 64bit if this is the only way to rectify the problem.
While a 64 bit system is preferable, Photoshop CS6 ought to be able to work in a 32 bit system since that's an acceptable system per the system requirements.
Do you have the latest Photoshop and Bridge updates? I know that Bridge had some performance enhancements done to it just recently.
Both bang up to date! So what the devil is going on - I've even partitioned the hard drive and assigned the new partition to be used as the Scratch setup - made no difference at all - shortage of RAM appears to be the problem.
I guess I could uninstall CS6 and reinstall it and hope (and pray) that might do the trick. I have tried setting the preferences back to defaults, made no difference.
It's a bad idea to partition a single drive just to have Photoshop scratch point to another volume. You should undo that. If you don't have a physically separate hard drive, then just using the boot volume is preferable, as it makes the entirety of your free space available for temporary use.
I can't suggest any workarounds for your out of RAM issue as I'm running a 64 bit system myself. Do you see this problem when Photoshop is not running, or just when both Photoshop and Bridge are running? If the latter, try reducing the RAM setting in Photoshop, so it will leave more space for other things.
I had been told somewhere that that was a good thing to do - I have now removed the partitioned volume - before I tried the partition I tried a new and empty external HD (WD My Book 2TB) for the cache - it made no difference - but should that have been a better approach?
The problem is the same whether Photoshop is running or not.
I am with Noel 100% on NOT partitioning HDD's. Other than for dual-boot setups, and a very few backup schemes, partitions slow things down, and often greatly. See this article: http://forums.adobe.com/message/3774098#3774098
For problems with resources, you might take a look at your Windows Virtual Memory (Page File) settings. See this article: http://forums.adobe.com/thread/632449?tstart=30
PS - both of those articles were written with Adobe Premiere (video editing) in mind, but PS benefits from most of the same solutions.
Bill - glad to have the advise re the partition so strongly backed up (not that I had any doubts about Noel's info of course) and thanks for the info - bit late now so I look forward to checking the two articles tomorrow.
I have read your info and thought my next approach was to look at the Page File. Attached is how my PF looks at present and can I ask you to advise on its appearance and whether it could be changed? I can say that the I Drive is a new 2TB external hard drive (WD My Book). Also shown is my system info.
Sorry my last post looks a tad messy - clearly didn't get the attachments in the correct place - but I would be pleased if you can see anything that might be altered to improve the 'No RAM' situation.
Sometimes, the forum Reply editing screen can develop a mind of its own, and things get cattywompus. Happens to all of us.
With a 32-bit OS, you will only be using ~ 4GB of RAM, out of your 8GB installed.
I would look at statically managing your Page File (Windows Virtual Memory). The dynamic management (allowing Windows to increase/decrease the size of the Page File, as is needed, or anticipated) is good for general computing, where Page File usage is rather limited, and where calls for it come in rather slowly. With some programs, Photoshop and Premier for two), much RAM is used, and in a hurry. Then, the program signals the OS that it needs more, and the OS goes about creating that, then allocating that. It takes CPU cycles to do the dynamic management, and as the pipline to create (or decrease) that Page File size is rather slow (and you have the slower HDD Page File, which is slower still), the program's request can time out, or at least slow things down. The program might go into Not Responding, while it waits. Dynamic Page File management is useful, where one has limited HDD real estate, but on an editing rig, that should not be an issue, as one would have plenty of HDD space.
When I install my OS, before the programs (outside of the OS) are installed, and while my disks are clean, I will test where to locate my Page File, and have it statically managed. On my workstation with 5x internal HDD's, I found that the best location(s) were my C:\, and my D:\. On my laptop, it was slightly faster to locate the Page File on E:\. That was my setup. As my internal HDD's were empty (other than the OS on C:\), when I located my Page File on other than C:\, and as it was statically managed (created to my chosen size at bootup, before anything else is written to the HDD), the Page File was located at the inside of the platters, where access is slightly faster, than out at the edges of the platters (where it could be, if there were many files already written). This location is alwasy used, and fragementation is limited. Just some little benefits to that process.
With a 32-bit OS, and with programs that can use large Page Files, I like to go with ~ 2.5x the installed RAM for the Page File size. In my case, with 4GB RAM (max readily usable by the OS and the programs), I chose 10GB for the size of my Page File. With your 8GB RAM, and unless you have special management software, that can use addresses beyond the 4GB level, I would choose ~ 10GB RAM too. If your C:\ is fast, and not overly full (it will be partialy full now, with your programs installed), that would be a good place to locate it. If, for instance, your D:\ is also fast, and mostly empty, that should work well too. Same for your E:\. Do NOT locate it on an external.
Now, here is another consideration: your Photoshop Scratch Disks are like the Page File, but is only used by PS, when RAM is exceeded for operations. The Page File will only be used by the OS and then allocated to the programs, directly. While it is "virtual memory," used differently, than Scratch Disks. The idea behind having more than one internal HDD, is to spread the I/O load, so that the computer is not waiting for reads and writes to complete, before it gets the next batch of reads and writes. You might want to allocate your PS Scratch Disks on drives, separate from the Scratch Disks, which will be used by PS. With that in mind, you might be best to locate your Page File on D:\, and then your PS Scratch Disks on E:\ and F:\ (assuming that those are equally fast internal HDD's. This will help spread the I/O load over three physical HDD's. Note the word "physical" there. That assumes that your Volumes ARE separate physical HDD's, and not logical partitions of physical HDD's. Partition are to be avoided with Image, or Video editing programs.
After one has made a change to their Page File, a reboot will be necessary to implement the change. Test.
With Page Files, there are seldom hard and fast rules. Much will depend on what programs one has, and has in use at the same time. With the Page File on the boot drive, things are not bad, as the OS uses that HDD for getting itself up and running, then just a bit, afterwards. It then calls on a program to launch, so some reads and writes take place. When that is done, the boot drive is not used that much, so requests for reads and writes for the Page File, are seldom interrupted by other things. Keeping the Page File on a separate HDD, than the PS Scratch Disks, which WILL receive a lot of read and write requests, is a good thing.
Lot to think about initially, but after one gets the general concepts down, it's not that difficult to implement.
One more thing to consider is that defragmentation on an HDD can slow things down. Defragmenting on a regular basis is good. Some defragmentation programs WILL move system files, like the Page File, to the beginning of the HDD's platters, ahead of regular files. That might be something to consider, when picking a defragmentation program, especially if you have already partially filled it with other files.
Noel - I shall probably move on to 64-Bit in the next couple of days - but other users working in 32-Bit don't appear to be getting the problem so there must be something fundamentally wrong with my system.
Incidentally I installed CS5 today and all is working pretty good there - that possibly means something - I'll see what can be done when I have absorbed Bill's post above.
Bill - I have read and absorbed your info and have made the change to the Page File - sadly it has made no difference, after looking at two or three images (40GB each approx) I still get the message you will see on the attachment - attached is also a copy of the updated Page File and perhaps you can advise me if I have done it correctly.
I've done nothing about the scratch disk situation and this is posibly part of the problem - I only have one internal HDD (although I have partitioned it and it is called volume I) and I do have a couple of external HDD's, one of which is new and empty.
Once again this post is untidy!
Partitions are a hold over from OS's, that could not see large (for the day) HDD's. They tend to slow down many things. See this article: http://forums.adobe.com/message/3773586#3773586.
While written with Video editing in mind, it applies to Image editing with a program like PS.
Now, what are the sizes of those logical drives, and how much free space does each one have?
Next, how have you allocated those logical drives, relative to both Photoshop and Bridge (which builds "catalogs" when you run it)?
Last, after you made the change to the Page File, did you reboot the system?
It's good that you've followed-up and checked everything, but it's really high time to move to 64 bits. You're apparently trying to do too much on too large / too many files with a 32 bit system.
Is there something you're unsure about with regard to moving up to 64 bits? Keep in mind Windows 7 x64 runs all 32 bit software just fine.
Although i agree 100% with Noel that now is the time to move to 64 bits (before you get forced into windows 8), i'm running cs6 on a windows xp 32 bit machine and don't seem to have the problems your describing.
Putting aside the bridge problem, i be interested to know it in what scenario you see out of ram messages in photoshop cs6.
Are you running other programs at the same time?
I should say that i also run cs6 on a windows 8 64 bit system.
(windows 8 works fine, just not my first choice in os's)
I'm installing Win7 64-Bit tomorrow - so I will come back when that is working.
To answer your questions:
C: has 1.28TB free space
I: (the partition) has500GB free space
Please advise me how they should be allocated
Yes, I did reboot after I made the changes to the Page File
This is what worries me - it''s working OK for you (albeit on XP) - and I imagine it worked 'out of the box' without any messing about with extra drives and cache re-arranging - I strongly feel that there is something fundamentally wrong with my setup.
Incidentally I thought I'd check out CS6 on my old Dell XP setup - so I installed it and all seemed to go accordingly well but when I attempted to open CS6 I got the following dialog and could go no further - have you any idea what it means?
message reads: The procedure entry point GetLogicalProcessorInformation could not be located in the dynamic library KERNEL32.dll
Are you running xp with the sp3 service pack?
Thanks for the info - I have now installed SP3 and, of course, CS6 now opens up on the XP machine!
At this stage I have not yet checked how SC6 on XP is going to cope with the problem of 'low memory' I have been getting with my other pc, which I have now upgraded to Win7 64-bit and 64-Bit CS6 - haven't check that yet either - still busy re-installing software and printers etc.
I will get back to the forum when I have made the checks.
I would like to discuss the problem with anyone out there who is using the Nikon D800 with it's 40MB raw files?
I think I can bring this post to an end now.
I have installed Win7 64-bit and CS6 64-bit and all is working very nicely and as I would expect it to - so, although I'm a happy bunny now, there was clearly something amiss with my 32-bit setup that was never resolved, although I learnt an awful lot on the way!
My grateful thanks to all who took the time to respond and to help me get up and running again.
I've no doubt I shall be back!