Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Lookout intro emblem will not disappear

We recently ran into a problem on our server machine where when we first open Lookout the NI emblem that pops up will not disappear after the process file(s) open. The processes are open behind it and working properly but you cannot see anything because the emblem is in the way. We have to keep reopening Lookout until the emblem disappears.
 
Is there a way to prevent this emblem from appearing? If not, any ideas on what is causing this problem?
 
We are running Lookout 6.1 on a Dell machine with Windows XP Professional.
 
 
Jason Phillips
0 Kudos
Message 1 of 5
(5,252 Views)
The NI emblem is just a window with a pic. Lookout creates the windows first. After a while, it destroys the windows. So, it is supposed to be closed.
One possible reason is that when opening the process Windows is overloaded and can't refresh the display in time. Maybe your process is too big. It's just my guess.
Another reason is that the "close" message is not handled correctly by Lookout. But without reproducing it, I can say if this is a bug.
If you launch Lookout without any process, will it work properly every time? If yes, next time you can launch Lookout first(run lookout.exe), and then open a certain process.
Ryan Shi
National Instruments
0 Kudos
Message 2 of 5
(5,240 Views)
After some further investigating, I noticed that lkcitdl.exe was not running while this problem was occurring, so I closed Lookout, manually started lkcitdl.exe, then opened Lookout and that resolved the problem. Any idea why lkcitdl.exe would take so long to open or what could prevent it from opening when Lookout opens? 
Jason Phillips
0 Kudos
Message 3 of 5
(5,215 Views)
If the lkcitdl.exe really matters, it's weird.
lkcitdl.exe is the Citadel 4, used by Lookout 5.x.
Lookout 6.1 actually doesn't need it. Lookout 6.1 should work fine no matter if lkcitdl.exe is running or not.
Ryan Shi
National Instruments
0 Kudos
Message 4 of 5
(5,203 Views)

I know, but that is all I did. Maybe something else was running in the background and stopped. I will investigate more if the problem surfaces again.

 

Thanks!

Jason Phillips
0 Kudos
Message 5 of 5
(5,192 Views)