I currently have a copy of labview 8.0, and 8.2, and a windows 10 64 bit laptop. We have one experiment setup (3 pieces of hardware) we want to use with this labview, but are having some issues. I believe these issues stem from the 64-bit operating system/installer. (When trying to install I get an error: "the windows installer engine is corrupt. to attempt to resolve this issue, please register the engine by running regsvr32.exe on msi.dll" I have already looked at posts on labview forums related to this error). Namely, we can install labview 8.0 onto the system, but not labview 8.2. However, the .vi's from the company only work in labview 8.2. It appears there was an patch version of labview 8.2 called labview 8.2.1 that allowed it to be installed on 64-bit systems, but this is unvailable to me since I do not have a service membership.What are my options? Is there another way to install labview 8.2 on my system? I am NOT proficient in labview, and this is my first time trying to use it, so I would not know how to create my own program for this equipment.Thanks!
"Namely, we can install labview 8.0 onto the system, but not labview 8.2. However, the .vi's from the company only work in labview 8.2." I'm surprised you can install 8.0. But just because it installs doesn't mean you won't have problems.
Activation Code Labview 8.2 64
Download Zip: https://urluso.com/2vHb5N
"However, the .vi's from the company only work in labview 8.2" Is there a specific reason it won't work in LV 8.0 like it uses a feature that didn't exist? If you don't want to give up yet, you can trying uploading the VI's to the Version Conversion board and request to have them downconverted from LV 8.2 to 8.0.
Thank you for the reply. You are right that it is surprising that labview 8.0 is working, but it seems to interface fine with 2/3 of the pieces of equipment. The version conversion forum actually reverted the 8.2 .vi's to 8.0. However, in one of the programs it is calling for some subvi's that are not present. Specifically I am missing:
I believe it is using Mathscript. And I think that is where the issue is. It is my understanding the labview 8.0 does have MS, but maybe not all of the same subvi's as 8.2. Another possibility might be that for some reason not all of the subvi's installed correctly for me. Nevertheless, that is what I am trying to figure out right now.
Dynamic ELF libraries can be output but the C compiler does not generateposition independent code (PIC). It means that the dynamic librarycode generated by TCC cannot be factorized among processes yet.
TCC linker eliminates unreferenced object code in libraries. A single pass isdone on the object and library list, so the order in which object files andlibraries are specified is important (same constraint as GNU ld). No groupingoptions (--start-group and --end-group) are supported.
Note that pointer size is unchanged and that code generatedwith bound checks is fully compatible with uncheckedcode. When a pointer comes from unchecked code, it is assumed to bevalid. Even very obscure C code with casts should work correctly.
The generated code and data are written in sections. The structureSection contains all the necessary information for a givensection. new_section() creates a new section. ELF file semanticsis assumed for each section.
The TCC code generator directly generates linked binary code in onepass. It is rather unusual these days (see gcc for example whichgenerates text assembly), but it can be very fast and surprisinglylittle complicated.
vsetc() and vset() pushes a new value on the valuestack. If the previous vtop was stored in a very unsafe place(forexample in the CPU flags), then some code is generated to put theprevious vtop in a safe storage.
The gv(rc) function generates code to evaluate vtop (thetop value of the stack) into registers. rc selects in whichregister class the value should be put. gv() is the mostimportant function of the code generator.
ActiTools has the following features: - Trigger: Shows how to convert between binary to decimal trigger codes. - Muter: Make a new BDF file with selected Trigger lines kept Low from an existing BDF file. (new in version 9.02) - Cropper: Crops large BDF files into smaller files. - Merger: Merges 2 .bdf files into 1 .bdf file. - Decimator: Decimates (downsample) your BDF file into a smaller file. - Reducer: Reduces the number of channels in a BDF file. - Converter: Converts 24 bit BDF files to 16 bit AC (high-passed) EDF file. - Repairer: Make a new BDF file from an existing BDF file with a corrupted file header. - Editor: Edit the ID fields and channel labels in an existing BDF file. - Configurator: Edit items which are not editable from ActiView in an existing configuration (*.cfg) file. (new in version 9.02) - Equalizer: Make new BDF file with equalized ABR channels from an existing BDF file. (lower high-pass point) (new in version 9.02)
ActiTools has the following features: - Trigger: Shows how to convert between binary to decimal trigger codes. - Cropper: Crops large BDF files into smaller files. - Merger: Merges 2 .bdf files into 1 .bdf file. - Decimator: Decimates (downsample) your BDF file into a smaller file. - Reducer: Reduces the number of channels in a BDF file. - Converter: Converts 24 bit BDF files to 16 bit AC (high-passed) EDF file. - Repairer: Make a new BDF file from an existing BDF file with a corrupted file header. - New in version 9.01: editor for BDF headers. 2ff7e9595c
Comments