A blog on blogging, computers and such

I was hoping Adobe would fix the problems with apdproxy.exe, which crashes my machine ever so often, and that they would stabilize Dreamweaver CS3, which I love, but which also make my PC crash ever so often.

But instead the folks at Adobe seems to have used my remaining confidence in them to upload a program called ComponentLauncher.exe onto my PC, presumably calling it an “update”. This program too will suddenly come alive and steal all my CPU, thus making my mackine useless. Fixing the problem requires turining the program off in Task Manager, or, occationally, closing down everything and rebooting (and sending off a quick prayer that neither CompnentLaucher not apdproxy will kill the machine after reboot).

Searching Google,
I find that a large number of people have the same problem as me.

So, what can I say, apart from “Congrats Adobe - you did it again!” I think Adobe is hell bent on shedding its customer base as soon as possible. Good luck!

Yesterday I lost about half an hour of my work time, thanks to Adobe. As I have stated before, I am a great fan of Adobe. I love the functionality of their software - Flash, Dreamweaver, Fireworks, Photoshop, and so on. All excellent software.

But all is not well in my relationship to Adobe. A little program that comes with the Adobe software, apdproxy.exe, is really annoying. When I boot up my machine (a new Dell XPS with 2 Gb RAM, running Windows XP), this little program sometimes makes my machine grind to a halt. When this happens, and I eventually get into the Windows task manager (this takes a while because all CPU is taken up by this annoying program), I most often can observe that apdproxy.exe is eating between 95% and 99% of my CPU. Then it is a matter of closing it down. With this done, my PC comes alive again.

Also, I frequently experience Dreamweaver crashes when I am working on my Web sites. In the middle of editing something, often simple copy and paste operations, Dreamweaver simply freezes. Sometimes it recovers, sometimes not.

I wonder why Adobe doesn’t do anything with these problems. They are well known. I am not the only blogger who has expressed dis-satisfaction.

I am getting quite grumpy over this. At this point I have started to wonder what to do? Should I discontinue using software I otherwise love? Or should I simply start sending bills to Adobe for my lost time?

– Peter