Crash during Compile in Lookout 6.1

[Ryan.S]

How about this issue now?

Could you try Lookout 6.0.2 on the new computer? I want to know if it is the Lookout 6.1's bug, or it is the compatibility issue between the computer and lookout with directlogic driver.

[JPhillips]

After installing Lookout 6.0.2 with the updates for 6.0.2 applied, I obtained the following results:

1.) With both DSComm.cbx and DSComm4.cbx in the Lookout directory, Lookout crashed during compiling. Attached is the screenshot of the crash.

2.) With only DSComm4.cbx in the Lookout directory, Lookout had 2 crashes during compiling. Attached are the 2 screenshotd of those crashes.

3.) With only DSComm.cbx in the Lookout directory, Lookout did compile, but then hung during loading of the .l4p as it did in Lookout 6.1.

The only difference in 6.1 with these combinations was that with both DSComm.cbx and DSComm4.cbx in the Lookout directory, Lookout hung during loading of the .l4p.

[Ryan.S]

Is the process the same one you sent me before, named ebfpsvr?

I tried it again with Lookout 6.0.2, but didn't see the crash. I use DSComm4.cbx.

Probably this issue is related to this specific computer or OS as you said, but it's hard to troubleshoot.

Could you try to create a new process, with the DirectLogic object and some simple connections? Then let's see if you can open the simplified process on this computer.

[JPhillips]

No, actually that file opened on this computer. The file in question is called wbserver, and I uploaded this file to the ftp site in a folder called jphillips.zip.

Remember to have the ctcalc.cbx file I sent you earlier in the Lookout 6.1 folder.

Thanks!

[Ryan.S]

I can open this file with both lookout 6.0.2 and 6.1.

I go through the file, but don't see anything special in the process.

One thing I notice is the state file， #statefiles "<PF>|Z:\wbserver.l4t"

Change it to

#statefiles "<PF>"

and try again.

[JPhillips]

Ryan,

I solved the issue with Lookout hanging up. These new computers have a bluetooth wireless keyboard and mouse, and after going into task manager and shutting down programs until I got the file to open, I narrowed it down to the bluetooth program. I went into MSconfig and disabled bluetooth on startup and that did it! Luckily, the mouse and keyboard still function properly even though that program is disabled. 

[Ryan.S]

Great!  This is very useful information for other customers as well as NI. Thank you for updating, Jason.

[icpsa]

Hi Ryan, I have the same problem, may I get the update to solve it ?

My E-mail maguerrero@icp.com.do

Thanks in advance.

Message Edited by icpsa on 06-15-2008 02:58 PM