Something I found impressive was the new campus.  Here’s some info:

The Lone Star campus, which is home to AMD’s business operations and the Austin design engineering center, was designed and constructed by a diverse team of internationally recognized architects, engineers, ecologists and sustainability experts. The site development plan for the 58-acre, 870,000 square foot campus was based on three key tenets: limit site impact, protect water quality, and use innovative sustainable design. Some of the sustainable design elements include:

• Energy Use: Powered 100% by Austin Energy’s GreenChoice® electricity, which comes from clean, renewable energy sources such as wind power
• Rainwater collection: Designed with a 1.2 million gallon capacity rainwater collection system, which is designed to provide water for the buildings’ cooling towers and irrigation
• Construction materials: Incorporated more than 20% of construction materials based on recycled content, and with more than 20% of locally sourced construction materials
• 100% Native Landscaping: AMD partnered with the Lady Bird Johnson Wildflower Center to salvage the native trees, shrubs and grasses within the footprint of the campus, and replant them following construction.

“You are running a 64-bit guest operating system, but the virtual machine is configured to run a 32-bit operating system. To ensure that a 64-bit guest operating system will function correctly you must:
1. Power off this virtual machine.
2. Change the guest operating system type to a 64-bit operating system in virtual machine settings.”

However, I found that after bypassing this message that the guest will run properly with no changes.

“Win32/Malum (similarly known as Win32/VMalum and/or Win32/AMalum) may be reported when CA Anti-Virus uses advanced techniques to generically detect a worm or trojan that affects the Win32 platform.
Should you have this detection reported, we highly recommend that you submit a sample of the affected file to CA Anti-Virus Research for analysis.”

I just started practices for summer co-ed softball.  Sooo hot out there, ha.  We don’t start playing till around the 13th of July at HYBSA and then go through October.  I believe our team name is going to be “backyard bruisers”.  Not sure if that had anything to do with me and my dive-flips & bleeding knee at the first practice   But after that and then hitting the ball up into the playground, they said I would play the hot corner and bat clean up.  Not bad for only playing 2 seasons (9yrs ago) since playing in college.   Made me Feel great and not so old!

I noticed that my system had started slowing down a few days ago.  Then it got to where the cpu was tied up so much that it took a couple of minutes to switch apps.  So I checked to see who was doing it, but nothing pushing the cpu that hard from my account in task manager.  So I checked the system account and there it was – svchost.  So I checked the services running from that iteration of svchost and out of the 3 (Superfetch, ReadyBoost, and Windows Audio Endpoint Builder) it was Superfetch that was tying up the cpu.  So a simple stop service fixed that, except I would like to use Superfetch.  I don’t understand why it just started doing this.  I’m not aware of any updates to the service that occured lately.  I have not changed my application use habits drastically so that it would have to completely rebuild it’s database.  I’ve seen others posting to boards with this same problem, but no answers.  So for now I am running without the super-, just with the pre-, ha.