On looking at that older release list (win8.1 64 bit), I was actually only one release behind on my PC: My dealer installed release was "13.12V10 from 18/12/2013" Not too shabby after all. :-D
Although, the dealer actually felt very guilty when I called him about my situation, when I got stuck between the uninstall and reinstall phase. He actually sent one of his support guys over to my place to help me resolve it. He had thought the drivers "would be completely up to date" on the DVD. He did not think of checking online first. Profusely apologised and partly redeemed himself with that gesture of sending someone for helping me resolve it.
As to not buying AMD cards, too late. It's done already.
I'll remember this experience for the next purchase (6 years from now?)
Yes, I did go through those links to begin with. Ironically, the AMD catalyst software gave me the links and helpfully suggested the complete uninstall utility too. After uninstall and reboot, the screen went garbled completely and I could not get the low-res video to work, nor could I manage to get the old drivers reinstalled... It was this restart, safe-mode, debug, rinse, repeat drill that ruined the six hours for us.
We eventually rolled back to a restore point, and installed the latest drivers to get it going.
Well, now I can see that the most recent version, and the one before have not helped with the mod. How many versions further back should I attempt to roll back? I feel now that having outdated drivers by more than two releases is not an optimal solution to getting some mod to work for me.
This time, I went through the crash log, asnd saw this line:
Code:
Caused by: java.lang.NoClassDefFoundError: poersch/minecraft/util/keyhandler/IKeyReleasedCallback
and
Code:
Caused by: java.lang.ClassCircularityError: poersch/minecraft/core/IClassPatcher
at poersch.minecraft.core.ClassPatcher.transform(ClassPatcher.java:48)
Searched with those in the net, and this error was previously reported by other users to him, and the modder poersch was having a discussion in MCF with another modder over this error cropping up on his mod! So, technically speaking, there is something amiss with his mod.
As mod pack dev, I assume you were in touch with the mod dev over permissions and such? Could you be kind enough to let him know of this problem with his mod too? I asm asking this from you, since I assume you'll have a direct channel of communication with the guy.
Cheers for the help though, man.