Jump to content

Bob Schor

Members
  • Posts

    66
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Bob Schor

  1. I recently installed LabVIEW 2021 on a PC that is not allowed to access the Internet.  Used a combination of the Offline Installation (similar to the USB Key of Blessed Memory) plus some interesting communication with NI (very clear instructions) to (a) get a Computer ID, (b) go to an NI Web Site and type in relevant information, including name, license #, and Product, get by return screen a 20-character Activation code, enter code on "locked" PC, and (as we say) "Bob's your Uncle", it is activated.

    So now I want to add the OpenG Toolkit.  I have other PCs where I've installed this easily using VIPM, but the machine I need to place this on has ... no Internet.  Is there an "off-line" way to install the OpenG Toolkit?  [I'm only using a few of the things in OpenG -- I usually install the Toolkit, which brings in about 80% of the packages listed, but I don't mind doing a one-at-a-time bit of work, either ...]  I'm sure it's not quite as simple as copying a bunch of files and folders from my "work" PC, which does have Internet, and where the relevant packages are installed, as there are probably "behind-the-scenes" links and other goodies that are best done "automagically" by VIPM ....

    Bob Schor

  2. I've been using VIPM for years to access the LabVIEW Tools Network.  Recently, one of my machines was set up with a User Account (where I do most of my work) and a separate Admin account.  A while ago, I tried to install EasyXML and got a strange error (among other things, I was told the package was not compatible with my OS nor any version of LabVIEW installed on my computer).  Turns out the "fix" was to run VIPM from my Admin account.

    But do I learn?  No, months later, I try to install another package.  Similar error.  While browsing this Forum, I run across my previous note and see "Run VIPM as Administrator", which (are you surprised?) fixes this "new" error.  You'd think I would have learned my lesson, but I can at least pass on this warning.

    Bob Schor

    • Like 1
  3. Running as Administrator did it!  I was about to do a Follow-up Post saying I'd just "built" a second PC with LabVIEW (on a system where my normal account is NOT an Admin account, just like the PC where I had the problem), and over here (PC-2), EasyXML installed without problems.  So back to PC-1 (where the problem occurred), did Steps 1-3, no go, but Step 4 worked.  Who knows, some permission flag got "stuck", I guess ...

    Many thanks for the quick response.

    Bob Schor

    • Like 1
  4. I've just (re-)installed LabVIEW 2016 (32-bit), 2018 SP1 (32-bit), and 2019 (32-bit) on a Windows 10 PC.  I successfully installed the OpenG Toolkit in LabVIEW 2018 (so VIPM 2019 is clearly working).  When I try to install EasyXML 3.0.0.170, I get an Error message:

    Main Package Name: EasyXML Toolkit for LabVIEW v3.0.0.170
    Package Name with Error: EasyXML Toolkit for LabVIEW v3.0.0.170
    Error Message: VIPM could not install the package jki_lib_easyxml-3.0.0.170 .
    Error Code: 8
    Error Source: Open/Create/Replace File in C67C17A61D892A779727551BEF09A84E->43105161E3ECC5D5EE650DF274C1CB11->0ED5338B9A29C49A512F6049C2CCAE99->1DBEABF39FB76470575E756F0E9DB3AC->87355405EFC0DDB6ACE0A96175E31D86->OGPM Class.lvlib:89AC7BADF759B8183E200C1F7AFA7855->OGPM Class.lvlib:3617A98EB64CF6012064A2A881466B07->579BE417495B7ADCD1FF111EE165D832->VIPM Main Window.vi<APPEND>
    C:\ProgramData\JKI\VIPM\cache\jki_lib_easyxml-3.0.0.170.spec
    ===============

    Please advise how to proceed.

    Bob Schor

  5. It is about four years later, I'm re-installing EasyXML, and this Example is still broken.

    • The newly-installed Package still has the 4-year-old "wrong" Address, not the "corrected" one listed above.  Why not put the "right" address in the Package?
    • When I manually put the corrected address in and tried to run the example, I got "Error 1181 occurred at DataSocket Read in Read RSS Feed.vi.  Possible reason:  Protocol not recognized by LabVIEW.
    • Can you please do the following:  (1) Figure out how to make this example work!  (2) Update your Package Repository to include the repaired, working Exmple.

    Bob Schor

     

  6. I just tried the Read RSS Feed example for EasyXML 2.0, and failed the parse. I'm guessing that the rss cluster that "defines" the parse is very wrong.

     

    The feed is coming from http://forums.lavag.org/rss-8.html. The first few lines of the raw rss data are:

     

    <!DOCTYPE html>
    <html lang="en" xmlns:fb="http://www.facebook.com/2008/fbml">
    <head>
    <meta charset="UTF-8" />
    <title>LAVA</title>
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <link rel="shortcut icon" href='https://lavag.org/favicon.ico'/>
    <script type='text/javascript'>
    //<![CDATA[
    jsDebug = 0; /* Must come before JS includes */
    DISABLE_AJAX = parseInt(0); /* Disables ajax requests where text is sent to the DB; helpful for charset issues */
    inACP = false;
    var isRTL = false;
    var rtlIe = '';
    var rtlFull = '';
    //]]>
    </script>
    Please advise. Is there an alternate rss site that I might use to see this in action?
    Bob Schor
×
×
  • Create New...

Important Information

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