Jump to content

Fluke

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fluke

  • Rank
    Novice
  1. I had the exact same issue. I had to go back to the previous version of WINDOWS 10. I didn't spend much time trying to figure out what was wrong.
  2. Are you using the OGM web interface to tell IVM to do this? If so, try using the OGM interface from within the program itself. I was frustrated for days until I happened upon that solution. Somehow the web interface doesn't record the information correctly in the .ini file.
  3. Are you using the OGM web interface to tell IVM to do this? If so, try using the OGM interface from within the program itself. I was frustrated for days until I happened upon that solution. Somehow the web interface doesn't record the information correctly in the .ini file.
  4. Are you using the OGM web interface to tell IVM to do this? If so, try using the OGM interface from within the program itself. I was frustrated for days until I happened upon that solution. Somehow the web interface doesn't record the information correctly in the .ini file.
  5. Fluke

    Call Counter

    I’ve been searching for a solution to this for days and finally found the setting in the Windows registry. Load REGEDIT and search for “callsequenceno” (without the quotation marks). Then change the value to whatever you want the next call to be. For example, change the value of "callsequenceno" to 1 to have the next call be call number 1.
×
×
  • Create New...