Yobgul Converter Error (See file)

I get this error whenever I start, 721 with normal war3.EXE, and 621 with the supplied war3.EXE

Please tell me how to fix it - just made a test MDL following one of Nicoli's tutorials and need to finish it off :bgrun:

Did you copy all other required DLLs (game.dll, ijl15.dll, mss32.dll, storm.dll) from Warcraft III version 1.0. I think any of these exept game.dll have not been changed since 1.0. To retrieve a game.dll from v1.0 you can do one of the following things:

• Reinstall Warcraft III. Copy game.dll 1.0. Patch it after that.
• Use W3Reseter (browse this forum) to reset Warcraft III to v1.0. Copy game.dll. Patch it again.
• Open war3.mpq with a MPQ editor/viewer like WinMPQ and extract game.dll v1.0 into your File Converter directory

This is the only problem I can think of at the moment.

I used the resetter and it still has the error. Any other suggestions?

OMFG I just realised why, the damn resetter screwed my frozen throne beta. Stupid Blackdick could of said so.

And to top it off the converter doesnt work with the screwed beta either. Wonderful.

Well, you didn't say that you have installed the beta. Anyway, you could have taken into account that when it resets Warcraft III back to v1.0, it'll also delete the beta.
Swearing at BlacKDicK is inappropriate.
Your should have done the third suggestion to do it. Anyway, the converter has to work. Follow the steps explained in my FAQ thread. There you can find a step by step guide on how to install it.

Additionally I'm sorry for you about the beta. I only hope that you are not a 56K user.

Where did I swear at Blackdick? I don't think "stupid" is a swearword.

And, I only meant the readme should have said it read the Directory from the registry. I placed it in

C:/Warcraft/War3 1.00/Resetter

And I wanted it to reset War3 1.00, but instead it reset C:/Warcraft/War3 Beta

If you are talking about the readme, you should have read it carefully (or more carefullier):
It says you should not put it into the Warcraft III directory. As a result it has to obtain from somewhere else where Warcraft III is installed. This is in the registry. When BlacKDicK programmed it, there was no beta, so he couldn't know of it.

I read that, and I assumed he didnt mean put it in C:/Warcraft/War3 1.00 so I made a new folder inside it called Resetter.

Hey, couple of things i have to say:

1) When I created W3 Reseter there was no FT BETA around.
2) W3 Reseter is a W3 Reseter, not a FT Reseter. I do have a FT Reseter of my own but didn´t release it yet coz this registry stuff is causing lot of trouble to ppl around and I dont want to get flamed.
3) Blame Blizzard. When my tool runs it gets where the W3 is installed by checking this value on the registry: "HKEY_CURRENT_USER\Software\Blizzard Entertainment\Warcraft III\InstallPath". The problem is that BLIZZARD did not create a "InstallPathX" for FT, as they did for the "ProgramX". Blizzard is using the same REG ENTRY for both the W3 and the FT beta, and it´s not my fault. This "mess" caused and still causes lots of trouble when ppl with "double" installs (W3 and FT beta) try to run a patch to update the FT beta.
They DO have a "HKEY_CURRENT_USER\Software\Blizzard Entertainment\Warcraft III Expansion Beta\" but guess what? There is NO "InstallPath" for the FT, FT is using the original W3 RoC registry and this is not my fault.

BTW, I guess Yobgulls converter needs the DLLs and the EXE of the W3 RoC 1.01 version.
I also updated the W3 Reseter. Now on version 1.0.2 it will check if it is a FT Beta or W3 RoC and will not work if it turns to be a FT Beta.

Thanks blackdick, wasn't intending to flame you, I was just angry my beta was ruined.
Oh well, the beta will finish soon anyway.