Send To OneNote Fix for 64-Bit Available
Over a year ago, we commiserated in your Microsoft OneNote frustrations. A key feature, the “Send to OneNote” function, simply didn’t work if you were running a 64-bit version of Microsoft Windows Vista. We heard from the OneNote team way back then and although I understand the technical challenge involved, it still left a bit of a bad taste in my mouth. Pity too, because I still believe that OneNote is one of the most impressive bits of software to come out of Microsoft.
We later heard of a workaround that involved snapping and sending an image of captured data; the image file was then sent into OneNote. That’s a partial help but the ability to read and convert any text or ink data was lost in translation, i.e.: not ideal.
Yesterday I got a tweet from Bhavishya telling me about a newer workaround that appears to be a far better solution. It’s not perfect, but pretty darn close and should carry OneNote users through the issue until the next release of the software. David Rasumussen developed the solution in his spare time and you can find it right on his blog. Essentially, his code uses Vista’s XPS printer driver and monitors a specific folder for new XPS files. Note that this isn’t an official solution from Microsoft, and as such, isn’t supported by them. Thanks Bhavishya!
Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.
Microsoft was never going to master that technology anyways, they have become a liability more then a assert to America
This ummm makes no sense at all. the ENTIRE world uses their software… how is that a liability?
Wow, thanks for the tip. Just installed it on my vista 64bit HP and it works exactly as advertised. I’ve been looking for a good solution and this will do until MS gets its act together.
Actually, this is not a “pretty decent” solution, it’s a crappy one. See, I used OneNote for school. My professors usually provide a PowerPoint presentation before the class, which I would “send to OneNote”
The whole presentation would appear on a single page and then, during class, I would take notes over the PowerPoint. It was a perfect setup, at least for me.
Then I updated to a 64-bit VAIO and I was shocked to find that the “Send to OneNote” was gone. This new solution would let me import a PowerPoint preso to OneNote but… the preso would come out as one slide per page. This means that a 60 page powerpoint will create 60 tabs, resulting in my notes being all over the place.
I’m still pretty upset at Microsoft. If you read David Rasmussed you’ll get even more upset. He tells you, with a straight face, that the 64-bit driver was too complicated, goes through what seems a long technical explanation (but it’s just a long winded excuse explaining they didn’t feel like doing it now) and that there may be a better solution available with the next version of OneNote. I’m ok with that, as long as I get it for free. Otherwise, having had to pay for OneNote and having to upgrade to get back a feature I already had and lost thanks to an update feels like abuse on the hands of MS.
Try this solution http://onenoteprintdriver.blogspot.com/
It works just like this feature does on 32 bit systems.
what idiot designed this, i feel like i have been stolen from. the sanitized version is that this is crap. what moron would want to print to a file when it should be sent as a cut and paste item with full document sub component cut and paste capability. I urinate on microsoft… and as for those who do not see it… well 50% of the population has an iq below 100…
I purchased the xp pro x64, office suite pro and one note and all say on the cover that they support xp. No distinguishing between x64 and x86, this should be a class action suit. As for the dumb kid that took his own time to give the print setup. His supervisors should be hung.
As for the guy that said MS is a liability. It is, 8x the cost of the software for support. and why because MS and Disney are screwing up the patent office and have to keep changing or… the end of their patents. That is why no compatibility… we used to have code that lasted 20-30 yeas beofe MS. Oh yeah no de-duplication, we already had it. Stupid morons at ibm wanted to sell hardware so they found the most inefficient system around and the morons bought it… and still are… and guess what there is no more money in the kitty to pay for this nonsens and to make it worse MS shipped all the jobs overseas or handed them to H1Bs. Liabilitiy, oh yeah. This is crap… most are just too brain washed… please rinse and economically tumble dry.
Bad monkey
set my windos