NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft Tablet PC Platform Component, skchui.dll error

Every time I close my TestStand OI, I get this message (attached)
 
 
0 Kudos
Message 1 of 18
(6,941 Views)
And did you view the readme for more details?  The readme says:


Applications that create and destroy the Microsoft Internet Explorer (IE) control may leak GDI memory, making both the application and system unstable. The memory leak occurs when running the application on Windows XP and the Handwriting feature (version 1.0.1038 of the Skchui.dll file) is enabled for a Microsoft Office product that is installed on the computer. For TestStand, the Sequence Editor creates new instances of the IE control for each new execution document, and each ReportView Operator Interface control creates a new instance of the IE control. To prevent this GDI memory leak, you must uninstall the Handwriting feature of Microsoft Office and for any other product that uses this shared feature.

Refer to the following Microsoft KnowledgeBase article for more information: http://support.microsoft.com/default.aspx?scid=kb;en-us;896429


It is up to you as to whether you uninstall it or not, but I did as I was annoyed by the constant reminder and I saw no use for it handwriting recognition on a desktop.

Hope that this helps,
Bob Young




0 Kudos
Message 2 of 18
(6,931 Views)
After stepping through the 'Workaround' the error message no longer appears when I exit my app.  However, I still can't exit from my application without going through Windows Task Manager.  Any suggestions where to start debugging?
0 Kudos
Message 3 of 18
(6,915 Views)
Can you give more details on what problem you are seeing?  What happens if you try to exit the application?
0 Kudos
Message 4 of 18
(6,887 Views)
When I click File::Exit, the loaded sequence file goes away, but the OI is still visible.  None of the menu selections is active.  If I click on the 'X' in the upper right, nothing happens.  Another wierd thing is that this little TimeStamp that I added to my Full OI - Top-Level VI continues to run.
0 Kudos
Message 5 of 18
(6,883 Views)
It sounds like maybe that TimeStamp loop is never exiting. How do you have that implemented? Is this in LabVIEW or some other language?

If you're coding in LabVIEW I'd suggest just turning on highlight execution - open the OI then try to exit. Take a look around and see what is still running.

Since your TimeStamp is never stopping, I'd be willing to bet whatever loop that is in isn't exiting.
Dan Weiland
0 Kudos
Message 6 of 18
(6,855 Views)
I'm sure the TimeStamp is the guilty party.  I've attached a bitmap that shows how I've implemented it within the Full OI - Top-Level VI.vi.  I'm wondering how to tie the application exit condition to the exit condition of the timestamp loop.
0 Kudos
Message 7 of 18
(6,851 Views)

Hi,

Use a local variable set to write which you set True in the Exit Case and wire the local variable set to read to the loop terminate terminal.

Remember to initialise the local variable to false at the program start.

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 8 of 18
(6,830 Views)
At the time I read your reply, I thought I understood what I needed to do.  Now that I'm getting around to doing it, though, I seem to be having difficulties.  I can create a local variable in the "Quit Application" case of the Event Structure.  However, I don't know what control/indicator to tie it to (when I right click and choose 'Select Item').  Anyway, could you please provide just a little more detail?  Thanks.
0 Kudos
Message 9 of 18
(6,803 Views)
I'm getting back to this problem and realize I still don't quite understand how to do this. 
0 Kudos
Message 10 of 18
(6,727 Views)