I like Parallels, even if it can be a real memory hog, but even the latest version doesn’t have very good USB support. Unfortunately, there’s a Windows application I want to use that requires good USB support. Even more unfortunately, it will never, ever run under Vista.

Why not? Because Minolta sold off their entire camera business to Sony, who has no interest in updating the remote-control software for the Dimage A2.

I don’t currently own any computers that run Windows XP, and I don’t particularly want to. But if I ever find the free time to start playing with studio lighting again, I’ll want to remote-control the A2, and with XP gradually disappearing from the market, now’s the time to figure out how.

With the latest Parallels 3.0 build, plugging the camera in while it’s in remote-control mode locks up the virtual machine.VMware Fusion not only handles the camera correctly, it seems to use about half as much memory.

[Note that there is an abandoned open-source project to decipher the Minolta protocol and write a GUI capture tool. I’m not really interested in hacking on it.]

Okay, I’m stumped. We have a ReadyNAS NV+ that holds Important Data, accessed primarily from Windows machines. Generally, it works really well, and we’ve been pretty happy with it for the last few months.

Monday, the Windows application that reads and writes the Important Data locked up on the primary user’s machine. Cryptic error messages that decrypted to “contact service for recovering your corrupted database” were seen.

Nightly backups of the device via the CIFS protocol worked fine. Reading and writing to the NAS from a Mac via CIFS worked fine. A second Windows machine equipped with the application worked fine, without any errors about corrupted data. I left the user working on that machine for the day, and did some after-hours testing that night.

The obvious conclusion was that the crufty old HP on the user’s desk was the problem (it had been moved on Friday), so I yanked it out of the way and temporarily replaced it with the other, working Windows box.

It didn’t work. I checked all the network connections, and everything looked fine. I took the working machine back to its original location, and it didn’t work any more. I took it down to the same switch as the NAS, and it didn’t work. My Mac still worked fine, though, so I used it to copy all of the Important Data from the ReadyNAS to our NetApp.

Mounting the NetApp worked fine on all machines in all locations. I can’t leave the data there long-term (in addition to being Important, it’s also Confidential), but at least we’re back in business.

I’m stumped. Right now, I’ve got a Mac and a Windows machine plugged into the same desktop gigabit switch (gigabit NICs everywhere), and the Mac copies a 50MB folder from the NAS in a few seconds, while the Windows machine gives up after a few minutes with a timeout error. The NAS reports:

smbd.log: write_data: write failure in writing to client 10.66.0.151. Error Connection reset by peer smbd.log: write_data: write failure in writing to client 10.66.0.151. Error Broken pipe

The only actual hardware problem I ever found was a loose cable in the office where the working Windows box was located.

[Update: It’s being caused by an as-yet-unidentified device on the network. Consider the results of my latest test: if I run XP under Parallels on my Mac in shared (NAT) networking mode, it works fine; in bridged mode, it fails exactly like a real Windows box. Something on the subnet is passing out bad data that Samba clients ignore but real Windows machines obey. The NetApp works because it uses licensed Microsoft networking code instead of Samba.]

[8/23 Update: A number of recommended fixes have failed to either track down the offending machine or resolve the problem. The fact that it comes and goes is more support for the “single bad host” theory, but it’s hard to diagnose when you can’t run your tools directly on the NAS.

So I reached for a bigger hammer: I grabbed one of my old Shuttles that I’ve been testing OpenBSD configurations on, threw in a second NIC, configured it as an ethernet bridge, and stuck it in front of the NAS. That gave me an invisible network tap that could see all of the traffic going to the NAS, and also the ability to filter any traffic I didn’t like.

Just for fun, the first thing I did was turn on the bridge’s “blocknonip” option, to force Windows to use TCP to connect. And the problem went away. I still need to find the naughty host, but now I can do it without angry users breathing down my neck.]

The 250GB drive for my MacBook arrived, and with two fresh backups in hand (plus a third on the old drive), I quickly installed it. It was completely painless to migrate my Mac environment over. You can do it half a dozen different way for free; I chose SuperDuper.

But I also have a Vista partition on this machine, and Vista (if you bought the right version) includes a Complete PC Restore tool that’s designed specifically for moving a complete, working installation onto a new disk… as long as you don’t mind the risk of spending half an hour on the phone reading authorization codes to someone in India to reactivate it.

The old disk had 124GB for Mac, 25GB for Vista. The new disk had 185GB for Mac, and 47GB for Vista. After finishing the Vista restore, both partitions booted correctly, so I went ahead and activated. Then I checked the free space, and found that Vista was still only using 25GB.

No problem, thought I. It’s trivial to extend an NTFS partition into the remaining free space, so I opened up the relevant tool, and found the original partition sizes, with an empty 80GB partition at the end of the disk.

fsck and chkdsk both insisted that the volumes were valid from their respective OS’s, but on the Mac side, it thought the Vista partition had a lot less files in it than it should have. Not good. Very, very not good.

Not being an idiot, I started over, rebuilding the disk from scratch again. Since it’s a Mac, I just booted the old drive from an external FireWire enclosure and ran SuperDuper again. This time, though, I didn’t bother using the Vista restore tool; I just dd’d the old partition over and ran the repair tools from the install CD. I still need to do an upgrade install to clean up the boot files, resize the filesystem to fill the new partition, and then reactivate again, but it should work this time.

There’s actually a checkbox in the Vista Restore process that theoretically allows you to restore onto an existing partition without trashing your new disk, but it was grayed out, and clumsily worded. Net result: one of the features you pay extra for in certain Vista versions is not only useless, but dangerous.

In a rare example of good sense, though, you can get at all of the data in the backup; it’s a disk image in VHD format.

My friends keep whining about certain behaviors in Apple’s Mail.app. Specifically, the inept way it wraps URLs in allegedly plaintext email, which simply don’t work in most other mailers. I can’t really defend its behavior, because I think that Mail.app’s concept of “plain text” is pure shit and violently anti-WYSIWYG, obviously only tested against itself. [note: don’t bother complaining to Apple, the bug will be closed with “working as intended”]

Claws Mail seems to be much more sensible, and at this point I’d cheerfully send some cash to support a native port to Mac OS X. The X11 port works, but it’s a bit clumsy to use (especially for Japanese; Apple’s X11 server doesn’t support their own Kotoeri input method, so you have to use an external editor), and like virtually all Open Source applications, it’s in desperate need of user interface design. I need to poke around some more and see how it handles some of the features I rely on in Mail.app (particularly SpamSieve), but the initial experience is pretty good, and it sends honest-to-gosh plain text.

There’s a native Windows port available, but it hasn’t been updated in quite a while (2.4, current is 2.10).

[Update: Tip for the day: don’t open an IMAP folder containing 17,167 messages. Claws locks up until it finishes downloading and processing all of their headers, and then (at least on Mac OS X) the X server locks up for a few minutes when you try to scroll through the massive message list too quickly.

Mind you, until today I didn’t know that I had an IMAP folder with 17,167 messages in it (it was a trash folder full of spam, on a server I’d only been reading via POP), so I really can’t blame Claws Mail for being a bit overwhelmed. And to its credit, it recovered perfectly when the X server came back, and the memory footprint was still nice and lean.

It doesn’t look like the Mac port includes any plugins right now, so I need to keep something else around to handle spam. The account I most want to get mail from is of course the one with the most spam, so I need to continue processing it through SpamSieve for now. Most likely, what I’ll do is leave Mail.app running with SpamSieve on one of my machines, but turn off all of the other filtering rules and port those to Claws.]

Whether I try to upgrade some of my music to the new iTunes Plus format, or buy something new, I just get this:

It can wait.

[update: I can’t buy anything at all; my account is now thoroughly confused in their database.]

[update: okay, it took a week, but they figured out which Dean Martin album shouldn’t have been trying to upgrade to iTunes Plus, and with that out of the way, I could determine that the season pass for The Dresden Files (not as good as the books, but not bad) was also broken]

While browsing the newly-updated iTunes store, I stumbled across the following podcast: 女の子の写真スライドショー/Japanese Cute Girl Slide Show. It’s exactly what it sounds like.

Of course, you could download the same photos at higher resolution from someplace like Zorpia, and you wouldn’t be limited to this person’s taste in music and girls. But then it wouldn’t auto-download a new one to your iPod every week, which I guess counts as a feature.

There’s a set of sample images over on No, Dave, it’s just you that, in theory, will help you determine if your Apple laptop display has 24-bit or 18-bit color. I can detect no banding in the 24-bit image, so I must have one of the (allegedly few) good MacBooks, right?

Wrong. Before trying this test, I used SwitchResX to determine that my MacBook has an AU Optronics B133EW01, which is definitely an 18-bit display.

I suspect that all Apple (and most other) laptops have 18-bit displays, and the real news here is that Apple bought some lemons.

Thanks for pretending that I eagerly signed up to get email about the iPhone. This is, of course, a lie.

From: News@InsideApple.Apple.com
Subject: Thank you for your interest in iPhone.
Date: May 16, 2007 3:06:48 PM PDT

Talk to you soon.

Thanks for signing up. You'll be the first to hear the latest about iPhone--coming this June. That gives you just enough time to think of ways to break the news to your current phone.

...