Christmas 2010?22 Dec, 2016
I wrote this six years ago. Flip 2010 for 2016!
So, the veg. are done, the table is laid, the turkey a-ready: I can now sit down and wish my readers a very merry Christmas and happy holidays! You three make my day, and I run this site just for you guys.
Here’s hoping for a splendiferous 2011 for us all (and let’s face it, it can’t be any worse than 2010, surely??!)
Merry Christmas one and all. Here’s hoping for better days ahead.
New Macs, function key strips30 Aug, 2016
By most measures, Apple is well overdue a refresh of its Mac and MacBook lines: 2016 has seen nothing on that score, and the latest press event announced for next week doesn’t really tell us any more. One of the more persistent rumours for the new machines, whenever they may turn up, states that the row of function keys on the new MacBooks will be replaced by some kind of context-sensitive “touch strip”
Sweet baby Moses, if this is true then I hope to all that is holy that Apple know what they’re doing. Anyone who uses Lenovo hardware will recall the (justified) screams that greeted the Carbon X1. Here’s a reminder:
My goodness but that was an aberration.
VMWare Fusion tip: drag n drop21 Jul, 2016
I have a recurring, not to mention infuriating, issue with Fusion which has existed since I started using the software in those heady beta days (2007?). To wit: drag n drop from the host to the guest OS just stops working for no apparent reason. Occasionally, this extends to copy and paste too. One way to address this is to restart the VM (bah!) or when it gets really bad, repair the VMWare Tools installation. Nasty.
When the problem happened again today, I decided to dig a little deeper, and found fragments of commands in various web pages / discussion fora. This pair of commands does the trick for me, so I’m posting here in the hope I find them again (this tip is for when using a Windows guest):
- Open the Windows command line as an administrator (important that) and issue this to blat VMWare Tools for now: taskkill /F /IM vmtoolsd.exe
- Now issue this command (doesn’t need to be as an administrator): "C:\Program Files\VMware\VMware Tools\vmtoolsd.exe" -n vmusr (you may need to adjust this for your VMWare Tools installation, although that is the default location).
And there you have it: basically a forced restart of the VMWare Tools layer.