Thought it'll be useful to have this here.
Error Code 0x30000000Summary: This occurs when your bdcap32.dll file has been altered. You may not have necessarily done anything, but there's something changed and HackShield doesn't like it.
Solution: Delete the bdcap32.dll you have there, and if there's another bdcap32 file in your Mabinogi directory (possibly named bdcap32.dlx?), rename it to bdcap32.dll.
However, in the event that's not true (you DON'T have bdcap32.dlx), you can now use MabiFresh to obtain fresh .dll files, thanks to tbstewa. nvm
Error Code 0x0000005Summary: Well, Skitty pretty much explained it, but here it is:
Restart your computer.
Serriously.
Restart your computer. it may sound stupid but that error message is when Mabinogi surpasses the memory requirements for the computer.
Restarting your computer tends to fix it. You shouldn't need to uninstall Mabinogi or anything just restart your computer
Solution: Should be obvious by now, but if not:
Restart your computer.
Error 0x0000203Summary: You
really shouldn't be getting this error, however, this is caused from not allowing EagleNT full permissions, as Marck said.
If you are recieving this error, you must re-enable all permissions for EagleNT.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EagleNT
Reset ALL permissions to Full control, that will absolve the error.
Solution: This too, should be obvious, but:
Reset ALL permissions to Full control, that will absolve the error.
Error code 0x00010303Summary: Pretty much what Marck said.
This error can be caused by your computer system entering what is called a "catatonic" state. It's basically where your computer is totally frozen, and loops code wherever it was at that moment in time; So basically, your computer time would be off by maybe 2 seconds if this happened to a high degree.Although it doesn't matter the length of time, it could be frozen for the un-noticable time amount of 0.0000001 seconds, and that error would pop up because the time was out of sync from Hackshield's time log.
Even more dumbed down version: Basically, you lagged and went out of synch with HackShield.
Solution: There
really isn't a solution, as such, however, you can try and close down any unnecessary programs you have open. Open Task Manager by pressing Ctrl+Alt+Delete (on your keyboard) at the same time which will open Windows Task Manager (On Windows XP), or right click on the taskbar (anywhere blank next to the Start Menu), and pick "Start Task Manger" (All Windows Operating systems compatible for Mabinogi) or press and Ctrl+Shift+Esc to open Task Manager. In Applications, select a program and pick end task. Alternatively, restart your computer/laptop and start Mabinogi straight away, without opening any other programs.
Tip: You should also disable any programs that start when Windows start, this actually adds lag.
Runtime Error! R6030 -CRT not initializedSummary: If you've done something incorrectly when using both JAP and MNG.
Solution: Follow these steps.
Download MNG, extract all files to Mabi folder, pick what you want in MNG.ini
Rename the dbghelp.dll to dbghelp.dl_
Download JAP and extract all files to the Mabi folder except dbghelp.dl_ (since MNG is now dbghelp.dl_)
pick what you want in JAP.ini, start Mabi, should be good.
client.exe caused an ESL_EXCPT_CODE_TERMINATE()Summary: This is pretty much due to data folder modifications.
Solution: Try going into your Mabinogi folder, and (considering you've installed Tiara) navigate to data>db, and check if you have any files under the names of
itemdb.xml and
racedb.xml. These are the common culprits, however, it may not always be those files.
This thread.
Error code 0xe904000eSummary: Seems to be caused by the Mabinogi Revision 82 installer.
Solutions: 1. Get a previous or earlier Mabinogi installer.
2. Delete your .pack files and force re-download (by launching the patcher).
3. Modify your version.dat by opening it with hex editor, and drop the value by one. (Advanced method)
Authorization Error (MNG)Summary: Um...what? Just follow the solution.
Solution:
MNG Notes, there is a very good chance you will have to change the delay timing values to get this to work on your machine. 30000 seems to
work well, but otherwise if the error Auth, add 1000, if the error is memory mod detection subtract 1000. if it occurs at say 29k auth, and 30k
memory mod, go by 500, and so on.
- Copied from the readme.