Running on Windows

Prerequisite: Installing on Windows

Once the EMM OSINT Suite has been installed on your system, running the application requires you to define a workspace folder on local disk to keep your user data.

Important

The workspace folder needs to be placed on a local disk drive. The application will fail if the workspace is on a network drive.

By default the application places the user data in the default Windows User Directory under c:\Users\<User-Name>\osint-workspace.

To run the application do the following:

  1. Open the installation location in Windows File Explorer. By default the location is c:\Program Files\osint_<version-number>_x86_64.

  2. Double-click on the osint.exe executable to start the application. The application shows a splash screen, then shows the Workspace Selection dialog.

  3. In the Workspace Selection dialog either

    • Click OK to choose the default workspace location

    • or Click Browse to define a custom workspace location. The application shows a file dialog to choose the custom workspace location.

  4. In the Workspace Selection dialog you can also enable the Remember Workspace Location check box. If enabled, the application will not show the Workspace Selection dialog during next startup but simply re-use the selected location.

You can switch to a different workspace location from within the running application by clicking on File > Switch Workspace in the main menu. This option is needed if you enabled Remember Workspace Location previously in the Workspace Selection dialog and want to change to a different workspace location later on.

Startup Fails - What now?

[Windows 32-bit only]

If starting the application fails and you see a message "failed to create Java Virtual Machine", you can try the following:

  • Edit osint.ini in the installation directory

  • Change the line "-Xmx924m" which defines the maximum amount of memory for the application to a lower number (but not much lower, maybe something like "-Xmx850m")

  • Save osint.ini

  • Double-click on osint.exe to start again

Repeat if this procedure if necessary.

The reason is that the underlying Java VM needs a contiguous memora area. If there are a lot of other applications open and drivers loaded the system is not able to allocated the needed memory area.

(The 64-bit version does not suffer from this limitations)

Related Topics:

Created with Scroll EclipseHelp Exporter for Confluence.