[September 3, 2023]Abyss Patcher

[vb286]

Redistributables wouldn't cause an error like that. It would tell you you're missing a dll or something. That's caused from bad/conflicting/missing code somehow.

Where does it point to?  I can't seem to find the missing data.  Me and Proff think its a coding failure on NX's part.  But, if you can find out else that would be great as this issue has never arisen before.

[Yiting]

[7C812FD3] kernel32.dll::RaiseException() + 0x52
[0041ABCA] Client.exe::??4IIMEEventHandler@esl@@QAEAAV01@ABV01@@Z() + 0x14285
[00426DE4] Client.exe::??4IIMEEventHandler@esl@@QAEAAV01@ABV01@@Z() + 0x2049f
[005DFD07] Client.exe::?IsEnabled@CIMEHandler@esl@@QBE_NXZ() + 0xe9244
[00B9FC50] Client.exe::??4CIMEHandler@esl@@QAEAAV01@ABV01@@Z() + 0x4d9092
[00B9FCD0] Client.exe::??4CIMEHandler@esl@@QAEAAV01@ABV01@@Z() + 0x4d9112
[78543433] MSVCR90.dll::_endthreadex() + 0x44
[785434C7] MSVCR90.dll::_endthreadex() + 0xd8
[7C80B729] kernel32.dll::GetModuleFileNameA() + 0x1ba

at location [005DFD07], you can see the exception message:

Code: [Select]

expression : !"Cannot fount data file!"
file : _Utility\_BeautyShopDescMgr\BeautyShopDescMgr.cpp
line : 123then, that means missing data/db/BeautyShopMotionDesc.xml

[Lordsithis]

So I was going through my mabi files to scan for any abnormalities (as I do every so often while waiting to talk to Tarlach on my newb characters), and to my surprise I found a dsound.dll in my "C:/Nexon/Mabinogi/mp3" folder. I'm pretty sure it isn't supposed to be there, as I've never encountered it there before... I was wondering if I should remove it, or if I should leave it. It came up as an "Insight Network Threat" when I ran a scan after finding it, but I wanted to be sure it wouldn't mess up my client before/if I did remove it. If needed I can send you a screeny, but I'm sure there's no need.

EDIT: Little errors that needed fixing (grammatical mostly).

[╰(　´◔　ω　◔ `)╯]

So I was going through my mabi files to scan for any abnormalities (as I do every so often while waiting to talk to Tarlach on my newb characters), and to my surprise I found a dsound.dll in my "C:/Nexon/Mabinogi/mp3" folder. I'm pretty sure it isn't supposed to be there, as I've never encountered it there before... I was wondering if I should remove it, or if I should leave it. It comes up as a "Insight Network Threat" when I ran a scan after finding it, but I wanted to be sure it wouldn't mess up my client if I did remove it. If needed I can send you a screeny, but I'm sure there's no need.

EDIT: Little errors that needed fixing (grammatical mostly).

It shouldn't be there, and it won't affect mabinogi if you delete it (as it is never loaded from that folder).

[Lordsithis]

It shouldn't be there, and it won't affect mabinogi if you delete it (as it is never loaded from that folder).

Okay, thank you. I'm just curious as to how it got there in the first place, considering the fact that only that specific file is in there, and when I copy/cut/paste all of them at once...

[Lordsithis]

Hey Blade, I was wondering... What ever happened to the zoom mod that allowed you to zoom out further than normal. I dearly miss it because in my opinion, the character is always too close to the camera, and I can't get far enough away. I know that it was in Solaris, but it hasn't been around for a while and I've been meaning to ask but I always forget.
Thanks for your time 

[╰(　´◔　ω　◔ `)╯]

Hey Blade, I was wondering... What ever happened to the zoom mod that allowed you to zoom out further than normal. I dearly miss it because in my opinion, the character is always too close to the camera, and I can't get far enough away. I know that it was in Solaris, but it hasn't been around for a while and I've been meaning to ask but I always forget.
Thanks for your time 

Code: [Select]

////////////////////
//Start Zoom Hooks//
////////////////////
; 0=normal, 1=union of zoom range, 2=fixed zoom range
Zoom=1
ZoomMin=200
ZoomMax=3000
//////////////////
//End Zoom Hooks//
//////////////////All the way at the end of the ini.

[Lordsithis]

Code: [Select]

////////////////////
//Start Zoom Hooks//
////////////////////
; 0=normal, 1=union of zoom range, 2=fixed zoom range
Zoom=1
ZoomMin=200
ZoomMax=3000
//////////////////
//End Zoom Hooks//
//////////////////All the way at the end of the ini.

I saw that, but i thought that 3000 was much higher than the normal ZoomMax... Then again I might just think that because I don't actually know the normal zoom parameters... I'm just wasting forum space with my noobness, aren't I?

EDIT: THANK the heavens for you, thatguysteve Now I don't feel like I'm going crazy by being super close to my character *phew*

[daomeister]

[05/03/13 20:59:30] - Abyss : second pass success
[05/03/13 20:59:30] - Abyss : themida patching fail: SearchPattern (0)
[05/03/13 20:59:30] - Abyss : alt name color patching success
[05/03/13 20:59:30] - Abyss : clock minute patching success
[05/03/13 20:59:30] - Abyss : control day time hooking success
[05/03/13 20:59:30] - Abyss : deadly life patching success
[05/03/13 20:59:30] - Abyss : disable alt enter patching success
[05/03/13 20:59:30] - Abyss : enable fsaa patching success
[05/03/13 20:59:30] - Abyss : enable multi client patching success
[05/03/13 20:59:30] - Abyss : far alt display patching success
[05/03/13 20:59:30] - Abyss : infinite dye time patching success
[05/03/13 20:59:30] - Abyss : interface while dead patching success
[05/03/13 20:59:30] - Abyss : item detail hooking success
[05/03/13 20:59:30] - Abyss : last position patching success
[05/03/13 20:59:30] - Abyss : metalware expiring hooking success
[05/03/13 20:59:30] - Abyss : minimap zoom patching success
[05/03/13 20:59:30] - Abyss : move to same channel patching success
[05/03/13 20:59:30] - Abyss : nodelay hooking success
[05/03/13 20:59:30] - Abyss : party time patching success
[05/03/13 20:59:30] - Abyss : party to housing patching success
[05/03/13 20:59:30] - Abyss : quiet pet patching success
[05/03/13 20:59:30] - Abyss : remove landing height patching success
[05/03/13 20:59:30] - Abyss : right click self patching success
[05/03/13 20:59:30] - Abyss : scouter patching success
[05/03/13 20:59:30] - Abyss : scrapbook patching success
[05/03/13 20:59:30] - Abyss : show item price patching success
[05/03/13 20:59:30] - Abyss : show ping patching success
[05/03/13 20:59:30] - Abyss : talk to unequipped ego patching success
[05/03/13 20:59:30] - Abyss : zoom hooking success
 
so my abyss doesnt work for some reason, and i think its the themida patching, anyone know how i can fix it?

[╰(　´◔　ω　◔ `)╯]

so my abyss doesnt work for some reason, and i think its the themida patching, anyone know how i can fix it?

You clearly haven't read the last few pages of this thread, or the notice on the front page of MabiMods.

[Yaiishi]

Sorry to jump in on all of the tech talk.. but I was wondering about the log-in portion of the ini? I'm a bit confused to how I set it up.

;Enter your user name or email used to sign into your account along with your secondary password.
; Example: If you log in with the credentials:
; Username: Blade
; Password: 3575
; Secondary Password: 0000
Blade=0000

Do I just start entering info right after "Blade=0000"? And what format is it in?

Like this?

;Enter your user name or email used to sign into your account along with your secondary password.
; Example: If you log in with the credentials:
; Username: Blade
; Password: 3575
; Secondary Password: 0000
Blade=example,password,1234

Sorry if this question was asked before, but 50+ pages is quite a lot to read.

[Chacha]

It would be in the format of:
username=secondarypassword

[vb286]

[05/03/13 20:59:30] - Abyss : second pass success
[05/03/13 20:59:30] - Abyss : themida patching fail: SearchPattern (0)
[05/03/13 20:59:30] - Abyss : alt name color patching success
[05/03/13 20:59:30] - Abyss : clock minute patching success
[05/03/13 20:59:30] - Abyss : control day time hooking success
[05/03/13 20:59:30] - Abyss : deadly life patching success
[05/03/13 20:59:30] - Abyss : disable alt enter patching success
[05/03/13 20:59:30] - Abyss : enable fsaa patching success
[05/03/13 20:59:30] - Abyss : enable multi client patching success
[05/03/13 20:59:30] - Abyss : far alt display patching success
[05/03/13 20:59:30] - Abyss : infinite dye time patching success
[05/03/13 20:59:30] - Abyss : interface while dead patching success
[05/03/13 20:59:30] - Abyss : item detail hooking success
[05/03/13 20:59:30] - Abyss : last position patching success
[05/03/13 20:59:30] - Abyss : metalware expiring hooking success
[05/03/13 20:59:30] - Abyss : minimap zoom patching success
[05/03/13 20:59:30] - Abyss : move to same channel patching success
[05/03/13 20:59:30] - Abyss : nodelay hooking success
[05/03/13 20:59:30] - Abyss : party time patching success
[05/03/13 20:59:30] - Abyss : party to housing patching success
[05/03/13 20:59:30] - Abyss : quiet pet patching success
[05/03/13 20:59:30] - Abyss : remove landing height patching success
[05/03/13 20:59:30] - Abyss : right click self patching success
[05/03/13 20:59:30] - Abyss : scouter patching success
[05/03/13 20:59:30] - Abyss : scrapbook patching success
[05/03/13 20:59:30] - Abyss : show item price patching success
[05/03/13 20:59:30] - Abyss : show ping patching success
[05/03/13 20:59:30] - Abyss : talk to unequipped ego patching success
[05/03/13 20:59:30] - Abyss : zoom hooking success
 
so my abyss doesnt work for some reason, and i think its the themida patching, anyone know how i can fix it?

idk you could tell us what isnt working.

[Chacha]

So, I've tried to do some testing to try and determine the cause of the random freezes in Windows 8. To recap, the game client freezes for about a minute under some of the following events:

-Closing the mailbox
-Closing the Resident Menu from housing channel banker
-Closing the house management menu from the Brownie
-Skipping some cutscenes (possibly still happens when watching through them?)
-Possibly other cases?

However, it only seems to happen the first time when any of these happen while the game client is running. If you open the mailbox again after it stops freezing, it won't freeze again. So, I've tried a few different things to try and see if I could pinpoint the cause of it.

I've unpacked data folder mods (UT, etc.), still froze up.
I've disabled everything Abyss does (even the secondary password skip), still froze up.
I removed Abyss, and the freezing stopped.

So... while the new version of HackShield does work with Windows 8, it does seem to cause some freezing at some intervals. I'm not sure what the cause would be, though. Not really sure how to further test this, either.

[Blade3575]

Curious as to how you disabled Secondary Password Skip.. Also, when you say you removed Abyss and the freezing stopped, are you saying you removed dsound.dll or dsound.dll and dinput8.dll. If it's the latter, then try just taking out dsound.dll (or rename it) and check if it freezes. If it does freeze with just dinput8.dll and HSLaunch.exe, then it's CrackShield (given it doesn't happen on a clean Client).

[Chacha]

Curious as to how you disabled Secondary Password Skip.. Also, when you say you removed Abyss and the freezing stopped, are you saying you removed dsound.dll or dsound.dll and dinput8.dll. If it's the latter, then try just taking out dsound.dll (or rename it) and check if it freezes. If it does freeze with just dinput8.dll and HSLaunch.exe, then it's CrackShield (given it doesn't happen on a clean Client).

Well, looking at the log, I guess it's, technically, not possible to disable that. Even with my user/secondary password removed, it was still listed in the log as being enabled. I just had to manually enter it, but I guess it doesn't stop it from working. ^^;

What I did was I removed both dsound and dinput8, which I kinda forgot how this works (dsound = Abyss, dinput8 = CrackShield)... so I tried it again just removing dsound (Abyss), and the game would still lock up closing the mailbox. Looks like it is due to CrackShield?

[vb286]

Well, looking at the log, I guess it's, technically, not possible to disable that. Even with my user/secondary password removed, it was still listed in the log as being enabled. I just had to manually enter it, but I guess it doesn't stop it from working. ^^;

What I did was I removed both dsound and dinput8, which I kinda forgot how this works (dsound = Abyss, dinput8 = CrackShield)... so I tried it again just removing dsound (Abyss), and the game would still lock up closing the mailbox. Looks like it is due to CrackShield?

Well, the memory allocation tables did change in 8, so how memory is written and read is different from 7, but not far from 7. 

[Yiting]

So, I've tried to do some testing to try and determine the cause of the random freezes in Windows 8. To recap, the game client freezes for about a minute under some of the following events:

-Closing the mailbox
-Closing the Resident Menu from housing channel banker
-Closing the house management menu from the Brownie
-Skipping some cutscenes (possibly still happens when watching through them?)
-Possibly other cases?

Finally, I got a chance to try this problem myself...

According to my test, it does not randomly happens and has nothing with abyss or crackshield.
I tried closing mailbox by hitting Quit and Close button:
In clear client, press 'quit' will close conversion normally, press 'close' will cause client freeze, then terminate.
In client with crackshield, press 'quit' will also close conversion normally, press 'close' will cause client freeze several minutes, but continue.

Indeed, it's an old bug about micro thread always normally throw a c++ exception for termination, but not all caller have try/catch statement.
Since UnhandledExceptionFilter has set to handle all c++ exception, it seems not a big problem before windows 8.
But in windows 8, WER seems try to classify any uncaught exception before executing UnhandledExceptionFilter, and dump FULL memories into temp folder for creating minidump file. Even I played with crackshield and client didn't crash, I still got a minidump file in my CrashDumps folder after froze up...

I tried blocking exception "esl::E_MTTerminated" throwing from micro thread (only one byte modified), and everything looks fine....
Maybe abyss could consider to include this patch, even I don't think it is a good idea...

[「★Ｓ２９★シ」]

I tried blocking exception "esl::E_MTTerminated" throwing from micro thread (only one byte modified), and everything looks fine....
Maybe abyss could consider to include this patch, even I don't think it is a good idea...

why do you not consider this a good idea, If I may ask?

[vb286]

Because it not mod based or Client based.  It's a severe issue within Windows itself that needs addressing.  The patch would work then it would send windows into a decaying spiral.

Finally, I got a chance to try this problem myself...

According to my test, it does not randomly happens and has nothing with abyss or crackshield.
I tried closing mailbox by hitting Quit and Close button:
In clear client, press 'quit' will close conversion normally, press 'close' will cause client freeze, then terminate.
In client with crackshield, press 'quit' will also close conversion normally, press 'close' will cause client freeze several minutes, but continue.

Indeed, it's an old bug about micro thread always normally throw a c++ exception for termination, but not all caller have try/catch statement.
Since UnhandledExceptionFilter has set to handle all c++ exception, it seems not a big problem before windows 8.
But in windows 8, WER seems try to classify any uncaught exception before executing UnhandledExceptionFilter, and dump FULL memories into temp folder for creating minidump file. Even I played with crackshield and client didn't crash, I still got a minidump file in my CrashDumps folder after froze up...

I tried blocking exception "esl::E_MTTerminated" throwing from micro thread (only one byte modified), and everything looks fine....
Maybe abyss could consider to include this patch, even I don't think it is a good idea...

I have a suspicion its a kernal issue

[Yiting]

why do you not consider this a good idea, If I may ask?

every exception should be meaningful, removing that will also break the program logic, and make it more unstable.

I have a suspicion its a kernal issue

not yet fully tracing the SEH chain, but i guess it may be a bug of bugtrap library or themida, and trigger a minidump action unexpectedly.
because it sounds a little crazy if windows try to create error report for any unhandled exception automatically.

[Yiting]

I tried blocking exception "esl::E_MTTerminated" throwing from micro thread (only one byte modified), and everything looks fine....

I found above patch will crash the client by several cutscenes, then I got another idea after tracing SEH chain.
Since minidump only happened in kernel-mode procedure, why not just handle c++ exceptions in user-mode, they are not native exception at all !!!

So I added a hook in c runtime to capture all c++ exception, then visit the SEH chain by myself......
It will also bring minor benefits if you're not using windows 8, because switching between user and kernel mode is expensive.

2.0r15
 - allow merging multiple requests into single message.
 - hide risky information from AhnReport.

[Chacha]

I found above patch will crash the client by several cutscenes, then I got another idea after tracing SEH chain.
Since minidump only happened in kernel-mode procedure, why not just handle c++ exceptions in user-mode, they are not native exception at all !!!

So I added a hook in c runtime to capture all c++ exception, then visit the SEH chain by myself......
It will also bring minor benefits if you're not using windows 8, because switching between user and kernel mode is expensive.

2.0r15
 - allow merging multiple requests into single message.
 - hide risky information from AhnReport.

I was about to report to you about the cutscene crashes, but looks like you were already on top of it. Great job, Yiting. I'll let you know if I run into any other issues. ^^

[vb286]

I found above patch will crash the client by several cutscenes, then I got another idea after tracing SEH chain.
Since minidump only happened in kernel-mode procedure, why not just handle c++ exceptions in user-mode, they are not native exception at all !!!

So I added a hook in c runtime to capture all c++ exception, then visit the SEH chain by myself......
It will also bring minor benefits if you're not using windows 8, because switching between user and kernel mode is expensive.

2.0r15
 - allow merging multiple requests into single message.
 - hide risky information from AhnReport.

So it isnt a Win 8 issue then?
Well, I've been wrong before.  Will this solve the ego lock on conversation issue as well?

[Yiting]

So it isnt a Win 8 issue then?
Well, I've been wrong before.  Will this solve the ego lock on conversation issue as well?

I have no idea it is or not, it seems only happens on mabi game client, not all programs.
At least, it must be something wrong that WER creates a minidump for a handled exception on win 8.
So I just keep them out from kernel exception handler, since c++ exception is near a goto statement.

It will solve the freezing issue for ego conversation on win 8, others should be as usual.