About the scrolling text issue in Glidewrapper:
If you have windows 8 or newer, and run any version before 1.14 with the glidewrapper, you will get scrolling text in the upper left hand corner of the screen. This slows down load times greatly. There are a few ways to fix this if you are dead set on using the wrapper:
1. Run a version of windows before windows 8. In older versions of windows, there is an option in properties to "Disable Desktop Composition". If you right click your D2 shortcut and check this box in properties, it will fix the scrolling text issue. This option isn't available in windows 8-10 so
@knightmarewraith @Mezion this won't work for you.
2. Use version 1.14. Blizzard fixed the issue in this version.
3. Modify your d2glide.dll to disable the /fps command in the game. This might not be allowed according to forum rules as it does change a file.
The scrolling text issue is caused by a bug in the code of this file that can be attributed to the combination of the in-game /fps command and the addition of Aero in windows. In older versions of windows, this scrolling text actually does exist when using glide, but it does not cause the issue because the text goes so quickly it is unnoticeable.
I actually contacted the famous Sven of Sven's Glidewrapper about the issue and he says that there are 8 bytes of code in the d2glide.dll that applies a "handbrake" to the scrolling text that is there so that the /fps command will work. This handbrake can be removed by a simple change (changing the 8 bits to remove the handbrake), but then the /fps command will not work.
If you are seriously interested in using the wrapper, I could try to contact Sven about it again, he's a really nice guy! I could also try to remove the handbrake myself, I have opened the d2glide.dll before and I know where the problem resides, but I haven't tried fixing it yet since I am not great with editing hex (meaning I don't know anything about it). There isn't much risk involved with this change because it only affects the /fps command. You wouldn't be able to play on battle.net anymore though since it changes a core file.
About the 1.5x speedup:
I have no idea on this one guys. It's the first time I've ever heard of the glidewrapper producing this problem. You could try some of the solutions posted in sven's FAQ (
http://www.svenswrapper.de/english/faq.html), like adding the -3dfx. Unfortunately there are so many stumbling points that you might have to try a bunch of different settings before you find a solution if at all.
It sounds like d2 is running fine without glide, why do you want to use it?