Douglas,
Finally, a previous version of PS is installed.<<
Er, that just doesn’t make sense. Do you have a previous version already on the machine that you are trying to upgrade? If so, you MUST install to a new folder, NOT the same folder the previous version was installed to.
I copy the DLL’s into the CS 2 folders<<
Copy from where? You cannot use the plugins from a previous version.
Your responses puzzle me.
" >>Finally, a previous version of PS is installed.<<
Er, that just doesn’t make sense. Do you have a previous version already on the machine that you are trying to upgrade? If so, you MUST install to a new folder, NOT the same folder the previous version was installed to. "
My statement is correct – there is a previous version of PS installed. I am installing into a new folder, as well.
" >>I copy the DLL’s into the CS 2 folders<<
Copy from where? You cannot use the plugins from a previous version."
I have copied the aforementioned DLL’s from PS CS into the PS CS 2 folder and they appear to function correctly because the alerts no longer appear. These are DLL’s, not plug-in and they were copied from PS CS to PS CS 2 so there’s a good chance that they are exactly the same code.
The problems remain.
Every time I’ve run an PS CS or PS CS2 installer, it has hung. When I launch PS CS 2, I receive errors about the "Core" module and the multi-processing module (can’t remember the names off the top of my head).
Anyone have any insight?
Thanks in advance.
clear out your temp folders then try again. setup is finding old temp setup files and trying to run them.
Dave:
Hmm…that would make sense. I didn’t think to check for that.
I’ll give that a try.
Thanks,
Doug
Douglas,
so there’s a good chance that they are exactly the same code.<<
No there isn’t!
fastcore.8bx Version 9.00 35,840 bytes
fastcore.8bx Version 8.00 24,576 bytes
Len,
You have repeatedly failed to understand my statements and seem to take some interest in demonstrating that they are "wrong".
While it would be child’s play to show the logical errors in what you have written, I won’t bother since I suspect that would only entice you to make further, silly comments.
In closing, if you have something constructive to add, please do. If, however, you are only capable of attempting to point out problems in what I write, try to understand that I can’t be bothered to respond.
Douglas von Roeder
doug, there was nothing wrong with that post. they are 2 different files. as he showed by posting the versions and date/time stamps. do not install OVER an old version. they’re meant to be kept seperate and the default is to install in a new folder.
and len’s a moderator. he doesn’t post when he doesn’t have something to add.
Dave:
I can’t agree with what you’ve said, amigo.
When I wrote
"there’s a good chance that they’re exactly the same code"
Len responded
"No there isn’t!"
Perhaps I should have written "there’s a chance" but I made the mistake of using the qualified "good".
So now we have an argument over whether there was a "chance" or a "good chance".
Contradicting my assertion did not help solve the issue.
What was helpful would have been to have mentioned that they are different file sizes and creation dates, understanding, of course that all the means is that they’re not exactly the same file. And then we can get into a contest about what "the same code" really means.
Is that the same executable code (we don’t know) or do we mean the same file (they’re definitely not).
My approach would have been different
"Heh Doug, I don’t think that they’re the same code since the file sizes and creation dates are different."
That’s a lot more pleasant stating arguing over my statment "there’s a good chance that they’re exactly the same code"
And of course, it doesn’t disprove my statement – it only shows that IN THIS CASE the file sizes and creation dates are different.
* **** Next item
" >>Finally, a previous version of PS is installed.<<
Er, that just doesn’t make sense"
Hmmm…look at that exchange
I make a statement and he responds "that just doesn’t make sense". He doens’t say "I don’t understand how that could be so" or "I’m not clear about how it’s set up".
It’s a bald statement that what I’m saying doesn’t make any sense.
* **** Next item
" >>I copy the DLL’s into the CS 2 folders<<
Copy from where? You cannot use the plugins from a previous version."
I write something about DLL’s and he answers saying that I "cannot use the plugins".
I won’t argue that point because it has NOTHING TO DO WITH WHAT I WAS TALKING ABOUT.
My statement was about ==> DLL’s <== which are very different from ===> plug-ins <===.
So, you might think that there was nothing wrong with Len’s postings but I looked at them and I really thought that I was dealing with a troll out to make trouble instead of someone who was taking the time to help solve a problem.
Heh, different strokes for different folks, n’est ce pas?
Douglas von Roeder
Now that we’re beat that to death…
Len, thank you for your service as a moderator. Tough job but I’m sure that there are some people who get out of line… 😉
One thing that you said did help me solve the problem and I want to give you credit where credit is due.
In Preferences, I had set the file path to the Plug-ins folder for the install of PS CS since I have some plug-ins from Fred Miranda. When I moved those plug-ins into the folder for PS CS 2 and reset the file path, PS CS 2 opens without any problems.
Pat on the back for you.
I’ve also deleted the folder for PS CS and PS 7 and now I’ve got to get copies of those two DLL’s that are different. 😉
Keeping my fingers crossed,
Douglas von Roeder
I don’t know dude. I’m glad you’re fixed, but it just seems to me you took what were correct yet terse postings and tried to make something sinister out of them. I suggest a bit of "lighten up" juice when you get out of work today. 🙂
I’m pleased to hear your troubles are solved, Douglas
