I have both versions of PS CC 32 and 64, running on windows 10 64 bit.... up to now everything has been fine with both versions. However yesterday my 32 bit software gives me a video card error message when loading and it has temporary disabled accelerated graphics, so ok i try to open a PSD file and it opens, however when i try to edit the file with the styles or other commands like crop etc, the software stops and gives me the generic message of PS has encountered a problem and needs to close, and it does close.
So i am open to suggestions of what to try here, i have no idea why the 32 ver wont work now, but the 64 will work... My system is a custom rig, built in 2014. i-74770 with 32 ram, again things have been great up till now.
Download Zip https://urlca.com/2yN2Ml
Here are my 2 versions... I also have reset the 32 bit with no luck, i have updated my driver software with no luck, i am not sure if reinstalling the 32 bit will help....not sure if my software is up to date even.
use Creative cloud desktop application see it it will be able to update CC 2017 x32 none of the updates seem to be installed. if not try using the offline the offline installer to install the 32bit version on top of the current CC 2017 x32 to insure you have a good installation. And then try to update the reinstalled CC 2017x32. Keep Adobe Photoshop up to date
so i installed this with the CC updater ....and once i loaded the software, i get the same driver error message, then i checked the version of the software and it is still the same version ( so it didnt really update it i guess)....and i tried to use PS and it crashed as normal ...
I am using pythons win32com module to automate Adobe Photoshop. This works fine on some machines (have had issues with it not working on users with limited windows account permissions, but thats another issue).
But on machines with both the 32bit and 64bit versions of Photoshop installed, I am getting errors when trying to access com objects, not the Photoshop.Application object itself, but Photoshop.PhotoshopSaveOptions, and Photoshop.SolidColor com objects.
Alright, so this is confusing me, I bought my wife's laptop from the dell site about 4 weeks ago, I put on options like the Radeon 4350 256 and 4gb of ram, but I was never given a option for 64bit windows Vista in the choices, yet in 32bit it shows 4gb of usable ram, but in Photoshop is shows only 2.75. This is ridiculous and borderline false advertising. On top of it, I called dell and they said I would need to pay 199 for 64bit Vista and I still wouldn't be allowed to get the windows 7 upgrade. What gives dell, I've been buying PC's from you for years, don't go all HP on me.
I would agree to that. Up to the point, that newbies might need a nudge in the right direction. Before they make really bad decisions. Finding out about third party software errors, can help with over all knowledge of how your OS plays with others.
Some programs and hardware like windows vista can 'see' how much ram you have in your computer, however they can not access anything above 3.5GB due to 32-bit limitations. I agree that Dell should not have sold you a 32 bit OS if you had more then 3 Gigs of RAM installed on the machine. Dell has issues knowing the fundamentals of how computers work so its really no surprise.
But that's false reporting, saying I have 4gb and not being able to use it is poor judgment on there part. I don't think I should have to pay for a new operating system when the one they shipped with the PC says I can use 4gb. And if it is a cover up, it's a poor one. I would like a Dell Representative to tell me why they decided to put a false reporting mechanic into an operating system version that can't do what they claim.
I know that, but why is windows (in everything, even task manager and programs that check for memory) shows 4gb (hence the screen shot) Most pcs on 32bit with 4gb show 3.25 or 2.75 but this one shows all 4gb yet I can't use all 4 that windows is reporting to have available.
As long as the bios is correct, I really don't think it should make a difference. Windows 7 64 bit would defiantly take care of that though. Updates in vista might be why you can see 4gb. The operating system, who's name can not be spoken of, made some significant changes in sp2 to the fundamental os. This is probably why you can see 4, I am sure that many people have complained to OEMs about this, and it has cost lots of time to explain these issues. So updating the os to give the end user the ability to see this i probably a good thing.
i don't understand why people having problems with 3rd party software come here complaining in the Dell forums. this should be in the Adobe Photoshop support forums or in one of the microsoft help forums, but i'd go with adobe if it was me :emotion-5:
Again this is the limitation of the operating system period there is no false advertising or anything. a 32 bit os can only physically address 4 gigs and the lower number is the result of reserving system memory.
A change was made in Vista I cannot remember which sp it was but that change was to report the TOTAL SYSTEM RAM INSTALLED, just like the bios. How much you have actually free is dependent upon you particular system configuration .
Nobody seems to be understanding the point, THE OPERATING SYSTEM, THE OS. WINDOWS IT'S SELF IS REPORTING ALL 4GB (not like my other 32bit system that reports 3.25gb in the system properties) I don't understand community sites that have condescending answers like "This might help if you want to do some work" I know about the "Architectural Decision" but this isn't about Windows showing less ram than I have, it's about it reporting all the memory is avalible but programs not being able to access it all. I did a test, pulled out 1 stick and it System Properties reports 2gb, put it back in and it reports 4gb. either way photoshop only sees 2gb. While on MY 64bit system, Photoshop see's all 4gb.
I'm not complaining about an Adobe issue, I'm using it as an example. Community forums are no replacement for paid assistance, that I can see. In retrospect, I can see why nobody understands the issue. They are all goggling or searching the issue, but it's not something that I saw in my 4 hours of researching my self, thus why I decided to post in this "Help" forum. Anybody can link to someone else content and call it help, it takes paid assistance to give answers I suppose.
My question is, how is it that my VOSTRO 1500, when I put 4gb in it, shows in system properties as 3.25gb (and then says something about 32bit windows) and my Inspiron 1545 shows 4gb, nothing about an issue with 32bit windows and memory, and programs all see MUCH LESS memory than what windows reports as True amount of RAM.
Calm down, he's right. When I go to HP's site and make a pc, anything at 4gb and above get's 64bit windows. This was an oversight on dells part. How would you like to be sold a new tv that says it does 1080p and you get home to find out it only does 720p due to a firmware limitation, sure, the panel is 1080p, but due to the firmware, it only allows 720p. Why advertise and sell more than you can use?
having a problem with, is really not a problem. It is the software coding of a 32bit system. By definition, a 32-bit processor uses 32 bits to refer to the location of each byte of memory. 2^32 = 4.2 billion, which means a memory address that's 32 bits long can only refer to 4.2 billion unique locations (i.e. 4 GB). SORRY
I'm trying out a 32bit back-to-beauty compositing workflow and photoshop is saying my EXRs are in the RGB Built-in colourspace. Is this just a way of saying it's effectively no colour profile/ linear image?
Also the photo I'm using (in the 8bit file) seems to have the ProPhoto profile assigned, presumably because it was taken in RAW. I know this probably means that I should be working in Adobe RGB, but I don't have a wide Gamut monitor, nor does anyone else at my company.
Does any of this even matter if I've got an sRGB working space assigned in colour policies? Am I right in thinking that photoshop is translating the native profiles of the source imagery to the working space? As it happens the image looks identical in the 32bit and 8bit files.
If you want to be ultimately in 8bit you can either place it as a smart object or just double click on the layer to make sure its unlocked, select Image > Mode > 8 Bit > Don't Merge. This will keep the colors as they are in the EXR.
The photo you are using if its using pro photo was probably exported with this color profile from Lightroom or such. It doesnt matter if you are converting this to sRGB as its a lower colorspace, as long as it looks as expected.
As a side note, if you are rendering to EXR I would advise using a 16bit sRGB color space for post production, you will have more depth for your 3D elements and if you really need extra blacks/whites (zdepth for example) then keep this as a 32bit smart object.
Will back-to-beauty compositing work correctly with 16bit? My research seemed to suggest it would be slightly off, and photoshop opens them as 32bit anyway, although I suppose the EXRs themselves will be slightly smaller on disc.
you have very limited options working in 32bit mode in photoshop, nuke would be a better option if you want it 1:1. However I still prefer photoshop for its simplicity/layer workflow. That being said, working in a 16bit photoshop file will give you most of the flexibility you need (again you can just keep what you need in 32bit mode such as zdepth layers and light selects and have them as a smart object within the 16bit working file so you can readjust the blacks/whites when you need separately).
b1e95dc632