Jump to content
Software FX Community


  • Posts

  • Joined

  • Last visited

marco.shaw's Achievements


Newbie (1/14)



  1. Check this out: http://community.softwarefx.com/blogs/powergadgets_team_blog/archive/2008/04/29/Integrating-PowerGadgets-with-your-website.aspx
  2. Then give this a try to see if it gives anything: PS>osql /L It doesn't work for me though even with a local install.
  3. And you can create a SQL connection to that SQL 2005 without any problems other than PowerGadgets not being able to? Do you have the SQL client tools installed on that machine where PG is? Just so we might be able to try some calls to see if it can connect.
  4. Are either of the SQL 2005 or 2008 installs on the local machine or are both on a remote system? Let me know... Double-check that the SQL Server browser service is running on all the machines. If not, and it's not considered a secuirty issue, enable the service.
  5. The only way I could see this being done is to send a direct stop/kill to the PowerGadgets process. Then you would call your other PGF files to open up your new dashboard. Not an elegant solution, and I'm concerned killing processes (any process, not just PowerGadgets) could lead to unpredictable results in the longer term. I this something you're going to be looking at doing at very short intervals?
  6. Not a definite answer, but I suspect there may be problems with using scriptblocks for parameter values with PowerGadgets and PowerShell v2.
  7. Not that I'm aware of any version issues, what version are you running and on 32 or 64-bit?
  8. Thanks for trying that out. Yes, Windows 7 is bundled with PowerShell v2, and that can't be changed on that platform. So it is possible that PowerShell v2 introduced this problem... Sorry, I wish I had more free time to try to help...
  9. Please open the PowerGadgets Creator, go to Help, then About PowerGadgets. Please check the version you are currently running, and compare that against the version you had running on XP (if you can). This feature is known as scriptblocks. Not all parameters accept scriptblocks and I believe that support for it improved with later releases as more and more parameters provided support for it.
  10. Is there any more information you can provide? Maybe this is an issue with PG. You might have the option of continuing possibly, creating your template file, then editing the template file to add-in the .ps1. The template file is just simple XML for the most part.
  11. In most cases, using a .pgt or .pgf file developed on 32 or 64 should work fine on the other. It is possible that some of the information used as input may be different (different path, for example).
  12. OK, I see what you are referring to. Give me a few days to take a peak.
  13. If I follow correctly, have you tried something simple like this: PS>out-chart -template my_chart.pgf -output my_chart.png Now, oddly enough, it seems this method *might* lose some of the formatting, but could you give it a try with your examples? I like how you're using the product... Please feel free to post if you have any more questions!
  14. **I'm not a professional developer** Off hand, can you confirm that you are running the 64-bit version of PowerGadgets on your system? I have a Windows 7 64-bit VM, and may try to reproduce what you're seeing in the next 3-4 days.
  15. I did try a very basic test, and I do agree that it appears that if you call out-chart from a PowerShell script versus what things end up looking like when use the creator wizard can be a bit different. I may try to come back to think about this at another time (as my free spare time is pretty much zero these days), but it might require getting PG devs involved to confirm the different behavior. Either Juan from SoftwareFX may chime in or you may also want to contact support AT powergadgets.com also.
  • Create New...