Tag Archives: cs3

How to Install Custom Photoshop Brushes in CS3 CodeUnit 02 DEC 2011

One of the many things that make Photoshop such a powerhouse when it comes to image manipulation is its ability to be extended through things like custom brushes and shapes, generated by users themselves.

Photoshop CS3 custom brushes are packaged as .abr files and to install them is actually pretty simple.

First, download the custom brush .abr file you wish to install (it may be zipped, in which case extract it first). Next, browse to the install path of your CS3 installation. Locate the Presets folder, and in that, the Brushes folder. The most common path under Windows is usually:

C:\Program Files\Adobe\Adobe Photoshop CS3\Presets\Brushes

Move your downloaded .abr file into that folder. Note that the file name determines the label under Photoshop, so it is a good idea to give the file a nice descriptive name, like “Polka Dot Brushes.abr” for example.

Now simply restart Photoshop, and you’ll find your new brushes available for use in the system.

When Adobe CS3 doesn’t Want to Install on Windows Vista CodeUnit 11 JUL 2009

Adobe Photoshop Feather LogoRight, you’ve got a shiny new copy of Adobe Photoshop CS3 in your hands and a desktop loaded with Microsoft Vista in front of you. However, each and every time you attempt to install CS3 the installer just bombs out with nary a single error message.

Not cool when you consider how much the application actually cost in the first place!

Anyway, run the installer from the command line and see if it spits out an error. If it does, and the error reads “End Adobe Setup. Exit code: 4” then you are in luck.

(Alternatively, take a look inside the Adobe log file named Add or Remove Adobe Creative Suite 3 Web Premium 1.0.log.gz. Again, if you find a line reading “DEBUG: Error 2739: Could not access JavaScript runtime for custom action Internal Error 2739” then you’re definitely in luck)

The problem is caused due to the MSI installer code running custom Jscript and to fix it one simply needs to re-register the jscript DLL file.

So without any further ado:

Open an administrive cmd prompt
cd windowssytem32
regsvr32 jscript.dll

Note: you might have to run the cmd prompt as Administrator in order to gain the necessary rights in order to re-register the offending DLL.