@DGPhoto: "I installed CS3 with no issues. However, every time that I try to open more than one image (of any format, and by any method - menu, dragdrop, doubleclick, from bridge) PS crashes with "an unhandled win32 exception occurred in Photoshop.exe[3188]"
I regard this application as junk and unusable at this time. My confidence in Adobe is badly shaken. I'm just glad that I didn't uninstall CS2...
David"
    @Jeff_Schewe: ""I regard this application as junk and unusable at this time. My confidence in Adobe is badly shaken."
Uh huh. . .well, do you want help or are you satisfied with just ranting? Cause if you want help, it may be useful to include some basic info...you know, like what OS, what CPU, what ram allocation, whether you had the beta of CS3, whether or not you properly un-installed the beta. You know, the basic stuff that might help somebody HELP YOU...
Course, if ya just want to RANT, that's ok too....won't help YOU, but if it makes you feel better..."
    @David_Beronja: "I'm getting the same problem. Install also went with out problems but getting the same error. I did try to uninstall CS2 and re-installing the CS3 Suite just in case there was a conflict. No change.
Gateway PC, XP Pro (2002) service pack 2, Pentium 4 3.2GHz, 1gig Ram
No install of CS3 beta. I am using a Wacom Tablet with Control Panel 6.02-1 and Driver Version: 6.02-1. I upgraded the previous tablet drivers with no change"
    @Ariel_Popper: "I have a problem similar to this as well. every time i try to start a new document or open a document photoshop crashes. there are no error numbers or anything, just a plain dialog that says:
"Adobe Photoshop CS3 has encountered a problem and needs to close. We are sorry for the inconvenience." (with buttons for sending the report to microsoft or opening in a debugger)
had uninstalled both cs2 suite and the cs3 beta before installing web premium suite. i believe that i saw this behavior in cs2 after i had uninstalled the cs3 beta, but since i had web premium here i thought the new version would take care of it.
am running XP Pro x64 SP2, Core2Duo E6400, 2GB RAM"
    @DGPhoto: "It's not a suprise that I get flamed by some 12 year old. You want a rant Jeff? My post was far from it. The releases of 5.5, 6, 7, CS, and CS2, COMBINED, were less buggy for me than the release of CS3. Period. I spend enough time debugging MS apps after their release - I don't have time to do that with Adobe too. If you've have better luck then enjoy it, but if you don't have anything constructive to add then go play with some Legos.
For anyone who wants more information on my issue:
- it happens on 6 different machines: 2 Lenovo laptops, 2 Dells, and 2 homebuilts, ranging from a few years old to a few months old
- ram ranges from 1 to 3GB
- all are running Windows XP, fully updated
- all have Visual Studio installed, fully updated
- all are up to date on drivers, etc.
- some ran the beta, some didn't
- some uninstalled CS2 first, some didn't
- uninstalling and reinstalling doesn't help
If I debug it I get:
"Unhandled exception at 0x7c918fea in Photoshop.exe: 0xC0000005: Access violation writing location 0x00000010."
And if you really like nuts and bolts, it breaks here:
...
7C918FA7 sete byte ptr [ebp+0Bh]
7C918FAB mov eax,dword ptr fs:[00000018h]
7C918FB1 movzx ecx,byte ptr [ebp+0Bh]
7C918FB5 mov dword ptr [eax+0F84h],ecx
7C918FBB cmp byte ptr ds:[7C97C030h],bl
7C918FC1 jne 7C919493
7C918FC7 mov al,byte ptr ds:[7C97C148h]
7C918FCC neg al
7C918FCE push edi
7C918FCF sbb eax,eax
7C918FD1 not eax
7C918FD3 and eax,7C97C140h
7C918FD8 mov edi,eax
7C918FDA mov eax,dword ptr [esi+10h]
7C918FDD cmp eax,ebx
7C918FDF mov dword ptr [ebp-4],eax
7C918FE2 je 7C919086
7C918FE8 mov eax,dword ptr [esi]
7C918FEA inc dword ptr [eax+10h] < BREAK LINE ...
David"
    @John_Joslin: "DGPhoto
You are making a fool of yourself.
Your original post wasn't exactly lucid and you obviously don't know who Jeff is!"
    @dave_milbut: "      It's not a suprise that I get flamed by some 12 year old.
LMAO!
 <<url>
HA! OK Mr Schewe, I'm going to have to see some ID if you want that 6 pack!!! :P :)"
    @Lawrence_Hudetz: "DG meant it metaphorically, I presume.
C'mon, Jeff! Somewhere inside, doesn't a 12 yoar old lurk there? I have one and he is always driving me crazy! Try this, try that.
Hey, whadda ya know! The kid was right!:D"
    @DGPhoto: "Um...that was intended to be a touch humorous. Next time I'll include more smilies. And yes he has a nice website, and I'm sure he's a nice guy, and I'm sure he's been making far more for far longer than I have.
But if it's not a rant don't call it a rant. My original post was a starting point, because I was insanely busy and trying to get stuff out the door, so I was a tad rushed.
This isn't my only issue with CS3, and since CS2 has been running flawlessly on some of the same systems, it would be logical to conclude the issues lie with CS3. The BETA didn't even break as much as the production version. How often do you see that?
David"
    @DGPhoto: "OK, here's more:
- we don't have MS Intelipoint drivers, so I can't remove those
- removing Bonjour didn't help, although I don't need the service running anyway
- changing my default printer from a network printer to "Adobe PDF" fixes the problem...wait what?
I verified this on both Dell boxes and a laptop. I'll have to check this on one of the homebuilt machines tonight, because there it was happening with an attached Canon printer.
And since there was some confusion earlier, the following statement can freely be taken as a rant: there is no good reason that a default printer being on a network should cause an application of this caliber to crash in such an ungraceful manner.
More to follow.
David"
    @tar4heel2: "David is absolutely correct; He's being nice about it, if you want my opinion. And it doesn't matter who Jeff is, because David has hit the nail on the head; this is B******* that Adobe is putting everyone through this nonsense. Totally inexcusable. It is absurd to assume that the seasoned, professional, very busy user base is going to lie down for all the crap you have to do just to get the damned thing installed. They actually say to do a clean install of Windows XP and then install CS3? Do you have any idea what that entails and how much time and grief one has to endure to do that? Manual changes to registry, incomplete instructions during the final version install... crashes that have no fix, changes in the print dialoque box that are stupid...
Adobe should be taken out behind the barn... and to think they had the temerity to levy a 33% increase in price over the last upgrade pricing... pour salt in the wound...
Phil"
    @Lawrence_Hudetz: "Adobe needs to deal with it, yes. But here is one persons's experience:
I installed or witnessed the installation of CS3 on four machines. Three went flawlessly. Two had Beta, two did not. Both machines w/o Beta went flawlessly. My machine did have Beta and I had no trouble. The last machine did also have Beta and it was a messy installation, but it is now running.
FWIW."
    @Ariel_Popper: "Just FYI. The change default printer to Adobe also worked for my problem (detailed earlier in the thread). The only other printer i had installed was Microsoft XPS Document Writer. Thanks."
    @Kim_Huff: "I am also having the same problem. I did have CS2, but this is a new machine and was installed for me after the laptop was built.
This is a custom built laptop with an MSI case and motherboard. AMD Duo Core 1.8 ghz with 533 fsb, has 2gbs of ram, 100 gb sata 7200 rpm hd, has a bunch of other features like card reader, webcam, etc but dont think you need that. I always disable the touchpad (i hate those things) and use my USB MS Trackball.
The performance tab in preferences has the following:
Available RAM: 1711 MB
Ideal Range: 941-1232 MB
Let Photoshop Use: 941 MB (55%)
Scratch Disk points to the C drive ands says free space 53 GB
Not sure what else you might need. Any help would be greatly appreciated.
Thank you in advance,
Kim"
    @Kim_Huff: "FYI, I just saw DG's post about changing the printer to ADOBE PDF as the default and it worked.
I can keep it like this for now, but does anyone know if Adobe is working on a fix for this?
Kim"
{'source': 'USENET', 'other_information': '{"reply_count": 14, "forum_name": "adobe.photoshop.windows.20140909.mbox"}', 'file': 'data/output/usenet-adobe.photoshop.parquet'}