Unable to delete messages - a Mail.app 3.0 bug

There's a bug (surprise!) that hits a few Mail.app users when they upgrade from OS X 10.4 to 10.5.

I just ran into it upgrading my mother's ultra-plain Mac Mini from 10.4.11 to 10.5.2 and then directly to 10.5.7.

I did an update in place, not an archive and install. I didn't run Mail until the machine was at 10.5.7 and had gone through a post-update "safe boot" cycle to clean out old caches and debris. So I was surprised to find a very significant bug!

When I tried to delete an email from Mail.app 3.0 I got this error message:

The destination mailbox “Deleted Messages ... " does not allow messages to be moved to it.

I found several posts on this topic, but they were all IMAP configurations. The associated fixes in those posts didn't work.

My mother's mail uses POP against her Gmail account, this 2008 post by "Davl" had the fix:

In finder I opened the folder containing the mailbox folders of my POP account. It was located at:

My User Home Folder --> Library --> Mail --> POP/account name --> additional POP folder

In this folder were the mailboxes folders with .mbox extensions.

• Deleted Messages --> empty
• Drafts.mbox --> Messages
• INBOX.mbox --> Messages
• Sent Messages.mbox --> Messages

Note my Deleted Messages doesn't have a .mbox extension like the others do...

This is what I found  in icon view. Clearly there's something wrong with Deleted Message!

Yech.

This is what I did after confirming my Gmail POP settings were correct.

• In Mail.app I saw some "child" trash items. I deleted those and emptied the Trash.
• I quite Mail.app and moved the "Deleted Messages" folder to the desktop
• I restarted Mail. app and then deleted a message. The Deleted Messages folder was recreated

This bug goes back over a year, so it's disappointing that even in 10.5.7 Apple hasn't fixed it.

OS X internet bridging is WEP only

My parents don't have a wireless LAN at the moment, so I turned on Mac OS X 10.5 Internet connection sharing on my mother's Mac Mini. This is a bridging connection; it links my wireless clients with the household wired cable modem connection.

It works pretty well in their house -- I can work with my laptop and iPhone as needed. If you want to do mail, etc though you either have to turn off the firewall on the Mini or mess with ports.

There's one oddity -- unchanged from 10.4. When you set up "connection sharing" (bridging) the only available encryption is WEP (!). This is slightly better than nothing, but not much better; it's now trivial to hack WEP encryption. WEP also a pain to configure on a PC.

So why just WEP? Seems out of place, esp in 10.5.

Update 5/29/09: It's not only old-fashioned, it's also flaky -- like a LOT of things in 10.5. I find I have to periodically toggle it off and on again on the Mac Mini to get it working.

OS X 10.5.7 has a wireless problem?

We're on the latest round of OS X (10.5.7) and Airport Extreme (old, flying saucer model) fixes and something's gone downhill

No real mention on Google, so it's probably something with our older setup (Airport Extreme saucer station, Airport Express WiFi extender, 802.11g/b).

What we see is my MacBook on awake from sleep takes a while to get a connection, then it loses it, then it gets a lower power connection (maybe one of the stations) then it gets a full power connection.

Not lethal, but very annoying.

Update 6/7/09: I think I've found the problem.

Blank an iMac display - instantly (Leopard only?)

For years I've wanted to be able to turn my iMac display off on demand. There's no on/off switch of course, that would hurt the vibe.

It's a common desire. I need my iMac running at night so it gets backed up, but I don't want the photo show ("screensaver") running all night. On the other hand, I do like to have it run when I'm around. Problem is, nobody knew how to do this two years ago.

The best solution I found then was one of the elegant "dockables", which have been recently revived and updated (get the whole set!). The screen off dockable was quite good, but it had a few drawbacks. It couldn't be activated when the screen was locked, but when activated it left the screen unlocked. That's a problem with my kids.

Tonight, on a whim, I looked for current solution, and found How to turn off the iMac display | eHow.com.

Control-Shift-Eject. Presto, the screen is dark. It even works on a locked screen running my slideshow. (Control-Eject brings up the shutdown menu.)

WTF?! Why couldn't I turn this up two years ago? It's trivial to discover today. Was it some secret addition to an OS release? Was it always there, but only discovered a year or two ago?

The answer appears to be Yes and No. It's new to 10.5 (Leopard) and it's never been officially documented by Apple.

It doesn't appear in this 2006 article on similar shortcuts and it doesn't work on my old 10.3.9 iBook. It really only gets mentioned after Leopard is out.

Sigh.

On the one hand, a great feature. On the other hand, would it kill Apple to document it? It doesn't appear on Apple's recently updated screen shortcut kb article.

For me it justifies almost 10% of Leopard's purchase price. Hell of a way to run a company!

Following the trail leads to some other obscure Mac tips:

• Ctrl-K and Ctrl-Y will cut and copy text -- independently of Cmd-X and Cmd-Y. A separate clipboard.
• Option - Command - Eject: sleep computer (I knew that one)
• Many obscure Leopard tips

See also: Command-Option-Control-8 for reading in a dark room.

Why are all my Windows 2003 server folders read-only with a gray checkbox?

In the midst of a Kafkaesque episode of IT torture, I realized that all of my Windows 2003 server folders on every drive had a grayed-out (greyed-out) checkbox in the read-only attribute. The value of the checkbox could not be changed. (That is, it appears that it can be cleared, but on review it's set again. This is true even if one requests that changes propagate down the tree.)

In theory this means that somewhere in the tree of child folders there exists a read-only folder.

Was this related to the mind-crumbling miseries of my past week of IT hell?

Probably not, but the truth is dark enough. Microsoft has a kb article on this. I've cleaned it up, the original is poorly written. Emphases mine ...

You cannot view or change the Read-only or the System attributes of folders in Windows Server 2003, in Windows XP, or in Windows Vista

... Unlike the Read-only attribute for a file, the Read-only attribute for a folder is typically ignored by Windows ... you can delete, rename, and change a folder with the Read-only attribute by using Windows Explorer.

The Read-only and System attributes are only used by Windows Explorer to determine whether the folder is a special folder, such as a system folder that has its view customized by Windows (for example, My Documents, Favorites, Fonts, Downloaded Program Files), or a folder that you customized by using the Customize tab of the folder's Properties dialog box.

As a result, Windows Explorer does not allow you to view or change the Read-only or System attributes of folders.

When a folder has the Read-Only attribute set it causes Explorer to request the Desktop.ini of that folder to see if any special folder settings need to be set.

... if a network share that has a large amount of folders set to Read-only, it can cause Explorer to take longer than expected to render the contents of that share while it waits on the retrieval of the Desktop.ini files. The slower the network connectivity to the share the longer this process can take to the point where Explorer may timeout waiting for the data and render nothing or appear to hang.

Let's walk backwards to appreciate the horror of what Microsoft did here.

Suppose you want to display NTFS metadata like a file's name or comments in an Explorer view. This is a handy way to do what, millennia ago, we did using things like PC Magazine's dirnotes.com utility. Well, it's easy to enter that data, but how does Windows know to display it.

Ahh, here's where the horror of the hack sets in.

The metadata directions are stored in Desktop.ini files for each folder. It would be slow, however, for Windows to check that file every time an Explorer view is to be shown. So Windows 2003 needs to know when to check.

Cue dramatic music.

Some poor benighted soul realized that Windows (95? 98? NT? 2000?) doesn't use the read-only attribute for much. So he (must have been) had a brilliant idea. He'd hijack that attribute, and use it as a way to tell Windows that it needed to check the Desktop.ini file.

We know how the play unfolds now. Once this data value had been used this way the meaning changed. The text says "read-only" but the meaning is "look at the desktop.ini file".

We call that semantic drift.

Of course there's no reason for an attribute that really means "look at desktop.ini" to change the UI for a parent folder attribute of the same name, but that was inherited from the original use of the folder "read-only" attribute. It's a hack side-effect.

Finally, since "read-only" now meant "look at desktop.ini" it had to be reserved for system use, so Windows Explorer can no longer change that attribute. Of course attrib. exe can still change it, but probably you don't want to -- you're really telling Windows then to "ignore desktop.ini".

The Horror, The Horror.

Ping.FM: a router for status updates ... with just one small problem.

There are some disadvantages to being a mid-western geek of a certain entropic state.

If something doesn't show up in my Feed stream, I don't hear of it from my peers.

Take Ping.FM - for example. It's not new, but a GR search shows none of my sources called it out (but they did mention it -- with the assumption that any reader would know what they meant).

I found mention of it in a corporate blog I track at work ...

lbenitez . Luis Benitez . Socialize Me 

"... Ping.fm allows users to update their status in the following services from any of the following clients...".

So Ping.fm will update my status on LinkedIn, Facebook and Twitter. Great! Just what I've been looking for.

Except ...

Ping.fm needs my username and password for each of these accounts.

Riiigggghhhht.

Ok, that's a FAIL.

Maybe that's why no-one I read is keen on Ping.FM.

I'll check back if they're able to implement on OpenID mutual authentication framework.

Update 9/14/10: A relevant xkcd comic.

Address book Google synchronization weirdness

Now this is really weird.

Here are the OS X Address Book "General Preferences" on my 10.5.7 MacBook (where I sync my iPhone):

And here are the same settings on my 10.5.6 iMac

Right. The 10.5.6 iMac has an option called "Synchronize with Google".

How the #$! did that get there? Why doesn't the MacBook have this option? (By the way, Google Apps Exchange Sync still doesn't work in 10.5.7).

Lifehacker has the answer. Turns out this is quite old (I even sort of remember reading about it):

Mac OS X Leopard only: Today's release of Mac OS 10.5.3 added a juicy little tidbit to Address Book: the ability to automatically sync your Google contacts. After you've run Software Update and gotten 10.5.3 (and restarted your Mac), hit up Address Book's Preferences pane. At the button of the General tab, check off the "Synchronize with Google" box to get started. Be sure to back up your address book before you sync, and see the FAQ for more info. Update: Several commenters rightly point out that this capability only exists for iPhone and iPod touch owners by default, which is quite possibly a crappier move than forcing Safari onto Windows users on Apple's part. Time to switch to Linux. Update #2: Only a few hours later, a workaround surfaces. Non-iPhone/iPod touch owners, here's how to enable Google Contact sync.

Alas, I read through the comments on the hack to enable Google Contact sync without an iPhone/iTouch and it sounds problematic.

Based on a similar story with Exchange Sync this feels like a side-effect of iPhone synchronization. It's obviously disappointing that none of this stuff improved with 10.5.7. I'll take a look at the Google sync, fortunately it's easy to restore contacts. I'll just make sure I turn off MobileMe sync before I experiment.

Plaxo - just not a good feeling

An informed comment on my latest Project Contacts windmill tilt led me to take another look at Plaxo. I ended up deciding to wait and see what happens elsewhere over the next few months.

Plaxo launched about 6-8 years ago, and had a very nasty reputation for quasi-spyware behavior about 4-5 years ago. They've cleaned up their act and since been acquired by Comcast.

Nowadays they're sort of a cross between LinkedIn and Facebook -- leaning more to the former. Their secret sauce is contact synchronization across Outlook, OS X Address Book, and some phones. It sounds like that's reasonably robust. They also provide some calendaring services, but there's no support for CalDAV, calendar subscription, feeds, etc. It's all proprietary. Their only outward link is to Facebook, and you can share status updates with FB (so a Tweet can go to FB and then to Plaxo).

They can authenticate with a Gmail or OpenID account -- so I didn't need a new un/pw to try them. Based on my Gmail address they suggested links to everyone who has that address in their Plaxo Contacts -- which turned out to be a lot of people I know.

So what turned me off for now?

1. It's really unclear how they make money. Their premium services are pretty mediocre. I know how LinkedIn, Google and Facebook make money.
2. The complete lack of standards support (ICS, CalDAV, Feeds, vCal, etc).
3. No clear way to subscribe to calendars, just their sync.
4. All their sync and import/export require that they get my Google un and password!! Huh? In Jeff Atwood's words, that's a total FAIL. I'd sooner give them my DNA.
5. The stuff I care about seems to be an increasingly distant second thought to their Facebook-play.
6. They are incredibly obnoxious and persistent about trying to get me to give them access to my Gmail and other accounts and the rights to invite everyone in those accounts to Plaxo using my name.

So I'll give this one a pass for now. Let's see if Google gets their Contacts act together in the next few months -- even if that means I have to shell out for a year of Apple's sub-mediocre MobileMe while the smoke clears.

Update: Faheem responds in comments. He avoids all the Google and other password issues, strictly deals with iCal and Outlook and Address Book sync. He avoids all the social stuff and Plaxo arm twisting and just concentrates on Contact sync. He sure is persuasive; I'm convinced he knows this turf at least as well as I do.

Blogger editing madness

Switching between editing posts using Windows Live Writer, Blogger in Draft with Safari 4, and Blogger draft/standard using Firefox 3.x leads, sooner or later, to bizarre line space problems.

Not to mention applying blockquote operators to Blogger in Draft text with Safari causes new space doubling.

I fear it's all tied up in the ancient wars between unix, mac and dos (yes, DOS) around CR, LF and CR/LF pairs.

Interestingly IE 8 behaves like Safari 4, so Firefox may be a bad actor.

Update: It's worse than I'd thought. I wonder if Google is screwing this up again, I remember a period about a year ago when the line spacing behavior went berserk.

Update 5/23/09: I've experimented further. It's fubared. I have learned that if one uses the rich text "remove formatting" tool the formatting becomes more predictable. It's the interaction between source text formatting and the rich text editor that makes things really messy. I wonder if Google is giving up on blogger.

Project Contacts: Now mixing Outlook/Exchange, PST file, Outlook/Home, MobileMe Sync, OS X Address Book and the iPhone.

A recent Apple Discussion Thread led me to take a new direction with Project Contacts.

To put it mildly, there’s a lot of complexity in this post. However initial results are very positive. This method will require me to purchase a MobileMe account, something I was hoping to avoid. (See below for a partial index to past efforts.)

The end result is that I have a single collection of work/home contacts across iPhone and OS X Address book at home. The work contacts portion of this collection is updated weekly. At this time the update is one way, from Work to Home.

For anyone who may be facing these challenges, I have provided a skeletal outline here of what I did and what I would do if starting from scratch. You will see how insanely complex this is. Note that as of this writing the care PIM data that was once in Palm/Desktop is now scattered across Google (Calendar and a detached set of Contacts), Outlook/corporate, Toodledo and MobileMe. Everything does come together in my iPhone. The current solution involves a wide variety of vendors. For example, Apple's MobileMe calendaring is pathetic; far weaker than Google Calendar and a joke compared to Outlook (which makes Apple's no-show on tasks even more crazy). On the other hand Apple's Contact framework is very robust, much stronger than Google and a rival to Outlook.

This ruddy mess is a real indictment of Apple and a fat opportunity for the PalmPre.

So much for prelude. Here’s the outline, strictly for the uber-geek:

Here’s what I actually did:

• Copying contacts from Outlook/Exchange root to Outlook PST caused the EX (Exchange server x.500) email addresses to be updated to SMTP (standard internet) email addresses.
• PST on thumb drive to home (simple)
• Copy into Home Contacts
• Sync to MobileMe
• In MobileMe web assign all to a Group
• Sync to OS X Address Book (small conflicts)
• Sync to iPhone (ok)
• Sync to Outlook Home: Each Group in OS X Address Book became a Contacts Subfolder in Office 2003. This means the cardinality relationship to Address to Group may have to be One to One.

Expected problem:

• Contact belongs to two Groups in OS X Address Book (multiple inheritance)
• Contact assigned to ONE Subfolder in Office 2003.
• In OS X change Group assignments.
• What happens in Outlook?

Here’s what I suggest doing (LOTS of backups of OS X Address Book as go along)

1. Outlook/Corporate create PST file, copy work contacts. Do not copy lists or groups of contacts, only contacts.
   
2. PST file to thumb drive
3. Home Outlook mount PST data file. Make sure Contacts folder is empty
4. Sync iPhone to OS X Address Book
5. Create new group in OS X Address Book that will hold corporate contacts
6. Sync to fresh MobileMe Account
7. Sync fresh MobileMe account to home Outlook
8. Now Outlook will have an empty subfolder. Dump the Contacts transported into the PST file into that empty folder.
9. Sync from Outlook to MobileMe
10. Sync from MobileMe to OS X Address Book
11. Sync to iPhone

A partial index to past and related efforts at work/home Contact integration:

• Synchronization (all)
• MobileMe (all)
• Outlook (all)
• Contacts (all)
• Synchronization is Hell.
• Root causes: Why you can't sync your work and home calendars to your phone
• Project Contacts: Integration across iPhone, Google and whatever
• Work home contact integration: Outlook to Google to OS X Address Book (X.500 EX email problem)
• Synchronization case study: Address Book, the iPhone, and Google Contacts
• iPhone sync to Google contacts - 3 methods and work/home implications
• Outlook contacts to OS X Address Book - 3 techniques
• Google saves my iPhone (Google Exchange Server emulation for iPhone)
• Googaby: Novel approach to Google Contacts and OS X Address Book integration
• OS X Address Book to Google Apps Contacs using Google ActiveSync
• Work home contact integration: Outlook to Google to OS X Address Book
• Access OS X Address Book records using OpenOffice database?
• Synchronizing iPhone and Gmail contacts: getting OS X Address Book into Gmail
• gSyncit vs Google Calendar Sync with Outlook 2007
• gSyncit for Outlook 2007 to Google Calendar and Contacts Sync
• Prediction: We won’t see a fixed MobileMe until 10.6 is out
• MobileMe alternatives – including for iPhone Sync (MacWorld)
• Palm Pre is Exchange sync based
• iPhone: MobileMe vs. Google services
• MobileMe, Microsoft Outlook, Exchange, iTunes and yes, sync Hell
• Is it too late to go back to Palm 1994?
• Palm to iPhone - the update
• Synchronization is hard - more evidence
• Palm to iPhone migration - address book and notes
• Spanning Sync tells us what's wrong with Google's free CalDAV sync
• Apple can't do synchronization - again
• MobileMe syncs with Outlook (but then Apple turned it off for Exchange clients)
• Interoperability and my Contact information: Microsoft Outlook and Access, FileMaker Pro and Palm Contacts

Update 5/15/09: Now that I've got this working I'm trying various optimizations. For example, my contacts don't change that often. It's easy to create a view in Outlook that sorts by modified date. It's fairly trivial to send out a few changed .msg in an email and let Outlook at home merge them in. I still have to think about how to work with Google's Contacts, but I'm seeing a few interesting options.

It's weird how powerful MobileMe contacts are, yet how feeble MobileMe calendaring is. We're due for a MobileMe relauch, so I expect some developments before September.

Lastly, I should probably mention why I took this route. The more I looked at the workarounds for getting Outlook/Exchange corporate contact data to Google or the OS X Address Book the worse they looked. Their are problems with data models, problems with the intractable horror of the Outlook Add-In architecture, problems with Exchange server and problems with corporate access. This approach is crude, but for me, once I figure it out, fairly painless. I think it will fly until we get something better.

In the meantime, I'm rooting for the PalmPre to humiliate Apple and make them reconsider the direction they're taking.

Update 5/15/09b: Now that I've got this setup working I can see weird new affordances. For example, one of my top 10 OS X frustrations is the inability of FileMaker to work with the Address Book SQLite data stores. Ahh, but now my address data is synchronized between Outlook/Home and Address Book, and I can use Microsoft Access with Outlook/Home. So I can clean things up there, and MobileMe sync will propagate my fixes. I think I'll find a way now to get my Google Contacts into the battlefront.

Update 5/16/09: Great comment by Faheem, who's achieved a similar outcome using Plaxo without paying for MobileMe. I took a look, but Plaxo didn't feel right for me.

Outlook contacts to OS X Address Book - 3 techniques

In 2006 MacWorld outlined 3 ways to move Outlook contacts to OS X Address Book. It's rather annoying that Microsoft doesn't provide a standards-compliant export from Outlook; they're usually a bit better about data mobility of this sort.

Outlook contacts to Address Book | Root | Mac 911 | Macworld

... Under Outlook 2002 you could simply open your contacts and drag them to the desktop to turn them into vCards. No longer. Try this and the contacts are converted to messages.

While you can select a single Outlook contact, choose File -> Save As and, in the resulting dialog box, choose vCard Files from the Save as Type pop-up menu, this works only for individual contacts—you can’t export a group of contacts this way.

You have a few options for eventually getting the things out of Outlook. The first is to select all your contacts and choose Action -> Forward as vCard. Outlook will create a new email message that contains all your contacts as individual vCard attachments. Send this message to yourself, pick it up on the Mac, drag these files into Address Book or Entourage’s Address Book and you’re good to go.

Or Sperry Software can lend a hand with its $20 vCard Converter Add-in for Microsoft Outlook. This adds a service that enables Outlook to export all your contacts as a single vCard. (Yes, it’s galling that OS X’s Address Book lets you do this for free.)

Or you can use a go-between application to get the contacts out of Outlook and into an application that offers more flexible export options. That application is the Windows version of the free cross-platform email client, Thunderbird. Within Thunderbird you’ll find the Tools -> Import command. Choose it, select the Address Book option, click Next, and in the Import window select Outlook and click Next to import your Outlook contacts into Thunderbird...

I tried the Action - Mail feature, but it doesn't work for 980+ contacts.

Next on the list is the now $25 vCard Converter Add-in for Microsoft Outlook, but I fear all Oulook Add-Ins. I think the Outlook Add-In architecture is 75% unstable antimatter. (Alternate source?)

It's not on this list, but a few months ago I tried the export to Google to Address Book route. It was "ok", but I ran into problems with EX style x.500 email addresses.

So this time I think I'll try the Thunderbird option first, and if that's not satisfactory I'll try the (currently) $25 vCard converter add-in.

Once I have the Work contacts in OS X Address book, then they'll go to my iPhone ...

Update: Thunderbird had the same X.500 (EXchange server) email address translation problem as CSV export. Also, I couldn't limit import to a single contacts collection, it brought them all in. Lastly, it was very slow. If the Sperry product can do the x.500 to internet standard email translation I'll give it a try.

Also, this export utility has a 30 day trial.

Make iTunes window more like a standard OS X window

iTunes started out as a pretty un-Mac like application, but over the years the platform and iTunes have grown together.

Except for one real oddity.

Every Mac application has 3 "ball" icons in the upper left side of the window - red, yellow, green. In Safari if you mouse-over they display a symbol as well.

Red closes the window. Yellow hides it. So far, so boring. But what about green?

Green is the expand window button. This isn't well documented, the OS X zoom window (expand window) behavior is quite different from windows. A well behaved app doesn't necessarily zoom to full screen, it zooms to the maximal logical size (which for many apps is full screen). It doesn't always work as expected, and I think apps are behaving more like Windows zoom over time, but I personally like this smart zoom.

So the green button is the expand button ... except in iTunes, where it instead launches the iTunes mini-player! How annoying.

Happily, there's a workaround, which I came across here  and have since added to an old post of mine on iTunes shortcuts and modifier keys...

Gordon's Tech: iTunes keyboard shortcuts, safe mode, prevent mounting, and more

.... option-click the top-left round green window (+) icon: instead of switching to a mini player, the iTunes window adjust to an optimal size for the current display. In other words, it behaves like the green icon on every other OS X app...

I'd prefer iTunes behave like a standard Mac app, but option-click is better than nothing.

Retrospect restore failing, network flaky – a hardware problem?

Maybe it’s the incipient dementia, but I’m having a hard time telling hardware problems from software problems these days.

It didn’t used to be this way. Even ten years ago if something went wrong, it was almost always a software problem.  The only exception was the slowly dying drive, but you could usually hear that going.

Now, who can say? Systems can run hot, solder isn’t what it used to be, and quality is an issue everywhere. Software is very complex now, and software changes can make latent hardware issues into active problems.

It’s also true that hardware is much older than it used to be. Moore’s Law failed a while back; my 6 yo XP box just keeps on being useful. I don’t ask much of it since we’re largely an OS X shop, but it’s good enough for basic work.

It all adds up. Oh, and the dementia too. Being an OS X shop means it’s been a very long time since I’ve had to think about BIOS age, memory maps, interrupts, and the like.

My latest experience is a case in point. It began when I replaced my old USB backup drive and enclosure with a LaCie 1TB drive/enclosure. My old XP box wouldn’t boot! It simply hung in early startup. I found I had to turn the drive off to boot, then turn it on again when XP was up. Then it all worked.

Ominous.

Next I started getting oddball network problems. I beat them back and things seemed to settle down, but then a Retrospect Professional restore of a 50GB iTunes Library failed with a typically cryptic Retrospect error code of "-519". I had to throttle my 100 gbps network back to 10 mbps to get the restore to work.

That got my attention. I can’t live with unreliable backup/restore.

In some earlier testing I’d eliminated cabling and my Netgear gigabit switch as contributors. So the problem lay in my 3 yo G5 iMac or my 6 yo XP box. Neither had had major software changes recently, so I bet on hardware. Since some network glitches had required power cycling the XP box I put my bet on that.

So I bought the Intel PWLA8391GT PRO/1000 GT PCI Network Adapter. It came from Amazon in about 2 days (free shipping!) in a plain package with a single DVD. Nothing fancy here.

So I swapped out the old 100 mbps SMC NIC for the Intel and rebooted and got a … turquoise screen.

Nothing. The drives were spinning, the CPU fan was spinning, but the system locked pre-BIOS! I pulled the card, restarted and things looked good.

So then in desperation, I moved the NIC to a different slot, and then rebooted and looked through all my BIOS settings. I made one change. The BIOS had previously been set to manage devices, now I set it to ignore PnP devices and let the OS handle them.

So I did two things at once – but I wasn’t trying to identify the root cause. I wanted the thing to work.

I then restarted with the LaCie 1TB drive attached and … it worked.

I’m really getting tired of figuring this stuff out.

The Intel adapter requires drivers, so I installed from the CD and … wait for it …. found a bug.

Immediately.

It’s a gift.

The installer bombed with a poorly written complaint about my “S:” drive.

Turns out I’d mapped the “My Documents” folder to a (now inaccessible) network share that I’d mapped to the “S:” drive. So of course there was nothing there. Even when I dismounted the “S:” drive, the installer still bombed. I had to reset “My Documents” to the default setting.

So, pretty dumb coding on the installer. On the other hand, once the install completed, I was impressed by the diagnostics suite. The NIC, cabling and network passed every test.

These hardware diagnostic tests are critical in the modern era, so this utility was a definite plus.

I then repeated the restore that had previously failed at the 200MB mark. This time it went easily past 1GB, with a throughput of about 830 MB/min (probably limited by the USB drive).

So I think my problem is solved. Was it really a problem with the IDE slot? Or the old NIC? Or the 1TB USD peripheral causing some problem with the 8 yo BIOS? Was the fix the new card, changing the BIOS settings, or moving to a new slot?

I don’t know.

Don’t care.

My network’s much faster now…

Why I'm downloading Windows 7 RC tonight ...

It works on VMWare -- and it's free ...

VMware: Team Fusion: Windows 7 on Mac with VMware Fusion: A Practical Guide Revisited

... More important, I am excited that the Windows 7 Release Candidate is the easiest way for you to try out Windows on your Mac for FREE (at least until the beta expires). That’s right, you can download Windows 7 Release Candidate through July 1^st and it’s free to use until it expires on June 1, 2010...

The VMWare post has more details, but basically the RC works fine with some trivial and standard configuration options.

A very nice surprise for me. I've been tracking Windows 7 from a distance, but primarily as my way to avoid Vista (Windows 7 is Vista 2.0 of course, but I'm good with that). In the meantime I've had Parallels 1.x and Windows 2000 (!) running on my MacBook for about 2 years (man, does Win2K ever boot fast on that machine.) This setup worked for the handful of times I've needed it, and the two take up very little CPU or disk space. Windows 2000, of course, is essentially immune to modern viruses.

That's a good setup and it cost me nothing but Parallels 1.x since I have several unused Win2K licenses. It probably won't work on 10.6 though, and I'm about due for a new iMac.

So I'll put my unused VMWare license on the new machine, install Windows 7 RC, and be good for a year or so. Then I can decide if I want to buy Win 7 or regress to Win2K ...

(I wonder if I need to get more than one copy of Win 7 RC, in case I put it on two Macs ...)

5/26/09: Updated to remove a stupid mistake where I confused 2009 with 2010. The RC1 download is good for one year. That's just fine.

iPhone incompatible with old auto adapter? Salvation from Griffin

I like Griffin stuff, so I was willing to take a gamble on the just released Griffin Firewire to USB Charge Converter for iPod and iPhone 3G.

In short, it works. One of the truly infuriating iPhone aggravations has been ameliorated.

The $20 device is a bit bigger than the proverbial postage stamp, about an inch square. It's quite light. The standard iPhone/iPod adapter is the modern friction-only style, no lock feature. (I'd prefer the positive lock for this use, but Apple has moved away from them.)

I plugged one end into my SONY car stereo with iPod adapter cable and the other end into my 3G iPhone. The iPhone began charging. More importantly, the kludgy but useful iPod control software works, and the sound quality really is better through that cable than through the AUX in mini-jack connector.

I did get an error message from my iPhone saying the device was not compatible with the iPhone and offering to reduce audio interference by putting my phone into airplane mode. This is not related to the Griffin converter, I get this message without it. It's different from the "can't charge" message -- it's saying that the radios built into the iPhone can cause interference with many devices not built for the 3G iPhone. In my case there's no hum or other problem in standard mode.

The adapter does make the cable to iPhone connection long and somewhat fragile. It would be easy to whack the end of this longish lever and injure a connector. It would be best used when the iPhone is securely mounted.

It's probably not worth buying this device to extend the utility of a firewire charger -- it costs almost as much as a Griffin USB charger and cable. It's really made for an automotive head unit, and it works on mine.

Note that Griffin makes no claims that the automotive head unit controls and audio inputs will work -- only that charging will work. I took a chance that everything would work, and it did.