No problem. If you watch my Singling 1.0.3 video, I show how to use the 'data' folder as well. But if you are using RRM/RWM, might as well use Singling since Singling has Orange Color Runes + Rune Word Mod + Modified D2gfx.dll all together .
Good. Just confusing me, then. Not hard, I know ...
You are probably doing something incorrectly.
Doubtless.
Here's what I've done. Maybe someone can let me know where I've gone wrong.
1) downloaded installers from Blizzard.
2) Installed 1.12a
3) Upgraded to LOD
4) Put the Classic and Expansion folders from the big bundle in the Diablo II folder.
5) Put the Version Switcher in the Diablo II folder.
6) Started D2 to make sure it was working (A-OK).
7) Opened the Version Switcher.
8) Added a new entry, set to 1.12A Expansion, put the path in (C:\Program Files\Diablo II\Game.exe), and didn't bother with flags.
9) Launched from this entry, and D2 started.
10) Exited D2, added a new entry, set to 1.00. Made sure the isos were mounted in DAEMON tools.
11) Launched from the new entry, watched the files move around, then nothing. No joy.
12) Created another entry, set to 1.07 expansion, launched, watched files move around, then: no joy.
13) Created another entry, set to 1.12 Classic, launched, watched files move around, got a Classic start.
I'm thinking this has something to do with the CD-less versions that I pulled from the internets.
14) Created another entry, set to 1.13c Expansion, launched, watched files move around, got an Expansion start with 1.13 showing.
Pretty sure now it's something in the downloadable, cd-less versions that doesn't really like the old patches, but maybe I'm wrong.
I'm happy to try whatever, but for now I'm way too frustrated and am just going to go to bed. I'll try again after work tomorrow.
Thank you for the program, FB! I hope to get it working, as I've never played most of the old versions.
Actually it most likely is, I tried getting it to work for ages using the online installer with no luck. Worked first time doing a fresh CD install (for patches pre 1.12).It's not related to the online installer.
User Account Control (for Windows Vista and Higher):
---------------
On Windows Vista, 7, 8 and higher, UAC is enabled by default and Diablo II.exe and Game.exe require administrative privileges.
Because of this, Bliss Version Switcher will not be able to launch Diablo II when you click launch (Clicking the button won't do
anything). If you are using one of these operating systems, you have two options:
1. Disable UAC.
To disable UAC, Press [Windows Key + R] and type "msconfig", then go to Tools -> Change UAC Settings, and switch the slider all the way down.
Then restart your computer. Now you can launch BlissVersionSwitcher.jar as usual and you are good to go.
2. Use the BlissVersionSwitcher_UAC.bat script to get the appropriate permissions
Launch the BlissVersionSwitcher_UAC.bat script which will ask you for administrative privileges, Windows will then give
Bliss Version Switcher correct permissions. After this, BIS (and in turn Diablo II.exe and Game.exe) will have the permissions
necessary to launch.
This approach requires your system to know where your "javaw.exe" file is which is the file that Java uses to run its applications.
If you run the script above and it works, then you don't need to do anything, however if you get an error saying that javaw wasn't found,
your system probably doesn't have java in its PATH. To add your java directory to your path, do the following:
1. Find where you installed java, and locate the bin directory (Mine is installed at: C:\Program Files\Java\jre7\bin)
2. Go to Control Panel -> System (or press [Windows Key + Pause/Break] button)
3. On the left click "Advanced System Settings" then navigate to the "Advanced" tab and at the bottom click "Environment Variables"
4. On the bottom box where it says "System Variables", find "PATH" and click "Edit"
5. Add the bin directory where java is installed to the end of the line and press Ok. Make sure there is a semicolon ( ; ) separating
the entries. Example: C:\Python33\;C:\Program Files\Java\jre7\bin
6. Run the script again :)