I've seen this happen when I stop a VI without closing all the GPIB related references. Closing LabVIEW closes these references. Trying to rerun a VI without closing the references can cause LabVIEW to just quit and a reboot seems to be the only way to clear the problem after that.
Kelly Kelly Bersch Senior Technician Anadigm Telephone: 480-344-5262 Email: [EMAIL PROTECTED] http://www.Anadigm.com Anadigm - The Programmable Analog Company -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of wayne galbraith Sent: Sunday, 08 February, 2004 18:54 PM To: [EMAIL PROTECTED] Subject: gpib board crashes pc Hi there list I have a system comprising a PCI 6034 DAQ, a PCI 7344 motion control and a PCI GPIB NI card. The complete system works fine and all boards runs seamlessly within the system. I have though a problem that seems to be getting worse and worse. If I make any alterations to my LabVIEW code and then try to run the complete software the system crashes - as far back as to a machine reboot. This did not used to occur and seems to be occurring more and more frequent. The crash occurs without fail (now) and the alteration to the code can be any alteration. If though I make an alteration and then save it and shut down LabVIEW - completely not just close all vi's, then the system does not crash. Now if I take the GPIB board out of the system and perform any of the above, then the system does not crash and I have not been able to make it crash. It looks like this problem is attached to the GPIB card in some way, although I can't work out why. btw - I have tried the boards in differing PCI slots just to eliminate that but without any change to all the above behaviour. Has anyone seen this previously thanks for any ideas wayne
