inaki castillo

<p>All tests pass ok.</p> <p>However, in the Error Log i can see several &quot;user interface&quot; errors, some of them from May 2023.</p> <p></p>

<p>It fails from time to time. When it fails it happens always when setting waveform intensity. So this seems to be the door to the problem. My waveform has nothing special. I am using 4 analog channels plus some digital channels. I work a lot with the zoom and panning tools. Usually i do not change the intensity. But, after the first crash i have tried it several times just to be sure it wont happen again. Unfortunately it keeps crashing. It is not systematic. I could not tell which sequence of events is exactly triggering the problem.</p>

I was trying to set wave persistence time in my MDO3054. Then I realized I was unable to set persistence using 'a' knob. I was able to set it using the numeric keypad though. Then I tried to move the cursors on the display. No way. Apparently these two knobs did not work after entering persistence setup.<br> I had to restart the system. After restart knobs 'a' and 'b' started to work again.<br> <br> Firmware version: 1.30.<br> <br> Looks like a bug to me.

<p>These are different things. You can be an user that belongs to Administrators group, and you can still be running below the &quot;administrator&quot; level. If you have access to a Windows machine, right click on any program on your desktop and chose &quot;run as administrator&quot;. This does not change your user at all (you can see there is no logon involved). This extra level is made so that an user, even belonging to Administrators group, can be restricted in some actions that can change system configuration.&#160;</p> <p>Some programs avoid running as administrator because that level allows to access resources that are forbidden to normal programs and can be used to reverse engineer a program. Thats why i asked on my post about the possibility for this behavior to be intentional by Tektronix. &#160;In case you wonder why i want to run my program as administrator it is because some performance analysis tools need this level to work.</p> <p>The NI stuff is possibly having some influence. I will try to clean it.</p>

When I say 'administrator' account I mean i raise the current user to run as administrator. I am not changing the user, so the profile is the same.<br> I do not have other Visa sessions running. I can repeat the test under the same user, not raised to Administrator, and it works as expected.&#160;<br> <br> It is weird i did not detect this problem before, because I use my user raised to Administrator all the time. It might be related to some update somewhere... Also, in the past I used a NI Visa library. Dont know if it can be related to the problem. I can see parts of NI software still installed.&#160;

<p>I am trying to connect to a MDO3054&#160;scope. However, the problem happens before I can access the scope. I mean, the scope can be OFF and the problem still happens.</p> <p>When the call fails I am just opening a VISA session, At this moment I&#160;do not know how many instruments are connected.</p>

<p>Thanks for your feedback, but I have updated to 4.2 and the behavior is exactly the same.&#160;</p>

<p>Tektronix Visa 4.1.1.22</p>

<br> I have found that function viOpenDefaultRM fails when the calling thread is running as Administrator.<br> The call to the function never returns.&#160;<br> It works fine when the thread runs under a normal user account.<br> Is this intentional&#160; ?&#160;<br> (I am compiling the program with VS2017)<br> <br> &#160;

FYI, the problem is solved by entering again the options key.&#160;