DIY: A 'Classic' Sawhorse!

So I was rummaging through some printouts I had when I was cleaning out the garage and came across this - Instructions to build a 'classic' sawhorse. I know, not very exciting but I decided to post this because I did make a set of these many years ago (2005 as a matter of fact) and they are still solid as ever TO. THIS. DAY.

I tried to browse to the url that was listed on the printout however it looks like the source (PopularMechanics.com) decided to re-vamp the design/instructions a bit. HOWEVER, through the magic of the internet, I was able to dig through The Internet Archive: WayBackMachine (Archive.org) and find the article. Click HERE for that original post.

If you're looking for a breakout/detailed diagram of the pieces needed, no need to worry... I scanned in my analog copy and posted it HERE!

Enjoy!

PS: Here is the updated post from PopularMechanics.com as it stands today: http://www.popularmechanics.com/home/how-to-plans/woodworking/4248458?click=main_sr

Here are some other plans (some for free and some for $$): http://www.toolcrib.com/blog/2008/07/24-free-sawhorse-plans-in-the-hunt-for-the-ultimate-sawhorse

VMware Fusion - "No permission to access this virtual machine." error

For those of you that use VMware Fusion on the Mac may run into this issue so I thought I'd post it for others to see. Basically I believe I ran into this issue as a result of running a Macware Disk Tools Pro app on my machine and running the "Defragment Files" feature against my MacOS boot drive. The error I was getting when I tried to launch a VM was generally this: "No permission to access this virtual machine." The reason I believe the defragmentation was the cause was because I remember Disk Tools working on the *.vmwarevm files; it was taking a long time to process.

Anyway, after several google searches, I found a post buried in the VMware community forums where some people were talking about this issue but in the Windows VMware Workstation platform. Figuring I'd give it a shot, I took this info and applied it to the Mac side of things and was able to get it resolved! Here's what I did:

1. Right-clicked on the *.vmwarevm file that is having the issue.

2. Select "Show Package Contents" from the context menu

3. Rename all folders with a ".lck" to ".lckOLD" (or take a risk and delete them)

4. Re-open the file within VMware Fusion.

BINGO! Worked like a champ. It looks like VMware Fusion automatically creates fresh ".lck" folders on it own too. (NOTE: One thing I did do afterwards was go back into the 'package contents' and delete the old *.lckOLD folders.)

That's it! Hope this helps someone down the road!