Version 10 not loading when starting from network share

Issue #30 new
Former user created an issue

Hi,

I've just installed EKF, and it seems to be crashing 30% into loading the program.

Are there any frameworks that need to be installed prior to running it?

Any way to turn on verbose logs?

Jon

Comments (6)

  1. Paul Seidel repo owner

    Hi Jon,

    There is a log file in the directory (log-file.txt). The only thing you should need is the .NET framework version 4 or higher. But I would expect it to stop loading before 30% if you miss that.

    At 30% EKF is loading historic results. These are stored in cache/results.json. This file should not be around for clean installs, but If that file is there, can you try renaming it and run it again? If it runs fine, I would like to have a look at that file.

    If it still fails - After results it will load decks_EW.txt, decks_KW.txt and decks_Hydra.txt (all from the cache folder as well) - you can try to remove/rename those too

    I noticed I currently set the log verbosity in the code - I'll make that configurable.

  2. Jonathan Zion Mozes

    no results.json in the cache directory. Renamed all three txt files, but still nothing. Any suggestions? (I have .Net 4.6.1 installled, so that is no problem)

    I can see 50% for a second before it crashes. I'll have a look at the loading source code, see if I can find out the problem.

  3. Paul Seidel repo owner

    Hmm, very weird. I recently downloaded it myself on a fresh system and it had no issues (Windows 10)

    The UI loads all data in LoadingForm.cs. If you are able to run the source code from Visual Studio, it should pause execution with the concrete exception, instead of bailing. Otherwise I can upload a debug build with different exception handling.

  4. Jonathan Zion Mozes

    Found the problem: I'm using parallels on a mac to run windows 10, and I've saved the app to a location on the mac filesystem, which translates into a network share starting with '\' on the windows virutal machine. This caused the app to crash.

    moving the app to a directory on C:\ solved it.

  5. Paul Seidel repo owner

    Nice find! I'll change the title of this issue, so I can try and find a solution for it later.

  6. Log in to comment