07-18-2008 06:51 AM
07-23-2008 02:56 PM
01-05-2019 11:12 PM
NiMax needs a complete rewrite!
Needing to uninstall and reinstall 1400 Megabytes of code because of a stupid error of this stupid little program is completely unacceptable! You are a software company and you SHOULD write robust code!
Then when I try to repair it with Ni utility I get these stupid errors like "Could not stop service "NI GPIB Hw Enumeration service" (gpibenumsvc) . Verify you have sufficient privileges. "
I am the administrator of this machine. Any idiot can count to 32 ( the number of GPIB devices) Why not use the standard windows error " Enter the administrator password to continue"? This NiMAX error has plagued me for over 10 years now on at least 5 different machines and wasted countless hours of my time. I installed latest versions of NiVisa and Ni488.2 two days ago, on this very capable Windows 10 machine ( 16 G Ram, Intel uP) that I have owned for 9 months and has never thrown an error with very complex simulations, and NiMAX ran successfully exactly ONCE. Now you want me to reinstall both packages again? What is my time worth?
If the NiMAX data base gets corrupted easily you NEED to rewrite how it is done. I see by doing Google searches that this is a common problem, and that there is no easy fix.
I am VERY frustrated, as I need to make code that can be easily deployed across multiple locations and I NEED NiMAX to search out the addresses of the instruments I need my program to communicate with. I do not want to make my system dependent on a poorly designed piece of code. Others are exploring Python and/or Keysight Visa options, and it looks like I will need to do that as well, because this is just not acceptable! JonDutra(AT)apple(DOT)com
01-06-2019 07:18 AM
Could you please provide a little more information about your system to help us make better suggestions and possibly understand better the nature of your problem?
Bob Schor
01-06-2019 12:37 PM - edited 01-06-2019 12:38 PM
@JonDut wrote:
I am the administrator of this machine.
Windows 10 has a better security model (and that's a good thing!), so even if you are administrator, it does not mean that the software you are running has automatically also administrator privileges and can do whatever it wants (unless you actually right-click..run as administrator).
If you use windows 10, you probably should not follow 10+ year old advice (or respond to a 10 year old thread), because it might be stale and not even applicable to windows 10. It is impossible to get to the gist of your problem or help, because 90% of your post is just rambling. Are all your software versions officially supported under windows 10?
So start answering Bob's questions above and we'll try to help.