I could be wrong, but I thought that Moodle did this intentionally (or at least was actively doing something to prevent your browser's back button taking you back to where the link you clicked is located).
I did however, also think that this had been corrected, though when I tried it a moment ago it didn't work the way I thought it would.
I don't think the problem is due to the include path, or to PEAR that is just extra information provided to help you locate the problem.
Perhaps if you cut and paste the exact error messages you are receiving into a forum post then someone will be able to help.
You may wish to do so in etheir the Installation Problems or the General Problems forum.
Sometimes the error report shows the include path. If your server is set up to use PEAR then you will have it in your include path, even if Moodle isn't using it.
For example you might see something like this:
Warning: print_recent_activity(): Failed opening '/var/www/html/moodle/mod/attendance/lib.php' for inclusion (include_path='.:/usr/share/pear')
in /var/www/html/moodle/course/lib.php on line 602
Changing the sample rate should not change the speed of the file playback unless the player is expecting a different sample rate from the one the file has.
This might happen because the player is hardcoded to only accept certain sample rates or because the file is contradicting itself by claiming to be a sample rate it is not.
Either way, something odd is going on.
Too late. Microsoft already has the catchily named WVG (Windows Vector Graphics) which looks exactly like SVG if you squint a bit.
It's a vital component of their new XAML display engine which is part of the Avalon display layer that will be unveiled with the introduction of Longhorn in a few years.
Luckily both Flash and SVG have a wide base of support so I don't think they are particularly threatened.