• Replies 4 replies
  • Subscribers 581 subscribers
  • Views 281 views
  • Users 0 members are here
Options
Related

DspPlaySound causes Windows 'egg timer' on client

Ashley

Hi,

I've recently upgraded from VJC 2015 SP1 patch 13 to Citect 2016 + latest update (23, Nov 13). Pretty much my whole system looks happy running on Citect 2016, with one exception. It seems every time i call the DspPlaySound() function on the client, it causes the Windows 'egg timer/busy' icon to be displayed next to the mouse pointer. Note - the intended sound (defined as C:\Citect\Alarm\<filename>.wav) still plays/sounds ok.

I'm trying to determine if this problem has been introduced with the upgrade to Citect 2016. I've compared the help file for this function from both versions of Citect, and they look identical.

Anyone got any thoughts on this?

Thanks

Parents
  • Hi Ashley,
    I haven't seen any mention of the DspPlaySound function causing a Windows 'egg timer' appearing, but it may be specific to your Windows environment. You are absolutely correct, that the DspPlaySound() function did change in Citect SCADA 2016 (June 12). It was modified to address a memory leak that was caused by older Windows OS (Windows 7, Vista) which microsoft refused to patch the bug. The work around that Citect developed was to launch another app SE.Citect.PlaySound.exe then shutdown this app once complete, thus freeing up the memory. The change is tracked in bug 65606. I'd recommend getting in contact with Citect Support to diagnose this issue further. It certainly sounds like something is initially blocking the app, perhaps something to do with Windows DEP?
Reply
  • Hi Ashley,
    I haven't seen any mention of the DspPlaySound function causing a Windows 'egg timer' appearing, but it may be specific to your Windows environment. You are absolutely correct, that the DspPlaySound() function did change in Citect SCADA 2016 (June 12). It was modified to address a memory leak that was caused by older Windows OS (Windows 7, Vista) which microsoft refused to patch the bug. The work around that Citect developed was to launch another app SE.Citect.PlaySound.exe then shutdown this app once complete, thus freeing up the memory. The change is tracked in bug 65606. I'd recommend getting in contact with Citect Support to diagnose this issue further. It certainly sounds like something is initially blocking the app, perhaps something to do with Windows DEP?
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.