Jump to content

vix

Members
  • Content Count

    16
  • Joined

  • Last visited

Everything posted by vix

  1. I had the same problem too, but I noticed this only happens with some OpenG packages: ogrsc_rename_folder_of_vis 4.0.015 OpenG Error Library 4.2.0.23 OpeG LabVIEW Data Library 4.1.0.16 OpenG MD5 Digest Library 4.1.1.10 OpenG Numeric Library 4.1.0.8 OpenG String Library 4.1.0.12 I reproduced this issue even with a fresh LabVIEW 2011 installation on Win 7 64-bit if I try to install one of these packages without any other package already installed. I installed without problems other packages (OpenG, MGI, LAVA, ...), or different versions of these ones.
  2. Hi Justin, I think that the same problem occurs with: ogrsc_rename_folder_of_vis 4.0.015 OpenG Error Library 4.2.0.23 OpeG LabVIEW Data Library 4.1.0.16 OpenG MD5 Digest Library 4.1.1.10 OpenG Numeric Library 4.1.0.8 OpenG String Library 4.1.0.12 I reproduce the same issue even with a fresh LabVIEW 2011 installation on Win 7 64-bit if I try to install one of these packages without any other package already installed. I installed without problems other packages (OpenG, MGI, LAVA, ...). Could you confirm that the old VIPM 2011.0.0 is not affected by this problem, please?
  3. Japan is not my preferred mirror. It's Switzerland! When the packages haven't beem available yet on Japan mirror, I saw them listed in VIPM, so the mirror list works properly, I think And I'm quite sure the problem is not in the download, but during installation. I attached the *.spec files (downloaded in cache folder) for OpenG Error Library 4.1.0.13 and OpenG LabVIEW Data Library 4.1.0.16. In C:\Program Data\JKI\VIPM\cache, for OpenG Error Library 4.0.0.12 (currently installed) I can see 3 files: *.spec, *.bmp and *.vip. For the new 4.1.0.13 release, only the *.spec file is present cache.zip
  4. OK. I tried today and I was able to successfully upgrade all the MGI packages, and OpenG Array Library (to 4.1.0.13 version). But when I try to update OpenG Error Library (from 4.0.0.12 to 4.1.0.13) OpenG LabVIEW Data Library (from 4.0.0.7 to 4.1.0.16) VIPM hangs in the usual way (Ready... bar and toolbar icons flickering). I attached the log file =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: mercoledì ottobre 12, 2011 at 01:27:34 = Automated Message Start = Error 1 occurred at (No Package Info found for "oglib_lvdata-4.1.0.16") 4B1BC73B58CE6FEED2537F0E786EA332 in OGPM Class.lvlib:4A07E0C9A3D3DE00F4DB57E804C0A08E->VIPM Package License Dialog.vi->VIPM Main Window.vi Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi = Error Handler Call Chain End = =========== END of VIPM Error Message =========== =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: mercoledì ottobre 12, 2011 at 01:27:34 = Automated Message Start = Error 1 occurred at (No Package Info found for "oglib_lvdata-4.0.0.7") 54A2F77E1067504A41D4F02B10720CB6 in A64AC4750BC7802DAF1C36B4023E12C9->VIPM Main Window.vi Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi = Error Handler Call Chain End = =========== END of VIPM Error Message =========== =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: mercoledì ottobre 12, 2011 at 01:27:34 = Automated Message Start = Error 1 occurred at (No Package Info found for "oglib_lvdata-4.0.0.7") 54A2F77E1067504A41D4F02B10720CB6 in A64AC4750BC7802DAF1C36B4023E12C9->VIPM Main Window.vi Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi = Error Handler Call Chain End = =========== END of VIPM Error Message =========== and so on...
  5. I still can't install most of the OpenG packages through VIPM, and now I found the reason: they're not existent packages!!! But listed in VIPM. For example in VIPM I can see "OpenG Error Library v. 4.1.013", but I can't install it (message = VIPM can't dowmload the package from the server). But I can install the old version 4.0.0.12. The problem is that in Sourceforge I can find 4.0.0.12 (here) but not 4.1.0.13.
  6. yes, but they don't support LV 6.1 anymore... and so, no help from NI... Vix
  7. I tried on a fresh openSUSE 10.2 installation with LabVIEW 6.1 only, and I had the same "another labview version on the port" message. So I'm not able to register lv 6.1, even if it's alone!!! I noticed that when I enable the VI Server TCP/IP, every time I launch lv 6.1 I see the splash window completely black for 8-10 seconds, then labview starts correctly. What could be the problem? -Vix
  8. Thanks for your help. I've found the .labviewrc file in the home directory, and I've noticed that it has got three kinds of entries: - labview6 - labview8 - labview Unfortunately the TCP/IP settings are in the labview group: so they're common to labview 6.1 and 8.0 I've tried to duplicate the settings (labview6 and labview8) but this didn't work. I've tried to move this settings in the .labviewrc files in the installation directories, but labview doesn't recognize them and re-write labview.server.tcp.enabled and labview.server.tcp.port in the ~/.labviewrc file. So I've started a topic in the NI forum, and I hope someone could help me... -Vix
  9. Hi Jim, thank you for your quick answer. I had already read on the NI site the informations you remembered me, but there should be something wrong. Probably it's connected to a LabVIEW problem, but I let you know the situation. I installed lv 6.1 in /user/local/lv61/ folder (the one proposed as default by the installer) and lv 8.0 in /user/local/natinst/labview/ In all my linux partition there isn't any labviewrc file, so I don't understand where labview stores its settings. I created a labviewrc file in /user/local/lv61/ and lv 6.1 loads this settings in the right way. Reading the informations on the NI site, it seems that settings as the TCP-IP port should be in the labviewrc file in the two labview folders (/user/local/lv61/ and /user/local/natinst/labview/, correct?) but these files don't exist. So I'm confused.... on monday I'll try to check if they are hidden files, or something like that... If you have any suggestions, you're welcome Tks a lot -Vix
  10. I have linux Suse 10.0 with LabVIEW 6.1 and 8.0 installed. I installed VIPM 1.0 and I'm able to register LV 8.0 (TCP/IP port 3363) and successfully install package. I can't register LV 6.1: if I use port 3363 I find a warning saying that there's another labview version on that port (and OK, there,'s the 8.0). But if I change the port for LV 6.1 (as recommended, choosing for example 3364), in LV 8.0 the setting is automatically changed to 3364. And if I change the setting in LV 8.0, the same TCP/IP port is automatically set in LV 6.1. So I always have the same TCP/IP port for both the labview version, and the "Port Test" is successfullt only for LV 8.0. Is there some known problem in registering two different labview version under linux? Tks
  11. Hi, I'm trying to install VIPM in Linux Fedora Core 6. I checked, and the LabVIEW 8.0.1 Run Time Engine is installed. I downloaded the vipm-1.0-linux, but I receive this error message: Can't load LabVIEW runtime library /usr/local/lib/liblvrt.so.8.0 libOSMesa.so.4: cannot open shared object file: No such file or directory The problem is that I have the shared object liblvrt.so.8.0 in /usr/local/lib/ (as expected), and libOSMesa.so.4 in /usr/local/matinst/LabVIEW-8.0/ could someone help me? Thanks in advance vix
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.