Free canon powershot software for linux

recoverPhotos is a program that recovers digital images from camera memory cards that have been formatted or damaged.
This program relies on the fact that most photos are composed of contiguous sectors. If you tend to delete a lot of photos before a format, then you might not have very good success. But if you are like me: who reformats every time) then you fill get most of your pictures back.
This program has only been tested with a 20d. Any success stories are welcome.
HOW TO USE
To run this program I recommend you first copy the contents of the card to a file in your machine. The easiest way is to use the dd command.
Instructions:
- Connect the camera or the flashcard to the computer.
- Check what is the mount point for your camera or the flashcard. You can use the mount command for this. For example in my computer the flashcard is mounted as device /dev/sdc1
dmg@platinum recoverPhotos]$ mount
[...]
/dev/sdc1 on /media/EOS_DIGITAL type vfat ...
[...]
Now, use dd to copy the flashcard to a file. For example, this command copies the contents of my memory card to a file called /tmp/card.bytes (You might need to run this command as root).
dd if=/dev/sdc1 of=/tmp/card.bytes
Make sure the device name (in this case /dev/sdc1) is correct!
The resulting file should have the same size as the flashcard.
./recoverPhotos /tmp/card.bytes
and check the output. Hopefully you will have a bunch of photos in the current directory. Run the program without parameters to see all the options available.
CANON USERS
If you use a camera that uses the custom function "Add Decision Data" (CF18 in the D20), and you are 100% sure it was on when you took the photos, then make sure you specify the --canonADD option. The option is not critical (it is not part of the photo), but the data is there if you want to recover it.
Enhancements:
- JPEG and Canon CR2 files are supported.

PhotoRec is a small tool to recover pictures from digital camera memory. Photorec software searches for MOV and JPEG headers, and because there is (usually) no data fragmentation, it can recover the whole file.
It can recover data from CompactFlash, Memory Stick, SecureDigital, SmartMedia, Microdrive, MMC, USB Memory Drives...
PhotoRec is safe to use, it will never attempt to write to the drive or memory support you are about to recover from. Recovered files are instead written in the directory from where you are running the PhotoRec program.
Photorec ignores the filesystem, this way it works even if the filesystem is severely damaged.
It can recover lost files at least from:
- FAT,
- NTFS,
- EXT2/EXT3 filesystem
Digital Camera
PhotoRec has been successfully tested with:
- Canon EOS300D, 10D
- HP PhotoSmart 620, 850, 935
- Nikon CoolPix 775, 5700
- Olympus C350N, C860L, Mju 400 Digital, Stylus 300
- Sony DSC-P9
- Praktica DCZ-3.4
- Casio Exilim EX-Z 750
PhotoRec searchs known file header and because there is no data fragmentation (usually), it can recover the whole file. Photorec recognises numerous file format including:
Archive
- .7z 7zip archive file
- .bz2 bzip2 compressed data
- .gz gzip compressed data
- .rar Rar archive
- .tar tar archive
- .zip zip archive
- Multimedia
- .asf, .wma, .wmv: Advanced Streaming Format used for Audio/Video
- .au Sun/NeXT audio data
- .avi .wav RIFF audio/video
- .bmp BMP bitmap image
- .cdr Corel Draw
- .crw Canon Raw picture
- .ctg Canon catalog
- .dcr Kodak Raw picture
- .dsc Nikon dsc
- .fla Flash Project File
- .gif Graphic Interchange Format
- .jng JPEG Network Graphics
- .jpg JPG picture
- .mng Multiple-Image Network Graphics
- .mov MOV video
- .mp3 MPEG ADTS, layer III, v1 audio
- .mp4 MPEG 4
- .mpg Moving Picture Experts Group video
- .mrw Minolta Raw picture
- .ogg OGG Vorbis audio
- .orf Olympus Raw Format picture
- .pcx PCX file format
- .pef Pentax Raw picture
- .png Portable Network Graphics
- .psd Adobe Photoshop Image
- .qxd QuarkXpress Document
- .qxp QuarkXpress Document
- .raf Raw Fujifilm picture
- .raw Contax picture
- .rdc Rollei picture
- .sit Mikron
- .sr2 Sony Raw picture
- .tif Tag Image File Format
- .x3f Sigma/Foveon X3 raw picture
- .xcf GIMP XCF File
Office
- .doc Microsoft Word
- .mbd Access database
- .odd OpenDocument Drawing
- .odp OpenDocument Presentation
- .ods OpenDocument Spreadsheet
- .odt OpenDocument Text
- .pap Papyrus word file
- .ppt PowerPoint presentation
- .rtf Rich Text Format
- .sda StarDraw
- .sdc StarCalc
- .sdd StarImpress
- .sdw StarWriter
- .slk Sylk, Multiplan Symbolic Link Interchange
- .sxc OpenOffice Spreadsheet
- .sxd OpenOffice Drawing
- .sxi OpenOffice Presentation
- .sxw OpenOffice Text Document
- .txt Text file
- .vis Visio document
- .xls Microsoft Excel
Others
- .asp ASP script
- .bat Batch
- .c C source file
- .dbf DBase 3 (prone to false positive)
- .dbx Outlook Express
- .eps Encasulated PostScript
- .exe MS executable
- .frm MySQL table definition
- .h C header
- .html HTML
- .jsp JSP script
- .MYI MySQL MISAM compressed data
- .pdf Portable Document Format
- .php PHP script
- .pl Perl script
- .prc PalmOS application
- .ps PostScript document
- .pst Outlook
- .py Python script
- .qdf Quicken
- .sh Shell script
- .wab Windows Address Book
Enhancements:
- A new method for handling fragmented data is now used, making recovery more reliable and faster.
- This release can be set to search for files in FAT16/FAT32 unallocated space only, which avoids wasting time recovering files that are still accessible, making the recovery of lost files much faster and more efficient.
- New file formats have been added.

multican is a Canon EOS class camera remote control utility.
multican is able to remote control 300D, 350D, 30D, 20D, and 5D cameras and can be scripted to control up to six attached cameras.
Which functions are supported?
Several remote control functions are available in scripts, they are:
- setting shutter release speed (Tv)
- setting aperture size (Av)
- setting ISO sensitivity
- releasing shutter (currently only allows to store the image on CF)
Known Bugs:
The timing in the script strongly depends on the camera type and CF card which is used to do shooting. This is to be tested by multican user himself. If too short times are described in the script, the communication may hang, may skip some commands. Thanks to camera image caching, the shooting rate could be set under 1s if only several images are takes since the most of the EOS camera models contains an image cache, so that the images are stored into a queue and written to the CF lately.
The known bug in this multican release is that cameras need to be switched off and on again when a scripted sequence is finished and a new one is to be done. This is likely caused by the fact that the communication is not correcly terminated in the actual multicam release.
Enhancements:
- fix typos, update docs
- fix warnings

Image::MetaData::JPEG::MakerNotes contains random information and details on MakerNotes.

Pieces of information available after parsing the MakerNote

The result of the process of parsing the maker note is stored in a directory in the internal data structure for the APP1 Segment, whose path is "IFD@SubIFD@MakerNoteData_$format", where $format is the specific note format; the MakerNote entry in IFD0@SubIFD is then removed. This translation happens always, because there is a catch-all unknown rule for a binary makernote with very broad acceptance rules. The maker note directory contains, in addition, a special subdir with some fields reporting about the parsing process.

key content
-------- -------
ORIGINAL the raw content of the maker note (unparsed)
SIGNATURE the first few bytes which allowed the format to be chosen
ENDIANNESS the byte order chosen during parsing
FORMAT the maker note format chosen during parsing
ERROR [optional] error details, in case of failure while parsing

Supported MakerNote formats

Maker note formats are specified in a special internal hash, with a key for each format (including the unknown format). Each format entry corresponds to an anonymous hash containing information for parsing the MakerNote; the "normal" format is considered to be an IFD-like MakerNote with a next_link pointer, offsets counted from the global TIFF header and no MakerNote internal TIFF header.

key meaning or effect
--------- -----------------
signature the MakerNote signature (a regular expression)
maker the Maker signature (i.e., its name, no regex)
tags a reference to a hash for tag translations
(A) mkntstart if set, offsets are counted from the maker note start
(B) mkntTIFF if set, offsets are counted from the internal TIFF header
(C) ignore if set, the format is to be ignored
(D) nonext if set, the maker note IFD does not have a next_link
(E) endianness if set, the byte order is fixed to this value
(F) nonIFD if set, the maker note is not IFD-like

Currently, "supported" formats are described in the following table; authoritative data is indeed kept in Tables_makernotes.pl, to which the reader should refer for tag definitions and translations. Remember that both the signature and the maker fields are regular expressions matching at the beginning (the real signature corresponds to $1).

A B C D E F Maker Signature
----------- --------- -----------------
Agfa AGFA (AGFA 00 01)
Canon Canon ()
Casio_1 CASIO ()[^Q]
Casio_2 CASIO (QVC 00{3})
Epson EPSON (EPSON 00 01 00)
Foveon FOVEON (FOVEON 00{2} 01 00)
Fujifilm x FUJIFILM (FUJIFILM 14 00{3})
HPackard x Hewlett-Packard (HP)
Kyocera x x KYOCERA (KYOCERA {12} 00{3})
Kodak B x KODAK (KDK INFO[a-zA-Z0-9]* )
Minolta_1 MINOLTA ().{10}MLT0
Minolta_2 Minolta ().{10}MLT0
Konica x Minolta|KONICA ((MLY|KC|(+M){4})| 01 00{5} 04)
Nikon_1 NIKON (Nikon 00 01 00)
Nikon_2 NIKON ()[^N]
Nikon_3 x NIKON (Nikon 00 02[ 20 00] 00{2})
Olympus OLYMPUS (OLYMP 00[ 01 02] 00)
Panasonic_1 x Panasonic (Panasonic 00{3})
Panasonic_2 x x Panasonic (MKED)
Pentax_1 x Asahi ()[^A]
Pentax_2 x x Asahi (AOC 00..)
Ricoh_1 x RICOH (Rv|Rev)
Ricoh_2 x RICOH ( 00)
Ricoh_3 RICOH ((Ricoh|RICOH) 00{3})
Sanyo SANYO (SANYO 00 01 00)
Sigma SIGMA (SIGMA 00{3} 01 00)
Sony x SONY (SONY (CAM|DSC) 00{3})
Toshiba x TOSHIBA ()
unknown x . ()

References

MakerNote format details are not usually released by vendors (well, this is an euphemism: no vendor ever, to my knowledge, released any detail on its format, exception made for Sigma/Foveon). All information used for this package was collected on the Internet (and its reliability is therefore limited) or through personal tests. Some interesting sites are (not an exhaustive list at all):

General: home.arcor.de/ahuggel/exiv2/makernote.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/makernotes.html

Agfa: www.ozhiker.com/electronics/pjmt/jpeg_info/agfa_mn.html
Canon: www.burren.cx/david/canon.html
Casio: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.dicasoft.de/casiomn.htm
Epson: www.ozhiker.com/electronics/pjmt/jpeg_info/epson_mn.html
Foveon: Foveon is the same as Sigma, see Sigma
Fujifilm: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
......: www.ozhiker.com/electronics/pjmt/jpeg_info/fujifilm_mn.html
Kyocera: www.ozhiker.com/electronics/pjmt/jpeg_info/kyocera_mn.html
Kodak: my personal tests with my Kodak DX3900 (not IFD-like)
Minolta: www.dalibor.cz/minolta/makernote.htm
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/minolta_mn.html
Nikon: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.tawbaware.com/990exif.htm
...: www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
Olympus: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/olympus_mn.html
Panasonic: www.compton.nu/panasonic.html
Pentax: www.ozhiker.com/electronics/pjmt/jpeg_info/pentax_mn.html
Ricoh: www.ozhiker.com/electronics/pjmt/jpeg_info/ricoh_mn.html
Sanyo: www.exif.org/makernotes/SanyoMakerNote.html
Sigma: www.x3f.info/technotes/FileDocs/MakerNoteDoc.html
Sony: www.ozhiker.com/electronics/pjmt/jpeg_info/sony_mn.html

DX3900 MakerNote format

Kodak MakerNotes are written in a proprietary binary format, which is not IFD-like. So, there is no way to detect the beginning, end and type of a field; everything here was inferred through a careful comparison of the content of a set of Kodak JPEG files and their shot parameters. Fields seems to be aligned on four bytes boundaries. For the DX3900 model the endianness is always fixed to big endian. The signature regular expression is "^(KDK INFO[a-zA-Z0-9]* )", the maker is KODAK. The meaning of the tags is as follows:

BYTE ??? firmware version? This is always 3
BYTE Compression 1 = normal, 2 = 2160x1440 high compression
BYTE BurstMode 0 = off, 1 = on
BYTE MacroMode 0 = normal, 1 = close-up
SHORT PixelXDimension allowed 2160x1440, 1800x1200,
SHORT PixelYDimension / values: 1536x1024, 1080x720
SHORT Year the year value, with four digits
BYTE Month the month value (in [1,12])
BYTE Day the day value (in [1,31])
BYTE Hour the hour value (in [0,23])
BYTE Minute the minute value (in [0,59])
BYTE Second the second value (in [0,59])
BYTE SubSecond (in 130th of seconds?)
SHORT ??? ???
BYTE ??? ???
BYTE ShutterMode 0 = auto, 32 = manual
BYTE MeteringMode 0 = multi-pattern, 1=centre weight., 2=centre spot
BYTE BurstSequenceIndex index in [1,8], 0 if burst mode off
SHORT FNumber 100 times the Exif F-number
LONG ExposureTime in 10^-5 seconds
SSHORT ExposureBiasValue 1000 times the exposure bias in [-2,+2 step .5]
SHORT ??? ???
LONG ???
LONG ??? is this an estimate of the subject
LONG ??? / distance? If so, it is very rough.
LONG ??? /
BYTE FocusMode 0 = auto, 2 = close, 3 = infinity
BYTE ??? always 2
SHORT ??? ???
SSHORT PanoramaMode 0 = normal, -1 = focus at infinity
SHORT SubjectDistance (x-28)*2.54+7 looks like the distance in cm
BYTE WhiteBalance 0 = normal, 1 = fluor., 2 = tungsten, 3 = daylight
(27 bytes with unknown meaning here)
BYTE FlashMode 0 = auto, 1 = on, 2 = off, 3 = red-eyes
BYTE FlashFired 0 = yes, 1 = no
SHORT ISOSpeedMode the requested speed in {100,200,400} or zero
SHORT ??? ???
SHORT TotalZoomFactor 100 times the zoom factor in [+1,+6 step 0.1]
SHORT DateTimeStampMode 0 = none, [1,6] = the six modes
SHORT ColourMode 1 = black & white, 2 = sepia, 32 = colour
SHORT DigitalZoomFactor 100 times the zoom factor in [+1,+3 step 0.1]
BYTE ??? always zero
SBYTE Sharpness 0 = standard, 1 = sharp, -1 = soft
(808 bytes with unknown meaning here, maybe a thumbnail?)

libptp2 is a library used to communicate with PTP devices like still imaging cameras or MP3 players (KODAK mc3).
You can download files or tweak camera properties using ptpcam program boundled with libptp2.
Supported Cameras
The list of cameras implementing PTP is constantly growing. Most (if not all) USB still cameras designed after 2002 are supporting PTP. Below is the list of vendors implementing PTP in their cameras:
- Kodak
- HP
- Nikon
- Canon
- Panasonic
- Olympus
- Konica
- Minolta
- Fuji
- Ricoh
- Sony
More are comming...
Please note that if your camera is supporting PTP it does not mean that it is capable of performing all PTP operations (like trigerring capture, uploading files or tweaking properties). Sony cameras are good example of poor PTP implementation where the only thing you can do is downloading files. Sony even breaks the USB specification assigning all its cameras the same product/vendor IDs so dont buy Sony if you want to stay out of problems.
Currently most PTP features are supported. Uploading/downloading files, taking pictures and setting camera properties is supported as long as your camera supports it. However there are many Vendor Extensions that are not supported.
For example Canon uses some proprietary extension operations to take pictures (entering capture mode, extending lens and so on), Nikon introduces proprietary PTP properties.
Unfortunately I have access to couple of Kodak cameras only so to help support extension features you may send me a patch or donate/lend the camera.
Enhancements:
- A number of bugs were fixed, including leaving the camera in an unpredictable state when an I/O error occurs.
- The projects own reimplementation of the old libusb interface (IOCTL_USB_BULK) is used instead of the new URB interface, which is 20% to 50% slower and sometime leads to I/O errors.
- File time preservation across download was added.
- Better capture support was added.
- A bug that caused files over 2MB to be corrupted while downloading was fixed.
- The --loop-capture feature was added.
- Configure errors and parralel build with make -j were fixed.

GNU Trueprint is a project which allows you to print source code.
Trueprint is a program for printing source code in a variety of languages (C is the best supported) and other text files to postscript printers.
It supports a wealth of options to support printing source code, such as diff-marking, line numbers, indentation levels, file and function indices, and many others.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
Enhancements:
- Trueprint now uses autoconf and automake (Paul Smith, and the book GNU Autoconf, Automake and Libtool by Gary V. Vaughan et al, published by New Riders).
- Mention of trueprint.uu removed from README (Othmar Pasteka).
- Suffix .pike added for pike programs (Othmar Pasteka).
- Added include of sys/types.h before sys/stat.h to support FreeBSD (Dmitry Sivachenko).
- README.mswin removed (John Morey).
- If there isnt an lp or lpr command on your system when you run configure, trueprint will now be built to send postscript output to stdout by default (Othmar Pasteka).
- Choice options like --landscape and --option were broken due to a serious bug in options.c (Paul Smith).
- Added Canon LBP 3260 (Bjorn Wingman).
- Added HP Laserjet 1100 (Peter Green).
- Fix for handling arithmetic<<less