Quote (GRATS @ Feb 13 2016 12:37am)
nobody cares what you think, because unlike you I know things.. I don't google them and get shit wrong all the time.
windows throws errors that are wrong ALL THE TIME
Well, one we have a Youtube that explains how to do it. and two, I have a text file I wrote to myself back in the D2 Open Battle.net days.
Quote
Save the OCX file to your Windows System32 directory... usually c:\windows\system32
Once you've saved the file then... Go to the Start menu, select Run...
Then type:... regsvr32 c:\windows\system32\comdlg32.ocx
Make sure you change the path to YOUR system directory where you saved the .OCX file.
Use a similar technique for the MSVBVM60.DLL and other files if you need it.
PUT ALL THESE FILES IN SYSTEM32 FOLDER AND TYPE COMMAND FOR EACH ONE JUST CHANGE THE FILE NAME IN THE COMMAND EACH TIME
There was like 8 .ocx or .dll files that were needed for the open battle.net, mods, editors etc.
We had to dump all eight in the System32 folder then register them one at a time.
/e @Deny
Never thought of duplicates, could be an issue. In the old D2 case, they were just missing...aka...didn't come with Windows.
Video seems pretty explicit.
I will say one thing....read the topic title.
Also, I had so much trouble on Win 7 after Visual C++ Redistributable 2013 ...I just removed it and went back to 2010.
Quote (Deny @ Feb 13 2016 12:43am)
yes but delete all but 1 and your games won't work
Microsoft doesn't actually have shared dlls any longer. They claim they are but in games your command lines go through the game folder itself.
/ee First off, youn suggested duplicate files. I can't see a Visual C++ file going in a game folder...but if that has changed recently...the command STILL has to have the right file path to register the file.
This post was edited by Ghot on Feb 12 2016 11:57pm