Sunday, July 15, 2012

Lost in the Woods / Learning from my Mistakes

In my high school days, I enjoyed hiking a great deal.  Mt. Rainier National Park, the Olympic National Park, and the San Juan Islands (short hikes as we island-hopped aboard a rented sailboat in my youth) were a few favorite areas.  As my weight came on, though, my hiking adventures became less and less frequent.  This summer I've been trying to change that.  Sometimes, though, it's good to just pause and remember some of the basics.


First, here's the somewhat embarrassing account of yesterday's hike--a day in which my daughter and I walked about fourteen miles of trails--including one section of the roundtrip route TWICE.  You can see our route here, if you follow the Walkmeter link.  (To see our last route, go here, and our first adventure is shared in an earlier blog post.)


So, our day began with the four of us (myself, wife, son, and daughter) leaving the Lake Pamelia trailhead and walking into the Willamette National Forest.  Less than three miles later, we stopped and had lunch on the banks of the lake.  Other than the occasional distant rumbles of thunder, it was a pleasant day to be there.  We enjoyed watching a lone duckling traverse up and down the lake in front of us looking for insects and other food sources.


Finishing lunch, my daughter and I decided to hike around to the east side of the lake and see how close we could get to the Pacific Crest Trail.  My wife and son opted to stay behind and relax beside the shaded lake.  We had no concerns about finding them again.  The two of us had a blast as we forded several streams and headed up a steep and narrow trail towards the valley's rim.  Fast forward about an hour later, however, and my wife and son were nowhere to be found when we returned to the lake.  We went to the site where we thought we had left them, but there was no sign of them.  We called out and walked around the lake for a few minutes before mistakenly deciding that they must have returned to the van parked at the trailhead.


Imagine our frustration when we did not find them there an hour later!  Evening was fast approaching now, and there was absolutely no cell service in this area.  (No emergency phone either.)  We picked ourselves back up, and returned to the familiar trail.  Every so often, I'd ask passing hikers if they had seen anyone matching their description, but we had no luck until we almost were back at the lake.  A friendly younger couple remembered seeing them and gave us a general idea of where they were on the lake-- the described location sounding strangely familiar.  


About this time, my fatigue hit hard, and I gave in to Sarah's request to run on ahead and look for the two of them.  I knew this was not a great idea, but, I was exhausted as well as dehydrated (having left most of the drinks in the pack with my wife and son).  Ten minutes later, I plodded out of the forest and to within sight of the lake.  My heart sank, because there was not a sound.  I called loudly into the air, but there was not even a faint response.  


A couple hikers happened along, and I explained the series of events that had taken place.  We decided the best thing for me to do at that time was to sit myself squarely on the main trail in order to ensure we not pass each other in the trees on parallel trails).  They agreed that the trails were less than clear on the west side, and it was easy to get a little turned around.  Just after we had decided that they would go ahead and notify the Detroit Ranger Station, Sarah responded in the distance to one of my calls.


It was with great relief that I saw all three of them appear, heading for my direction in the soft evening light.  I collapsed onto the ground and rested for a while before we undertook the journey back (again).  Where had they gone?  We learned to our astonishment that they had never moved.  It wasn't until that evening that I realized that I must have turned right when I should have turned left when we came back out of the trees at the lake after trying to connect with the Pacific Crest Trail. 


Moral of the story--for newer hikers anyway?  I'd say there are a few that come to mind.  


1.  Invest in backpacker whistles.  Voices just don't carry in the thick woods and brush.  In retrospect, I realized that I called very loudly within probably fifty feet of where my wife and son were sitting, but they didn't hear anything.  (Author Cheryl Strayed writes about using one to discourage a charging bull on the trail, but that's not exactly recommended usage.  I plan to review her book, From Lost to Found, in the near future, by the way.)


2.  Have a plan.  It's best to stay together, but, if you decide to separate temporarily, have a clear plan for re-connecting.  I think our problem was we second-guessed the plan we knew had been in place.  (If you do realize you are truly lost, stay put!)


3.  Before doing something risky (like hiking back), it's best to double check the entire area should you find yourself in a similar situation someday.  If the brush is thick, you may be able to wade out a foot into the lake or stream and check the area from that vantage point, too. 


4.  Ensure you spread around the food and drinks between different people's packs.  Besides balancing weight, this ensures that everyone has emergency drinks available.


5.  Always pack more food and drinks than you think you will need.  Fortunately, we did this--although they were not with us until the end.  Don't forget the small first aid kit, too!


6.  In case you have to hike out at night, it's always a good idea to carry a flashlight or two.


7.  If you're going into an area with poor trail marking, be sure to bring maps or guides for your hike.


8.  Dress for the weather of the day, but, if heading into the mountains, it's always good to bring some extra clothes or jackets in case of sudden weather changes.


9.  It's a good idea, especially for smaller groups, to have someone with whom they check-in when they return from the backpacking trip.  You don't want people guessing as to where you went, if something unforeseen happens.


10.  As Cheryl Strayed laments in From Lost to Found, make sure you're wearing comfortable shoes!  Avoid making beginner errors on your boots.


Another Top 10 List for Hikers 




"Bonus" Feature!  



It's not every blog that provides bonus content...but here are a couple photos of an Orange bellied Taricha granulosa which we happened across along the trail around the lake's eastern edge.  Although I handled this newt without any problems, apparently it is poisonous if one tries to eat it.  (Thankfully, I wasn't even tempted a little.)



















New:  You may also enjoy "Injured and Alone."  

Sunday, July 8, 2012

A Critical Review of MacKeeper

Back about the time I decided to buy a new Canon EOS Rebel T-3 digital SLR, I started to actively search for ways to trim the memory usage on my iMac (2.66 GHz Intel Core Duo, using Mac OS X).  I found some interesting things I could do myself--including removing duplicate copies of my entire (voluminous) photo library--but I turned to MacKeeper for some extra help to free up even more memory.  Here's a how MacKeeper describes itself to potential buyers.
"What is MacKeeper?
MacKeeper is like 911 for your Mac. It’s an easy way to manage routine tasks and keep your Mac secured, clean, reliable, fast and attended!
What makes it so special?
MacKeeper is a bundle of most important system utilities for performing different tasks on your Mac. It will rescue you from numerous apps and dozens of customer support centers!"
While I liked its simple user interface, its constant critical, "red alert-style" warnings soon became increasingly annoying.  I'd fix everything, then a few days later it would tell me that my system status was critical.  I knew this was nonsense, simply a marketing technique to make its non-tech savvy users feel a breathless need for its "magic."
As it did free up gigabytes of memory, though, I was patient..at first.  When MacKeeper sent me an invitation to do a review in exchange for an upgrade, I foolishly thought "Sure, why not?" and shared my thoughts in a quick and dirty online review.  That was a mistake.  The upgrade immediately caused problems with what they call their binary cutter, creating one of those false critical system warnings.  Their advice finally?  Just ignore it, because it's not a bug.  That, of course, begs the question...if it's not a problem, why does your MacKeeper tell me the sky is about to fall?
Here's an example of the "helpful" tech chat they offered me.
You: That's fine, but there's apparently a bug that should be addressed.
Vincent: I don't think it's a bug.
Vincent: In case if those junk files are in use I'm not surprised you can't remove them
You: Hello...
You: I'm supposed to give you remote login info, so you can check this issue...
You: 485 116 209 (remote id)
You: Ready for password?


Dear Karl B. Erickson, We are terribly sorry for all the inconvenience you have faced. In order to deal with the situation in the most efficient way we decided to offer you a remote control session. Our technician would connect to your computer and make the necessary steps - this is absolutely risk free, you would be able to spectate all our actions and we ensure you your privacy and personal information safeness. It usually doesn't take more then 10 minutes. If you agree to our offer, please follow instructions from the link below. http://mackeeper.zeobit.com/remote_support Then please start a live chat in Mackeeper application or from MacKeeper official website http://mackeeper.zeobit.com/support_livechat and describe your issue to agent. If you are not willing to accept this offer we will do our best to deal with the issue in other ways, but it could take longer.Thank you for cooperation, ZeoBit customer support department.

You: Ready?
You: Waiting...  Support, are you there??
You: MAX, are you there?
You: signing-off in ten seconds...
As you can perhaps gather, ZeoBit customer service and tech support came across along the lines of the clueless Barney Fife of the software support world.  But the fun had only just begun.
Today, I realized with unbridled joy that MacKeeper had sent yet another update.  What new problems would I find?  I was not to be left disappointed.   The new warning message coming up repeatedly today is copied below.  Despite numerous attempts to clear, which included changing system preferences, no luck. It comes up as often as mosquitoes on a camping trip.
MacKeeper wants to use your confidential information stored in "com.zeobit.MacKeeper.ZeoAccount" in your keychain."
Try as I might, I can't get the new warning to go away for long.  I am just about fed up with MacKeeper and will likely be deleting it shortly--if they can't fix with an...update.  Gulp!
Some Other User Friendly Articles on "Techie" Subjects:


Update (1):




Update 2:

Per MacKeeper's suggestion this morning, try deleting the program, then reinstalling it.  So far, it does seem to work better.  (One potentially new security vulnerability has been shared with MacKeeper.)

Update 3:

I've long since stopped using MacKeeper.  In case you were not aware, there is a legal settlement in-the-works with regards to this product.



Monday, July 2, 2012

A Day Hike to Lake Pamelia

Wild Rhododendrons in bloom around the lake.
Trying to get in better shape, I recently took my kids on a day hike to Pamelia Lake in Oregon's Mt. Jefferson Wilderness Area.  It was a lot of fun, and I thought I'd offer some quick notes to readers (and reminders for myself) who may be interested in trying it in the future.


The first thing to bear in mind is that this is a limited access area.  This means that a special wilderness use permit must be picked-up first at the Detroit Ranger Station.  You will also need a parking permit for the trailhead.  As of 2012, the use permit was free, but the parking pass was five dollars.  If you don't like surprises, you may want to call ahead to reserve the permit.


The Pamelia Lake Road, leading to the trail head, is located about fourteen miles east of the ranger station off of Highway 22.  It's paved most of the way, but it is a single lane.  Use caution also due to the irregular road surface which can cause underside damage if you try to go to fast.  (No comment on how I know this.)  


The hike itself is not that difficult, but it's probably not fair to call it easy either.  Moderate difficulty is probably the most accurate description.  Make sure that you bring more food and water than you think you'll need, and remember that weather conditions can change quickly, so bring appropriate clothes (and sunscreen).  The pleasant sound of Pamelia Creek accompanies the hiker for much of the way--a good reminder to stay hydrated!


Two and a half miles later, the winding trail deposits the hiker on the lake's west side with impressive views of Mt. Jefferson to the northeast and wild rhododendrons gracing the lake's shoreline.  It's a great place to sit and relax for a while.


It may be helpful for the reader to pause here and take a quick look at our journey online, bearing in mind that there is no GPS signal in these woods, so the iPhone's mileage figures are not as exact as usual.  You'll see that we went around to the east side of the lake for quite some distance.  This was an enjoyable hike, with picturesque waterfalls and geese gathered on the lake's eastern shore, but we lost the trail completely at the end of that stretch.  


A more experienced hiker would have been able to successfuly ford the streams and follow the trail's path beyond and up the steep foothills to where the path intersects with the Pacific Crest Trail.  (You'll note that this section of trail is actually running parallel to the PCT, which lies a short distance to the east.)


The only last suggestion I'd offer is to watch your way carefully. There are a number of poorly marked and intersecting trails on the lake's western side.  It's easy to get a little turned around and find yourself going in a circle--not exactly filling the hiker with wonderful feelings of accomplishment.  If you get confused or lost, it's best to return to the lake to regain your bearings.  


I hope the reader finds this information of some value.  It's a great little hike for those of us in the beautiful Willamette Valley.  


(Here is one more link that may prove useful!  Particularly good explanation of the trails in this area.)



New:  You may also enjoy "Injured and Alone."  

A Note for Readers Concerning Future Interviews

Lunch with Emir (and John C) in 2008.
Begining almost exactly a year ago with Sean Astin's interview, I have endeavored to offer new interviews on a quarterly basis.  Recently, I thought I'd ask a distant friend of mine, Dr. Emir Shuford, about answering a few questions--only to learn that he passed away late last year.  


This is probably as a good a time as any, then, to suspend all further blog interviews for the time being.  I'll likely return to them after the completion of my current novel.  As Frodo said," I feel thin; like too much butter spread over a piece of toast."  Time to pull back just a bit!

Sunday, June 24, 2012

Fortnight for Freedom in the Pacific Northwest

Usually, it's somewhat amusing to listen and read reports from within the liberal ranks of the secular media when it comes to their clumsy and ill-informed analysis of matters pertaining to faith--Washington Post, for example.  Many don't even seem to have a working knowledge of the Bible in terms of its mere literary value; it's a stinging indictment  on the state of public education when the media gets away with so much.  The reporting is so exceedingly poor and biased lately on these issues that I find myself turning more and more to conservative networks such as Fox News or Catholic networks such as EWTN.  After NBC's recent creative soudbite editing, Raymond Arroyo is a breath of fresh air.


This brings us to The Fortnight for Freedom, a 2-week event from the United States Conference of Catholic Bishops.  Below is an excerpt from their site on the aim and goal for this endeavor.


The fourteen days from June 21—the vigil of the Feasts of St. John Fisher and St. Thomas More—to July 4, Independence Day, are dedicated to this “fortnight for freedom”—a great hymn of prayer for our country. Our liturgical calendar celebrates a series of great martyrs who remained faithful in the face of persecution by political power—St. John Fisher and St. Thomas More, St. John the Baptist, SS. Peter and Paul, and the First Martyrs of the Church of Rome.  Culminating on Independence Day, this special period of prayerstudycatechesis, and public action will emphasize both our Christian and American heritage of liberty. Dioceses and parishes around the country have scheduled special events that support a great national campaign of teaching and witness for religious liberty.


With our eyes on the Supreme Court this week, I hope Catholics will remember the fight for religious freedom and stand up for what is right and just.  As Saint John the Baptist stood up against King Herod and as Saint Thomas Moore (an ancestor of my wife, by the way) stood up against the outrageous claims of King Henry VIII, we're also responsible for standing up today for what is right and just and should be capable of articulating and defending the Church's position concerning the sanctity of all human life--from conception through natural death.  If you don't believe this...then you're not really Catholic at heart.  You may be a "cultural Catholic," but if it's not rooted in your heart, you might as well join the local Elk's Club.  Sanctity of life is a fundamental and non-negotiable component of the Catholic tradition.  (For an insight into my feelings on Obama Care, see the following letter to the editor from This Rock.  Please also see The Coercive Attack on Free Speech.)


If you haven't already seen it, I invite you to watch this well done video, Test of Fire.  I hope and pray you will do what's right and take a stand for religious liberty this election season.