MarsEdit 3.1.3 - Still not Windows Live Writer, but definitely worth the money

I've been evaluating the MarsEdit OS X blog writing tool since November 2004. In 2007 I gave it a good try, but it fell short. Finally, in May 2010 I bought it, but by July 2010 I threw it out. It didn't measure up to my lost love - Windows Live Writer [1].

Six years is a long time to evaluate a product, but not as long as I've been fighting with Google's incompetence. Evidently billions of dollars aren't enough to create a rich text editor that knows the difference between <div></br> and <p></p>. This past October Blogger broke me. While I researched alternative hosting solutions, I decided to give MarsEdit another try. By this time it was at version 3.1.2.

MarsEdit is now good enough. Try it, buy it ($40).

No, it's still not the equal of Microsoft's free Windows Live Writer, but WLW was one of the finest pieces of consumer software created in the past five years on any platform. WLW is one hell of a high standard. MarsEdit is now about 60% as good as WLW, and that's more than good enough.

The key to succeeding with MarsEdit is not to mix MarsEdit posts with any Blogger product. Don't use Google's BlogThis! to create a draft post, use the "Post with MarsEdit"/Blog This bookmarklet that comes with MarsEdit. Don't touch your posts with Bloggers pustulent editor, open them with MarsEdit [2]. When you paste text, always use "Paste and Match Style" (sure wish that didn't strip out URLs though).

You can alternate editing a post with MarsEdit and WLW by the way. The post formatting will not be injured.

There are several bugs with the rich text editor portion of WLW. I don't see them very often because I've learned workarounds. Sometimes you just have to switch to the HTML editor to remove <div> tags that seem to confuse MarsEdit -- though if you stick with WLW (Windows) and MarsEdit (OS X) you won't run into this problem. There are bugs with <blockquote>, it helps to include an extra line before the paragraph.

The good news is that you can learn to work around the bugs, and there's an end to them. Honestly, I rarely notice them any more. I notice more the rich text editor's lack of keyboard shortcuts or menu bar icons for commonly used commands. Daniel Jalkut is actively working on MarsEdit though, and I think they'll be there in the next release.

MarsEdit has made my life better. It's not perfect, but it improves. Within a year or two I bet it's 75% of WLW, and that's way more than good enough.

[1] Lost because I'm pure OS X at home, and because Microsoft has abandoned the product. Since it was about perfect though, it will be a fine tool for years to come. They've relabeled a "2011" version, but really there have been no changes.

[2] Ok, so I do open quite old posts with Blogger's editor.

MarsEdit 3 - you're no Windows Live Writer

I bought MarsEdit 3. After a couple of months of use I'd give it a B+. It's much better than anything else on OS X for publishing to Blogger, but it's a weak shadow of Microsoft's (abandoned) Windows Live Writer (Win only).

The image handling is particularly weak. On the other hand the bugs aren't too awful and the customer support is superb. I'd love to see Red Sweater study WLW and emulate as many features as possible.

The real competitor on OS X is Google's own web based editor. If Google were to put their A team on blogger I think MarsEdit would get squashed. They're not going to do that though, and the current team can't even get paragraphs working. So there's an opening for MarsEdit. I hope they squeeze through ...

Update 8/7/10: I threw MarsEdit off my drive after it produced a complete hash of a post. It looked fine in MarsEdit's wysiwyg editor, but it was a mess in Blogger. I had to fire up an XP VN and use Windows Live Writer to repair the damage. Using a rich text editor as a proxy for a true HTML editor is a bad idea.

The Blogger in Draft line spacing bug - illustrated

In a kind rebuttal of my claim that Blogger is troubled, Rick Klau, a Google Product Manager, wrote:

… There is a new text editor available on www.blogger.com (available under settings) which is the default on Blogger in Draft. It significantly improves the authoring interface, addresses a number of the issues you referred to, and opens up a number of integration opportunities for us with other Google properties - we're doing QA on the next batch of integrations right now…

When I described the longstanding troubles I’ve had with the Blogger in Draft rich text editor Rick responded;

… Odd to hear about formatting problems with Draft's editor - it's pretty rock solid. Please ping me with any indications of what you're seeing - that's almost certainly a bug that we'll want to fix if it persist…

So I’m pleased to say I have a good example of the bug. I believe it’s related to the old CR/LF, CR, LF problems in DOS/Windows, MacOS and Unix – augmented by the transition to the unicode standard. (I’ve read recently that all of Google’s new tools require translation to unicode).

Here’s a recent post of mine, authored using Windows Live Writer (Windows only) as it renders in Chrome 4.0.249.78 after posting (it shows the same way in WLW):

Here’s how it looks in Blogger Classic using Chrome:

And here is how it renders in Blogger In Draft using Chrome:

Yes, the line spacing is wrecked. From past experience, this is messy to fix up. When you fix the line spacing here, it comes out double-spaced on publishing.

I’ll point Rick to this post. Hope it helps!

Update 1/29/10: Based on Rick's comment below, Google is looking into this one.

Update 2/1/2010: There's a similar bug with Safari on OS X. When you quote a block of text everything double spaces.

Update 3/10/2010: I just had blogger in draft completely screw up a post composed 100% in Chrome on XP. It's far from ready.

Windows Live Writer: moving between machines (yech)

I love WLW, but it has an Achilles heel. On XP it’s pretty much impossible to move your configuration data between machines.

Of course that’s true for almost all of  Microsoft’s products, but we expect better of WLW. On the other hand, I hear rumor there’s a configuration migration service built into Vista (some OS), so maybe it works fine there.

I found out about this after I switched machines. I have the old data of course, but I’ll just migrate manually. It would be nice if the WLW were to build in a migration utility, but for now here are two somewhat useful references:

• Backup your WLW Settings: a post about this utility, but the utility is quite old and hasn’t been updated
• Migrate Windows Live Writer data: reveals location of the files, unfortunately key data is in the foul pits of Hell, aka the Windows Registry.

There’s some accessible data in ..

• C:\work\My Weblog Posts (path will vary)
• C:\Documents and Settings\[userid]\Application Data\Windows Live Writer

You might imagine you could copy your older WLW posts and drafts to C:\…\My Weblog Posts and WLW would be able to browse and search them, but that doesn’t work. It can open them if you double-click on them, but there’s a cache/index missing somewhere.

Happily, if you copy our old posts and drafts into the new WLW folders (ex: C:\work\My Weblog Posts) and delete the XML cache files WLW will rebuild them and find all your draft and new posts.[1]

[1] I got messed up here because when I forgot to point the “My Documents” folder to my personal file store. So WLW was only looking in My Documents. I copied the data from My Documents then pointed My Documents to c:\work then launched WLW.

Update 6/17/09: Corrected my mistake about posts recovery.

Debugging network account lockouts: issues with Microsoft Active directory authentication

I recently experienced a personally new and novel set of computer network related issues. I'll have more to say on Gordon's Notes about my take on the implications and lessons of this experience, but on this blog I'll stick to measures end-users might take.

If you're reading this I'll presume you are a user on a corporate network and you are now unable to get at network services. If you request a shared drive or other network resource you are asked to provide your credentials (username and password). You may be unable to login to your workstation while you are connected to the network, though if you pull the network cable or disable wireless access you can login locally.

In this case it is likely that your network authentication is failing. Your credentials are not valid, you've been locked out.

There are legitimate reasons to be locked out of course, but most of the time this is an error. A Microsoft Active Directory group policy setting in your organization specifies an allowed number of failed authentication attempts in a certain time interval and "you" have passed that limit.

By "you" of course I mean whatever is trying to login with your username -- but not your current password. The problem, you see, is that many things may be doing that. Some may be on your machine, some may be on other machines you've used or use, and some may be in places you can't imagine. One of these things may be you, of course, entering your password incorrectly more than, say, five times, in a certain interval.

Ahh, but you say you only made one mistake? Well, maybe something else was trying four times in the key interval. Your one mistake was the last straw.

This is a big problem. You'll find many hits on the topic if you start looking. It's a Cloud problem (new tag today!). It's what happens when authentication starts to diffuse, and when you don't have a robust system for distributing authentication privileges. It's what happens when credentials are cached or distributed, and there aren't robust tools in place to monitor and track -- or when organizational structures block recognition.

Microsoft has tools for diagnosing active directory account lockout issues, but they are not accessible to end-users like you ...

• http://technet.microsoft.com/en-us/library/cc738772(WS.10).aspx
• http://www.microsoft.com/downloads/details.aspx?FamilyId=7AF2E69C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
• best overview (private blog).

As an end-user victim these are some things you may investigate once your help desk has unlocked you. Good luck ...

• Change your network password, that may fix some caching issues.
• OS level drive encryption software, bolted onto a decrepit XP infrastructure, can be a problem. These typically synchronize credentials with Active Directory -- and we all know synchronization is Hell. Look into any associated logs that might show how synchronization is preceding. See if you can change your password using the UI controlled by the encryption package and watch that propagate to the server.
• Group policy updates may be failing, resulting in passwords failing to comply with standards and leading to rejection. Research use of the gpudate.exe /force command to update local copies of corporate policies.
• Eliminate all drive letter mappings on all machines. I know longer do drive letter mapping on corporate networks. These can have cached credentials that fail to update.
• If you use Remote Desktop, log in to every RD machine you use and make sure you are fully logged out again. You may need to apply all fixes and patches there as well.
• Try shutting down your main workstation when you are not at working -- or disconnect it from the network. If you're locked out then you may suspect the problems are from other sources.
• Do not use Windows Search to index mounted drives.
• remove all IE stored information - cookies, passwords, etc. Used Delete All from the IE General/Delete settings tab. Note this is the ONLY option if you want to be sure to remove any stored credentials from IE Add-Ons.
• Consider uninstalling any applications that authenticate with Active Directory, such as Office Communicator.
• Evaluate all applications that might interact with Microsoft Sharepoint, because these require Active Directory authentication. This may include:
  • Windows Live Writer: Posting from WLW to a SP blog implies an authentication event
  • Lotus Connections: If you use Lotus Connections web-based feed reader against a Sharepoint feed there's an implied authentication event. (In my testing these subscriptions appear to fail, but does LC attempt to authenticate with its internal credentials? What about if the user IDs match between LC and SP but the passwords differ?)
  • Outlook 2007: Outlook 2007 is able to subscribe to SP Calendars and other Sharepoint Lists. All of these imply authentication. Prior to SP1 Outlook 2007's subscription/feed support was extremely buggy.
  • Any feed reader that works against Sharepoint authenticated feeds

Personally, this is the nastiest problem I've come up against in 25 years "behind the mast". I'll have more to say in my opinion-oriented blog about how this has changed my approach to personal and cloud computing and to the new approaches I'm taking to risk mitigation going forwards.

Update 6/2/09: Focus is now on a combination of a Sharepoint List synchronization that could not be removed from Outlook 2007, a possible configuration error on Sharepoint, Outlook configured to send only on manual send/receive, send/receive configured (by default) to include the unremovable SharePoint list, and Outlook offline caching of credentials.

Update 6/4/09: Microsoft Wireless PEAP always caches credentials. Could be a contributor in some situations.

Update 6/12/09:The saga continues. To remove the long stuck Sharepoint list in Outlook 2007 I had to remove reference to it in the Outlook send/receive group. In fact, I removed most things from that group. The NTLM account lock problem went away -- but I then had to manually authenticate the first time I used Outlook to access Exchange server. In other words Outlook was no longer able to deliver my credentials automatically. (The advanced security settings for Outlook did not have "manual credential" checked.)

After a week of this my laptop was refreshed. Using a brand new image I was again locked out. (I did have to install Retrospect Pro to restore data, but I think the first lockout was before I restored anything.)

This went on for a few days, then I did into an obscure option in Outlook 2003 (and 2007) properties and set Outlook to always require manual credential entry. The account lockouts stopped.

I'm going to study this for a few days, and see if I can get locked out by turning off manual credential entry. If I can confirm this does the trick, I'll try to bring very specific fix suggestions to our puzzled help desk and security services. I need to better understand the NTLM/Exchange/Outlook authentication procedure.

Update 6/12/09b: I've asked this question on serverfault.

Update 6/27/09: I post an answer to my own serverfault question:

... I've not been locked out for over a week even after turning re-enabling Outlook pass-through authentication, so even though there was no definitive cure I can report where I left things.

As a reminder, the last time I was locked out I'd just received a brand new laptop with a fresh corporate image.

The very last things I did were:

1. I found the brand new corporate image included two drive mappings. Sigh. (Sound of head hitting wall.) I'd removed them from my old laptop long ago, but they were back. I removed them again. It wasn't the only problem in the corporate image.

2. I experimented with switching Outlook 2003 authentication between "automatic" (default), Kerberos only (modern) and NTLM only (legacy). Switching to Kerberos only seemed to resolve problems, but I think that was a red herring. Switching back to the default didn't restore the lockout problem.

3. I use Retrospect Professional (EMC Retrospect) for Windows to backup my workstation to an external drive. (Corporate backup isn't bad, but restore takes about a week.) That software has an autolaunch feature. I'd set it to auto-launch using the logged-in credentials rather than the treacherous feature of providing credentials. I wonder though about an intersection between the mapped drives and the auto-launch. I turned off Retrospect Pro auto-launch for now.

I very much appreciate the link Neobyte provided to Microsoft's June 2008 troubleshooting page - Troubleshooting Account Lockout

http://technet.microsoft.com/en-us/library/cc773155%28WS.10).aspx

I'm left with some psychic scars. Given the astounding variety of problems associated with Microsoft's authentication services and their pile of legacy hacks, and the intersection with distributed authentication and post-hoc security features like authentication lockouts, I'm now deeply conservative about my use of any new or novel corporate network or "cloud" initiatives. They need to be built on a far more robust infrastructure than what Microsoft provides, and they require both IT funding and IT reorganization to implement.

7/21/09: I found yet another potential contributor -- one I'd long forgotten about. I'd once set up my iPhone to connect to the corporate WLAN. To do this I had to enter my Active Directory login credentials. The iPhone connects automatically when the WLAN is in range. So what happens when my network credentials change and the iPhone tries to connect? I'm not sure. Maybe it fails once and doesn't try again -- generating only one lockout hit. Maybe it tries repeatedly. Who knows. The point is, we're screwed.

We need better ways to manage user authentication and privilege control, and we need them desperately.

As for the iPhone, there's no way to have it remember network credentials yet not automatically connect when WiFi is enabled. So I deleted my corporate WLAN credentials from my iPhone.

Ecto 3 - still breaking my heart

I'm a huge fan of Windows Live Writer.

There's only one problem with WLW. The first W.

So I've long hoped someone would clone WLW for OS X. It doesn't have to be as good as the original, a reasonable clone would be a joy.

Unfortunately, the closest thing to WLW for OS X is ecto, and I'm saddened to find it hasn't changed since October of 2007.

It still has one fatal flaw for use with Blogger. It requires that Blogger blogs have "convert line feeds" disabled.

If that feature is enabled (default behavior) then Ecto posts have extra line feeds. If it's disabled existing posts lose their paragraph formatting.

There are other issues with Ecto, such as the way it retrieves Labels (it just looks at Labels on recent posts), but this one is a killer.

Won't anyone please try to clone Windows Live Writer? I mean, I know there's no market out there but ...

Oh, right. No market.

Annals of abandoned Windows desktop feed readers: Onfolio, Omea ...

Microsoft bought the superb Onfolio product a few years back, but they gave up on it in favor of the feed reader built into Outlook 2007 (miserable piece of ****) and the feed reader built into IE 7 (weak, but workable, heaven forfend don't sync it to Outlook's feed pool).

Alas, Onfolio has a .NET DLL-like conflict with Windows Live Writer (and you thought DLL-Hell was gone?). Since Onfolio is dead, and since I live by WLW (same team did Onfolio!), I again looked for a Windows feed reader I could use with our corporate sharepoint feeds.

I thought I'd give the once well regarded Omea Reader a try. It sure sounded a lot like Onfolio, and it didn't carry the baggage of Omeo Pro (which is far more than I want).

Omea Reader did a great job importing my Onfolio OPML file, including retaining the folder structure. I did run into a number of bugs and UI glitches though, so I figured I'd check on the development status.

Cough.

This is what shows up in the Feeds view (the originating web site is now gone) from March 2008:

Dear JetBrains Omea Users,

We are pleased to finally come to you with these news.

We know that many of you were waiting for this to happen for so long, and we would like to thank you for your patience.

So, after several months of thorough work on polishing the software itself and its API, we are happily ready to announce the full availability of our "Omea" line of products in their open-source incarnation.

We hope that this step will allow us to rise the development of this great product to a new level and to attract energy and talents of everybody who likes to participate in this "adventure"...

By "adventure" they probably mean "hell-ride that nearly destroyed our company". Things were happier in 2005 ...

... In the February, 2005 issue of Home Computer Magazine (www.homecomputermagazine.com/), Omea Reader was announced as their Five Star Pick for free RSS Readers. But you knew that already... isn't it nice to be proven right?...

I'll keep trying Omea, it seems more stable than Onfolio for the moment. I can't recommend a dead product to anyone else though.

I fear I'm the only one looking for a Windows feed reader, which makes me wonder if a very excellent technology isn't really going to make it this go-round ...

Update: When I do a Google search on "windows feed reader" I get exactly NO Adword advertisements. The moving finger of history has moved on.

A workaround for image uploading to Microsoft’s Sharepoint Wiki.

There are some good things to say about Microsoft’s Sharepoint based Wiki.

There’s also, sadly, one very bad thing. The approach to image embedding is lousy.

Happily I have found a convoluted workaround that uses one of my favorite apps – Windows Live Writer …

1. Create a SP blog that will hold the images that will be referenced in the wiki.
2. Use Windows Live Writer to post to the wiki-image-blog. Drop your image into WLW, resize it as needed, etc. If you like, use WLW to write your image associated wiki text first draft as well.
3. After you post to the Wiki, copy and paste image and text into the Wiki editor rich text field.

This takes surprisingly little time, far less than any other option I've read of. I admit, it is convoluted!

Update 1/11/09: I've been doing this for a while now. It's bloody brilliant, even if I have to say so myself. You can take advantage of the wiki-image-blog to attach a bit of metadata, including labels, to help with image reuse. If you read this and know anyone using Sharepoint 2007, I suggest send this on to them. They'll be forever grateful.

Microsoft's amazing WLW team also did Onfolio?!

I was happily scanning the release notes for the sure-to-excel WLW 2009 release when I came across a surprise note ...

Windows Live Writer 2009 RC released « whateverblog.

... On a more reflective note, this was the first full milestone (Beta to RC) we did without Charles Teague, our dev lead and voice of reason since the earliest days of Onfolio...

Onfolio is the only Windows app besides Windows Live Writer that I use and admire. I'm quite sad that Microsoft bought it only to kill it.

So one team did both products.

They must be Minnesotans.

I hope Microsoft is paying 'em very well!

Windows Live Writer news: 2009 and Blog This for Firefox 3.0

The really big news on one of my favorite apps from any vendor is that Joe Cheng has released a version of the "Blog This" add-on for Firefox 3. So we don't have to follow Joe's prior workarounds. Unfortunately it's in "sandbox mode" and won't be generally available until it collects a number of positive reviews.

So take a moment, register as a Firefox add-on tester, and contribute your five star review with a big thank you to Joe. My guess is he had to make time from his Microsoft duties to get this out.

In comparison, the announcement of a new version of WLW is a minor detail: Windows Live Writer 2009: Release Candidate. I mean, it's not like WLW 2.x was missing very much. The only WLW version news that would excite me would be a Mac version, which falls into the hell freezing category.

There's nothing in the features list I care about. Really, what I'd most like is a way to search against the titles of the post history list, and have other ways to manage the list of past posts. [See updates. Turns out the preview has some nice fixes to minor bugs and some great new features – like searching the list of retrieved past posts.]

WLW 2009 is bundled with "Windows Live Essentials", but I think you can choose which to install.

I'll wait for the release version. It's hard to improve on something as fine as WLW 2.x. Except, of course, by releasing the Firefox Blog This add-on.

Update: Joe commented that Firefox "Blog This" is a certified Microsoft product, not solely his project. Joe also tells us that the new version of WLW has the title search feature I wanted, implemented as filter.

Guess I'll have to test earlier than expected!

Thanks for the correction Joe, and thanks for your work and that of the WLW team.

Update 12/23/08: Blog This! is still stuck in the sandbox, so it needs more reviews. Works great, of course. WLW 2009 preview looks very good, so I’m glad I didn’t wait. I love the “filtering” feature – but I think it’s better than title filtering. I think it’s searching entire posts. They’ve also fixed the minor but annoying bug where the display of some labels/categories/tags for Blogger was truncated. The problem’s been long understood, but it wasn’t serious enough to justify a patch outside of this update. You have to uncheck a few things, but the new Windows Live installer will eventually agree to simply update WLW 1 and the IE toolbar.

ScribeFire: so many updates, so little progress

Ive been intermittently using the ScribeFire: a Firefox extension blog editor for about a year.

The "release fast and often" strategy is fashionable now, but ScribeFire is a good counter-example.

It still only shows recently used "labels"/"categories" from blogger. It still doesn't handle blogger's line wrapping correctly.

These aren't subtle things, and they aren't new. They've been present from day one.

Windows Live Writer is proof that, given sufficient genius, these problems are solvable [1]. Release often is not a panacea.

[1] WLW is also proof that there's life at Microsoft. Nobody has released anything comparable for OS X.

Using Blogger: Camino in place of Firefox 3

Things were going too well with Blogger. It had been months since a real disaster. Heck, I was even using Blogger in Draft (draft.blogger.com)!

Then, after installing Firefox 3, the wellness resolved ...

Gordon's Tech: Blogger a mess with Firefox 3

... Every other post I've written over the past 3-5 days has had problems with lost line breaks. All my text runs together. It's as though Blogger had broken their age-old management of paragraph breaks. I've tried Safari 3, Firefox 3, ScribeFire, XP, OSX, Blogger-standard and Blogger-in-Draft...

I'm not sure what's going wrong, but on various posts Blogger will abruptly treat the text as though it were true HTML -- instead of treating paragraph breaks as though they included a paragraph tag.

I think the trick is having edited it at one point with Firefox 3 and the Blogger in Draft editor. I think there's some style sheet persistence that's not exposed to the HTML editor. Subsequent editing with FF 3, even when Blogger in Draft is disabled, can trigger the problem.

Once a post gets into this mode, there's no escaping it -- turning off Blogger in Draft or using the HTML editor doesn't fix things.

I've found I can fix the post using either the superb Windows Live Writer (XP only) or Safari 3.

I've disabled the beta/draft version of blogger and returned to regular Blogger. On XP I can avoid this by simply using WLW. On OS X though I don't want to revert to FF 2. Safari 3 doesn't work very well with regular Blogger. So how can I get FF 2 type behavior on OS X?

Easy, use Camino. Works great.

I'll take another look at things in a couple of weeks, but until then I'll stay with Camino for my OS X blogging.

Make Firefox 3 beta accept the Windows Live Writer Blog This extension

Update 8/20/08: See the last update for the new way to do this.

I can't get the changes I've made to WLW's rfd file, per Joe Cheng's (WLW engineering) blog, to do anything. I'm hoping Joe will have some advice, but, in any case, the illustrious WLW team is promising an update to the "Blog Ths in Windows Live Writer" Add-on. I might just wait for that.

I ended up installing the Firefox Nightly Tester Tools add-on. Then I removed all non-compatible add-ons except for WLW (note I'd already uninstalled Google Web Accelerator), then I clicked the over-ride compatibility button in the test tools options. That worked.

Update 5/27: Joe Cheng's (WLW engineering) blog has a post about a finer grained workaround. Joe also promises to update the extension soon. I continue to be amazed that the WLW team is supporting Firefox use. (Tip via Brandon T. I subscribe to Joe's blog, so I should have caught his posting. I need to check out Bloglines and see if I've somehow lost his feed ...)

Update 8/18/08: At the end of July Joe updated his post. Note the renaming install.rdf trick to force Firefox to refresh its version. The advice now works, but it's also becoming obvious that Microsoft manage understands the value of WLW, and is no longer interested in maintaining a plug-in that supports Mozilla Firefox.

Windows Live Writer - gallery of plug-ins

The world's greatest blogging tool has a new and improved Plug-In gallery. (The Firefox Blog widget is prominently featured.)

As fond as I am of WLW, it does pain me to praise it. It's a Microsoft Live product, and there's no OS X version on the horizon. It's a bit much to load VMWare Fusion and XP only to run WLW, but I'm tempted.

There's nothing comparable for OS X. Ecto showed promise once but every time I've tried it I've been disappointed. In particular it made a mess of Blogger posts; WLW handles Blogger quirks and bugs as well as anything can.

Update 5/20/08: The WLW Firefox add-in is not compatible with FF 3! Wow. Wish I'd thought about that before I upgraded. I'd have held off on my XP machines.

Windows Live Writer cursed by Google's bugs

You know you're in a new era when Microsoft is the humble good guy doing the noble thing, and Google is the arrogant foe of justice.

Google's hacked-together Blogger-Picasa pseudo-integration breaks when image-containing posts authored using Windows Live Writer are migrated to a personalized domain or to an ftp site.

The honorable WLW team has put together a partial solution, but really this is Google's bug.

I'm a longtime user of both Blogger and Picasa. Google is not wasting any of their billions on funding those products. I'd guess it's some manifestation of old-style revenue-funding business discipline. Personally, I'd prefer Google sell both properties to someone who's willing to fund them. I'm more than willing to pay for value delivered; Google's low-cost B-team funding approach is really annoying.

Google Desktop Search bites the dust

I've posted frequently since January 2005 about various approaches to full text search in Windows XP in general and Outlook 2003 in particular.

My test environment is harsh. GBs of Outlook PST files. GBs of documents. Machine never rests. Hard drive always on the edge of meltdown.

The best solution, by an order of magnitude, was Lookout for Outlook. Fast, stable, and the bugs are manageable. Alas, it conflicted with some other Outlook Add-Ins (that environment reminds me of DOS TSR hell). Lookout also doesn't work in Outlook 2007 and it's definitely not supported anywhere, so I thought I needed to change. That was probably a mistake.

I used Yahoo Desktop Search for a while, but it was increasingly buggy and Yahoo finally abandoned it. It reverted back to X1 but it was even buggier when I tried their version.

Recently I decided Windows Desktop Search was my only option. It was slow and sucked performance, but it did all I needed and it incorporated Lookout's search syntax (see the help file). Unfortunately, my work machine has been possessed lately.

I'd removed about everything I could think of to try to stabilize my system, so it was time to remove WDS and try the only remaining contender Google Desktop Search.

Yech. This is what I wrote when I uninstalled it:

... I don't have enough control over indexing behavior. I don't have enough search syntax control - esp. for outlook tasks vs. email search. It was WAY slow to do a search against my multi-GB Outlook archives. It doesn't treat folders as first class search objects...

So now what do I do? I could buy a MacBook Pro and run XP in a VM, but Spotlight won't search PST files.

I need full text search - esp. of PST files.

I'm going to try Lookout again; I've gotten rid of most of my Outlook plug-ins / add-ins anyway.

Gee whiz, I miss my home OS X machines. I know people complain about Vista, but I'm not a great fan of any Microsoft products at the moment (though my problems, to be fair, may be hardware related). Even my beloved Windows Live Writer is buggier at the 1.0 release than it was in the last two beta versions!

Update 11/16/07: Joe Cheng (see comment) noted I hadn't submitted my WLW bug reports. They're really not awful, but they stood out relative to the perfection of the last beta. One is certainly a bug -- the category/tag names can be truncated randomly (last few characters are missing). The other two I need to prove are really bugs, which is a bit tough since my Dell laptop is definitely flaky.

I'm going to be more careful going forward about what I call a bug ...

Update 11/16/07b: The regressions (bugs) will soon be history. In the meantime don't use the Post to Weblog as Draft feature with Blogger.

Windows Live Writer is out of beta

The best blogging tool on any platform is now out of beta:

Finally Final! « whateverblog

We’re thrilled to bring you the final version of Windows Live Writer 2008–our first non-beta release!

It's an excellent product. Ecto 3 beta is probably the closest OS X alternative, and it's much less robust than WLW (editor is buggy, it doesn't download a full tag set, etc).

Free, too. I use it extensively with Blogger and Sharepoint 2007.

Don't miss the Firefox integration. (Unsurprisingly that doesn't appear on the Live.com page, but surprisingly it does exist.)

Ecto - the first good blogging app for OS X?

I've tried several OS X blogging tools, but none of them compared to Windows Live Writer. This post, however, was authored in Ecto 3 beta from infinite-sushi.com, and it comes close to WLW. It even supports OS X services! The link to the "alpha" version in the news blog actually downloads the beta version, I'm on 3.0b2.

I'll have more to say on Ecto as I test it, but it's great to see this emerging.

XP: Recent lessons from the dark side

[see update about the two "versions" of WDS and a later update as the saga continued ...]

At home I sail the often calm waters of OS X. At work I fight the fury of the storm, trapped in the XP triangle.

Now, it must be admitted that if my Dell XP laptop were sentient I'd be condemned as a cruel master. I torture the darned thing. I know few who see as much of XP and Office's brittle nastiness as I. Maybe if I treated OS X the way I do XP it would break to. (Vista? You're joking, right?)

That said, a recent flurry of cascading messes taught me a new lesson and reminded me of old ones.

1. Sometime in the past few weeks my 75GB drive suddenly had only 9GB free. It's dangerous to fall below 20% free space on a heavily used XP or OS X system, and I think this was one of the "straws" that pushed my XP system from its usual metastable state to accelerating collapse. In retrospect I'd somehow ended up with a 5GB orphaned pagefile.sys. I couldn't see it, because I somehow had Explorer configured to not show system files [12]. I eliminated the orphaned pagefile.sys by accident [1], but I think if I'd had Explorer showing me system files I'd have seen it, and dealt with it. New lesson: always display the hidden files so you can track pagefile.sys.
2. A combination of Windows Desktop Search [5], an unstable corporate network with intermittent Exchange connectivity failure, a 3.5 GB Outlook PST file [11], severe disk fragmentation [2], bugs with Outlook 2003 [3], my use of Microsoft's Onfolio [4], my insanely persistent use of Palm synchronization [6], Microsoft's Live Meeting Outlook Add-in [7] finally led to a system meltdown with increasingly odd Outlook behavior and, finally, OST corruption.
3. Good news: no covert alerts of drive read/write errors in XP's monitoring tools (XP quietly tracks many disk failures without notifying even admin users) and no chdksk/scandisk/whatever-it's-called-now problems.

So now my OST file was corrupt. Happily, that's usually not a big deal and it wasn't this time either. I turned off WDS (I snoozed indexing but I think I should have disabled the indexing service using XP's service manager - it kept trying to return to life) and found my OS file in "C:\Documents and Settings\[user_id]\Local Settings\Application Data\Microsoft\Outlook". I renamed it and restarted Outlook, which then rebuilt my OST file from the Exchange Server. The new version was about 7MB smaller than the old one (103MB) but I seemed to have everything -- including some old tasks that suddenly reappeared from the twilight zone. I then ran my series of Outlook clean-up switches [9]

/cleandmrecords
Deletes the logging records saved when a manager or a delegate declines a meeting.
/cleanfreebusy
Clears and regenerates free/busy information. This switch can only be used when you are able to connect to your Microsoft Exchange server.
/cleanprofile
Removes invalid profile keys and recreates default registry keys where applicable.
/cleanreminders
Clears and regenerates reminders.
/resetfolders
Restores missing folders for the default delivery location.

DANGER (don't run this one unless you need it):
/resetnavpane
Clears and regenerates the Navigation Pane for the current profile. This will vaporize your Outlook Shortcut pane

When all was done I restarted WDS and had it rebuild its index from scratch, then I set my Palm sync to have Outlook overwrite the Palm.

Another fun lunchtime with Microsoft ...

------------- footnotes --------------------

[1]I removed my cache to free up enough space to run defrag, and when I restored a fixed 2GB cache the system asked if I wanted to delete an old pagefile.sys. Then my free space reappeared. A new 160GB high speed drive is on order.

[2] XP won't defrag when free space is less than 15%. OS X is much less prone to serious fragmentation.

[3] Still, it's much better than its predecessor.

[4] XP has the world's best blog writer, Windows Live Writer, but XP's corporate-friendly blog readers are very weak - and getting worse. Onfolio was the best, but Microsoft has left it to fester post acquisition. I fear it's becoming increasingly unsafe. OS X has the opposite problem -- lousy authoring tools, great readers. Of course OS X can also run WLW in a VM ...

[5] Really, I need all this stuff. But WDS is trying to index 4GB of Outlook and hundreds of thousands of system files.

[6] If you're not a Palm addict, I beg you, don't start. Life with Palm and Outlook/Exchange is like juggling antimatter, and it gets worse all the time.

[7] Ok, so this is another straw on that broken back. I am very suspicious of that plug-in and how it impacts Outlook/Exchange behavior with an unreliable network.

[8] This is typical of whenever I regenerate Outlook's OST file. Something old always reappears, it's never been important. Bugs.

[9] I do them one at a time exiting Outlook after each one.

[10] Outlook 2003's Shorcut pane is a "pain in the ***". So dumb, yet so essential in a complex Outlook configuration.

[11] This is why WDS is not an option.

[12] This is the default setting, but I always change it. Not this time apparently.

Update 9/28/07: Wow. Microsoft is in such bad shape. After all of the above I discovered Windows Desktop Search wasn't working properly -- in ways to diverse and complex to document here.

I found that Microsoft has two somewhat different products they call "Windows Desktop Search". If you Google on WDS you will find the product they aim at the corporate sector. Don't get that version (so called "3.1").

I ended up uninstalling WDS-Corporate-individual user 3.1 I installed the version you get with Windows Live toolbar..

1. Install Windows Live Toolbar
2. This should install the right version of WDS. If not use "toolbar options" and "install buttons" to find and download WDS...

The version number of the "good" WDS looks like an IP address ...

Update 10/23/07: The saga continued with some improvements as noted above, but then the flakiness returned. In particular Outlook would exit with a hung process, and I'd lose network access. My employer has larded up my system with various inventory services, but, mercifully, does let me disable services. I kept working through the list, disabling various XP services but with little impact. I reviewed my list installed software, and uninstalled various apps I don't use. That' when I noticed a very suspicious Yahoo updater (don't you hate that every damned app has its own update infrastructure?) -- removing that did seem to help my startup time!

The error frequency grew, and it became apparent there was a hardware component to the debacle -- one that wasn't showing up in XP's event logs.

I hate hardware failures -- especially those the OS can't detect.

I replaced the hard drive on the general principle that drive failures are common. If that doesn't work it's time to test memory and even the video memory.

Windows Live Writer: Firefox integration

There's a Firefox extension that allows you to  "Blog This to Windows Live Writer". It works very well with Microsoft's unequalled blog authoring tool, I've been using it for months now, but these usage instructions are handy:

The Blog This gesture is available in two places: the toolbar button, and the right-click menu. I tried to be a little smart about what you are trying to blog. If you have a selection active in the browser, it’ll be used for the contents of your post. If you right-click on an image or link and select Blog This, that’s what’ll be used.

The "announcement" post this came from was reposted in error today -- the original came out last year. Even so, it's a good reminder of this terrific extension. The odd thing is that Microsoft offers it at all -- WLW is so good it could have forced me (very reluctantly) to switch to IE [1]. On the Mac WLW is threatening to force me to run FF/WLW within an Win2K VM!

Here's the download link for the released version. As I've noted before I used to have problems making it work, but they went away ...

[1] I only have two nits with WLW. One is that it's a modern .NET app, so it's slow to launch on all but the fastest machines and uses a lot of memory. Secondly, it quits after use, or stays open with the post remaining. I'd rather after each post it stayed resident but closed the post window -- in part because it's so slow to launch. (Maybe that's one nit?)