Windows Photo Gallery stores tag information directly in the files you are tagging, when possible. For instance, when tagging JPEG files, the tags are stored in the JPEGs using XMP. Also, if you modify other information about the files (such as the date/time a photo was taken), that information is stored in the file if possible.

In some cases, the information cannot be stored in the file itself; for instance, if the file is marked “read only,” or if the file format does not support metadata (PNG, AVI, etc.). In this case, Windows Photo Gallery still allows you to do anything you could to a file that it could store the information in, only, it stores the information in its own little private database. This is transparent to the user.

If you want to move your “gallery” to a different machine, and your gallery consists only of JPEG images, you can probably just copy them all to the new machine, and Windows Photo Gallery will automatically index them and rebuild its list of tags. However, if you have other types of files in your gallery, the information will not be carried along with these files and you’ll have to re-tag them. Ugh.

I’ve been looking into migrating the Windows Photo Gallery database. There doesn’t seem to be any supported way to do this (someone please correct me if I’m wrong).

The database itself is easy to find — it is the Pictures.pd4 file, found in AppData\Local\Microsoft\Windows Photo Gallery in your Windows profile folder. So, to migrate the database, it should be as simple as moving this file to the new machine, and making sure that the paths to all of the files in your gallery remain the same, right?

Well, after trying this and running Windows Photo Gallery, we come up with a curious dialog box.

Note that the folder it is complaining about is actually present on the machine.

Here, you have some options. If you click on “Find the folder,” and browse for it, you might end up with a duplicate of every file appearing in your gallery (and the folder is listed under “Folders” on the left twice, with no way to remove either of them). If you click on “Remove the folder,” all of the files in your gallery disappear, and your tag information is lost (even if you manually add the folder back). And if you click on “Cancel,” everything works great, all of the files appear and all of the tag information appears to have been migrated succesfully… Except, this dialog reappears every time you run Windows Photo Gallery.

In trying to figure out a way to either migrate the information without causing this dialog to appear, or to figure out why Windows Photo Gallery doesn’t seem to like the Pictures folder even though it has the same path as before, I set up two identical galleries on two separate machines and compared their Pictures.pd4 files. Skipping a lot of the details, I did eventually stumble on the key difference.

Windows Photo Gallery is checking your volume information (volume label and serial number) and storing it in its database; it is then using this to verify that the files are on the same drive that they were before. If you move the database to a different machine, the volume serial number is not the same, so it throws up the error we saw above. You can’t just edit the volume serial number in the Pictures.pd4 file to match the new one, though, Windows Photo Gallery is able to detect that the file has been tampered with (you’d have to go fix some other checksum stuff to get that to work). The easiest thing to do is just to change the volume serial number on your “destination” machine to match the one of the “source” machine. You can do that with this SysInternals utility, VolumeID.

So, migrating your Windows Photo Gallery database, step-by-step:

• Copy all of the files in your gallery to the new machine. Make sure the path to them remains the same as it was on the old machine.
• Copy the Pictures.pd4 file to the new machine.
• Change the volume ID of the C: drive (and any other drives with folders indexed by Windows Photo Gallery) on the new machine to be the same as on the old machine, using VolumeID. (Reboot for the changes to be visible, before running Windows Photo Gallery.)

Note that Windows Live Photo Gallery can be migrated similarly.

Searching around online, I was unable to quickly find any place to download the software, or any kind of support page for this device. In light of this, I made a .iso image of the CD that came with it and I am posting it here in case anyone needs it. Here is a picture of the device for comparison with your device (to know if this is the software you need):

Download version 2.3 of the software (1.92 MB, Windows and Mac OS X software included in the image).  This is an ISO image of the CD that came with the device, and needs to be mounted or burned to a CD for you to be able to access the software.

I’m a long-time user of Paint Shop Pro. Or rather, I was. I remember finding a trial version of Paint Shop Pro 3 on my dad’s Windows 3.x office computer back around 1996-7 (as a sixth grader), and I was just getting into Internet stuff around that time, and what I hadn’t found yet was a program that could manipulate and convert between many different image types, specifically those that are used by web browsers (GIF/JPEG). I mean, all I really knew about back then was Microsoft Paint. (Sheesh, was that really only ten years ago?)

Anyway, this particular trial program was one of those that lets you keep using it even if you are well beyond the trial period (“You are on day 498 of your 30 day trial…”). It was a fantastic program, so I just kept on using it. I moved to the trial version of Paint Shop Pro 4, but it really kicked me off after 60 days (30 day trial plus a 30 day grace period), so I continued to use beta versions and other trials, falling back to Paint Shop Pro 3 (with the really annoying 16-bit Windows 8.3 filename limit) when nothing else was available, until I actually got a full version of Paint Shop Pro 6 in 1999.

I continued to upgrade with each release over the years, and I was pretty happy with it for a while yet, but it seemed like the quality started to go down (slowly) starting around Paint Shop Pro 9 in 2004. This was even more apparent after Corel bought Jasc, and I had to jump ship with Paint Shop Pro Photo XI, which was, in my opinion, a disaster (at least at its first release).

The biggest complaint I had about PSPXI was its photo “Organizer” feature. I have a lot of pictures, and PSPXI took it upon itself at first launch to start crawling through them and generating thumbnails. It continued doing this even even if the organizer was hidden, and excluding folders for it to catalog in the options didn’t seem to stop it. This caused a lot of hard drive trashing and CPU usage which made my machine, let alone PSPXI itself, quite useless. Even after going through other measures to disable it, PSPXI would bounce around between, say, 2% and 8% CPU usage if I had the program open, with no images open, not doing anything with it. What is it doing with the CPU when there is nothing for it to be doing? I don’t have any other programs that behave like this, so I’m really sorry but I’m afraid that I’m going to have to call it poorly-written software. I was able to reproduce this on every machine that I installed the software on, and I brought this issue to Corel and never received any useful response.

Anyway, the main complaint of my article here is software bloat in general. To continue my example, what did I originally start using Paint Shop Pro for, and what am I looking for in an image editor? I’m not a graphics artist or anything, so I’d say something like…

• Basic image editing capabilities
• Image mark-up (drawing rectangles or arrows to highlight things)
• Conversion between different image types
• Cropping / resizing images
• Simple effects
• Support for gradients, alpha transparency, and layers is a plus

Paint Shop Pro used to be a program that satisfied this quite nicely, without being way above my budget (like Photoshop). But for some reason, Corel wanted to expand the capabilities of the program and make it a full photo catalog application like Picasa or Microsoft Digital Image Suite, and force it on my just because I use Paint Shop Pro. (Not to mention the fact that they didn’t do a very good job with it.) If they had kept it properly componetized (just give me the option to not install or properly disable the “organizer”) and not broken the software, then I might have continued buying upgrades for years to come, but alas, I found myself searching for an alternative.

Free software has come a long way, and after trying The GIMP and dumping it (it’s a nice application, but seriously, how come I can’t just draw a rectangle?), I ended up settling on Paint.NET, which is, I must say, quite fantastic since version 3.0 added the MDI (actually, TDI). Pretty must anything I did in Paint Shop Pro can be done in Paint.NET, it comes with a number of nice effects that allow even non-artistic people like me to come up with some cool-looking pictures, and it’s very simply laid out and easy to use (just had to learn a few new keyboard shortcuts), not to mention the fact that it is free and the source code is available. Also, I like to see that the software I use is actively being improved and developed further; Paint Shop Pro hasn’t changed very much in years, and the upgrades have become perhaps worth less than you have to pay for them.

Anyway, this is just one example of fantastic software going astray. There are several others that I have observed lately (for instance, Nero used to be a favorite of lots of people but there are many more complaints about it now; another example may be some of the “Norton” branded products from Symantec). I’m not sure what it is, because some big programs continue on gaining only new useful functionality and ease of use (Microsoft Office, Photoshop), and yet some try to be too big and throw new functionality at you without you asking for it (Paint Shop Pro photo organizer, Nero Scout). This seems to be what really separates professional software from software that is trying to be more than it should be, a “jack of all trades but a master of none” so to speak. And of course, only big companies like Corel can make this mistake and still go along fine.

Not that I expect this to really accomplish anything, but to continue yelling from my soapbox here, if you were developing software, you should keep things like this in mind. In a large software program or package, components should be able to be added and removed and the programs should still work, and don’t create a worse experience for users who are used to using older versions of the product. New version should contain new functionality that ties in to the original purpose of the application; if you want to turn your image editor into a photo catalog, release a separate product, clarify the difference, and bundle it with your old one if you want but don’t force it on people.

(Paint Shop Pro Photo X2 was released last week. I tried it, and it’s a big improvement over XI, which itself improved as Corel released some patches for it over the last year. But I’ve already moved and I don’t really have any intention of moving back, especially when these upgrades are so incremental that I can’t really justify spending the $60 to upgrade. Also, there is still the issue of unexplained CPU usage when the program is idle, though it is certainly less than it was in XI.)

Now, I’m sure you had something better to do with your last ten minutes than sit around reading my rant. Go off and do something useful, will you!