First of all, thanks for your help simonduz in making the Text/HTML metaPost provider a solution that can work for everyone.  I'm committed to designing and supporting a product that works for the entire DNN community regardless of which edition is being used.

I'll address the questions above in order:

1) Windows Live Writer is able to pick up the styles for your site, which can be a nice feature if you have a fixed width border around the region where your content will be added.  I designed the Text/HTML provider so that you can specify a Text/HTML module that WLW will use during setup to try to determine the styles and template from your site.  Basically, WLW will write a test entry into this Text/HTML module and then "read" the page (this all has to be done on the home page) in order to determine where on the page the content is being added.  In the video I tried to demonstrate these steps which are necessary for this process to work:

• Add a new Text/HTML module to the home page (Just temporarily)
• Go to Settings for the module and disable caching (I believe this is in Page Options)
• Make sure the account you will use through WLW has edit access to this page!  I probably left this out of the video.  Argh!  I'll have to recreate the video if that's the case, because this is important.
• While you're in the settings, note the moduleID for this text module.  You'll see it in the address of the page.  This moduleID will be used as the style id that you can pass as a QueryString parameter to the Posting URL you have to enter in WLW.  If the moduleID for my new module is 650, then I'll add &sid=650 to the end of the posting URL I add when setting up my account in WLW.
• Complete the account setup process in WLW as normal, only with the addition of &sid=650 to the end of the second URL you add in the account setup inside WLW.
• Remove the temporary Text/HTML module.

It's not necessary to go through these additional steps, and if you don't, then the only thing your missing is the ability to see your site style when you hit F11 in WLW.  If you really don't care about seeing the site style while you're editing, you can ignore these steps and just enter a URL such as the following:  http://www.yourportaldomain.com/metapost.ashx?key=text/html 

I should also note that if you've changed the default friendly name of the text/html module, then you'll need to use your custom name instead.  For example, if I've changed the friendly name of text/html to mytext, then the URL I would add in WLW would be:

http://www.yourportaldomain.com/metapost.ashx?key=mytext

2) I bet the fact that I left out the step where you make sure the account used by WLW has edit access to your text/html module is the problem here. 

3) I'll be releasing the Professional Edition soon which will provide complete control over the content that's inserted into the footer of each post. 

Regarding the last issue you raised with the DNN pages as links, I would like to solve this issue if it's something on my end.  Are you using the Ventrian Child Links module?  It sounds pretty annoying to have text/html modules inserted automatically into the page. 

Again, thanks so much for using metaPost and for helping me make this resource the best it can be.  Once we get past some of these intial bugs, I hope you find it to be a resource that saves you time!

Don