Windows Installation Instructions

  1. Table of Contents

  2. Overview

    MIMIC runs on

    • Windows Vista Business Edition
    • Windows Server 2008
    • Windows 7
    • Windows Server 2012
    • Windows 8
    • Windows 10
    • Windows Server 2016 Standard
    • Windows Server 2019
    • Windows 11

    It is highly recommended to install the latest service pack for the respective OS. The following are some of the most common problems encountered on Windows, and their fixes:

  3. Account Privileges

    For Windows Vista, Server 2008 and Windows 7 and newer, please go to the section below.

  4. Firewalls

    Due to pervasive security attacks against Windows systems connected to the Internet, it has become common to run a software firewall on recent versions of Windows.

    MIMIC will coexist with a software firewall, provided that the firewall is configured to recognize MIMIC as a program allowed to access the network. MIMIC will, due to its very nature of simulating networked components, open network sockets and communicate with external applications (eg. network management applications, telnet clients, etc).

    There are certain components of MIMIC that will access the Internet (eg. specific web sites to determine software updates, etc), but only if explicitly configured by the user.

  5. Assigning IP Addresses

    MIMIC requires at least one operational network interface card (NIC). On Windows Vista or later, as on the Unix platforms, MIMIC dynamically assigns IP addresses when starting each agent instance.

  6. 5000 / 10000 agent support

    Different versions of Windows have performance limitations while running large numbers of IP addresses. The following are the limits on the different versions of Windows:

    • Windows Vista: 10000 agents;

    • Windows Server 2008: 10000 agents;

    • Windows 7: 10000 agents;

    • Windows Server 2012: 30000 agents;

    • Windows 8: 30000 agents;

    • Windows 10: 30000 agents;

    • Windows 11: 30000 agents;

    In empirical tests, going beyond those limits introduced non-deterministic instability and performance problems.

  7. 20000 / 30000 agent support

    You can run 20000 agents only on Windows Server 2003, and 30000 agents only on Windows Server 2012, 2019, Windows 8, 10, 11, and then only with 64-bit executables, and more on the Unix platforms.

  8. Virtual Memory

    MIMIC is a specially memory-intensive application, and it needs plenty of physical memory (RAM) and virtual memory (swap space) for the more complex device simulations. We recommend an absolute minimum 1 GB of RAM and 2 GB of swap space to start. Verify that you have enough swap space in the System Control Panel.

    You should as a rule of thumb have twice the swap space as your physical memory.

    Different versions of Windows on Intel systems impose different limits on the amount of virtual memory accessible for the MIMIC Simulator, but currently the absolute limit is below 4 GB due to 32-bit addressing limitations, which the 64-bit architecture does not have.

    On all 32-bit versions of Windows there is a 2 GB limit on per-process virtual memory. The following steps only apply to legacy 32-bit systems.

    On Windows Vista and later Microsoft has removed the boot.ini file and provided the BCDEdit command to enable 3 GB addressing as documented in this document.

    To enable this expanded capability on Windows Vista and later, as an Administrator in a Command Prompt window, type the command:

    BCDEdit /set IncreaseUserVA 3072

    And then restart your computer.

    This will make "a full 3 GB of virtual address space available to applications and reduces the amount available to the system to 1 GB."

  9. Duplicate IP Address

    For Windows Vista, Server 2008 and Windows 7 and later, please go to the section below.

    If Windows detects that an IP address on one of its Network Interface Cards (NICs) conflicts with another system (duplicate IP address), then it tries to resolve this problem by shutting down the NIC and displays a message such as:

    The System has detected an IP address conflict with another system on the
    network.  The local interface has been disabled.  More details are
    available in the system event log. Consult your network administrator to
    resolve the conflict.

    You must not have duplicate IP addresses on a connected network, neither with MIMIC or otherwise.

    NOTE: you can disable duplicate IP address detection by following the instructions in the article in the ( now defunct) Microsoft Knowledge Base titled How to Disable the Gratuitous ARP Function. It is appended here:

    How to Disable the Gratuitous ARP Function
    View products that this article applies to.
    Article ID	:	219374
    Last Review	:	February 24, 2007
    Revision	:	3.2
    This article was previously published under Q219374
    When a Windows NT-based computer starts, a packet is broadcast on the
    network containing the computer's TCP/IP address to prevent the use of
    duplicate addresses on the same network. This is called a gratuitous
    Address Resolution Protocol (ARP) packet. Routers and other network
    hardware may cache routing information gained from multiple gratuitous
    ARP packets. For both performance and maintenance reasons, it is possible
    to disable this feature in Windows NT.
    To resolve this problem, obtain the latest service pack for Windows
    NT 4.0. For additional information, click the following article
    number to view the article in the Microsoft Knowledge Base: 152734
    ( How to Obtain the Latest
    Windows NT 4.0 Service Pack
    Microsoft has confirmed that this is a problem in the Microsoft products
    that are listed at the beginning of this article. This problem was first
    corrected in Windows NT 4.0 Service Pack 5.
    To disable gratuitous ARPs after applying this hotfix:
    1.	Click Start, click Run, type regedt32, and then click OK.
    2.	On the Windows menu, click HKEY_LOCAL_ MACHINE on Local Machine.
    3.	Click the \System\CurrentControlSet\Services\TcpIp\Parameters folder.
    4.	Double-click the ArpRetryCount value, type 0, (for Windows XP, type 1) and then click OK.
    5.	Quit Registry Editor, and then restart the computer.
  10. Media Sense on Windows Vista and newer

    Newer versions of Windows (Windows Vista onwards) have a TCP/IP feature whereby it can sense if a NIC is actually connected to the network. By default, a NIC is disabled if it is not found to be on the network, which prevents agents from starting in MIMIC. There is a way to disable this behaviour so that you can work on standalone Windows machines. Attached is an excerpt of the Microsoft KB article on this topic... Please remember to make a copy of your registry before making any changes just to be on the safe side.

    NOTE Windows Vista and newer have no way to disable this feature. You can only run MIMIC on Windows Vista and newer with the system connected to a network.

    How to disable the Media Sensing feature for TCP/IP in Windows
    On a Windows-based computer that uses TCP/IP, you can use the Media
    Sensing feature to detect whether the network media are in a link
    state. Ethernet network adapters and hubs typically have a "link" light
    that indicates the connection status. This status is the same condition
    that Windows interprets as a link state. Whenever Windows detects a
    "down" state, it removes the bound protocols from that adapter until
    it is detected as "up" again. Sometimes, you may not want the network
    adapter to detect this state. You can set this configuration by modifying
    the registry.
    Let me fix it myself
    Important This section, method, or task contains steps that tell you how
    to modify the registry. However, serious problems might occur if you
    modify the registry incorrectly. Therefore, make sure that you follow
    these steps carefully. For added protection, back up the registry before
    you modify it. Then, you can restore the registry if a problem occurs. For
    more information about how to back up and restore the registry, click the
    following article number to view the article in the Microsoft Knowledge
    Base: 322756 How to back up and restore the registry in Windows
    To prevent the network adapter from detecting a link state, follow these steps.
    Note The NetBEUI protocol and the IPX protocol do not support Media Sensing.
        Start Registry Editor.
        Locate the following registry subkey:
        Add the following registry entry to the
        Name: DisableDHCPMediaSense
        Data type: REG_DWORD (Boolean)
        Value: 1
        Note This entry controls the behavior of Media Sensing. By default,
        Media Sensing events trigger a DHCP client to take an action. For
        example, when a connect event occurs, the client tries to obtain a
        lease. When a disconnect event occurs, the client may invalidate the
        interface and routes. If you set this value data to 1, DHCP clients
        and non-DHCP clients ignore Media Sensing events.
        Restart the computer.
  11. IPv6 Support

    IPv6 is supported only on Windows Vista and newer. This is an OS platform limitation.

    IPv6 is installed as detailed here. IPv6 addresses use an additional Scope ID as detailed on the Microsoft web-site.

    If the IPv6 module gets corrupted, you can fix this with this command from the COMMAND prompt:

    netsh interface ipv6 reset

    NOTE: check the Known Problems section for limitations.

  12. Performance impact of Windows services

    Running unnecessary Windows services impacts performance adversely on a MIMIC system. The observed impact has been an approximate 300% slowdown in starting and 1000+% slowdown stopping agents, and a 10-20% slowdown in servicing requests. This is documented in a Microsoft support page titled "Memory usage by the Lsass.exe process on domain controllers that are running Windows Server 2003 or ...". The executables running the services end up hogging the CPU. This can easily be seen in a process listing in the Windows Task Manager.

    Thus if you are running large lab configurations, we recommend to stop the following unnecessary services in the Services Control Panel:

    Display Name          Service Name      Path to executable
    IPSEC Services        PolicyAgent       WINDOWS\system32\lsass.exe
    Protected Storage     ProtectedStorage  WINDOWS\system32\lsass.exe
    Print Spooler         Spooler           WINDOWS\system32\spoolsv.exe
    DHCP Client           Dhcp              WINDOWS\system32\svchost.exe -k NetworkService
    DNS Client            Dnscache          WINDOWS\system32\svchost.exe -k NetworkService
    TCP/IP NetBIOS Helper LmHost            WINDOWS\system32\svchost.exe -k LocalService
    Windows Time          W32Time           WINDOWS\system32\svchost.exe -k netsvcs

    Additionally, on Windows Server 2003 we have seen the RPC service hog the CPU while MIMIC is busy servicing SNMP requests. On Windows XP SP2 we have seen the RPC service crash when stress testing MIMIC, thus rebooting the system by default. We recommend stopping all svchost.exe processes, and make sure that the services are configured not to restart or reboot the system.

    See also A description of Svchost.exe in Windows XP

  13. 64-bit support

    The optional 64-bit MIMIC simulator and protocol module shared libraries can run on a x64 or AMD64 processor. To do so, you need to run a 64-bit version of Windows , and use Update Wizard to download the optional update package with the MIMIC 64-bit executables.

  14. Windows Vista and newer

    1. User Account Control

      Windows Vista and later has the new User Account Control feature, which impacts the running of MIMIC. For details, consult this Analysis of the Windows Vista Security Model from Symantec. In order to enable to run MIMIC on Vista and later, you have 2 options:

      • Disable User Account Control

        This turns UAC off globally. NOTE: do this only if you are aware of the implications of this action.

        • On Windows 7, 8, 10, 11:
          Open User Accounts via Start->Control Panel->User Accounts->User Accounts->User Account Control settings.
          Slide scrollbar to bottom (Never notify).
        • On Windows Vista and Server 2008:
          Open User Accounts via Start->Control Panel->User Accounts->User Accounts.
          Click on Turn User Account Control on or off
          Clear the checkbox for Use User Account Control (UAC) to help protect your computer.
        • Click Ok
        • A dialog will popup prompting you to Restart Now or Restart Later. Choose appropriately. User Account Control will be disabled once the system reboots.
        • On Windows Server 2012:
          Follow directions at this Microsoft article.

      • Run MIMIC with User Account Control enabled

        This involves changing the access control level of the MIMIC programs.

        • Change the privilege level of MimicView application in the Mimic Start Program group using the following steps:

          • Click Start->All Programs->Mimic Simulator x.xx
          • Move the cursor to the MimicView entry
          • Right click and select Properties.
          • In the Compatibility tab, check Run this program as an administrator
          • Once this is done, MimicView can be started as above or by running the MimicView.bat script in the bin folder of the MIMIC installation.

        • If MimicD.exe will be run directly, set the privilege level of it using the following steps:

          • In Windows Explorer, select it.
          • Right click and select Properties.
          • In the Compatibility tab, check Run this program as an administrator

          • Then run MIMICview or any other MIMIC client on the same system as administrator.

    2. Duplicate Address Detection

      On Windows Vista and later, the new TCP/IP stack tries to do "duplicate address detection" by default. This prevents MIMIC from starting agents, because IP aliasing is delayed, and even with a workaround in our software would unacceptably slow down the starting of agents. To correctly workaround the problem, you need to disable "duplicate address detection" for the network interface using the Windows netsh utility:

      netsh interface ipv4 set interface "name or index" dadtransmits=0

      The interface name and index info can be obtained by

      netsh interface ipv4 show interfaces

      For example:

      H:\>netsh interface ipv4 show interfaces
      Idx  Met   MTU   State        Name
      ---  ---  -----  -----------  -------------------
        1   50 4294967295  connected    Loopback Pseudo-Interface 1
        7   20   1500  connected    Local Area Connection
      H:\>netsh interface ipv4 set interface "7" dadtransmits=0

      The same applies to IPv6.

      netsh interface ipv6 set interface "name or index" dadtransmits=0

    3. Services

      Windows Vista and later has the problem of services interfering with MIMIC operation as documented above.

      Here is the list of already documented services and their paths:

      Display Name                                 Service Name      Path to executable
      IPsec Policy Agent    PolicyAgent       WINDOWS\system32\svchost.exe -k NetworkServiceNetworkRestricted
      Protected Storage     ProtectedStorage  WINDOWS\system32\lsass.exe
      Print Spooler         Spooler           WINDOWS\system32\spoolsv.exe
      DHCP Client           Dhcp              WINDOWS\system32\svchost.exe -k NetworkServiceNetworkRestricted
      DNS Client            Dnscache          WINDOWS\system32\svchost.exe -k NetworkService
      TCP/IP NetBios Helper lmhosts           WINDOWS\system32\svchost.exe -k NetworkServiceNetworkRestricted
      Windows Time          W32Time           WINDOWS\system32\svchost.exe -k LocalService

      Additionally, these new services in Windows Vista and later MUST be disabled for reasonable start/stop performance.

      Display Name                                 Service Name      Path to executable
      Function Discovery
      Resource Publication  FDResPub          WINDOWS\system32\svchost.exe -k LocalService
      IKE and AuthIP
      Keying Modules        IKEEXT            WINDOWS\system32\svchost.exe -k netsvcs
      Network List Service  netprofm          WINDOWS\system32\svchost.exe -k LocalService
      Network Location
      Awareness             NlaSvc            WINDOWS\system32\svchost.exe -k NetworkService
      SSDP Discovery        SSDPSRV           WINDOWS\system32\svchost.exe -k LocalService
      UPnP Device Host      upnphost          WINDOWS\system32\svchost.exe -k LocalService
      Windows Remote Management
      (WS-Management)       WinRM             WINDOWS\system32\svchost.exe -k NetworkService

      These are new services that may be disabled for better start/stop performance on Windows Vista and later.

      Display Name                                 Service Name      Path to executable
      Background Intelligent
      Transfer Service      BITS              WINDOWS\system32\svchost.exe -k netsvcs
      IP Helper             iphlpsvc          WINDOWS\system32\svchost.exe -k netsvcs

      Service Details

      • Function Discovery Resource Publication

        Used for publishing network resources. Stopping will prevent other computers from discovering the network resources. Will impact applications that work with Network Connected Devices, Plug-n-Play Extensions and Web Services on Devices.

      • IKE and AuthIP Keying Modules

        Internet Key Exchange (IKE) and Authenticated Internet Protocol (AuthIP) keying modules are used for authentication and key exchange in IPSec. Stopping them will prevent IPSec from working.

      • Network List Service

        Used to determine the networks to which the system is connected, collect/store their properties and notify applications.

        Stopping this will prevent the Network Status tray icon from working properly.

      • Network Location Awareness

        Used to collect/store network configuration information and notify applications.

        Stopping this will prevent any applications (like Network List Service) that depend on this data from working.

      • SSDP Discovery

        Used to provide Simple Service Discovery Protocol based services. Stopping this will prevent UPnP from working.

      • UPnP Device Host

        Used to provide Universal Plug-n-Play services. Stopping this will prevent UPnP based devices from working.

      • Windows Remote Management (WS-Management)

        Used for Web Services for Management funcationality. Stopping will disable Windows Remote Management and WS Management

    4. Vista Power Management

      The default power options will put the Windows Vista system to sleep after 1 hour of inactivity. To disable this, perform the following:

      Open Power Options using Control Panel->System and Maintenance->Power Options.

      Change Preferred Plan from Balanced to High Performance.

      Verify by clicking on Change Plan Settings for High Performance. Ensure that Put the computer to sleep setting is Never.

    5. Program Compatibility Assistant

      After the install is completed or aborted, the Program Compatibility Assistant may prompt with the message

      This program might not have installed correctly.
      Please select This program installed correctly if the install completed. Else, select Cancel.
  15. Crashes

    Prior to Windows Vista, crashes can be analysed post-mortem using the Dr. Watson Tool crash dumps. This requires that Dr. Watson be enabled to handle any application exceptions on the system.

    To install Dr. Watson as the default exception handler :

    • Click Start->Run.
    • Type drwtsn32 -i
    • Click Ok.

    A subsequent crash should popup the Dr. Watson dialog. Search for the following files in the Windows directory (this location can be changed using the Dr. Watson GUI) : drwtsn32.log and user.dmp . Send these to Gambit Technical Support (

    On Windows Vista and later, by default the Problem Reports and Solutions feature handles program crashes. Crash information, including minidumps when available, is automatically sent to Microsoft.

    You can check if a MIMIC program crashed and if minidumps are available. Please use the following steps to extract any available MIMIC program crash data and forward it to Gambit Technical Support (

    • Go to Problem Reports and Solutions using Control Panel->System and Maintenance->Problem Reports and Solutions or using Control Panel->Problem Reports and Solutions
    • Click on View problem history
    • Find MIMIC programs in the list
    • Double click on an entry to view the problem details
    • If there is a Files that help describe the problem section, click on the View a temporary copy of these files link below that section
    • The files will be extracted into a temporary directory and an Explorer window will be opened to view them
    • Forward these to Gambit Technical Support

    If the Problem Reports and Solutions settings are changed to check with the user before sending the crash information to Microsoft, Windows Vista will prompt the user when a program crash occurs. If you choose Close the program, no additional details are generated. If you choose Check online for a solution and close the program, crash data may be saved.

    Microsoft's Debug Diagnostic Tool version 1.1 onwards may be used on Windows Vista and later to handle program crashes. If this is installed, please use the following steps to generate crash data.

    • Open Debug Diagnostic Tool
    • Click on the Rules tab
    • Click on Add Rule button
    • In the Select Rule Type dialog, choose Crash and click on Next
    • In the Select Target Type dialog, choose A specific process and click on Next
    • In the Select Target dialog, browse the process list, select MimicD.exe and click on Next
    • In the Advanced Configurations (Optional) dialog, change the number of userdumps as needed and click on Next
    • In the Select Dump Location and Rule Name (Optional) dialog, change the path and name as needed and click on Next
    • In the Rule Completed dialog, choose Activate the rule now and click on Finish

    When a crash occurs, the Rules tab in Debug Diagnostic Tool will show the userdump count. Forward the available files from the configured dump location to Gambit Technical Support.

  16. Known Problems

    We are constantly working to remove limitations, but currently we know of the following:

    • On Windows Vista and newer you cannot run MIMIC on a standalone PC (not connected to a network). This is due to the OS having removed the ability to disable media sense. We have found no workaround for this limitation.

    • On Windows NT, if the host is using DHCP to obtain its address, no agent instance can use that same address to export a MIB. The problem is that on stopping the agent this address is deleted which shuts off the TCP/IP services (ftp/telnet/internet). To restore working you either need to REBOOT or start the agent on the DHCP assigned address again (keep it running).

    • On Windows Vista you can only configure upto 10000 agents and 15000 +/- IP addresses.
      On Windows Server 2008 you can only configure upto 10000 agents and 12000 +/- IP addresses.
      On Windows 7 you can only configure upto 10000 agents and 11000 +/- IP addresses.
      Any subnets can be used for these addresses.

    • On all versions of Windows you can only run upto 64 MIMIC clients over the local management channel [bug 2371].

      The Unix versions of MIMIC have no such limitations on the number of clients.

    • On Windows, certain network interface cards have limitations supporting multiple IP addresses. In particular, some adapters and/or drivers from 3com have been giving us trouble (eg. 3C905-TX or 3Com 3C90x Ethernet Adapter). The symptom is that a small number of agent instances can be started and polled correctly, but connectivity is lost to the box when starting more.

    • On Windows, certain software is incompatible with MIMIC. In particular, if Novell Client is running, your machine may hang after starting and stopping a small number of agents (the System task will use 99+% of CPU). Just unchecking the box in Local Area Connection Properties is not sufficient - you have to uninstall it.

      This problem is unrelated to MIMIC. Any test program (eg. ifdiag shipped with MIMIC) which uses the Windows API to register/unregister network addresses will reproduce the problem.

    • If you want to run MIMIC inside virtual machine software such as VMWare, please contact Gambit Communications Technical Support (

    • MAC Bridge Miniport in Windows Vista and later is not supported. To remove the adapters from the network bridge, follow the instructions at this Microsoft support page .

    • IPv6 will only work on Windows Vista or later. It runs on all supported versions of Unix.

      When adding or deleting IPv6 aliases to/from an agent it can take 2 to 3 seconds for the operation to complete per agent. This slowness is caused by the Domain Name System (DNS) performing a lookup to see if the address is actually a registered domain name. To resolve this problem you must follow both the steps listed below:

      • Do not use domain names and only use IPv4 or IPv6 addresses for all agents.
      • Do either of the following:
        • add the line "hostname_resolve = 0" to your mimicd.cfg file in your MIMIC config/ directory;
        • set the environment variable "MIMIC_HOSTNAME_RESOLVE=0" on your Windows system.

        Even with this workaround, adding and deleting IPv6 aliases is approximately 5 to 10 times slower than on Linux or Solaris. If you are running thousands of agents, your performance will suffer. On Windows 7 or later the performance is comparable to Linux provided you have disabled duplicate address detection.

        Furthermore, our testing uncovered that the Microsoft netsh utility used to add aliases sometimes fails silently. For Windows 7 and later there is no such issue.

    • On Windows you cannot add IPv6 addresses on disconnected NICs, contrary to IPv4, where there is no problem. This is an OS limitation that we cannot overcome. There is no such limitation on other OS platforms.

    • On Windows 8.1 adding large numbers of IPv6 addresses crashes the Windows Explorer due to STACK_OVERFLOW. MIMIC continues to run correctly. Windows quickly recovers with no apparent harm, since Windows Explorer automatically restarts. This is reproducible with the Windows netsh tool, thus is a limitation outside of MIMIC.

    • Performance on Windows Vista is much worse than Windows 7 and later, specially with large scenarios. For this reason we DO NOT recommend running MIMIC on Windows Vista.

    • On all versions of Windows, there is a configurable limit on per-process "USER objects". The default limit of 10000 interferes with MIMICView for large-scale simulations. Eg. if you want to display a large number of device types (more than 1000) with Simulation->Devices, the display may hang and leave droppings on the screen, in particular a line of text at the top of the display.

      To work around this limitation, you have to increase the number of USER objects as described in this Microsoft support page . The absolute limit is 18000, which you will NOT be able to overcome. With this limit, you'll be able to display about 2000 average-sized devices. You can track "User objects" and "GDI objects" in the Task Manager "Details" tab, after enabling those columns.

      In addition, there is a limit on the "desktop heap", as detailed in this Microsoft support page . Change this parameter in the registry to overcome heap limitations.

      MIMIC on other platforms has no such limitation.

    • On Windows, the NVidia ForceWare Network Access Manager that is enabled by default for NVIDIA nForce Networking Controller cards causes problems when MIMIC is starting and stopping agents. The symptoms are that connectivity to the network is disabled. The only workaround we have found is to uninstall the program, since disabling it seems to have no effect.

    • The native telnet client on Windows has problems as documented in detail in the Virtual Lab Windows Installation Instructions.

    • remote access via Remote Desktop gets disconnected when starting agent(s)

      This applies to Windows 7 or later due to changes in Windows where Windows will automatically use the lowest IP assigned to an interface as the source IP address as explained in this Microsoft Forum and this Microsoft article.

      These are the possible workarounds for MIMIC to work in this scenario:

      1. Use IP addresses for MIMIC agents that are higher than the system's IP address.

        For example:

        MIMIC system IP is then use addresses like, etc. for MIMIC agents.

      2. Configure an extra interface on the computer for management/remote-access and having the agents bound to the other interface. Different interface can be assigned to MIMIC agents using Advanced tab of agent configuration dialog. Default interface to be used for MIMIC agents can also be configured by setting environment variable in the Control Panel-> System Properties as below:

        Variable: MIMIC_DEFAULT_NETDEV
        Value: Intel(R) 82566DM Gigabit Network

    • MIMIC display tiny on high-resolution monitors

      on newer high-resolution display monitors (eg. 3240x2160) you need to control the scaling of the MIMIC user interface. You can set the property on the wish86t.exe application as shown in this diagram.

      wish86t Properties

      Figure 1: wish86t Properties

      In Windows Explorer, right-click on the wish86t.exe file in the MIMIC install area bin folder, then select Properties.

      The wish86t.exe Properties dialog pops up.

      Click the Compatibility tab, then click Change high DPI settings.

      In the dialog that pops up, select Override high DPI scaling behavior. Scaling performed by and select System Controlled (Enhanced).

      Click OK to both dialogs, and when you invoked MIMICview, it should display correctly.

In case of difficulties, please contact Gambit Technical Support (

Obviously, Windows is a trademark of Microsoft. All other product and brand names are trademarks or registered trademarks of their respective holders.