Second - speed. If the speed is not up to snuff, adjust the cycles. Most games will either use cycles=auto to have dosbox adjust for you or cycles=max to get the most speed you can for heavier games. Swap between the two if you have issues, but so far with GOG's catalogue you don't need an exact number. Stick with those two.
I'd like to point out that cycles=auto is not actually much different from cycles=max. It runs the emulator at low cycles for games running in real mode and at max cycles (identical to cycles=max) for protected mode. Personally, I find manual fine-tuning of cycles to produce better results than autodetection.
Vista users - Do not use OUTPUT=Surface. I'm pretty sure no GOG.com games do by default, but don't change it. Surface causes some strange colours when it goes into fullscreen mode. Use DDraw instead, as it actually improves the performance for Vista. At least it does for me, it makes using alt-enter much quick for one thing.
Surface output is the slowest one and causes graphic glitches in some games. DDraw is the fastest, but the images appear to lose definition when using this output mode.
Personal suggestion? Overlay .
First off - the sound quality. It may be scratchy or just not quite as good as it could be. Under the [mixer] section change the output to "OUTPUT=44100". This raise the overall sound quality. There are also individual rates such as sbrate= and adlibrate=, I set everything to 44100. It gives you the best quality with next to no hit on performance. Even on my low end PCs it doesn't affect the speed.
True, but keep in mind that certain exceptionally resource-demanding titles might require the lower sampling rate to reduce CPU load (think: Quake, Duke Nukem 3D, System Shock Enchanced CD or X-Com: Apocalypse).