I haven't posted much about OneNote, which is very rude of me seeing it'd just about running my life, and has been for the past year and a half.

For those who don't know what it is, imagine that well used, probably slightly beaten up notebook that you carry around in your hand/man bag/ rucksack.  Now put that in your computer, let it be indexed and searchable (both inside the product and using windows desktop search/Vista search), sprinkle in some natty features like screen grab and you have a very neat little product.

It comes, as with most Microsoft Office products, with a lot of  out of the box templates for you to get going pretty quickly.

Content it broken up into notebooks, sections and tabs (yes that's three areas to manage).  This can be a bit daunting and can take some time to get used to.  You may even need to start shifting items around.  Thankfully this is really easily done with dragging tabs and sections into different notebooks.   It also provides an un-filed section for those quick phone messages or discussions that may not initially fit anywhere.

A nice add-on for this brings in one technology that I'm really loving at the moment is called Xiipy (Xiipy Desktop Edition for Microsoft OneNote 2007).  IT builds on the product by analysing and searching content automatically, providing an integrated interface, resourcing previews and (the one I like!) Tag Clouds.  It looks pretty good, and would be worth downloading the beta.

I'll let you know more after I've had a deeper look...

Firstly Muppets are great and my use of their great name as a slur is unforgivable.  I apologise to any Muppets reading the post for such abuse, and the assumption that they would make such a dumb mistake...

Anyway

Working on a doc yesterday I pulled together some useful factoids about App Pools and Web Apps within the wonder that is Moss 2007... cue end of the working day and a such down of all apps, including Word.  Techno-Spidey senses should have tingled at this point, to notify me that I DIDN'T PUSH THE SAVE BUTTON!!

Cue this morning, I enter the office, in my blissful state of ingorance, looking forward to the joy of writing up a Moss Design.  I open word... "oh, what's that recovered file pane doing there? I'm sure it's nothing... File > Exit"... continue with happy existence.

An hour and half later...

Oh, crap!!! I never saved that file yesterday!!!  Oh crap I said I didn't want to keep that recovered doc this morning!!!  Oh crap, I've deleted the reference to the core material... aaarrrrrggggghhhhhh, where's the nearest window?

But wait Microsoft has decided that there are some out there that go beyond normal Muppet-dom (sorry), and they have entered, the Mental-Muppet zone (do, do, do, dooo, do, do, do, dooo... sorry, again).  That trusty little file doesn't get deleted, but moved to the recycle bin... Here's how to recover...

1. Go to your recycle bin.
2. Right Mouse click the file (this will have an ASF extension, and probably something like document 1 as the file name if it hasn't been saved) and select recover.
3. Go to C:\Users\[username]\AppData\Roaming\Microsoft\Word - and there's your recovered file!! (Woo and indeed, Hoo).
4. Open up Notepad
5. Drag file into notepad...
6. Et Voila, you become French, no, wait, you can view the content of that file.

A few things to note:

• Word cannot natively open an ASF file... that I can tell (i.e. file, open, [filename].asf doesn't work!).
• The locate of your ASF file will depend on your recovery options - go to Office Opal () > Word options > Save and you will find the Auto Recover Option.
• The file when opened in Notepad will have some rubbish in there but your content will be there.
• Depending on when the last auto recover ran you still may not get all your data back.  Auto Save options can be configured at the menus in point 2.

Just for reference here's the (unedited) content, for those interested/bored/suffer from insomnia.

you require a large number of Out of the Box web applications that are running no custom code then assigning Multiple Web Applications to Application Pools will enable an efficient use of resources on a physical server.  There are some cases that this will not be recommended for use:
Where custom code is being ran within an environment.
Where security exploits become apparent, everything running on that app pool will be affected.
Custom code will be run within an Application Pool along with out of the box code.  If the custom code fails or contains an unknown bug this will then affect all code running within the Application Pool and therefore all SharePoint Sites running within the Web Application.  Where Custom code is required within a solution, it is recommended that this run within its own Application Pool.  If there are any issues then within that Application Pool then it will only affect that Web Application.
Recommendation are that you should not run more than 10 web apps per app pools, and run more than 20 web apps per physical server.
Web Gardens are created when more than one worker processes are defined within an Application Pool.  It is recommended that a web garden is defined where the more than one Web Application is ran within one Application Pool.  This enables the Application Pool to provision more resources when necessary – this is especially the case when STSADM is ran within an environment as this will lock one thread for its use.
As Application Pools are resource intensive (primarily physical memory) the number of app pools will be determined by the number of resources on the physical server.  An Application Pools will take at least 100mb to 500mb.  A recommended number is a maximum of 10.  This means that a total of 5Gb would be required to run with