Clarion randomly freezing for Windows 10 users


#1

Our company has recently started to move users to Windows 10. Well in doing so our Clarion applications have started to freeze up / lock up randomly on just Windows 10 machines. Windows 7 machines are just fine. Can someone shed some light on what could possibly be causing this one Windows 10?

Thanks


#2

Hi,

Could be the Alt key lockup.
Carl Barnes made a template for this.

See if it helps,
Rob


#3

Does this problem occur when the user presses the Alt key specifically?


#4

Yes, users were accidentally bumping the Alt key and Windows 10 will wait for a second key without any change to the screen. So, they don’t know they hit it.

Tell them to hit “F” and it should drop the “File” menu from the top line.

There is also another template, that is named “Ultimate Window Example”, and just Alert()'s a few problem hotkeys. But it seems to fix it, also.


#5

Alright I just tried it. The ALT key has no effect on the clarion app. The user states that its random, she walked away from the computer came back and the app is locked. Task manager does not show it not responding but nothing works in the app. A few things I have tried is launching the app in compatibility mode setting it back to Windows 7 as well as turning off ipv6. Waiting to hear back from her to see if it locks up again. Figures crossed.


#6

Has your user tried pressing the ESC key, ENTER key, and/or ALT+F4?

It could be possible that there’s a window open that is out of geographically out of view or hidden.


#7

I will try that the next time it happens. Thank you. I will report back.


#8

What version of clarion are apps built from? If older, the changes to the WinAPI can cause wait chain issues (we have this with an C6 app) If you use Task Manager look for the locked up clarion app and Analyze the Wait Chain,. that may point you to another windows app that is causing problems.


#9

I checked the wait chain today. Adobe Acrobat DC was in there, the application itself, and splwow64.exe.

Could it have anything to do with the user losing network connectivity? She works in two different applications at the same time and they both lock up.


#10

a wait with splwow64 has been the culprit in most of our lockups.
why? we don’t know.

What version clarion is the app developed with?

#11

Version 9 not sure on the exact version number.


#12

The problem could be that you do not have a proper manifest. Here is the example we are using for Windows 7 and Windows 10.
Name it as “program.exe.manifest” and include it in cwproj.
It should be like this in your cwproj file: Library Include=“program.exe.manifest”

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <assemblyIdentity
    version="1.0.0.0"
    processorArchitecture="X86"
    name="SoftVelocity.Clarion10.Application"
    type="win32"
  />
  <description>4D Wand</description>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
      </requestedPrivileges>
    </security>
  </trustInfo>
  <dependency>
    <dependentAssembly>
      <assemblyIdentity
        type="win32"
        name="Microsoft.Windows.Common-Controls"
        version="6.0.0.0"
        processorArchitecture="X86"
        publicKeyToken="6595b64144ccf1df"
        language="*"
      />
    </dependentAssembly>
  </dependency>
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application> 
      <!--The ID below indicates application support for Windows 7 -->
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
      <!--The ID below indicates application support for Windows 10 -->
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    </application>
  </compatibility>
 <asmv3:application>
    <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
      <dpiAware>true</dpiAware>
    </asmv3:windowsSettings>
  </asmv3:application>
</assembly>

HTH

Greetings,
Edin


#13

Ok I will send this over to our programmers thank you.