vix Posted October 10, 2011 Report Share Posted October 10, 2011 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. Link to comment Share on other sites More sharing options...
Jim Kring Posted October 10, 2011 Report Share Posted October 10, 2011 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. It looks like a problem with SourceForge's mirroring system. I see both files, here: http://sourceforge.net/projects/opengtoolkit/files/lib_error/4.x/ Note that this was just released over the weekend (I think on Saturday), so maybe the Japanese mirror will get updated soon. Link to comment Share on other sites More sharing options...
vix Posted October 12, 2011 Author Report Share Posted October 12, 2011 It looks like a problem with SourceForge's mirroring system. I see both files, here: http://sourceforge.net/projects/opengtoolkit/files/lib_error/4.x/ Note that this was just released over the weekend (I think on Saturday), so maybe the Japanese mirror will get updated soon. 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... Link to comment Share on other sites More sharing options...
Jim Kring Posted October 12, 2011 Report Share Posted October 12, 2011 Have you tried changing your preferred mirror to not be Japan? Link to comment Share on other sites More sharing options...
vix Posted October 13, 2011 Author Report Share Posted October 13, 2011 Have you tried changing your preferred mirror to not be Japan? 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 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.