It does when you set to photos and then to other in the file type. You can either do it in 2 operations or set up 2 operation lines, one for photos and one for other, both with the same destination folder.
I do this regularly when updating a backup hard drive with FP after creating raw qrs files and possibly jpeg's in Qimage.
Brian's idea to separate, in the operations table,  "Photos" into types, eg. "Raw" and "non-raw photos" seems a good suggestion to me.
Terry.

Right one can do it, but it's really not the right way of doing it. There are a couple of problems, first off, that's not expected behavior. THM and CRW files belong together, as they each have information that the other needs most software I've used treats them as one file. And second it requires a person to specifically set it up in a way which doesn't necessarily notice if only half the files are being copied.

Two cents worth more.... THM files are created in the camera as thumbnails mainly for the user to be able to see the images in the rear screen of his camera.
I have a Canon D 60 that makes THM files, and frankly, I don't want them. I delete them, since they are clutter to me.
I am very happy to be able to keep them away from the CRWs.
Qimage as well as all the other apps that I hear people use to moderate their images create their own set of thumbnail files anyway.

Seems like the perfect simple answer.
If you want the THM files from the card, you set a row with OTHER activated and the same destination folder as the CRWs.
If you don't want the THMs in there with the CRWs you don't activate the row with OTHER.

Fred

I have to disagree with you in general terms, as my other camera 20D, plus all the ones that I have tried recently within the last 4 years do not generate THM files.
Even on the old D 60, the metadata is carried in the RAW file and can be easily read.
I did some reading and found old articles written in 2003 referencing the need for the THM file; essentially pointing out that some browsers do not generate thumbnails, and use the THM for a thumbnail.
The only valid reason I could summon for the D60's need for the THM was the need to alter the metadata.
IPTC data can be written to the embedded JPG from the raw file if need be, but the THM is a tiny JPG file. 160 x 120 pixels. These were designed for viewing in the rear of the camera.

I will have to agree with you though, that a person who needs the facility to alter metadata or has a need to preserve that data in double file settings, should keep the THMs.

On the other hand, since most (can't say all. Didn't research all) cameras no longer generate any THM file, it would be a reasonable assumption that is was deemed unnecessary by the camera manufacturers.

Mike didn't leave you high and dry, though. You can still copy the THM files using the "OTHER" control and place the THMs in the same folder with your CRWs.
Simply make another ROW that is set to OTHER. The destination folder can easily be set to the same as the RAW by right clicking on the RAW destination setting and select make all destinations folders the same.
This does not alter the Drive or the main folder... so it becomes a one click deal.

Fred

Just to come back on this one:
I have a couple of CRW samples with their associated THM's so I thought I'd check the CRW's to see what is actually stored in the embedded jpeg raw file, extracted by Qimage. I use this method with my CR2 raw files when I need to copy any data to another file.
As far as I can see, using PhotoMe, Exifer and Irfanview, the data in the THM is identical to that in the embedded jpeg. Not surprising I suppose but it does show that Fred's attitude to THM files (he ignores them) is not the end of the world. As long as the CRW raw image is safe, so is the original meta data.  
Terry.