I don’t disagree with the argument about progress but we should all be careful of what we wish for. The system didn’t crash once and I certainly put it through its paces with InDesign and various other programmes working at the same time. I’m using 16GB memory on my iMac and the CS5.5 ran as smoothly as soft butter to bread. Had it been 1990, I wouldn’t be complaining and I wouldn’t have used the 7 year-old car analogy. CS5.5, which is what I have, was released in 2011 which is when I bought it. I don’t dispute your knowledge - you clearly know what you are talking about. It doesn't have to wait for you to quit a 32 bit app in order to access some of the RAM that app is holding onto.Ĭomputers move forward all the time. Having everything as 64 bit makes it much easier for the OS to allocate RAM dynamically to any app that's requesting it. Until you quit the app, nothing else can use that space. Doesn't matter how much is being taken up by an app that's running, but sitting idle. Likewise, a 32 bit app cannot use any RAM allocated as 64 bit. You cannot manage two types of memory addressing in the same block of RAM. Because the RAM allocated to CS5 is blocked out for 32 bit addressing, a 64 bit app cannot touch it. Let's say Photoshop CS5 grabs 4 GB of the 8 GB of RAM you have installed (I don't know in particular how much RAM your Mac has. Memory addressing in particular is a problem. I read somewhere that Windows 10 may likely be the last version you can get as 32 or 64 bit.įrom a technical standpoint, having a mixed system is a headache for engineers, and makes the entire system more prone to crashing. Windows is also, eventually, going all 64 bit. The entire concept of 32 bit software is being relegated to the dustbin of history, along with many, many other items from the relatively short time personal computers have existed. You did get your money's worth out of it the past 29 years, haven't you?Ī moderator can't do anything about how Apple is changing the OS. It's ancient software that Adobe stopped supporting a long time ago. I would be grateful if the Apple moderator could justify why it was impossible to make an allowance for 32-bit software to function within the Mojave OS and whether this is being looked into.Īpple didn't turn the lights out on anything. But here, we are supposed to just say, "ah well.". There is something very unethical about this If everybody's seven year old car suddenly stopped working and was rendered useless because a software update there would be a public outcry. I don't need the latest tweaks (which i probably wouldn't use anyway) and I wouldn't have updated to Mojave if I'd have been warned that any software pre-xxxx year would be rendered unusable. I realise that I can now go to adobe and shell out approx £50 per month for the latest Photoshop and Indesign but why is this deemed to be acceptable when the software that I had worked perfectly well for my needs prior to the Mojave update. Whilst I appreciate Kurt's comment that there isn't much to answer, and VikingOSX's post illustrating that CS5 is not supported, it is nevertheless extremely frustrating that Apple can just turn off the lights to what was a very expensive piece of software. Unfortunately the read-write solution didn't work for me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |