rainbow.exe starts and shuts down immediatly. (64bit, Windows)

[Former user]

Hi!

I have the following setup:

PS C:\Program Files\okapi-apps> .\startTikalPrompt.bat
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Program%20Files/okapi-apps/lib/okapi-application-logger-1.42.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Program%20Files/okapi-apps/lib/okapi-application-logger-1.44.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [OkapiLoggerFactory]
-------------------------------------------------------------------------------
Okapi Tikal - Localization Toolset
Version: 2.1.42.0
-------------------------------------------------------------------------------
Java version: 11.0.16.1
Platform: Windows 11, amd64, 10.0
Java VM memory: free=41.405 KB, total=49.152 KB
Tikal display encoding: cp850
-------------------------------------------------------------------------------
C:\Program Files\okapi-apps>java -version
java version "11.0.16.1" 2022-08-18 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.16.1+1-LTS-1)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.16.1+1-LTS-1, mixed mode)

I updated to okapi-apps_win32-x86_64_1.45.0.zip.

My 32bit setup worked fine until I now updated to 64bit (both JRE and OKAPI).

Any idea what might be wrong? Thank you so much

Each time I launch rainbow exe

[jhargrave-straker]

I was able to startup 1.45.0 Rainbow without any problems. However my anti-virus did complain - but I just overrode it. Its possible you have some old SWT DLL’s still in your path. Be sure to clean out all the old installations.

[jhargrave-straker]

Another user got his okapi working by uninstalling Java and reinstalling (make sure it is version 11 or 17)