I’m running Photoshop CS on a Fujitsu CELSIUS 670 Workstation, with double Xeon 2Ghz, 2Gb RAM RIMM ECC, SCSI Ultra160 Hard Disks and a nVidia Quadro 4 Graphic Card with 128Mb. Well, I never had a minimum problem with any kind of software in this machine, I worked with Photoshop 7 in this machine for more than one year and never had a small problem. After I upgrade Photoshop 7 to CS I start having "crashes" all the time, usually every time I use the Magic Wand Tool, the program "crashes" and close, I’m losing work more than 4 times a day. At this moment, when I need to select something in a image I need to use other machine where I have the great Photoshop 7.01. I don’t know what to do, I already contact adobe support lots of times but they never gave me feedback, I’m thinking in give up about this program, but, after all is a big waste of money buying it not to use.
Learn how to optimize Photoshop for maximum speed, troubleshoot common issues, and keep your projects organized so that you can work faster than ever before!
Have you tried , as a diagnostic, turning your hardware video acceleration down to zero? If that helps it indicates a video driver problem – check the vid-card manufacturer’s site for updated drivers.
Otherwise, suggest you do a complete uninstall from C/Panel Add/Remove programs, delete the whole of the Photoshop CS folder tree and the \Documents and Settings\~username\Application Data\Adobe\Photoshop\8.0 folder tree and then re-install.
Removing the MultiProcessor support plugin(Photoshop\plug-ins\Extensions} will prevent this crash. It will also prevent Photoshop from taking advantage of your dual processors, but at this point is the best workaround we can offer to this problem.
It is better for the application to run slowly than not at all. Jim wrote in message
Paulo,
Removing the MultiProcessor support plugin(Photoshop\plug-ins\Extensions}
will prevent this crash. It will also prevent Photoshop from taking advantage of your dual processors, but at this point is the best workaround we can offer to this problem.
I dont’t think that it is a good idea to Remove the MultiProcessor support plugin. I work with huge images, I take advantage of my full system, that’s a bigger waste of money. I think I’ll try to sell Photoshop CS and keep Photoshop 7.0 and in future I’ll try a demo of Photoshop before I buy it. Thanks anyway for all your help 😉
Paulo – keep CS, but remove that plugin and it’ll solve the crash. I’m trying to find the cause and a fix, but until then just disable the MP Support plugin.
OK! I’ll do that, but do you think that it’s possible to have a solution soon? Just another question, is it normal that CS is extremly more slow than 7.0 running in the same machine? it’s almost 4 to 5 times slower than 7.0 working the same projects.
I think I’ll try to sell Photoshop CS and keep Photoshop 7.0 The EULA changed with PSCS. If you upgraded from version 7 to PSCS, you have given up your license for 7.0. If you choose to sell PSCS, you cannot legally use version 7.0, as you must give it with your sale of CS. Your choice now is to disable the plugin and wait for a patch.
Regarding your slow down, please do a search and you will see there are others dealing with the same issue. Some have found a solution that has worked for them (RAMidle – search for that), while others are patiently waiting for answers.
The wording on the EULA changed a little but does say you can continue to use the older version during a transition period. There’s no set time limit for that period and if you’re having issues with CS, then the transition period would be even longer.
Most slowdowns have been tracked down to using the filebrowser in the background, or conflicts with third party applications or drivers. A few others have been tracked to bad disk issues (especially on the scratch disk) on NT2K. Launch time slowdowns have been tracked to bad fonts, or third party plugins that install thousands of non-plugin files into the plugins folder.
Grasshopper – RAMIdle is not a solution. It can’t affect Photoshop (except badly).
Bob, yes, understood. I was referring to him selling his version of PSCS, not simply leaving v7 on his system. 🙂
Chris, only relating what I have read here. I certainly wasn’t taking a stand as to whether or not it was best for PS, but that some folks have felt it worked for their systems.
I’m still with CS installed. As I said, I work with huge images and and I’m taking advantage of my full hardware system, I’m keeping both processors. In the box of Photoshop CS at "system requirements" I can read "4 processor" and "Windows XP" that’s why I expected to work in my system without problems. I’ll wait for a patch but in case it take too long I’ll change for 7.0 for sure.
I am a bit off topic, but here goes…. I have been using PageMaker 6.5 forever now, and the only think I here and read (from the experts!) is that this software is full of bugs. I have never experienced any of them… love the program and would never give it up. As far as PSCS goes, it is full of little annoyances and is so much slower than 7.0 (I can argue forever about this). I have stopped complaining because nobody seems to care (is ADOBE listening). When ADOBE comes out with a patch for PSCS, one of the many improvements will be….
Photoshop now offers better compatibility (and increased speed) with Intel® Pentium® 4 hardware."
On the previous thread about the magic wand crashing systems, it was also noted that most having this problem also had hyper threading. I have two dual system, and only the one with hyper threading has the crashing. However, CS is slower than 7 on both machines.
Disabling hyper threading or removing the afore mentioned plugin solved the crashing, but not the speed issue.
OH! Great… so it’s not only me! This CS as a real speed problem. I can tell you that when I first installed the upgrade of Photoshop from 7 to CS, I work for a few minutes and decided to reinstall the full system. After the install of Win XP I just installed CS and without anything more running I test it with an "in progress work" that I begun in 7, so as I told before it was 4 to 5 times slower. Even without the crashes it’s very bored to work with Photoshop now, I really miss 7.0 performance and stability. I hope that a soon update fixes the bugs and the speed problem.
*Most* of the speed problems we’ve heard about are because of mis-tuned systems. Search the forum. You have to watch your system and re-tune Photoshop’s scratch and memory preferences.
Very, very few of the speed problems aren’t related to this and we’re trying to track it down.
As for crashing, these hyperthreading related issues in just two tools are all that we’ve seen that wasn’t caused by bad hardware.
With all due respect Scott, most Photoshop users (the ones who make a living with this program)have top notch systems, fine tuned to the max (at least I know I have). Let’s face it, PSCS is slower than ver. 7.0.1. When so many (loyal)customers complain about this, maybe, just maybe, it might be real?
most Photoshop users (the ones who make a living with this program)have top notch systems, fine tuned to the max (at least I know I have).
That’s quite an assumption. I’m willing to bet just the opposite is true.
When so many (loyal)customers complain about this, maybe, just maybe, it might be real?
How many would that be? I’ve had a problem with previews but beside that no noticable difference in speed. You can’t come to a forum like this and conclude that everyone is having problems because the reason most people visit forums like this is because of problems.
Tony, there was a thread along those lines a while back, and many people responded saying that they weren’t seeing slowdowns.
Myself, I’m seeing some performance issues. I think this is a combination of a new release that hasn’t gotten a dot release update yet, and probably something about my machines that we haven’t figured out yet.
I feel certain that if Adobe can reproduce the problem, they’ll fix it. Until then, I think our best bet is to keep reading and posting here and trying to help them figure this stuff out.
Tony – no, most of them (even the ones making a living on it) haven’t got the faintest idea how to tune their system. Witness how many are running Norton programs….
OK, then try and figure out what exactly makes PS 8 run differently on the same machine than PS 7 does. (I know you’re trying, I’m just trying to clarify.) I didn’t change anything, you guys did. Hey, man, I’m your buddy, from a long time back. Well, maybe not your childhood, but at least PS 4. <g>
Thanks, Bob. I thought I may have been inadvertently running something that may have been contributing to my problems. I don’t run any of the other stuff.
Myself, I’ve run Norton Anti-virus in the past. None of the other stuff. But I went through a very detailed removal process with NAV, including not only removing NAV with Add/Remove Programs, but also going into the registry (damn, I hate that) and removing all Norton keys, etc.
– 3x Seagate Cheetah 37GB 10K U160 SCSI (using one disk exclusive for CS scratch other for the system and the last one only to save work)
– Microsoft Windows XP Pro SP1a (very well tuned for all the other apps and Photoshop 7.01)
Scratch Disks are well configured in CS, Memory Usage is configured to 90% and Cache Levels reduce to 4 in CS. Hyper-Threading is now disabled on BIOS as suggested. All drivers are up to date, there’s no "Norton Something" anywhere here, no games, there’s no virus, I only connect this work computer to internet just to activate software registrations, no plugins installed. More than 15 years of experience with MS-DOS and Windows Systems, and I know people tuning their Windows with less than 2 years of experience very well, so, 15 years should be pretty enough to learn how to work with Windows XP. I’m using this system exclusive with Photoshop since I bought it.
I have to say: Photoshop CS is much more slower than Photoshop 7.01 comparing in the same system.
I saw that all the scratch size of the images are higher now than in 7.01. I also think that reducing mem to 70% will make me use higher amount of virtual memory. I just set it to 90% because when I’m working with Photoshop I only have opened ThumbsPlus as I always did. I never used the file browser integrated because I really don’t like the way it works. Anyone knows a way to complete remove CS file browser? That thing should be a separated program, it could be very usefull tool as a stand alone program.
Chris – I’ll test mem reduced to 70% later today and I’ll tell you something, Thanks.
What’s supposed to happen when you click on his name on the spash screen?
lets you know he’s an adobe engineer. or looking at the splash screen and seeing him listed on the front page. sheesh! newsreader-ites! 🙂 see what your missing?
It just seems that Adobe is saying that the slow down is because of issues on my end? Yet PS7 worked great. Then upgraded to CS and now it is slow. I even did a reinstall and only had teh CS suite and it was stills slow. I installed all my applications and it didn’t effect the CS performance. The only change was upgrading to CS.
Yet my older machine at work that does not have hyper threading is faster with CS, but slower with everything else. Yet with PS7, my newer machine smoked my older machine in everything. CS is the only variable.
If you’ve read any of the threads on this issue you’d know that they suspect something is funky somewhere but they’re having a hard time pinning it down. They need to eliminate problems that are local to specific installations in order to focus on things that might be real issues. So don’t get upset if you get tons of questions and suggestions thrown at you. It’s not personal, it’s debugging. It’s process of elimination trying to figure out IF it’s something specific on your system or if it’s one of the cases that seems to be a genuine bug.
IIRC they suspect something with dual processors (only xeons?) when accessing a couple of specific tools, and maybe also something with 2 gig of ram under win2k.
Ranting doesn’t help, giving data on your system and what exactly is happening and when, does. Not that you’re ranting, but many are.
Please just read the threads – there are several about improving performance under cs – try the techniques already sussed out to boost performance, provide what info/feedback you can and respond to questions and these talented guys and gals will work it out.
I’ve been working all day with the Hyper-Threading disabled as suggested by Malameel (thanks) and I didn’t had yet a single crash with the Magic Wand Tool. I also have now the memory percentage reduced to 70% as suggested by Chris but I can’t notice yet any advantage, I’ll tell you something more later. Thanks to all who have been supporting.
I just hope Adobe doesn’t wait 6 months like MS did to come out with a patch…I am not really complaining…. simply I am very anxious for the patch/fix/improvement…you can call it anything you wish, as long as you come out with it!!! Anyways, speaking of tweaking software, I personally use Tune Up Utilities I love it so much You can find it here <http://www.tune-up.com> (Please do not say that this is causing my PSCS slowdowns)
What’s supposed to happen when you click on his name on the spash screen?
lets you know he’s an adobe engineer. or looking at the splash screen and seeing him listed on the front page.
Oh no, I think you miss my point. I *see* his name just fine (and of course I’ve long known who he is), but *clicking* on his name as suggested does nothing (or just closes the splash screen of you’ve used the About Photoshop command).
If Adobe is having a difficult time reproducing the problems on their machines, perhaps they should/could go out and buy the same machine/configuration that is showing the problems and try that. It seems like there might be a few to choose from.
It’s just very curious that Windows/XP/P4’s or Xeon’s seem to work ok with all of the other window’s apps out there (including PS 7). So, I guess that I am to understand that most of these problems are due to user misconfiguration?
Perhaps Adobe can disclose what they are using for systems and their configurations. That way, if needed, users could purchase the same system and at least have a better chance of getting reasonable/similiar performance.
Maybe (I am only being partly facetious here..), Adobe needs to offer a CS configuration training class where users can bring their systems in to class to tune up and they can show us mere mortals the "errors in our ways"….. And everything will work perfectly when we graduate from the class..
Give me a break, and give your customers at least some credit. I know that you run into all kinds of customers, but you need to recognize that while Adobe may be the world’s foremost expert on PS (and your other products), you are probably not the world’s foremost experts on anything else. A little humility goes a long way. Adobe, as a company, doesn’t seem to have much lately. Has Adobe even tried to reproduce some of the problems on machines that are what the customers use? Or are you just saying "well we don’t see that here, so it must be your problem.."?
All’s it would take for me is to have Adobe announce something like the following:
"We have seen some problems X that seem to be related to some machine types Y and we are looking at it. We don’t have workarounds, we will let you know when we do or if a patch will be required" "If you would like to submit your machine configuration and problem, we will add it to the list" And then at least Adobe can start looking for common things amongst them.
This has been done with the Dual processor issue & the plugin workaround, it just needs to be done more often.
Instead of constantly brow-beating every user that posts a problem with the standard "it’s a configuration issue on your side".
Of course, I still have a huge problem with CDS and activation, but that’s another (many) thread(s)….
mutator – we have most of the systems. But the problems don’t happen. That usually means it is some other software, or some non-standard configuration that the user changed that is causing part (or all) of the problems.
We have several hundred systems here, and they change configuration as needed for testing – there is no @#%@# way we’re going to try publishing a list like that.
Yes, we constantly try to reproduce the problems on exactly the same systems that customers use.
But the problems don’t happen. That usually means it is some other software, or some non-standard configuration that the user changed that is causing part (or all) of the problems.
Ummm… since one of the suggestions Adobe has made to some users is to "disable Hyperthreading in the BIOS," I’d say at least sometimes that it is Photoshop CS that requires a "custom configuration" to work properly.
Beyond that Chris, I might note that as helpful as Adobe tech support has tried to be in my case (a dual PIIIe 1gHz system), ImageReady CS still doesn’t even load fully.. It just dies! Their BRILLIANT answer after sending me tech documents on application crashes prepared specifically for PS 7.0? "Reformat your hard drive and do a clean install of PS CS and ImageReady CS. If you aren’t willing to do that, we can’t help you."
Funny thing is ImageReady CS worked fine in the Trial Version, but the Retail upgrade version has never worked since I loaded the software. Maybe I should have foregone the upgrade and simply hacked the trial version, at least the software would probably still work properly then!
Want the case number Chris, Ian, Scott, etc.? Try #5883801. I don’t care how helpful the Tech Support people try to be, if the application doesn’t work I deserve a partial refund for the missing ImageReady functionality.
To paraphrase a metaphor, talk about "the vendor always being right."
BTW: We all know that broader end-user/consumer BETA testing WOULD expose the software to more REAL WORLD prouction systems, and you’d see more of these problems then – when ISV’s are supposed to isolate and address them. You’d think that Adobe would ensure the broadest possible BETA testing of its arguably flagship product.. These kinds of issues showing up in PS CS and mine in ImageReady CS, don’t lead one to believe that sufficient time and effort is being spent on bullet-proofing during BETA. When I worked full-time in the IT biz, as a system analyst, EDP auditor, and computer security admin, I would have highlighted these problems and refused project completion payments until they were fixed.
povimage – that has NEVER been an official suggestion. We do have some outsourced tech support that isn’t quite up to speed — but the only time we’ve suggested disabling HT was when trying to diagnose a bug.
If the trial version worked and the retail doesn’t – I have to agree with support: most likely it’s a corrupt install. First try reinstalling Photoshop, then the next step is to clean out the OS and reinstall everything.
How do you deserve a refund for having a corrupt file on YOUR disk?
BETA – Bullshit. But that statement does tell us that you’ve never worked on commercial software before. (and caling yourself a system analyst puts you back in the dark ages of computing)
If the trial version worked and the retail doesn’t – I have to agree with support: most likely it’s a corrupt install. First try reinstalling Photoshop, then the next step is to clean out the OS and reinstall everything.
Gone through all those steps except redoing the OS, I’m not doing that for ONE application.
How do you deserve a refund for having a corrupt file on YOUR disk?
Ummm.. who wrote the installer? Me or Adobe? I followed the installation instructions.
you also said:
We do have some outsourced tech support that isn’t quite up to speed
I know this is tangential, but outsourced in the US or overseas..? I do note that apparently more Acrobat coding is moving to India..
Yup, guess my IT work was in the "Dark Ages" of computing, before the enlightened practices of using version X.0 as a large scale BETA. You guys seem to be learning a lot of things from M$ these days: feature bloat, version releases as BETA, overseas outsourcing, shipping American jobs overseas to reduce costs,… etc. Very nice, I congratulate you all for making Mr Warnock very proud there in San Jose.
Who wrote the installer doesn’t mean anything. You could have a bad disk, a bad controller, bad RAM, a virus, spyware, or a corrupt OS file. We don’t know. We just know that it works for us and just about everyone else. That only leaves a problem specific to YOUR system.
And I don’t know what product you’re looking at. We don’t do feature bloat, and we don’t ship a version until we’re sure it’s solid, and we do a VERY extensive beta test.
Along a more constructive line NAV has been known to cause problems with installers. Some of the older ATI drivers actually had to be loaded after NAV was not only disabled but after the NAV associated services were actually stopped.
However, given the ubiquity of NAV in the marketplace writing or more importantly releasing an installer or application that knowingly has issues when NAV is installed on the same system is brain dead IMHO.
You could have a bad disk, a bad controller, bad RAM, a virus, spyware,
None of the above except the Adobe LM Service Manager spyware (obviously a corrupt system file is a hazard on ANY system). Since you mentioned it, isn’t it the Adobe EULA for PS CS that specifically authorizes spyware behavior by Adobe?
to quote from the EULA:
"14.8 Online Services. 14.8.1 The Software may rely upon or facilitate your access to websites maintained by Adobe or its affiliates or third parties offering goods, information, software and services ("Online Services"). "
I knew it all along………"When we duplicated these tests using Photoshop 7.01, we found it was as much as 59% more efficient in the use of the scratch disk."
Proving once again that Barefeats never bothers to read a manual….
The scratch disk usage for PS 7 and CS is the SAME overall. There is some overhead in CS because of nested layer sets, and it allocates a little faster because of larger tiles – but the ovarall usage is still the same.
1) That section of the License Agreement is referring to Online Services – a feature of Photoshop that allows the user to send images to an online provider for printing. We currently offer only one such service in Photoshop (US) through Shutterfly. You can check it out for yourself by going to File | Online Services. If you don’t want to have this feature enabled, remove the Online Services plugin (Photoshop only | automate). Online Services are not related to the Adobe LM.
2) Adobe has not recommended people disable hyperthreading to address the tool issue on the dual Xeons – that’s been communicated by users. The workaround I would recommend would be to remove (or disable) Photoshop’s MP plugin. We are working to address this and other MP related issues.
3) ImageReady won’t fully load? At what point is the launch failing? Have you reset the IR prefs?
I really do not know exactly who here works for adobe or not, but in the thread about the thread about the "Photoshop CS Magic Wand bug" it is clearly suggested a few times that Adobe finally has awknowledged the problem and that the current work arounds is all we have for now. What was one of the two work arounds? Disabling Hyper Threading.
Also, the same arguement about the problem "must be on my end" was made untill Adobe reproduced the problem. So did all of a sudden my configuration become approved? I am not upset that Adobe has a few issue to be solved in a future update, but that Adobe acts like I must be an idiot or some mad computer geek that doesn’t know how to follow the installer. (NEXT NEXT NEXT… oh yeah… NEXT.) All I want is Adobe to publicly say, we found some issues, here is what we have confirmed and hopefully they will be solved soon.
Instead I get things like you must have a misconfigured computer or cracked software.
Sorry for the abbreviated earlier post.. This took some time to type up.
Thanks for the direct straight talk..
1) However, the legal implications are written quite broadly in a contractual sense..
2) Fair point.
3) It gets as far as creating the workspace and even the menu (but the splash screen is still there and the menu is inaccessible) the last process noted on the splash screen is:
"Layer Comps Palette Created"
I then get the warning dialogue box :Could not fully start the application. An unknown error has occurred."
When I click on "OK," ImageReady crashes to the desktop.
I’ve:
A) installed and uninstalled several times. I even uninstalled an reinstalled in Safe Mode.
B) Deleted the prefs
C) Removed the common file folders recommended.
D) Removed all but the base system fonts and delete the *.lst files.
E) Removed ALL the plugins..
F) even tried removing all the presets
G) checked for video driver issues (both checking for the latest drivers and disabling the video acceleration)
H) Used MSConfig to do a clean startup.
I) Changed the color depth.
J) Lowered the screen resolution.
K) Disabled the second monitor (the palette monitor)
L) Cleared all the temp files (all my temp and tmp files go their own partition)
M) Disks are defragged
N) Two primary scratch disks of 2gB each are empty
O) Virus software is all up-to-date and full system scans have been performed..
P) Even removed the Photoshop keys sub-folder from the registry AND the Adobe Systems subKey/Folder from the registry before reinstalling CS in safe mode.
Q) All my SCSI stuff (adaptec 2940UW card, Sprintscan 4000, and ZIp drive) is working fine..
R) RAM checks out ok…
PS CS, PS 6 and PS 7, as well as ImageReady 3 and ImageReady 7.01 all work fine when installed.
System is a Dual PIIIe 1gHz w/2 gB RAM @ 100mHz FSB
PShop is on the System drive (D:) where Windows XP also resides. Free space there is 30gB of 50gB.
Internet Temporary and Netcache files have their own partition.
Data files are on 2 separate partitions on two physical drives.
Windows XP pro has a fixed 4gB swap file.
Displays are a 21" Trinitron CRT running on an ATI 8500DV AGP card, and a 15" LCD palette monitor running off an nVidia GeForce4 MX420 PCI card.
Motherboard is a SuperMicro P6DGE. I’ve tried, at the suggestion of tech support, running ImageReady on another machine. The machine has the same MoBO and does not produce the same problems..
I did have the trial version installed first, and it had left a second LM service key in the registry, but that was finally dealt with when I removed PS CS and deleted all the related keys under \\HKEY_LOCAL_MACHINE\SOFTWARE\Adobe and \\HKEY_LOCAL_MACHINE\SOFTWARE\Adobe Systems
Thanks for being the VERY FIRST person on the Adobe Forums to actually take this seriously and try to offer help.. I posted this problem twice going back to over a week ago for the first post, while dealing with tech support and got not one response.. As you can probably tell, I’m getting more than a bit frustrated.
I’m not at the Mother Ship today so don’t have a lot of information at my disposal. <deleted info about plugins – should have read Keith’s post more carefully>. I’ll talk to folks about your issue when I get back to the office later this week.
I think your fellow professionals would appreciate these quotes you directed at me from another thread at "PS CS and serious memory problems under OS X (Panther)" <http://tinyurl.com/ywxjo>:
The quotes seem to be accurate – but then you go off into left field and draw conclusions that have nothing to do with the quotes.
(why does this smell more and more like a troll?)
followed by:
And you’re going off on other tangents that are also quite clearly non-problems.
So yes, it really does look like you’re trolling.
All in all, I’d call that distinctly unprofessional. NEVER, EVER, have I had an Employee of ANY Corporation call me something so unprofessional on a list hosted by said corporation. WHO THE HELL MADE YOU GOD?!!!
I suggest you check around in the inkjet business for people to verify my tenacity and tendency to stick to someone I consider unprofessional "like glue." Ask those same people about the EPSON Orange Shift debacle, or the following piece in Network World (among others): <http://tinyurl.com/2vcpz>
You chose to make it PERSONAL and now you’ve bought yourself the wrong person to have as a PERSONAL foe. If your personal arrogance towards users with complaints is the future face of Adobe, I hope to god M$ buys you out..
Don’t worry Chris, I’ll write a formal letter of complaint to Adobe corporate about your demonstrated arrogance towards the user community when I have the time. Ooops, I forgot, you’re GOD at Adobe… I guess nobody will care about your unprofessional behavior as a representative of Adobe on a forum hosted BY them then.
Keith
"Just some guy," caretaker of the Multiverse’s largest EPSON printer User Community (highly recommended by Vogon Poets and MegaDodo Publications), at: <http://groups.yahoo.com/group/EPSON_Printers/> and the Multiverse’s largest Canon printer User Community at: <http://groups.yahoo.com/group/Canon-printers> "For the rest of you out there, the secret is to bang the rocks together guys"
The relevant portion of the System Information (which no-one from Tech Support even asked about) is:
Adobe Photoshop Version: 8.0 (8.0×118) Operating System: Windows XP Version: 5.1 Service Pack 1 System architecture: Intel CPU Family:6, Model:8, Stepping:6 with MMX, SSE Integer, SSE FP Processor speed: 1002 MHz Built-in memory: 1535 MB Free memory: 739 MB Memory available to Photoshop: 1401 MB Memory used by Photoshop: 50 % Image cache levels: 8 Use image cache for histograms: No Serial number: 1045XXXXXXXXXXXXXXXX Application folder: D:\Program Files\Adobe\Photoshop CS\ Temporary file path: e:\temp\ Photoshop scratch has async I/O enabled Scratch volume(s): G:\, 125.6G, 52.2G free K:\, 4.00G, 4.00G free I:\, 4.01G, 4.01G free T:\, 512.8M, 364.2M free Primary Plug-ins folder: D:\Program Files\Adobe\Photoshop CS\Plug-Ins\ Additional Plug-ins folder: not set
That T: drive is a .5gB RAM disk leaving 1.5gB for System RAM.. and sincerely, thanks for checking into this.. I don’t need an answer anytime soon, as I’ve got ImageReady CS available if I need it on that slower second machine that I did the test install on to see if it was a MoBo issue.
You can reach me directly at the email attached to my case #5883801. Or by getting my email addy from <http://www.p-o-v-image.com/> (go to the "Office" section)
Almost 5 days working with the Hyper-Threading disabled and I didn’t have a single crash with the Magic Wand Tool. I really have to thank you again Malameel 😉 finally I can work! I still keep the memory percentage reduced to 70% as suggested by Chris, but it’s slowest than 7.01 anyway. If you want to test the diference of speed on the same system between CS and 7.01 try to work with one 400dpi CMYK image with 9220×3003 pixels with almost 10 big image layers and more than 50 small images, that’s my work at this moment. With this size of images you real can tell the diference between the two versions on the same system.
keith, i understand you’re upset w/chris right now, but for the record, chris is one of the few helpful techs that post here in an unofficial capacity, of his own free will on his own time. it would really suck if he decided not to post here any more. he can be terse at times (like others i know <g>, i.e. me.) and gruff with people who he feels are not listening to what he is saying, but overall he is extremely effective and a great source of info and technical help. please reconsider your attitude towards him before firing off a letter that causes him to desist from offering helpful advice here in his off time.
He’s referring to clicking on names in the forum – which brings up more information about the user.
Now *that* would make a difference (not that I use the web forum), but that’s not what they said originally ("click on his name on the splash screen" is different than "click on his name in the web forum.").
In any case, it’s obviously no big deal, I just didn’t understand what he was trying to say.
The other work around maybe better which is to remove a plugin called Multiprocessor Support under ~plugins/extensions. I am not sure which is better: Disabling Hyper Threading globally, or just bringing PS to one proc with hyperthreading?
It seems to do more with dual proc w/ hyper threading and not single with hyper T. I am not sure if I have heard anybody with the problem with a single processor. Either way, one of these solutions do work, and already one does for you.
Just one clarification: Chris isn’t a tech. Neither am I.
We don’t know that there’s a bug with memory handling yet. We haven’t yet gotten enough relevant information to be able to reproduce something unexpected here yet. We’ve seen a lot of "me too" posts from people who don’t understand and who don’t add information to help diagnose things.
The misstatement in the Barefeats article doesn’t help things either.
Keith,
You have written rather obnoxiously in several posts now. You really need to step back and consider what you write better. Chris is terse, and I know many people read too much into the gaps of what he says. But he was correct when stating that you seem to go off in left field quickly. You haven’t added much (if anything) positive to the threads you have been a part of.
keith, i understand you’re upset w/chris right now, but for the record, chris is one of the few helpful techs that post here in an unofficial capacity, of his own free will on his own time. it would really suck if he decided not to post here any more. he can be terse at times (like others i know <g>, i.e. me.) and gruff with people who he feels are not listening to what he is saying, but overall he is extremely effective and a great source of info and technical help.
Sure, I’ll reconsider.. IF AND IFF Chris posts public apologies for his complete lack of professionalism to me in each of the threads dealing with this issue AND posts a similar apology in new threads (with the words "Chris Cox apologizes to Keith Krebs" in the subject) in The Lounge, The Mac Photoshop Forum, and the Windoze Photoshop Forum. I’m not about to tolerate his arrogance, hubris, and unprofessional behavior. I’ve worked with people from Presidents, Governors, Senators, Four Star Generals, Congresspeople, countless ISVs, hardware vendors, to even homeless people and I’ve never had to tolerate such publicly unprofessional behavior from someone supposedly trying to help. Gruff is one thing. Publicly calling a user/consumer of your products a "troll" because you don’t like their commentary is quite another. Beyond that, that wasn’t his only comment, it was just the worst of it. Nor am I the ONLY user he has recently chosen to publicly belittle or attempt to humiliate.
Dave, I appreciate your candor and apology on Chris’s behalf, but he chose to make this personal, not I. If he’s going to do that it’s now his problem to resolve. I’m sure the people who’ve been reporting on Photoshop CS bugs, CDS, and activation would like to know how unprofessionally one of the ‘name’ software engineers / techs for Adobe is treating users on one of Adobe’s hosted fora. I haven’t yet taken this anywhere outside the forum, but IF I do have to go to the steps of penning a formal complaint letter to Adobe, I will ‘cc’ appropriate parties outside Adobe as well. I simply won’t be treated by an employee of a company I’ve paid significant $ to, to insult me publicly and personally on a forum run by said company. It’s wrong, plain and simple. You know it, I know it, and every Adobe staffer who has seen it to this point knows it.
To close, whether or not he is being helpful, I haven’t seen Chris being anything but coating his help in terse and combative behavior on these issues of late. This is not his personal forum in which to vent his frustration – he remains a representative of Adobe when he chooses to post here, and has a responsibility to conduct himself accordingly (that’s a basic rule of corporate life anywhere). At no point hitherto has Chris apologized or retracted one iota of his commentary (publicly or privately). When it reaches the point where I have to ASK for a public apology, where others are apologizing for him and pointing out his ‘value’ in contrast to his attitude, there is clearly a problem. If I further have to publicly contemplate writing to the Corporate side of the house in San Jose, and he still hasn’t apologized, it is then incumbent upon Adobe corporate to redress the issue as THEY see fit. If it’s not an issue as far as they are concerned so be it.
There is a difference between being terse and an Adobe staffer calling someone names like "troll."
My "obnoxious" commentary was not directed at Chris, but what I perceived as clear contradictions between statements by differing people at Adobe. In fact, I even said to Chris in that very thread, AFTER he called me a "troll" that I could understand the same facts resulting in differing conclusions (in part as an olive branch). What was the result? He immediately called me a "troll" again.
Bluntly if Chris can’t separate himself from Adobe, if he so identifies himself with Adobe as to confuse the two, and take personally complaints about product produced by Adobe, there’s a problem. He ISN’T Adobe and he has transgressed the boundaries of appropriate professional behavior.
Dave, I appreciate your candor and apology on Chris’s behalf,
It wasn’t an apology on his behalf… I wouldn’t presume. I was simply stating that his input is extremely valuable to this group. Yours? That’s yet to be seen. IMO you have no right to an apology and wouldn’t hold my breath waiting for one. He’s right, you have been combative and trollish. You need to lighten up a bit so we can all work together to solve problems – if that’s your intent here – rather than creating new ones.
Well, Chris is not required to be here. And I for one would find it a pity if he decided to stop coming around.
Anyone who’s been in this forum for any length of time is well aware of Chris’ way of doing things. He doesn’t beat around the bush. You’d do well to try to work with him instead of fighting with him. We’ll all be better off.
And as far as bashing Adobe, there’s no company that I can think of that has this many employees active in their user forums.
While I don’t doubt your expertise, I would certainly consider Chris to far more knowlegable about the inner workings of Photoshop than just about anyone else.
If this was Quark, the best you could hope for is that the forums would be started back up! We are very lucky that Adobe personnel come here at all-Never once in 7 years did I see any Quark employees post anything to the Quark forums! I have learned more from Chris and Len and Scott and Dave and Ian, phospor, et al. then I have ever learned at a seminar etc. Be glad that they care enough to answer posts, most companies employees don’t!
Anyone who’s been in this forum for any length of time is well aware of Chris’ way of doing things. He doesn’t beat around the bush. You’d do well to try to work with him instead of fighting with him.
There’s a difference between not beating around the bush and misidentifying himself as "Adobe." It doesn’t benefit anyone for Chris to behave like that. If he doesn’t like it, too bad. Fact is, when he chooses to post here he IS representing Adobe, and he is well aware of it.
Robert also said,
Well, Chris is not required to be here. And I for one would find it a pity if he decided to stop coming around.
Would it be? Probably. BUT, that doesn’t excuse his behavior. If he "needs a vacation" perhaps he should take one instead of directing personal insults at users.
If his style is to be rude and refuse to apologize, well, guess what? I don’t care how valuable he is as an "asset" to the community, I won’t simply ignore his truculent behavior.
Robert continued on to say:
And as far as bashing Adobe, there’s no company that I can think of that has this many employees active in their user forums.
No-one is bashing Adobe. You don’t hear me complaining about the behavior of any other Adobe staff do you? In fact, I’ve posted items praising tech support from Adobe etc. Disagreeing with a policy or the way something is implemented is not "bashing Adobe" – I’ve made very clear that OTHER companies do NOT provide fora like this, and that they are a great service to the user community. To analogize, churches may be a great service to the community but if a pastor kept insulting the congregants, eventually he/she would likely be asked to change his/her attitude or move on elsewhere. The point is that Chris’s behavior in no way increases disutility, what it DOES do, as when ANY employee ANYWHERE behaves poorly, is reflect badly upon that enterprise.
It wasn’t an apology on his behalf… I wouldn’t presume. I was simply stating that his input is extremely valuable to this group.
It’s a user to user forum. Whether or not a particular user is allowed to insult other users cannot be related to how useful the user spewing insults is. It’s a basic rule of any corporate enterprise that when representing the company one behaves professionally, and on this forum, whether he likes it or not, Chris DOES represent Adobe.
I’m not arguing that Chris’ input is not valuable here. It is.. The point is not whose input is more valuable. I don’t think my input will ever be as valuable as anyone at Adobe’s (I’d have to be delusional or megalomaniacal to think otherwise), this is a forum focussed upon Adobe products.
The bottom line is if Chris thinks his behavior was appropriate and beyond reproach, I’m sure you’ll see him back. If not, I didn’t start calling people names, he did. Not only that, I have not responded in kind beyond complaining about and pointing out his behavior.
Bottom line, no-one here controls Chris’ actions but Chris, he has to take the responsibility for them.
I don’t care how valuable he is as an "asset" to the community
Then leave the "community"!! You have little to no value if you don’t want to help us figure stuff out. You come in and start making threats? You want to brag about your episode with Epson? Fine. But you sound like a lawyer to me, as opposed to someone who wants to help. (Notice how I avoided the word "troll" because I didn’t want to get sued?) Mostly, what I’ve seen from you is an inability to be tolerant of how people express themselves. Myself, I’d like to see Chris keep posting here, and for you to find another target area.
You have written rather obnoxiously in several posts now.
There’s a differnce in being perturbed about a series of different issues with CS, and personal attacks.
Chris is terse, and I know many people read too much into the gaps of what he says.
There wans’t any reading between the lines here, I quoted him exactly.
But he was correct when stating that you seem to go off in left field quickly.
Again, he could have made the point professionally, or, AT THE LEAST, without resorting to name calling. It’s not Chris’ input it’s his tendency to be rude, insulting, and belittling of users. Name-calling aimed at individual users takes it over the top and is IMHO completely unprofessional. Let me ask you Scott.. Would such name calling be allowed as standard way of doing business between employees in cubicles on the San Jose Campus? If not, than the behavior he exhibits here is just as unacceptable. Whether or not Chris or you like it, the fact of corporate life is that employees when interacting with the public are generally held to a higher standard of professionalism than are buyers/consumers/clients .
You haven’t added much (if anything) positive to the threads you have been a part of.
Scott if you want to give me more reason to NOT back off, you’re doing a mighty good job at it..
Then leave the "community"!! You have little to no value if you don’t want to help us figure stuff out.
No-one said I don’t want to help.. What I said is that wanting to help does NOT mean a willingness to accept unprofessional conduct from an employee of Adobe on an Adobe hosted forum. Nor does it mean that I will leave as a weak kneed way of responding to his insults.
Notice how I avoided the word "troll" because I didn’t want to get sued?
Let’s be real about this. No-one is talking about suing anyone. What Chris did was engage in personal invective.. It’s not Adobe’s fault he did so, but once they are on notice of his penchant for doing so, if he then crosses the line into libel, or slander, etc. with another person, then Adobe COULD be held liable – that’s part of why when employees represent a company, they can’t simply tell customers to "go ____ themselves."
Nick also said:
You want to brag about your episode with Epson?
No-one is bragging, I’m simply pointing out facts as relevant to dealing with me, and knowing how hard-nosed I can be, as knowing Chris is an employee of Adobe when reading his insights into an Adobe product offering.
Mostly, what I’ve seen from you is an inability to be tolerant of how people express themselves.
No, I’m simply intolerant of direct personal insults which are, I believe, prohibited by the TOS here.. If an Adobe employee violates those very rules with impunity it makes a mockery out of even having them.
It seems there is some feeling on this board that if Chris isn’t allowed to behave in his own "unique" way, and vent as he wishes, that he won’t post. If that’s the case, that’s his choice, not mine, not yours, and no-one’s but Chris’s.
I’ll make this clear one last time.. I have NO grudge against Adobe, nor did I have any personal reasons to like or dislike Chris – I certainly held no enmity for him.. I didn’t attack him, he chose to attack me.
what do you call someone who has to get the last word in and is always right?
troll Last modified: Wednesday, April 16, 2003
(v.) (1) To deliberately post derogatory or inflammatory comments to a community forum, chat room, newsgroup and/or a blog in order to bait other users into responding.
Finally, I’ve said what I have to on this issue. It’s not worth me belaboring or arguing about. I don’t expect to change opinions on it.. Accordingly, I’m not going to engage in discussion of my opinion of Chris’s behavior further. (please DO note: I differentiate that from my opinion of Chris – bad behavior by someone does NOT mean I think they are an axiomatically bad person – as I’ve said Chris OBVIOUSLY has MUCH to contribute, both onlist or elsewhere, what my opinion of him is or was is unimportant and not beholden to his behavior)
The only response I can give is that if I KNEW Chris was likely to respond in the way he did, if I had also known that he was participating in that thread, I would likely have tempered my remarks. I was not looking for him to throw personal insults at me – that kind of divisive stuff doesn’t help anyone..
