astradele

The Siemens S40 and the Sony Ericsson T630 (which differs from the T637 only in GSM 850/900) have in common another characteristic other than being my latest two phones. They both come with synchronization software called XTNDConnect PC. Different versions, specific to each phone.

Now, I don’t know what the commercial version of that software is like, but the versions I used with the S40 and T630 are pretty finnicky.

1. You have to make sure you run the installation program as the user you intend to sync the phone with (so it picks the right Outlook data file). The program will need write access to files in C:\Program Files\Common\XCPCSync. Not well behaved multi-user or minimum-rights (i.e. non-admin users) behaviour, but this is okay with most people I’m sure.
2. It really doesn’t like being installed atop another version (or the same). This is a problem for many people, I’m sure. I think most people install new versions of software atop old ones. I know I did when changing from the S40 to T630. Always uninstall old versions of XTNDConnect before installing a new version.

#2 runs contrary to typical user behaviour (I believe), and uninstallers are known to become broken over time anyway. The bad thing about #2 is that it’s hard to determine what’s wrong once you do what #2 says not to. The error messages for XTNDConnect PC are terrible; they tend to be the same one for a variety of problems.

When I converted from my S40 to T630, I was a bad boy. Even when I uninstalled the old S40 software afterwards, the T630 version still wouldn’t install and run properly. As it turned out, the XTND version for the S40 left registry entries, and the the T630 version of XTND noticed them and silently did not replace and add to them as it should have. Had to uninstall everything, delete the registry, delete the two key directories (Program Files\XTNDConnect PC and Common Files\XCPCSync), and install the T630 software again.

And today’s event was the use of task manager to kill XTNDConnect after a snafu relating to Outlook and fighting for access with my Pocket PC (I think). Bad idea. Subsequent attempts to start XTNDConnect gave me “sync engine is already logged in for a different client”. Useful. I started looking for lock files. As it turned out, reading the help file reminded me there was a log file, and reading the log file told me one of my data files was corrupted. Oops. Although, what does this have to do with another user being logged in? Oh well. So I run the installer for the T630 XTNDConnect PC software again.

Wait, wasn’t there something about always uninstalling first?

So the installer failed to make the necessary modifications, seeing something there already and deciding to silently play it safe. XTNDConnect’s behaviour wouldn’t be so troublesome if it weren’t so tight-lipped. However, after uninstalling, and making sure the directories were pretty clean, it installed properly, and yes, actually works again.

Really… not the kind of program you want to be on the wrong side of.

Unix users know the value of symbolic links. Interestingly, the same sort of behaviour is available on Windows (NT, 2000, and up), although I believe they’re called “reparse points” and are quite different in the details. SysInternals’ Junction lets you create and manage them.

I use them mostly for two reasons:

• The directory I often want is buried somewhere obscure. This happens with my PDA’s mirrored directories, which end up in c:\Documents and Settings\username\My Documents\PDAname\My Documents. I point “C:\PPC” (Pocket PC) to that long mess, and when i put files in C:\PPC, I’m really putting stuff in that first directory. It’s like shorthand.
• Sometimes an application file dialog pops up and shows you the special “My Documents” folder (no leading prefix of directories). I find that folder annoying, since the Up arrow doesn’t really do anything from there. I know what directory it’s showing me, and I want to go up one further, but I can’t. The drop down list at the top often pauses when you click on it, as it checks \network drives and similar activities. So I create a junction in “C:\Documents and Settings\username\My Documents” that points to the directory I want. Don’t have to navigate any folders or fight Windows Explorer because it treates “My Documents” as a special folder that has no parent (even though it does).