app builder problems
I know this is simple, and I am just over looking something. However I can't seem to get to the bottom of this. Every now and then an application I build will create an installer that doesn't work properly. Instead of installing into the "Program Files" directory, it will great a new directory called "ProgramsDirectory" or something like that, and install itself in there instead of the standard folder. It does something similar with the Programs Menu. It seems like I figured out what I was doing wrong once before - but I can't seem to recall what it was. Any ideas? Thanks! John Howard
JOB POSTING - Test Engineer, Virginia
We are looking for test engineers with LabVIEW experience. This is a great company to work for! The job will be both challenging and rewarding. There are several positions open, requiring various levels of experience. Company: http://www.sperry-marine.com";>Sperry Marine Location: Charlottesville, Virginia Contact: [EMAIL PROTECTED]
RE: State machine diagram editor
>>> Lewis Drake 01/18/04 03:02PM >>> ... when I added a new value to the enum, the state case structure case labels would sometimes shift to ones which were incorrect, and I'd have to continually check every case and manually adjust the case names. Perhaps this is not a problem in LV7.0, I haven't bothered to check it because the strings work fine. Lewis, Just to let you know, this hasn't been a problem ever since 6.0 or so. (can't remember exactly when NI fixed this) John H.
DAQ OPC on Windows XP?
Since some of you use OPC, maybe someone will have an idea what I am doing wrong here. I have two Windows XP Pro SP1 computers. Both have the following common software installed: MAX 3.0.2.3005 NI-DAQ 7.1.0f1 DAQmx 7.1.0f1 Server Explorer 2.4.1 (National Instruments) I have some virtual channels set up for NI-DAQ, just to make sure DAQ OPC has something to look at. In Server Explorer, when I try to browse the OPC Servers on the remote computer, I consistently get the Windows error message "Unable to connect to \\! Make sure that this computer is on the network, has remote administration enabled, and that both computers are running the remote registry service." If I try to view the registry keys on the remote computer using 'regedt32', I can not view anything below HKEY_LOCAL_MACHINE\SYSTEM, even though I have modified security for the following keys to make sure DCOM should work. "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers ..." I gave "Everyone" full access to these keys just to be sure security wouldn't be a problem. Does anyone know if there is anything peculiar about Windows XP that might make DAQ OPC setup difficult (or maybe just different). I've done all the DCOM setup stuff that National Instruments recommends. I am using the Administrator account on both computers (same password for both). I am trying to use the simplest possible settings, and it just doesn't seem to want to work! A National Instruments engineer has been trying to help me as well, and I seem to have him stumped. Thanks for any ideas! John Howard
Re: bad news?
I should have included the link to the original article. Here it is: http://email.controleng.com/cgi-bin2/DM/y/efVG0GDREC0GXT0B6Ni0An >>> "John Howard" <[EMAIL PROTECTED]> 01/13/04 09:00AM >>> Here is an article from a recent Control Engineering newsletter... SoftWire's patent infringement lawsuit against NI to proceed Middleboro, MA?Measurement Computing Corp. and SoftWire Technology Inc. recently announced that the U.S. District Court in Boston granted on Nov. 5, 2003, the two firms' request to allow SoftWire to charge National Instruments (NI) in a pending lawsuit with infringing two patents owned by SoftWire. Judge Robert Keeton delivered the ruling over NI's objections. Subsequently, SoftWire filed an amended complaint accusing NI's LabView product of infringing two of SoftWire's patents. SoftWire alleges that LabView infringes on two virtual instrument technology patents that SoftWire originally acquired from Fluke Corp. These two patents reportedly predate the earliest of NI's patents. SoftWire is seeking unspecified damages for past sales of LabView. SoftWire is also seeking an order prohibiting NI from continuing to sell LabView.
bad news?
Here is an article from a recent Control Engineering newsletter... SoftWire's patent infringement lawsuit against NI to proceed Middleboro, MA―Measurement Computing Corp. and SoftWire Technology Inc. recently announced that the U.S. District Court in Boston granted on Nov. 5, 2003, the two firms' request to allow SoftWire to charge National Instruments (NI) in a pending lawsuit with infringing two patents owned by SoftWire. Judge Robert Keeton delivered the ruling over NI's objections. Subsequently, SoftWire filed an amended complaint accusing NI's LabView product of infringing two of SoftWire's patents. SoftWire alleges that LabView infringes on two virtual instrument technology patents that SoftWire originally acquired from Fluke Corp. These two patents reportedly predate the earliest of NI's patents. SoftWire is seeking unspecified damages for past sales of LabView. SoftWire is also seeking an order prohibiting NI from continuing to sell LabView.
Operating System issues
Just thought I'd pass along this article which some of you may find useful. http://linuxdevices.com/articles/AT4627965573.html Although not LabVIEW related, it deals with software timing issues and understanding how operating systems work. It is somewhat related to several recent info-LabVIEW topics and just too good not to pass along. John H.
