There seems to be an outstanding issue getting Abyss patcher to work on a new installation of Windows 7 with a new installation of Mabinogi R188 (or possibly earlier). I'm going to give you guys the whole story so maybe someone can pinpoint the issue.
Sorry for my name, I wanted something different from my Nexon Passport ID and couldn't think of anything. I've been using Abyss since early 2013. At the time I built a new computer and installed windows from a downloaded ISO "Windows 7 Ultimate SP1 (64) Integr January 2013". I'm sure Mabinogi isn't the first application I installed, I must have installed several Steam games, media codecs, Visual Studio 2010 and 2012 prior to installing Mabinogi. My current installation of Mabinogi, Abyss, and Tiara's Moonshine still works.
A few days ago, I bought a new solid state drive. The purchase also gave me a key I could use to download some 30 day trial software to clone my HDD onto the SSD. I'd rather not use that, so I brought out my same Windows 7 ISO I used to install on this system earlier. My UEFI BIOS lets me easily choose which drive to boot from so I installed Windows 7 on my SSD and have been using this dual booting system. I plan to format my old primary HDD, but it would not be wise to format until I know for sure that my most important software will work on my SSD.
After doing all the Windows updates and installing VC++ 2008, 2010, 2012, and 2013 Redistributables, The first non-Microsoft program I install is Mabinogi using the latest installer from the official site. I test it out and can get in game with my character. Loading times are a little bit better, but poor DevCat coding has it's limits. I then installed Abyss in order to get multiclient working, but when I load the game it crashes instantly. It never gets to the point of creating the client window, all I get is a "Mabinogi has stopped working" popup.
Here's two things that are interesting:
1) Now when you instal Mabinogi, it goes into its usual C:/Nexon/Mabinogi, and if you look in there, you'll see that some permissions have been set on all the files as if Nexon is trying to stop users from modifying them. It's laughable if they think they can stop client modification with Windows file permissions. That's the kind of solution a developer uses to show their idiot boss the problem is solved. I don't understand Windows 7 permissions as well as I should, but there were tiny padlock icons for every file, and I removed them.
2) I'm using the exact same Windows 7 installation base, same hardware, and have access to both drives. I can boot into my HDD and run the game with Abyss installed from my HDD and I can run the game with Abyss installed from my SSD. The Abyss.ini from my SSD shows that I am indeed using that installation from the SSD (I modify the WindowPositionX option for a sanity check). But if I boot from my SSD, I can not run either of the game installations on my HDD or SSD. This suggests that my SSD OS has an environment problem outside of the <C|D>:/Nexon/Mabinogi directory.
If I had an environment problem due to some bad Windows configuration or missing dependencies, then what are those supposed to be? It could be something that I have on my old OS installation but not my new installation. However, to the best of my knowledge, I've already installed all of the public .NET frameworks and VC++ redistributables. DirectX is already installed to begin with. For the record, I tried to manually disable all patches in Abyss.ini, including ExtraThreads=0, still doesn't work.
Just thinking about how the SSD installed game works fine when I run it from my HDD booted OS but not vice versa just confounds me. Should I post the two sets of Abyss.ini and Abyss_patchlog.txt in whatever states they ended at? Is it possible that Nexon found a way to lock the client through new registry keys and/or invasive DRM software? Can the next version of Abyss please contain more debugging messages?