CinePaint was known unofficially by many names: Gimp16, Film Gimp and Hollywood Gimp. The name was officially changed to CinePaint in March 2003, which may end the confusion. The first release of CinePaint was on the Windows platform because that happened to be released at the time of the name change. That it is Film Gimp 0.16 on some platforms and CinePaint 0.16 for Windows has no special significance beyond timing. Future versions on all platforms will be called CinePaint.

The base functionality is similar, but Adobe Photoshop doesn't include the special features that CinePaint has for working with motion pictures and film. CinePaint has higher color fidelity -- supporting 16-bit channels, plus a frame manager and a flipbook movie player. Photoshop is more mature as an application, with a more pleasing user interface, support for color spaces, and CMYK. These areas are being improved in CinePaint. CinePaint is available for many more operating systems.

The "GNU Image Manipulation Program" (originally the General Image Manipulation Program) sired by Spencer Kimball & Peter Mattis. In their own words, "GIMP is our answer to the current lack of free (or at least reasonably priced) image manipulation software for Linux and UNIX in general." It is a raster editor, which means that it performs operations directly on the pixels that make up the image, and not a vector editor.

There's an experimental compatibility header that fixes most problems. However, bringing plug-ins over to Windows presents special challenges because some are unfriendly to the new threading architecture and hang CinePaint by starving the event loop. It's being worked on. Another area in development is gimp-print 16-bit support so that high fidelity art prints can be output.

For 35mm motion pictures the studios have million dollar high resolution film recorders. Some can be rented. Studio gear can be custom made or bought commercially. Prices start at $120k for LaserGraphics printer.

Not really. It doesn't use the GNOME application framework. The only thing it has in common is GTK+. GIMP can optionally use gnome-vfs, allowing you to load and edit images from remote servers.

GTK was developed solely for GIMP, initially. Towards the end of the 0.99 development cycle in 1998, GTK was split from being bundled with GIMP to being a separately available library. See ancient history for some interesting tidbits from the GIMP perspective.

Yes. You can run xscanimage, the front end to SANE (Scanner Access Now Easy), either as a GIMP extension or in stand-alone mode. This supports Mustek and HP flatbed scanners, as well as the Connectix color QuickCam camera.

Yes. In either the system-wide gimprc file or your personal gimprc file, uncomment the line that includes install-colormap. If GIMP gives you a message similar to either of these when you try to start it: Xlib: extension "MIT-SHM" missing on display "198.51.29.58:0.0". or * WARNING **: XShmAttach failed! then you need to run it with the --no-xshm option. This happens for one of two reasons.

Any system capable of running Gnome 2, KDE 3.2, Windows 2000, Mac OS X and later versions should be able to run GIMP. GIMP's biggest appetite is for memory and how much you will need will depend on the how many images you are working with, their resolution, size, the number of layers you use and so on. As a general rule, more is better, but 128MB should be enough to be getting started with.

Use the elliptical select tool, hold down SHIFT key to constrain as circle, fill the selected area with new color, right click on selected area, choose SELECT, SHRINK, shrink selection by whatever number of pixels you want your circle width to be, right click again in selected area, choose EDIT, CUT. Voila, one beautifully antialased circle.

You need to copy the gtkrc file that comes with the GIMP source (in the top level directory) into $HOME/.gimp/gtkrc . As of 0.99.10, this should be recognized.

Some broken application placed a file named intl.dll to your Windows or Windows\System32 directory. Rename it, and GIMP will work fine.

Minimize the window and ignore it, as most of the warnings it displays are harmless, and GIMP will still work. This is usually caused by broken programs installing libraries to Windows\System32 directory. Most likely there's a bad version of intl.dll, libxml2.dll, xmlparse.dll or xmltok.dll in there. Rename or remove it, and GIMP should load fine.