TRasmussen

Thanks again Dan... I'll pop over to the ConnectSMART forums to see if there's mor on this there. WindowsApplication3.zip

Thanks Dan for the response. I'll go ahead and post it over on the ConnectSMART forum as well. I'm pretty sure that our drilldowns are working OK in the Windows 7 environment with PowerShell v2.0, I'm only seeing this with respect to the Script Blocks. The {$_.Size} as well as a Script Block we've been using for conditional attributes are the only two issues that have come up that I've discovered so far. I'm going to be spending some time to see if there is anyway to work around this problem and in the meantime, I'll try to get a hold of the latest version to test also.

It doesn't appear to be an issue with PowerGadgets versioning. I loaded the exact same version of PowerGadgets (the older v1.0.2760.16652) on another Windows 7 machine and I am getting the same error. If anything, I suppose it could be a PowerShell versioning problem. But Windows 7 comes with PowerShell, so I don't know what I can do about the version of PowerShell that I run from Windows 7. Can anyone else provide me with some clues as to what we can do about these scipt blocks in Windows 7. For my next test, I'm going to load this stuff on a Vista machine to see how it works in Vista.

My PowerGadgets is version 1.0.2760.16652 on my XP box and version 1.0.3049.17915 on the Windows 7 box. It seems like this would be a pretty major change for a minor revision from 1.0.2 to 1.0.3. Is there any documentation on these so-called improvements? Is it simply a matter of syntax or punctuation? If I can solve this, it will probably resolve our other issue as well as we were using script blocks in our conditional attributes for out-chart as well.

Aloha, It's me again. I'm back because I never received any replies for my last post. So, I thought I'd try again with a slightly different (easier) problem. Again this is related to our recent migration from Windows XP to Windows 7. I have several PowerGadget Digital Gauges that receive parameters from import-csv. I used to be able to control the size of the digits that are displayed by using the {$_.size} object item in conjunction with the out-gauge -Appearance_Size parameter. The CSV I import from looks something like this (read between the single quotes): ' #TYPE System.Object "Count","Size" "125",".66" ' The powershell script that works properly in Windows XP looks like this (read between the single quotes): ' import-csv

I am migrating my dashboards from a Windows XP environment to Windows 7 and I have several gadgets that no longer work properly. I don't get a lot of help from the Windows error handling. The error message simply reads, "powershell has stopped working", windows is checking for a solution message box appears (with its progress-bar) and eventually I get the message box that tells me "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." The only option button I have is "Close program". I get this with two different types of Powergadgets (which all worked perfectly in Windows XP - I don't know about Vista). Both of which are using pipeline objects for some type of programmatically set value such as size or condition. The first type of gadget I discovered this problem with was the out-gauge and the other occurs in out-charts that try to use the pipeline object for conditional attributes. I'm not sure which of the two to share here, so I guess I'll start with the conditional attributes example, since I've seen this documented frequently in SoftwareFX blogs. I get this error when I pipe results from an import-csv to the out-chart cmdlet as follows: # lcd1ToddTest.ps1 $condition = { if (([double] $_.overunder_pct) -le -20) { 0; } else { if (([double] $_.overunder_pct) -le -10) { 1; } else { if (([double] $_.overunder_pct) -le 0) { 2; } else { 3; } } } } import-csv