So I'm running vista. I'm trying to use maped 3, but whenever I try to open it, it immediately tells me that maped 3 has "stopped working."

Actually Grue, I also have that problem. I've got .NET 3.5 SP1 installed, and I've tried running it in all kinds of folders, and as an administrator, as an alligator... nothing seemed to work.

Product

maped3.exe



Problem

Stopped working



Date

11/9/2008 9:07 PM



Status

Report Sent



Description

Stopped working



Problem signature

Problem Event Name:	CLR20r3

Problem Signature 01:	maped3.exe

Problem Signature 02:	1.0.2786.36510

Problem Signature 03:	46c79a0c

Problem Signature 04:	maped3

Problem Signature 05:	1.0.2786.36510

Problem Signature 06:	46c79a0c

Problem Signature 07:	e6

Problem Signature 08:	7

Problem Signature 09:	System.IO.FileNotFoundException

OS Version:	6.0.6001.2.1.0.256.6

Locale ID:	1033



Extra information about the problem

Bucket ID:	290717295

Okay, make sure you have all of the following .dll files in the SAME folder as Maped3.exe:

corona.dll
MRU.dll
pr2-common-cpp.dll
RegisterFileType.dll
Render.dll
zlib.net.dll

Only other thing I can think of causing it, is maybe there's some odd discrepancy between dlls in XP and Vista (but there shouldn't be), or one of the dlls itself is throwing an exception.


EDIT: Not having Render.dll definitely nukes the thing right away with this error:



EDIT 2: It occurred to me, maybe it's crashing when it can't find MapedPreferences.xml, which seems silly. Try making sure you have a pre-existing one and copy it into your maped folder.

Oh! That's probably the issue. I mean, these are 32-bit binaries. Uhhhm, not really sure how to remedy that. Is there like OS compatibility settings on file properties?

EDIT: Try installing a 32-bit version of .NET instead of 64-bit (remove your old .NET installs first though).

I think what's happening is the Maped3.exe's being launched on .NET (which is 64-bit on your installation), and then trying to reference the native, 32-bit dlls in the folder.

64-bit code can only reference 32-bit code, and 32-bit code can only reference 64-bit code, and so you need to make sure you have compatible framework there.

EDIT 2: On second examination, this might not be possible. Which means somebody needs to update the Maped3 project to force .NET to run in 32-bit mode or somesuch.

EDIT 3: This sounds promising, though it's commandline (so not entirely friendly): http://blogs.intesoft.net/post/2007/12/Running-NET-Apps-in-32-bit-mode-on-64-bit-Windows.aspx

The examples have a typo though (it should say "corflags.exe" not "coreflags.exe")

If that works, upload the patched .exe to the site here.

EDIT 4: It occurred to me, you'd need Visual Studio and the .NET SDK installed for that to work. Hold on!

See below post.

It works! :D

Thanks very much.

I'm doing a little bump on this topic!
Can anyone help me on this one?
I'm still stuck with a non working version of Maped.
It seems no matter what version of Maped I use I can't get it working right with Vista 64bits.
Maped3 just crash on startup, and MapedPrime opens but crashes when loading a map.
Overkill's little batch file seemed to work once, but does not anymore ;) eh. Can't figure out why.
Thanks!