#2034 Exult Studio: Crash with Windows 10 64bit version 1809

[Dominik Reichardt]

With the latest Windows 10 Fall upgrade to version 1809, Exult Studio crashes when you click on any of the menus.
studio_out.txt and studio_err.txt are not really helpful in figuring out what is wrong. My guess is that the very old dlls that Kirben still uses are no longer compatible with Windows 10. It's likely that it works fine with newer ones.
exult.cfg:

<config>
 <disk>
  <game>
   <blackgate>
    <path>
    C:\Users\Dominus\Desktop\forgeofvirtue
    </path>
    <keys>
    (default)
    </keys>
    <waves>
    sqsfxbg.flx
    </waves>
    <autonotes>
    (default)
    </autonotes>
   </blackgate>
   <serpentisle>
    <path>
    C:\Users\Dominus\Desktop\silverseed
    </path>
    <keys>
    (default)
    </keys>
    <autonotes>
    (default)
    </autonotes>
    <waves>
    sqsfxsi.flx
    </waves>
   </serpentisle>
  </game>

studio_out.txt:

Looking for 'blackgate' at 'C:\Users\Dominus\Desktop\forgeofvirtue'... found game with identity 'FORGE'
Looking for 'forgeofvirtue' at './forgeofvirtue'... but it wasn't there.
Looking for 'serpentisle' at 'C:\Users\Dominus\Desktop\silverseed'... found game with identity 'SILVER SEED'
Looking for 'silverseed' at './silverseed'... but it wasn't there.
Looking for 'serpentbeta' at './serpentbeta'... but it wasn't there.
Black Gate   : not found (<BLACKGATE_STATIC>\.)
Forge of Virtue   : found
exult_bg.flx : found
Serpent Isle   : not found (<SERPENTISLE_STATIC>\.)
Silver Seed   : found
exult_si.flx : found

studio_err.txt

Warning, trailing slash in path: "<BLACKGATE_STATIC>\"
Warning, trailing slash in path: "<SERPENTISLE_STATIC>\"
Line 140 doesn't start with a number
Error opening temporary file in gamedat dir with port number.
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map01\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map01\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map02\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map02\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map03\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map03\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map04\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map04\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map05\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map05\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map06\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map06\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map07\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map07\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map08\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map08\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map09\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map09\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\static\map0a\"
Warning, trailing slash in path: "C:\Users\Dominus\Desktop\forgeofvirtue\patch\map0a\"

(there are no map folders in either static or patch folders, patch is empty.

[Knight Captain]

Using Process Monitor, it appears that ES crashes after trying to access C:\Windows\Fonts\StaticCache.dat.

[Dominik Reichardt]

I did try rebuilding the fonts cache but that didn't help :(
I couldn't get rid of the staticcache.dat file (and Process Explorer refused to run :( )

[Dominik Reichardt]

@Marzo, the newer branch, following your guide for msys and using the newer dlls you provided doesn't have that problem.
Maybe it's time to push that, so Kirben will use these instead of the ancient dlls.

[Dominik Reichardt]

somehow this must have been a fluke in this Windows 10 version. Works now in current Windows 10.