Jump to content

Jim Kring

JKI Team
  • Content Count

    1,666
  • Joined

  • Last visited

  • Days Won

    37

Posts posted by Jim Kring


  1. Chris,

     

    The problem was caused by one of the files inside the package having a read-only attribute, which was preventing it from being installed correctly -- this is a bug, and an internal report has been created (Case 2548).

     

    As a work-around, you should remove all read-only attributes from files, before they are packaged.

     

    Thank you,

     

    -Jim


  2. I added a new VI to an existing .ogp file.

     

    I looked in the directory you mentioned and found a couple of files, but neither one seemed to be related to my particular package. I've attached them for your information.

     

    FYI, my machine is stand-alone, so there is no way for it to connect to the internet.

     

    I spent some more time yesterday working on this problem after I reported this bug, and I believed I had it solved. Then I made a change to the "new VI", and recreated the package and this error occured again.

     

    I can email you the ogp file if it would help debug what is going on.

     

    BTW, I'm using beta 1 of VIPM at this point. I plan on upgrading soon.

     

    Thanks,

    Chris

     

    Chris,

     

    Yes, please open a support ticket, here, and then we can look into the specifics of your problem.

     

    Thank you,

     

    -Jim


  3. I work on several machines that will never be connected to the internet.

    So I am wondering how I can transfer my packages to these computers.

     

    For OpenG Commander I could take the cache folder and put it in with a new instalation.

    Is it the same for VIPM or does the database folder hold the information now.

     

    Mark,

     

    As Chris mentioned, you can simply copy the cache folder contents (from a Commander or VIPM installation) to another VIPM installation's cache folder. Another option is to use the Package >> Add Package(s) to Package List, menu option to add a folder of packages into VIPM's package list.

     

    Please note, that we are actively working on features to make it easier to import package configurations onto non-networked VIPM installations.

     

    Thank you,

     

    -Jim


  4. Mark,

     

    I'm glad that your using VIPM and that you've been able to quickly resolve your issue :)

     

    Here's a tip, you might find useful...

     

    We recommend putting each version of LabVIEW on a unique TCP-IP port. This will allow VIPM to communicate with different versions of LabVIEW, even when multiple versions of LabVIEW are running at the same time. When all versions of LabVIEW are configured for the same TCP-IP port, the first version of LabVIEW will grab the port and other versions of LabVIEW that are subsequently launched will not be able to start the TCP-IP listener. The easiest way to adjust your TCP-IP settings is to let VIPM automatically adjust LabVIEW's VI Server settings while testing the connection (see screenshot, below).

     

    auto_adjust_tcp.png

     

    Thanks,


  5. Like the title says, what is error 8? I get this error when installing a package that I recently added file to. I don't know if there is something wrong with the package or VIPM.

     

    Chris,

     

    Thank you for reporting this problem. Hopefully we can get to the bottom of it.

     

    Error 8 is a file permission error. Also, I need some more insight into what you mean when you say "installing a package that I recently added file to"? Did you add new VIs/files to the package (.ogp) file or that you added VIs/files into the installed location (such as the palette-sync'ed folders beneath user.lib)? Also please take a look inside "C:\Program Files\JKI\VI Package Manager\error\" for more error details.

     

    Thank you,

     

    -Jim


  6. Hi Jim,

     

    that might take a while, but can I run some other tests on your installer (or a subsection)?

     

    You can contact me via Lava

     

    Ton

     

    Edit:

     

    I've run the program on a Win2K dutch system (standard). No shortcuts as well...

     

    It is excellent that the program doesn't need administrator rights to install

     

    Ton

     

    Ton,

     

    Please see the announcement, VI Package Manager 1.0 Beta 2 Released. This release has a fix for your issue.

     

    Thank you,

     

    -Jim


  7. I'm quite new to Labview and I was looking for some examples. So I casually found this site, and it looks really like the perfect place for me.

    While I'm installing VIPM, I'd like to underline a couple of bugs.

    Both regard the installation on not english computers. On my pc Labview is located in the "programmi" folders instead the "program" one. It's not an important bug... all what I had to do is to point manually the labview.exe file.

    On my mac the problem is bigger: in fact during the installation of VIPM an error message occurs and it is impossible to complete it.

    Best regards!

    Luca

     

    Luca,

     

    Please see the announcement, VI Package Manager 1.0 Beta 2 Released. This release has a fix for your issue.

     

    Thank you,

     

    -Jim


  8. Hallo,

    I've installed VIPM on my machine but it does not recognized the package I've previous downloaded and installed with the OpenG Commander. So now VIPM ask me to download and install all the package I've already on my pc. Any solution?

    I work with windows XP and Labview 7.0

    Bye

     

    Please see the announcement, VI Package Manager 1.0 Beta 2 Released. This release has a fix for your issue.

     

    Thank you,

     

    -Jim


  9. I'm quite new to Labview and I was looking for some examples. So I casually found this site, and it looks really like the perfect place for me.

    While I'm installing VIPM, I'd like to underline a couple of bugs.

    Both regard the installation on not english computers. On my pc Labview is located in the "programmi" folders instead the "program" one. It's not an important bug... all what I had to do is to point manually the labview.exe file.

    On my mac the problem is bigger: in fact during the installation of VIPM an error message occurs and it is impossible to complete it.

    Best regards!

    Luca

     

    Luca,

     

    Thank you for trying VIPM and for the valuable feedback.

     

    The problem with the shortcut location is a known issue and the fix will appear in the next (Beta 2) release. See this discussion, for more info.

     

    Regarding the Mac installation, have you retried running the installer? Others have reported occasional errors when installing on Mac, but have had success on further attempts. Also, do you have Stuffit Expander 10, or later, installed? The VIPM installer uses this, on Mac, for unpacking some archives.

     

    Regards,

     

    -Jim


  10. Jim,

    What protocol(s) will my networked package repository need to be running to have the enterprise edition access its packages?

     

    Thanks,

    Chris

     

    Chris,

     

    We have the capability to support a variety of protocols, such as UNC path, local path, ftp, and http/https (with or without password authentication). I would be happy to discuss your organization's specific needs, off-line - please send us an inquiry via our contact form.

     

    Thank you,

     

    -Jim


  11. Hi,

     

    I've installed VIPM and I haven't had any problem (until now), but in the splash screen it appears a message that says that it expires in X days. As I suppose that I've got the community version, what does this mean?. We can only use the community version during 100 days?

     

    Thanks.

     

    Yes, the beta will expire. When this happens users are expected to upgrade to the final release (or perhaps another beta release). The final release will not expire and will be freely available to everyone.

     

    Thank you,

     

    -Jim


  12. I used the packagemanager to install the packages to LV 8.

    It appeared to work great. I closed every thing and reopened LV 8 and none of the vi's showed up in the pallet.

     

    I opened the package manager again and checked and they all appear in the installed list for LV8.

     

    Any suggestions on how to get the VI's to appear in the pallet?

     

    thanks,

    Fred

     

    Fred,

     

    Make sure that you have installed the latest version of the ogrsc_dynamicpalette package. This will create an "OpenG" category in the Functions palette, where all of the OpenG libraries will appear. I hope that works for you.

     

    Thank you,

     

    -Jim


  13. I installed VIPM last night, and was impressed with the self extracting installer (written in LV!), the look / feel of the application and its abilities. I liked the ability for it to recognize packages that were upgrades, and only install the latest versions. I am running LV 7 on the machine I'm working on right now, but I plan to install VIPM on machines with 7, 7.1, and 8.0.1. I see that VIPM has the ability to load packages from disk, which is the way I have to load packages, since most of my work machines are not connected to the internet. My group has developed our own reuse library and we distribute them internally via OpenG Packages, so this tool will help us keep those packages up-to-date on all our machines. I also look forward to reading your blog posts on how you developed VIPM and how you used subversion and OpenG builder to make your job easier.

     

    Thanks JKI :D Enjoy NI Week :D

     

    Chris,

     

    Thanks for taking the time to get to know and use VIPM. We are happy that you have had a positive experience! If you are using your own VI Packages, then you will want to keep an eye out for VIPM Enterprise Edition. This will provide support for connecting to your organization's networked package repository, as well as other power features like configuration management. Stay tuned :-)

     

    Regards,

     

    -Jim

     

     

    I found the whole process very polished and easy to use. My only hang up was having to "register" LabVIEW with VIPM. I thought it was telling me to register with NI, not with the program. Once I figured that out, everything went fine.

     

    Great job!

    Derek

     

    Derek,

     

    Thank you for the feedback! Other's, too, have commented about the fact that the term "register", with respect to registering LabVIEW versions with VIPM, is a little confusing. We'll see if we can remedy this, in the future.

     

    Thank you,

     

    -Jim


  14. Ton,

     

    Ton wrote:

    > I love to have an option to set a location for these items (eg. Start\Programs\National Instrument\Tools\VIPM)

     

    Thanks for the suggestion. One quick solution would be for you to create these Start menu folders/shortcuts yourself.

     

    > The documents folder in all 3 cases were located on the D drive. Program files, LabVIEW, in the 'normal' location

    > I've run the same installer on a 'english' laptop, and the shortcuts were installed in the right direction.

    Is it possible for you to test on a Dutch installation with the documents folder located in the standard (C drive) location? This might hint as to whether the problem is related to the non-English version of Windows or, rather, the location of the documents folder. My instinct makes me think that it is probably an issue with the non-English version of Windows.

     

    Thank you,

     

    -Jim


  15. Chris,

     

    Can you see if there is an error log file here (or in a similar location, depending on your choice of installation location):

     

    C:\Program Files\JKI\VI Package Manager\error\

     

    And, if there are any error log files, could you please post them as an attachement, in this thread.

     

    Thanks,

     

    -Jim


  16. Hi Chris,

     

    > Firstly can I congratulate you on the launch of VIPM, looks like a great upgrade for users of Commander. I certainly am looking forward to details of the Enterprise edition. :D

    Thanks. The team has worked very hard on this release and it is nice to get this feedback!

     

    > OK so the install of VIPM seemed to go quite smoothly, I successfully registered all versions of LabVIEW installed on my machine. When it came to setting the Proxy settings things didn't quite work out for me.

    I have set proxy settings on Commander with no difficulties in the past however there is now a UserName and Password section. Becuase we use Novell Client Trust here at work I am already authenticated and therefore no Password U/name is required however when I clear the contents of the Password box and select OK they reappear if I then return to the Internet Settings page at any time.

     

    This is just a display bug. The password field should be empty if there is no password configured, but it is currently being filled with 6 null characters (just for display). However, if you have not entered a username, then the HTTP request will not attempt to authenticate during proxy requests. I don't think that this bug is affecting you.

     

    > In addition to this I also noticed that the list of mirror sites is empty as is the SourceForgeMirrors.txt file. Can I used the same file that is used by Commander ?

    This should not be a problem. VIPM will automatically refresh the mirrors list, as needed. You can also refresh the list manually, by pressing the "Refresh Mirrors" button in the options dialog (see screenshot below).

     

    refresh_mirrors.png

     

    I am not really sure what could be the problem. Are you certain that the proxy host and port are correct and that you have a reasonable TCP timeout?

     

    Regards,

     

    -Jim

×
×
  • Create New...

Important Information

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