Jump to content

Dan Press

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Run as administrator doesn't change the behavior. Windows 7 x64 This is the same laptop that VIPM 3 woulnd't work with. VIPM 2 does work. - Dan
  2. Oops... I forgot to show hidden folders! Here is the error log. HOWEVER: This log only has records from earlier... before the uninstall / reinstall. The crash now seems to happen before any error log can be generated. =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Tuesday March 08, 2011 at 10:44:25 AM = Automated Message Start = Error -600 occurred at Query Registry Key Info.vi Possible reason(s): LabVIEW: Undetermined Windows registry error. = Automated Message End = = User Defined Message Start = Error(s) Generated in Splash Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM Error Message =========== =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Tuesday March 08, 2011 at 10:44:39 AM = Automated Message Start = Error -600 occurred at Query Registry Key Info.vi Possible reason(s): LabVIEW: Undetermined Windows registry error. = Automated Message End = = User Defined Message Start = Error(s) Generated in Splash Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM Error Message =========== =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Tuesday March 08, 2011 at 10:44:59 AM = Automated Message Start = Error -600 occurred at Query Registry Key Info.vi Possible reason(s): LabVIEW: Undetermined Windows registry error. = Automated Message End = = User Defined Message Start = Error(s) Generated in Splash Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM Error Message =========== =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Tuesday March 08, 2011 at 10:45:29 AM = Automated Message Start = Error -600 occurred at Query Registry Key Info.vi Possible reason(s): LabVIEW: Undetermined Windows registry error. = Automated Message End = = User Defined Message Start = Error(s) Generated in Splash Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM Error Message =========== =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Tuesday March 08, 2011 at 10:48:14 AM = Automated Message Start = Error -600 occurred at Query Registry Key Info.vi Possible reason(s): LabVIEW: Undetermined Windows registry error. = Automated Message End = = User Defined Message Start = Error(s) Generated in Splash Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM Error Message ===========
  3. I just installed VIPM 2010, and it crashed at the splash screen. I uninstalled and reinstalled, and I'm still getting the crash. I do not see a folder called "error" in the VIPM folder. Also, it installed as ...\JKI\VI Package Manager\ and not ...\JKI\VIPM\. - Dan
  4. The laptop is a Dell Alienware M15x with Windows 7x64 Ultimate factory installed. I hope that Dell is not using some strange installation of Windows, but it is tough to tell.
  5. The Input Device VIs in LabVIEW 2009 SP1 to read the mouse position are working.
  6. Update: I was able to install and run VIPM 2.0.3 successfully, so I'll use that for now. - Dan
  7. Hi guys, I've got a new laptop with a fresh install of LabVIEW 2009 SP1 and associated drivers (MAX, DAQmx, etc). I just downloaded VIPM 3.0 (1280) and it installed just fine. I would expect to be able to launch VIPM as usual and see the list of available packages, but instead I just get the loading screen and Windows tells me that the application has stopped and must be closed. I repeated that 3 or 4 times with the same results. I then uninstalled and reinstalled VIPM. Upon the first launch after the reinstall I got an actual LabVIEW error message. See attached picture for that one. So that should help point to something right? The really strange thing is that I do not always see that error dialog. I tried the old reboot routine too, but got the same result. I can find no error log in the VI Package Manager folder so this must be happening very early in the process. I am running Windows 7x64 but with LabVIEW 2009 SP1 (32-bit) installed. I am running VIPM as Administrator. Happy Bug Fogging! - Dan
×
×
  • Create New...

Important Information

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