ajulasilotr wrote:Same thing happened... I might search my old CD's and come back later, if you or anyone else still have some ideas that might work, I'll try them out. Thanks a lot for your input for now!
ajulasilotr wrote:Same thing happened... I might search my old CD's and come back later, if you or anyone else still have some ideas that might work, I'll try them out. Thanks a lot for your input for now!
RequiemLux wrote:Quirinus wrote:Yes, it's solved in the next version. It will be released some time before the ladder reset/patch. This time it will be released 100%.
Not to be pushy but time's almost up
Quirinus wrote:RequiemLux wrote:Quirinus wrote:Yes, it's solved in the next version. It will be released some time before the ladder reset/patch. This time it will be released 100%.
Not to be pushy but time's almost up
It's almost done.
I think i fixed the vidtest in this version.
The c0000005 error is weird. I think I know what approximately causes it and maybe how to fix it, but I could be wrong. I'll try to fix it in the next version after this, but otherwise whist will have to solve it. It's kinda hard to solve/test because almost no one gets the error (including me).
Unda wrote:Quirinus wrote:RequiemLux wrote:Quirinus wrote:Yes, it's solved in the next version. It will be released some time before the ladder reset/patch. This time it will be released 100%.
Not to be pushy but time's almost up
It's almost done.
I think i fixed the vidtest in this version.
The c0000005 error is weird. I think I know what approximately causes it and maybe how to fix it, but I could be wrong. I'll try to fix it in the next version after this, but otherwise whist will have to solve it. It's kinda hard to solve/test because almost no one gets the error (including me).
Once you add both Game.exe and Diablo II.exe to DEP, c0000005 error stop showing up.