What OS are you using? Apparently older versions of Windows have been encountering problems; try using the Windows 9x fix from the downloads page.

I'm using Windows XP. But I will try the fix anyway.

EDIT: It worked. Thanks.

Having to use the win9x version is a serious problem. That version has all kinds of quirks, and I wouldn't recomend that you use it for anything.

Could you help me debug this problem?
- Is there any additional information on the error dialog? Perhaps a 'details' button?
- What kind of CPU do you have?
- Here was an alternative build. Could you try it and report any problems you find?

Windows 2000 SP4
AMD XP 2500

This alternative build also has an Illegal Instruction.

The exception =Illegal Instruction
An attempt was made to execute an illegal instruction.
(0xc000001d) occured in the application at location 0x005a87e5.
Click OK to terminate the program
Click CANCEL to debug the program

Clicking CANCEL, I get my Visual C++ 6.0 environment up, and it shows an assembler instruction of movsd. I looked that up at wikipedia, and it shows that movsd was a recent addition to the P4 instruction set. Since I have an AMD XP 2500, that would certainly explain it for me....

The alternative build simply throws the "MSE has caused an error and will be closed" error.

Windows 2000, Service Pack 3.
AMD-K6

Thanks for the analysis Rob! That looks like the cause of the problem. Here was another attempt.

That did it

What's wrong with the 9X fix, exactly? I'm on an AMD with Windows 2000 SP4, same "illegal operation and will be closed" stuff, I Ued the 9X fix and it's fine.

Should I use the new EXE in this thread instead?

I just released the 0.3.6b hotfix version, that should fix all of these problems.

Just for completeness, neither works for me.

Knight Otu -

AMD K6 is still a generation behind my XP 2500.... I wonder if there's another opcode that your processor doesn't know about.... I was lucky that I know enough about assembler and had Visual C++ debugger to make the call for Twan.

I get "Magic Set Editor has generated errors and will be closed. You will need to restart the program." This is after the 0.3.6b Hotfix.

The 9x fix works fine except for the parsing of -- and etc. Also, apparently the Mythic Rarity has been implemented with .6b? If so it doesn't support that either.

I have Windows 2000, but I have no idea beyond that much. :/

Pich's right, I discovered it works for all of the styles I've downloaded outside of the actual program. So, where would I get the 0.3.6b? I've downloaded several different files several different times each.

I think I got it solved now. Referring to this page...
The first link, Magic Set Editor 2, is outdated. I downloaded this one three times and each time I didn't get 3.6b.

I downloaded the 9x fix, and then that worked.
Then when I came to this topic, I downloaded the "Update for 0.3.6 users" but for some reason that one didn't work.

I downloaded the Small version but unchecked all templates, because I already had them. This caused the mythic rare problem. :/

I re-installed the Small version with all templates on, and immediately the problem was solved. I'll have to download the full sometime and fix Planeshifted, Futureshifted, etc borders.

Sourceforge must hate me for pinging their server so much.

Pich, I know Mythic rare has already been a bother for you, but I just noticed that the slant of discoloration that runs through the symbols is actually going the wrong way in MSE.

So the 0.3.6b version does work for you?

I moved the rarity symbol discussion somewhere else to keep this thread on topic.

All the styles included in the Small version are fine and updated; and I'd assume all would be fine had I gotten the Full download. I'll let you know when I do, but I don't use Future Sight or the others that often. Also there is no need for the 9x fix for me. Thanks for all the help.