Well, the documentation coming with dgVoodoo might be "too much, too detailed" if someone is completely new to the wrapper and only wants to have a glance at it, giving it a quick try.
I think I'll move the docs inside a Doc folder and include a 'QuickGuide.html' with simplified practical instructions.
Thanks for listening and not taking offense, Dege. A Quick Guide sounds like a good idea. If you still have a Readme, may I suggest an opening line that reads something like "If you're new to dgVoodoo 2 and just want quick, simple instructions, see QuickGuide.html", just in case some users open the Readme first, out of habit.
If you separate out the simple, practical instructions into a QuickGuide.html, leaving the Readme*.html for more technical information, I wonder if you could then simply combine those three files into one. They're HTML files, so you could put links at the top of the page: "General" (that, when clicked, takes you to the section that has everything that was in Readme.html), "DirectX" (ditto for ReadmeDirectX.html) and "Glide" (ditto for ReadmeGlide.html). That would simplify your documentation and maybe eliminate the need to keep a separate Docs folder, since you'd have only two HTML files in the root folder, fewer than you have now.
Yes... I was even thinking on an installer. Clicking 'Next' button a few times and voila dgVoodoo could be 'there', installed.
But, since I don't want to copy wrapper dlls into system folders (DX ones couldn't even be copied there), I could only keep them in /Program Files/dgVoodoo2/
but then the CPL or some other extra application would always be needed for adding each game to dgVoodoo for usage.
If you decide to ever experiment with an installer, I have a lot of experience with Inno Setup and would be glad to help. I can't think of a good excuse for one, though, since, as you said, you can't copy the DirectX DLLs to the system folder and I think that most people just prefer copying the CPL to each game folder, as well. You could have an installer that copies the files to each game folder (so that users would run the installer once for each game that they want to set up with dgVoodoo 2), which could be a little convenient, but wouldn't do much besides copy the files for them. If it could somehow detect the DirectX version that the game uses (without launching it), automatically copying all required files would be useful, but I'm not sure that that's even possible.
What about an installer that, on first run, installs (or gives the option to install) all of the components that can go into the system folders (Glide DLLs, 3Dfx splash files, D3D compiler DLLs, D3DRM, etc.) and allows for setting up one DirectX game (i.e. copying files to the game's folder); then, can be run subsequent times to set up further DirectX games?