Why LV6.1's example:hostname will hang when "Run Continuously" under Win2K+SP2?

[Jiunn-Jyh Lin]

After I install the LabView 6.1 under Win2K+SP2,
I try to run a "hostname" example of LabView 6.1
that was placed "C:\Program Files\National
Instruments\LabVIEW 6\examples\dll\hostname".
Then I run it under "Run Continuously" mode. It
will hang. But I try use LabView6.02 to do same
thing that work perfectly!

[Randy_H]

Jiunn-Jyh,

I tried to reproduce your issue on Windows 2000 with Service Pack 2 on 2 different machines. I could not. Do you have any other programs running that might also be calling the WinSock API? This may be an issue. All LabVIEW is doing is calling directly into the WinSock DLL. If the DLL call hangs, then this can cause LabVIEW to hang as well.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

[Jiunn-Jyh Lin]

Dear Randy Hoskin

Thank your attention, my O.S. is Traditional-Chinese
Win2K+SP2.I had try four kind hardwares what are ACER
TravelMate 529TX/AcerPower 500/ACER Veriton 7100/ACER
Veriton 7200D, they have same problem!

I try to find out the real reason, so I just intall
Win2K+SP2 and LV6.1; no additional software run
simultaneously.

I run it under "Run Continuously" mode, then click
the STOP button, then it will hang. I use the Task
Manager to monitor the usage. LV6.1 take 99% CPU
usage when hang. Some time,LV6.1 can STOP after LV6.1
lost the focus.

This feature is very important to me. Because I have
many products use traditional DLL. I hope upgrade my
products to 6.1. The hostname is just a example that
to verfiy the LV 6.1 ca
lling DLL problem.

Best Regards

Jiunn-Jyh Lin

[Randy_H]

Jiunn-Jyn Lin,

If, when you say the "stop button," you mean the red stop sign looking icon on the toolbar, this is the Abort button. It should be used as an absolute last resort. To stop a continuous run, press the Continuous Run button again. It will run one last time and then finish. What is happening is that you are aborting out of a Windows DLL call and that is what is hanging. From what you have told me now, I would expect this behavior. As for why it is not happening in LabVIEW 6.0.2, I cannot say.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

[Jiunn-Jyh Lin]

Dear Randy Hoskin

Yes, I use the Abort button to test LV6.1. And I know
this is not correct method to verify LV6.1. But, I try
to divide my DLL's bug and LV6.1's bug. So, I use the
official example to test.

My DLL can work with LV6.0.2, but not LV6.1.
This feature is very important to me. Because I have
many products use traditional DLL. I hope upgrade my
products to 6.1 and do not modify DLL.

By the way, I had use same way to test under different
O.S. as following:
Win98SE:Work
WinMe:Work
Win2K+SP2:Fail
WinXP:Work

Best Regards

Jiunn-Jyh Lin

[Randy_H]

Jiunn-Jyh Lin,

All I can say is that it is the exact same LabVIEW code running on all Windows operating systems. We do not have separate versions for different Windows operating systems. If Windows 2000 SP2 is failing, it is somthing in the operating system that is doing it. I am sorry we cannot resolve this through LabVIEW. As I said, I have not been able to reproduce it.
Your should be able to upgrade to Windows 2000. That is what almost all of us at National Instruments have and we have had no problems with it so far in terms of DLLs. I would try out your code to see how it runs. There should be no problems at all.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

[Jiunn-Jyh Lin]

Dear Randy Hoskin

Finally, thank your kind help. I will try use different
Software Install Order to solve this problem. Maybe you
are right that something doing.

If it can not be solved, I will be forced to use LV6.02
then wait LV's newer version to upgrade.

Best Regards

Jiunn-Jyh Lin