enjoylife's Stuff

A workaround for no x64 SendToOneNote Print Driver

I just got this from Bruce on the OneNote Test team:

It's not optimal, but it does work. I use it here at Microsoft on my Vista x64 machine.

1. Install one of the many converter programs that will allow you to output images files when you “Print”. For example, I’ve played with http://www.print-driver.com/howto/msn_pdf_to_jpg.html 
2. Open your file in the native application (ie Adobe Reader, PowerPoint, etc)
3. Print to the new printer, outputting to TIFF (multipage color)(the defaults for the example program above work just fine)
4. Boot OneNote
5. Insert | Picture and choose the TIFF image file

Done! You can now take notes over your inserted images. I should note that we won’t OCR the images (it uses the same print driver that doesn’t install under x64), so you won’t be able to search for words in the images or copy–and-paste their content. You will be able to take notes over them, view them, and so on.

Bruce

As David wrote we are aware of this problem and there will be no fix for OneNote 2007 and we plan to address this in the next version of OneNote.  I just wanted to share this with everyone!

I love the Drupal CMS. One of my favorite features of Drupal is the ability to do a multisite install. This site and my other blog, i <3 stella, are hosted on the same box, using the same Drupal install. Several sites can share one codebase. Updates are easily rolled out to every site simultaneously. Overall, it's a wonderful idea. But I have some problems with the implementation...

The standard way to set up a multisite install is to point each of the domain names at the Drupal install folder and let Drupal sort out which domain each request is coming from. It does a good job, too. But this method introduces some complications. For example, any content uploaded to site a is accessible from site b. A user that visits http://site1.com/myimage.jpg will find the same image as she finds at http://site2.com/myimage.jpg. Websites can't have domain specific .htaccess or robots.txt files either, which might hurt search engine optimization of individual sites.

An interesting side effect of this is if you want to install something in a subdirectory of your site, for example a WordPress blog at http://site1.com/blog, that exact same WordPress blog will exist in its full glory at http://site2.com/blog...

Another, and perhaps more grave, problem is that all that stands between the interweb and your very own personal settings is an .htaccess file. Install scripts, includes, site configurations and database passwords are in web accessible directories, and that is never a good thing.

We'll look at one solution to these problems.

I assume here that you are using Linux hosting, that you have shell access, and that you have at least a passing acquaintance with symlinks. If you're looking for a webhost that meets these requirements, check out 1and1 shared hosting. I've been happy with them, and all of their packages above $9.99/mo will do what you need.

Microsoft/IIS guys, you can't do a symlink. You're looking for something called a junction... good luck with that.