Adobe only lists Intel and Pent processors under the specs and requirements for PSCS2. Are there any problems with the new AMD processors?? I have 1 gig of ram AND an Athlon 64 3400+ processor. I am planning to upgrade from PSE3 to PSCS2 and would like to know of any problems before purchasing and installing.
I have an AMD 3200+ w/1 gig ram CS2 runs just fine!
JJS
wrote:
Adobe only lists Intel and Pent processors under the specs and requirements for PSCS2. Are there any problems with the new AMD processors?? I have 1 gig of ram AND an Athlon 64 3400+ processor. I am planning to upgrade from PSE3 to PSCS2 and would like to know of any problems before purchasing and installing.
Be ware that CS2 requires activating on both OSs and that takes care of two computers allowance.
Andrew, are you sure that is the case? If so, things have changed. With CS, I installed on two different partitions on one machine as well as my laptop without any problem. I haven’t tried this with CS2 as yet.
Indeed, so long as a multi-boot configuration is set up on a single hard drive, then you can install CS2 to each O/S and use it without any problems associated with activation. If, before you install CS2 to the 2nd O/S, you first copy the Product License folder info to the corresponding location for the 2nd O/S, then you shouldn’t see any prompts at all for activation. This is completely as it should be, since no hardware changes are involved. If however you install CS2 to a 2nd O/S on a separate hard drive, a 2nd activation will be required and will count against the 2 permitted activations; this should NOT be the case so long as the hard drive are in the same system, but that’s where there is a flaw in the CS2 license manager design.
Mick, I missed that you said your experience was with CS vs. CS2…the latter’s license manager does behave differently but, for the most part overall, it is also better than how CS works. I’m rather surprised you were able to get CS2 to work in a multi-boot environment, but that may depend upon what sort of boot manager you use and how it works. Normally, the way CS updates its activation hashes with each launch/close of Photoshop, that alone would wreak havoc each time you switch between operating systems. I don’t doubt you got it working, but again, I think the boot manager used would be a key factor.
That is interesting Daryl. I currently have CS2 installed only on my H partition which is on the secondary hard drive. I’m not going to bother experimenting as I don’t want to run into trouble when I change machines down the line, even though it sounds like deactivation works ok. Incidentally I did a Ghost partition restore very recently and CS2 did not require reactivation although I had used it after I had created the backup.
As far as CS is concerned I have actually installed it on 3 (not 2) separate partitions on this computer: C, D (boot drive) and H (secondary) without any problems as well as on my laptop. I have since erased the D OS so did not bother to mention it above. With CS at least, the activation hash is written to the boot drive.
How did you manage not to forfeit your 32 bit XP license when upgrading to the 64 bit version?
I signed up for evaluation copy of XP 64-bit (RC2) with Microsoft, good to run for a year no need to forfeit XP license. That was couple of months ago (before final release) their current trial offer is 120 days. Im not interested in trading XP for XP-64 when I decide to install final build of this OS Ill just buy it.
I have 64-bit drivers for all my system components (video, HD controllers etc.) but peripherals support is another story. I think dual boot might be necessary for a while.
No, Im not sure. It was simply my understanding that with CS2 you get two activations period. Dual boot or two computers doesnt matter. Adobe doesnt support dual boot configuration so I think Id have to deactivate one before I could install CS2 on another computer but I didnt try to test that theory.
While my exploring various system configurations with PS CS2 didn’t involve any where I installed it to a hard drive separate from the system drive, so I’ll not speculate on how that might affect things. I’m not sure if the activation hash in that case would be written to the boot sector of the hard drive where PS CS2 resides or if to the system hard drive. With regard to ghosting the image, I too had no problems unless using the image to create a drive clone. In that case, while using the clone in the same system and with the clone being a complete image rebuild inclusive of the boot sector, that cloned drive still required an activation. Although treated as a repair activation, the repair was denied as a 3rd attempted activation although this was still only the 2nd system. That is, one PC used the 1st activation while the 2nd (with swappable drives) used the 2nd activation, yet that activation could not be cloned across the drives although it should’ve been permissible since the same system was being used. Again, this is the case of the license manager not behaving correctly as a true system license which is what it should be.
