19 August 2016
It’s been a miserable summer at the TreeHouse – hot, sticky, muggy, but little or no rain, so we’re officially in an “extreme drought” northeast of Boston, and our lawn looks like it! We’ve sworn off pouring treated drinking water onto our lawn for a number of years, and in past years it hadn’t been a problem. But this year, it’s a problem. Most of our lawn is now brown, except for the southwest corner that got the benefit of a failed flower-sprinkler-timer that shut on and didn’t shut off over a five-day period that we were up in Maine. The sprinkler timer was supposed to water the marigolds that line the front walk for 90 minutes every two days via a couple of soaker hoses that run along the front walk on either side. The southwest corner of the lawn was under water when we finally got home, and that area has endured while all the rest of the lawn went crunchy long ago.
The muggy heat has put a crimp in my ability to do much yard work either, so the shrubs along the front of the house are in extreme need of trimming too, but that won’t happen until I can bring the electric hedge trimmer back down from Maine. Maybe in two weekends. Sigh!
Woburn has a enacted a voluntary water ban (don’t water on Mondays, Wednesdays, or Fridays). The only watering we do is for flowers; 2 hours on the raised flowerbeds out back once every five days, one minute of the drip system on the deck each morning for the four hanging plants, and occasional watering of the front walk marigolds when they look like they need it. The raised-bed watering also nourishes the Concord grape vine on the pergola so it’s flourishing. I’ll have to start keeping an eye one the grapes now to make sure I harvest them after they ripen but before the birds get to them. I misjudged last year and didn’t get any harvest. I assume the birds enjoyed them.
(click on thumbnails to see full-size images)
12 JUNE 2016
A couple of hundred years ago I started a Mother’s Day tradition at the house in Woburn… the girls (at ages 7 and 9, with help and guidance from Dad) would plant “Yellow Boy” marigolds all along the curved front walkway. We’d plant them on Mother’s Day (much to the occasional rainy-day chagrin of the girls) and Mom got to do whatever she wanted while we worked. She usually sat in the shade, sipped her coffee, and offered occasional advice to the workers and the “knows-nothing-about-gardening” supervisor. Sold in flats of 48 plants each, and spaced at 6 inches apart, it took a little over four flats (192+ individual plants) to trim the entire walkway.
I continued the tradition as long as I could, but as the girls grew up and went off to college and one got married, scheduling the planting event on Mother’s Day became harder and harder. Eventually Lynn and I picked up the grunt work from the girls, which meant we could postpone the actual planting by a few weeks to avoid the late spring frost troll that occasionally showed up, trying to kill uncovered early plantings around Mother’s Day and the few weeks after. The 90+ feet of bright yellow marigolds became a neighborhood landmark over the years. We would have perfect strangers stop and chat while we were planting, telling us how much they enjoyed and appreciated the look of the yellow border. One unrecognized neighbor thanked us for planting such a stunning display as he often used it when giving directions to his house… “Take a right at the house with a gazillion yellow flowers along their front walk…”
Last year was an aberration. Lynn was in recovery mode from the accident, and I had a few more “ODARs” (Other Duties As Required) on my To-Do list associated with the recovery period, so we skipped the annual planning tradition and just mulched the empty flower-beds along the walkway; nothing got planted.
This year we resumed the tradition. Lynn found a couple of flats of “Yellow Boy” marigolds at the local garden center last week (a bit late in the season for whole flats, that’s usually an earlier-in-the-season option) so she grabbed them. I weeded and raked and sifted the flower-beds Saturday and early Sunday to remove the weeds and the ever-present pebbles and stones, and we set up an assembly line Sunday afternoon. With Lynn’s bad ankle and my bad knee we were a lot slower than usual, but we made up for it by spacing the plants 12 inches apart instead of the usual 6, so it was half as many marigolds and half as much work (yeah, right!). At this stage of growth they look more like runway landing lights than plants (see the image at the top of this blog entry for this year’s photo right after planting), but time improves them! The photo at the right is a shot taken in 2010 to show what the marigolds WILL look like after a month or so of growth.
We have 2.6 acres of land at the house up in Maine, with a LOT of trees, so I acquired a refurbished Homelite ZR10568 42cc 16-Inch Gas Chain Saw a few years ago for use up north to keep the trees in check. I’ve used it to clear out whole trees to expose a pair of nicely-shaped spruce Christmas Trees on the edge of the lawn in back, and I’m forever trimming the fast-growing white pines that are all over the meadow that used to be a grazing field for sheep many years ago.
But last February at the TreeHouse in Woburn, a mini-blizzard dropped a good-sized tree of the “willow” variety (not a weeping willow, a regular willow with buds that look like pussy willow buds). The tree itself was on the very edge of our neighbor’s land, growing right by the brook in our back yard. It fell across the brook and square into our yard, thankfully missing our pergola that sits in the raised flowerbeds and supports the Concord grape vine that sprawls over it and provides shade in the summer and fruit in the fall. However, the fallen tree did clip a few branches off the birch tree we’ve been encouraging for the past fifteen years or so and deposited the broken top of the willow in our giant arborvitae bushes/trees, remnants of the privacy bushes that used to hide the above-ground swimming pool that was where the pergola and raised beds are now.
Massachusetts (and most state) property law says that a neighbor’s tree that falls in my yard becomes MY tree – and my responsibility – so it was up to me to get rid of the now-horizontal trespasser. Ordinarily that would be a straightforward task, but this tree was also engulfed in Celastrus orbiculatus– invasive bittersweet vines, so I had to remove the knurled twisted tangle of sinews that covered the entire tree before being able to get the chainsaw anywhere near the trunk.
I spent three non-consecutive weekends cutting the knotted tangled bittersweet vines away from the fallen tree, packing my multi-bushel-sized bicycle-wheeled garden cart head-high with the pieces – so high I needed to cinch a strap around them to keep the pile from toppling out of the cart. After more than twenty runs to the community compost pile in the woods, I was ready to attack the tree itself. The top of the tree had broken off and was still hung up in the arborvitae, and it wasn’t going to be extricated by a single person, so I ignored that and attacked what I could with the 16″ chainsaw.
Serendipitously, newly-engaged daughter Audrey is beginning to pull together her plans for the wedding and reception (to be held in October 2017). She is planning a rustic wedding theme (outdoor wedding, reception in a barn, etc.) so she saw the felled tree as an opportunity to make, rather than buy, table centerpiece bases and a cake platform out of round thin-ish slices of the tree trunk. Running a chain saw is fun, so I sliced up 14-15 1″ thick slices of the tree – bark and all – for her to sand a bit and polyurethane. We also did a 3″ thick slice as a potential cake platform. It may not work out, but it will look way cool if it does, and costs next-to-nothing to try!
Once I had de-brushed the trunk and cut up as much of it as I could with my “light-duty” saw, I called on a friend to bring his industrial-strength 20″ chain saw and assorted equipment (ropes, come-along, peavey hook, etc.) to help me get the tree top out of the arborvitae and slice up the remaining main trunk. We threaded a long rope through the branches of the hung-up treetop, splayed out the ends of the rope about 40-50 feet out away from the treetop, and PULLED! Down it came out of the arborvitae, and we pulled it away from the work area to attack later. Then he fired up his bigger chain saw and attacked what was left of the trunk. He was able to cut up manageable pieces back to the middle of the brook (still enough water in the brook to impede a complete removal) which I stacked under a tarp to dry. Should have close to a half-cord of firewood once split. Willow is a light wood that burns quickly so it’s not much good for heating with, but would make great outdoor fire-pit fuel.
The final work involves clearing out the rest of the bittersweet vine and cutting up the smaller but long logs into shorter chunks suitable for stacking and/or burning. To assist with that I built a sawbuck that has been on my to-do list since I bought the chainsaw – five 8-ft PT 2x4s, three 5″ long 1/2″ bolts, six 1/2″ nuts, six 1/2″ washers, 24 3-1/2″ wood screws, and a couple of hours last Saturday with my miter saw and a drill. $45 in materials… almost as much as what the chainsaw cost me!
EPILOG – 17 April
And finally done! Cutting up the remaining bittersweet vines and remaining tree parts took longer than I’d like, but I finished up today. It looks a lot better than it did that first day I started hacking away at the mess. I even vacuumed up the little chainsaw chips left from cutting up the tree parts. The neighbors must’ve thought I was off my rocker!
As usual, I take pictures as I attack new projects like this, so the whole set (including some of the linked-to photos in this blog post) are in a Flickr “Album” titled 20160227-Downed Tree Removal.
We use Amazon Christmas lists in our family, but I’m not very good at keeping them up to date or remembering to put stuff I want on the list. This year I remembered to put something on my list I had been interested in experimenting with for a few years; A Raspberry Pi. What is a Raspberry Pi, you ask? The Raspberry Pi is a credit-card-sized single board computer that plugs into your TV or monitor and can accommodate a keyboard and mouse, and a lot more. This is a little computer that can be used for many of the things that a desktop PC does. The design is based on Broadcom BCM2836 system on a chip with a 900MHz ARM Cortex-A7 quad core processor, Dual Core VideoCore IV Multimedia coprocessor and 1GB RAM. This board is powered from a 5V micro-USB adapter and runs various operating systems such as Raspbian, RaspBMC, Arch Linux, RISC OS, OpenELEC, Pidora and Microsoft Windows 10(!).
Megan and Dan bought me the Raspberry Pi 2 Model B starter kit for Christmas. It came with a credit-card-sized motherboard, a clear plastic case, and a micro-USB power supply (the same kind of power supply you use to charge an Android phone). With the motherboard in the case, it slips easily into a shirt pocket. In addition to all the circuitry for the computer (CPU chip, 1GB memory, audio, graphics, etc.), this tiny motherboard has a power connector port, four USB2 ports, an RJ-45 Ethernet port, an audio-out port, an HDMI graphics out port, a CSI (Camera Serial Interface) in port, a DSI (Display Serial Interface) in/out port (for use with touch-screens), a long bar of places to connect various other controllers and sensors, and a micro-SD port for memory/data storage.
I made the silly assumption that there was a “BIOS” on the board, but when I hooked up a keyboard, a mouse, a 32-inch Hi-Def HDMI TV, an Ethernet cable, and powered it up… nothing! So I did a little more research. It turns out you need to hard-format a micro-SD card (I had a spare 4GB card, the bare minimum required) and pre-load the NOOBS (“New Out Of Box Software”) bootstrap loader on the card, then run NOOBS and use it to install any one of a number of graphical OSes onto the card. A 4 GB micro-SD card only had room for the Spartan RISC OS for Pi. A bigger card will give me more options (Raspian, Linux – a bunch of flavors, even Windows 10!) so I may pick up a few cards and try more than one OS.
Once the micro-SD card was prepped, it booted up into NOOBS, presented a list of possible graphical OSes available over the internet, and let me choose any of the OSes that would fit on the installed micro-SD card (of which there was only one; RISC OS for Pi). I installed RISC OS for Pi by downloading it directly over the internet to the micro-SD card in the Raspberry Pi.
Next step will be to pick up a few more micro-SD cards to try other OSes, and then experiment with adding components that can sense conditions (cameras, touch-screens, RFID proximity, accelerometer, temperature, clocks, etc.) and write some code that will respond to sensor inputs. Fun!
UPDATE 1 (30 DEC 2015)
I went out and bought a couple of 32GB micro-SD cards, loaded the full-featured Raspbian OS on one of them. Raspbian (a version of Linux based on Debian) is the Raspberry Pi Foundation’s official supported operating system, and comes pre-installed with plenty of software for education, programming and general use. It has Python, Scratch, Sonic Pi, Java, Mathematica and more.
On the other card I loaded Windows 10 IoT Core For Raspberry Pi 2. The “IoT” stands for “Internet of Things,” where little limited-function gadgets are connected to the Internet and can be monitored and controlled by dedicated small computers (like a Raspberry Pi!). THAT is the real reason I wanted to experiment with a Raspberry Pi; to build my own controllers for dedicated devices (a weather station, or a temperature alert system, or a synchronized lights-and-music controller, or…).
We’re up in Maine, spending the anniversary of the accident at the scene of the crime, so to speak. The actual anniversary is today (Sunday, November 1st), but Lynn wanted to drive (not be driven) to the scene of the accident yesterday, and then visit the Pen Bay emergency room where the people who took care of her that night do their magic every day.
We made a celebratory day of it, and took a roundabout route up to Rockport, driving up Rte. 235 past Seven Tree Pond, then zigging left on Rte. 17 for a bit, then zagging right onto Rte. 131 for a bit, and then a left onto Butler Road which sort of parallels Rte. 131 but is an occasional dirt road through blueberry country, which develops a deep red color this time of year. We saw them burning the blueberry fields with a mechanical dragon towed behind a tractor. We passed through a village called Appleton Ridge (not on most maps) to Searsmont and stopped at the Fraternity Village General Store / coffee shop / bakery / pizza parlor / liquor store. From there we doubled back on Rte. 131 a bit to Rte. 105 through Hope (how appropriate), past Megunticook Lake, and into Camden, where we headed north a bit on Rte. 1 to Mt. Battie State Forest and drove up Mt. Battie Road to the lookout point at the top of the “mountain” (more like a hill; elev. 846 ft.) and the view of Camden town below. By then it was 4pm, so we drove to the Reny’s discount department store in Camden, which is where Lynn stopped to do some shopping just before the accident. We did the same.
Lynn took over the wheel from there and drove south on Rte. 1 to the right turn onto Rte. 90 west, drove a few miles and then pulled into the parking lot of the antique shop next to the Yankee Stripper furniture refinishing shop. It was just past that parking lot that the accident had taken place. We sat in the car in the parking lot for a few minutes, talking about what it felt like to Lynn to be back at the spot.
Then we went back to Rte. 1, continued south for a few miles, stopped at the Dunkin’ Donuts shop in the Sunoco Station and bought a “Box o’ Joe,” a dozen donuts and a dozen muffins, and headed across Rte. 1 to the Pen Bay Medical Center where the emergency room is where Lynn was taken first, before being transported to the Maine Medical Trauma Center in Portland. It was that first stop that Lynn remembers most.
Luckily, it was quiet in the emergency room. We walked in and a woman in the waiting room immediately started trying to get us to give her a donut. We ignored her. We explained to the receptionist who we were and why we were there, so she called back and got permission for us to go back to the nurses’ station in the emergency room, where we talked to a bunch of folks. I got to meet “Kelley” who was the one who called me at home in Woburn and gave the perfect delivery of bad news like that. A goodly number of the staff remembered Lynn and that night, and Lynn got to meet “Matt,” the nurse she remembered as being so kind and caring and who focused on her the whole time. There were more than a few moist eyes, and exclamations of how great it was to see a former patient doing so well, and how that they hardly ever get to see or hear about how a former patient is doing. We didn’t stay long, but long enough to convey our profound thanks for the work they do in general and the work they did that night in particular.
We had made previous arrangements with Lynn’s sister Marcia and her husband Tom (who live in the area and were with Lynn in the emergency room that night) to meet at a new Scottish Pub in Camden – “The Drouthy Bear” – at 6:30 for a bite to eat (Lynn’s family is 110% Scottish – Munroe and Taylor). We were ahead of schedule so we drove downtown to the harbor parking lot by the docks and sat and looked out at the lobster boats and winterized wind-jammers for a while before heading up to the pub. The Drouthy Bear offers about 35 single malts from all the regions of Scotland, plus another 6 or so blended scotch whiskies, and some American whiskies, and they serve them in patented Glencairn whisky-tasting glasses (hard to find in the States, but ubiquitous in Scotland; we brought some home from our 2013 trip)!!
It was a symbolic “closing of the book” for the year for Lynn. She’s ready to move on.
Back in November 2012 I blogged about installing the new Windows 8® on my laptop and the experience of the installation and getting used to the new operating system (often referred to as an “OS”). Here I am now blogging about doing the same thing with the new Windows 10®!
Windows 10® was released to the unwashed hordes on 29 July 2015 with much media-generated fanfare, and it was (and still is, until 29 July 2016) FREE to anyone with a machine running an authenticated “genuine” (as opposed to pirated) copy of Windows 8.x® or 7®. Most of all, Windows 10® was going to be Microsoft’s tail-between-the-legs apologetic offering to the unwashed hordes to try to make amends for the largest business faux-pas since the Edsel (if you believed the media punditz); abandoning the START button.
To be sure, Windows 8® was significantly different from Windows 7® – 8 was the first mass-produced OS designed to work with new-fangled touch-screen devices, AS WELL AS old-fangled mouse-and-keyboard machines. It was going to revolutionize the computer industry; the first OS that would run on all sorts of platforms – desktops, laptops, tablets, phones, touch-screen, non-touch-screen, keyboard- and mouse-based machines, point-and-swipe machines, all of them. But it left off the START button (insert wailing and gnashing of teeth here)!!
The START button – as everyone in the known universe knows – was a button in the lower left of the computer screen (sometimes rectangular, sometimes round) that, when clicked on with a mouse pointer, popped up a sometimes cascading menu (cleverly called the START Menu) of programs that were installed on the computer and could be run by clicking on the program name and/or icon in the menu. It was first introduced with Windows 95® in August 1995.
It should be noted here that while the START Menu was displayed, the user could do nothing else with the computer except navigate the START Menu or click on a single item in the menu to start that program running. Clicking anywhere OUTSIDE the START Menu caused the START Menu to immediately vanish. While the START Menu was on-screen the user could see what had been displayed previously (except for the stuff that was occluded by the START Menu), but the user couldn’t get to it or interact with it without causing the START Menu to vanish.
But Windows 8® – the scourge of all Windows users everywhere (according to the media) – took that away… but not really!! The START Button (which started out rectangular in Windows 95®, changed to circular in Windows Vista®, and changed again to trapezoidal in Windows 8®) WAS STILL THERE, only instead of popping up a vertical cascading START Menu that occluded some of the desktop and vanished at the first click, it brought up a full-screen scrollable START Menu with square chicklet-like boxes for each program that was installed on the computer; same function, different look. The user had the configuration choice of two (sometimes three) box sizes, so youngsters with sharp young eyes could make the boxes tiny and get more of them on the screen at a time, while older people with bifocals could make the boxes bigger and easier to read.
Windows 8® removed the START Button from the screen, but made use of the previously-ignored keyboard button that has a “Windows” logo on it that started appearing on keyboards about ten years ago. Pre-Windows 8®, pressing that keyboard button was yet another way to open the cascading START Menu. With the advent of Windows 8®, pressing that physical button with your finger (instead of clicking that virtual button with your mouse pointer) would cause the screen to switch to the full-screen START menu. HOWEVER… the media-fanned public outcry over the removal of the START button on the screen was so incessant that Microsoft brought the virtual START button back with the Windows 8.1® release/upgrade. But that wasn’t enough for the unwashed hordes.
I too was confused and discombobulated by the lack of a START Button in Windows 8® – for about 20 seconds. It took me longer (about 2 minutes) to figure out where they had hidden the entry to the Control Panel! I can only conclude (and I have plentiful examples to back up my conclusion) that 99.44% of the computer-using public is violently allergic to change of any kind! Get over it folks!
Windows 10® brings back the START Button (in the lower left where it evidently belongs, and shaped like a trapezoid like it did in Windows 8.1®), and it pops up the START Menu, occluding some (or most) of what was on the screen, just like everyone (except me) longed for! Oh, by the way, the START Menu looks more like a miniature version of the START Screen, with little chicklet boxes for each program, and users can arrange them to their liking and resize them to their liking, like they could with Windows 8.X® if they bothered to learn about it, but that seems to be okay now. The media-led choruses of Halleluiah (that the START Button is back) have been sung since the preview copies were released almost a year ago. I will never understand.
Anyway, my upgrade to Windows 10® was done yesterday and was almost flawless, only a couple of minor hiccups. Microsoft had loaded a “reservation” tool on Windows 8.1® machines during a pre-July monthly update. The tool allowed the user to “reserve” their free copy of Windows 10® prior to the release date, with the reservation tool doing an authenticity check for the existing OS and a compatibility check against the system’s hardware and installed software before announcing that a copy “had been reserved” for this machine. It is projected that there are a billion and a half machines “in the wild” worldwide that qualify for a free copy of Windows 10®, so Microsoft staged the downloads so as not to bring their servers – and the entire internet – to it’s knees. I “reserved” my copy as soon as I saw the reservation tool on my machine. July 29th came and went; I guess I wasn’t going to be in the first wave. Just as well, as we were traveling in Montana on the 29th – I didn’t want to do the upgrade from a hotel room.
Once we returned home I started getting impatient. I poked at the “reservation” tool every few days to see if anything had changed. Mid-last-week I noticed what appeared to be a new link on the “reservation” tool’s screen – a “frequently asked questions” link – and the first question’s answer alluded to a downloadable “Media Creation Tool” that would let you do one of two things; download an installable copy of Windows 10® that would need a valid license before installing, or… kick off an immediate installation on a previously authenticated machine without waiting for Microsoft to decide it was “your turn.” You can guess which option I chose.
Using my copy of Acronis True Image 2015, I cloned a copy of my laptop’s hard drive onto a spare laptop hard drive to preserve my machine in case there was a problem, then kicked off the upgrade!
The upgrade took about 90 minutes, in twelve phases; Downloading Windows 10, Verifying Your Download, Creating Windows 10 Media, Getting Updates, Getting A Few Things Ready, License Terms, Getting Updates (again), Making Sure You’re Ready To Install, What Needs Your Attention, Ready To Install, Installing Windows 10, Upgrading Windows (yet a third time), and Login (I took screen snaps along the way).
The What Needs Your Attention phase told me about the first hiccup – two problems I had. One I had to fix and the other I had to agree to. It told me my copy of Symantec Endpoint Protection (my virus scanning software) was incompatible with Windows 10® and had to be uninstalled, and it told me that my paid-for copy of Windows Media Center (*not* Windows Media Player) is not available in Windows 10.
Once I logged in, all my desktop icons were there, my desktop background images were in place and displayed, my apps were all there (except for Symantec Endpoint Protection and Windows Media Center, obviously), and they all seemed to be working! The last hiccup was familiar from my upgrade to Windows 8® from Windows 7® back in 2012 – my speakers were silent; no sound. Once I found the Control Panel (they moved it again) I checked all the sound-related device drivers; all were listed as functioning and up-to-date. I begged to differ. I popped over to the Dell web site (using the new browser, Windows Edge) and sure enough the hardware on this 5-year-old Latitude 6420 got misidentified again by Microsoft’s OS installation routines. I downloaded the correct drivers, installed them, and VOILA! Sound!
And oh, by the way, this was the first time since I started down this road with my first personal computer over 30 years ago that a “whole-number” OS version upgrade (DOS2-to-DOS3, 95-to-“ME”, “Vista”-to-7, etc.) didn’t involve a wipe of the C drive, starting fresh and having to reinstall all my application programs all over again! Instead of a 2-3 DAY process, it took two hours, and I just watched! Dee-lightful!
So I’m spending time finding old things (like the Control Panel) learning new things (like the multi-desktop feature and the new browser – I like them both!) and slowly rearranging the chicklets on the new/old/restored START Menu. I declare it a winner, but what do I know? I declared Windows 8® a winner!