search

2000DTM / bizhawk

Automatically exported from code.google.com/p/bizhawk
0 stars 0 forks source link

bizhawk does not start #108

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download and run installer in bizhawk_prereqs.zip
2. Download and extract BizHawk-1.4.1.zip
3. Run BizHawk.MultiClient.exe

What is the expected output? What do you see instead?

I expect some kind of multi-system emulator to start. Instead it just crashes:

BizHawk.MultiClient has stopped working
Windows can check online for a solution to the problem.
View problem details:

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: bizhawk.multiclient.exe
  Problem Signature 02: 1.4.1.4300
  Problem Signature 03: 514e21ce
  Problem Signature 04: mscorlib
  Problem Signature 05: 4.0.0.0
  Problem Signature 06: 4ba1da6f
  Problem Signature 07: 23d8
  Problem Signature 08: d
  Problem Signature 09: System.IO.FileLoadException
  OS Version:   6.1.7601.2.1.0.768.3
  Locale ID:    1053
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

What version of the product are you using? On what operating system?

Bizhawk 1.4.1, Windows 7.

Original issue reported on code.google.com by fredrik....@gmail.com on 11 Apr 2013 at 11:25

GoogleCodeExporter commented 9 years ago 
Nevermind, I found out that it works if I copy the files from the dll directory 
into the main directory.

Original comment by fredrik....@gmail.com on 12 Apr 2013 at 5:41

GoogleCodeExporter commented 9 years ago 
I had the same issue, copying the DLLs in the main folder as fredrik suggested 
solved it. Here is the output in Windbg. 

ModLoad: 5d490000 5d53a000   
C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
(2180.1f18): CLR exception - code e0434352 (!!! second chance !!!)

Original comment by ekse...@gmail.com on 5 May 2013 at 2:40

GoogleCodeExporter commented 9 years ago 
same problem here, but it copying the DLLs in the main folder doesn't fix it...

Original comment by mantox...@gmail.com on 28 May 2013 at 8:40

GoogleCodeExporter commented 9 years ago 
The cause of this problem has been isolated. The need to fix it by copying dlls 
should be fixed in the upcoming released (or interim build)

Original comment by adeli...@tasvideos.org on 28 Jul 2013 at 3:27