Xperimentality

Building a Better Xperience with .NET

 Saturday, July 24, 2010

I am really late getting this out, but since my youngest daughter tried to blind me recently, everything is behind!  If you have not heard, Walt Ritscher released Shazzam 1.3 on July 14th.  Yes, you are correct, this is great news.  Wait, some of you have not heard about Shazzam!  Well there is no time like the present to find out about it.

If you do anything with pixel shaders for WPF or Silverlight, you need Shazzam.  Shazzam is a tool that allows for the simple editing and testing of pixel shaders for WPF and/or Silverlight.  You can write your shader code in the built-in HLSL editor, then compile it and test it against sample images or video with a single click.  If your shader takes input parameters, Shazzam will build a set of controls to allow you to tweak your parameters in real time.  Once you are happy with your shader, you just copy the code generated by the tool into your project and start using it.

I have been using Shazzam since it was first released and this upgrade adds some really nice features.  For one thing, with previous versions of Shazzam, you had to provide your own copy of the tool used to compile the HLSL.  This tool is found in the DirectX SDK which is a nice size download just for one executable.  In version 1.3, this dependency has been removed!  For WPF Shaders, the new PS_3 specification is supported.  And you can tell Shazzam which specification/platform you are targeting.  There are now over 80 sample shaders included with the tool.  And 20 tutorials have been added demonstrating the who, what, when, and where of some of the most common HLSL.  From what I understand from Walt, there were a number of folks who wanted to download and install Shazzam, but their network or company policies prevented them from installing Click-Once applications.  So version 1.3 is now available as a standard installer package.

This is just the tip of the iceberg for some of the new features of Shazzam 1.3.  I would encourage you to download and install it.  If you are writing your own pixel shaders, it is a great tool to have in your hip pocket.  If you have not written any pixel shaders and have been a little intimidated by HLSL, then Shazzam is the tool to get you in the ball game!

Friday, July 23, 2010 11:07:15 PM (Central Standard Time, UTC-06:00)
 Tuesday, July 13, 2010

Recently after installing some updates, I noticed that my computer kept waking from sleep at midnight.  This was especially frustrating when the machine was in sleep mode in my bag.  When I opened the computer the next day, the batter would be dead and the machine will have hibernated.

I found a command line tool to configure power settings.  I would not think you would normally use this tool to modify your power settings, but there are some interesting switches that can be helpful in my situation.  I am sharing them here as much for anyone else’s benefit as for my own lack of memory!

-lastwake
This switch will display information about the last event that woke the computer from the sleep state.  I found that sometimes this would not give me any useful information.  Not sure why it would give more information on some events than others, but it is still useful.
Example: powercfg -lastwake

-devicequery
This switch returns a list of devices that meet the query criteria passed as flags to the switch.  There are some really useful flags that can be used here.  The one that I wound up using to get the information I needed was wake-armed.  This flag lists the devices that are currently configured to wake the computer from any sleep state.  There are flags that allow you to list devices that are configured to wake the computer from various levels of sleep.
Example: powercfg –devicequery wake-armed

In my case, I ran the –lastwake switch to see what caused the previous wake.  This didn’t give me any information on the day I checked it.  But when I ran the –devicequery switch, I noticed that my network card had been reset to wake the computer.  I could have used the –devicequery switch to disable wake on that device, but instead I went into the device manager and disabled wake on the network card.  Problem fixed.

Hopefully this will help someone else solve a similar problem sooner!

Tuesday, July 13, 2010 9:35:14 AM (Central Standard Time, UTC-06:00)
Who Am I - Todd Miranda
Me
MVP Visual Developer - ASP/ASP.NET
Search
Links
On this page....
Calendar
<February 2012>
SunMonTueWedThuFriSat
2930311234
567891011
12131415161718
19202122232425
26272829123
45678910
Archives
Aggregate Me!
RSS 2.0 | Atom 1.0 | CDF
Categories
Blogroll
Contact me
Send mail to the author(s) E-mail
Administration