Hi, harkonen. So what you should do is open a Terminal and log in as root:
<enter root password>
and then run sysinstall...
This takes you to an ncurses menu; select "Configure" and then "Mouse"
If you seriously don't know how your touchpad is connected to your laptop, then trial and error will probably work. On this Toshiba, the magical choice turned out to be ALPS connected as a Bus Mouse, I think.
Accept those changes and get out of sysinstall and then restart X or reboot, whatever's easiest/quickest. Log back in and your touchpad will either be:
1. Not Working
2. Acting exactly the same as before.
Either way, it's actually a Good Thing™
then go back to sysinstall (see above) and try a different mouse protocol. If you're using Flux or KDE (which I am) then you can do all of this without a mouse. If your computer has virtual consoles that function properly (so far two toshibas I've owned have not) then you can also switch over to a text prompt by hitting control-alt-f2 or f3 or f4.
then open a terminal and run syndaemon and synclient and configure the things you want. In my case, this was:
bash$ synclient -l
<it lists all available properties of synaptics)
bash$ synclient TapButtonOne=0
or something like that...anyway, it was some property like TapButtonSomething and it was set to "1" meaning "yes, allow a tap to be read as a click" and so I set it to 0 meaning "no, taps are just me putting my finger on the touchpad or the edge of my hand brushing against it and should NOT send my mouse cursor to the other end of the screen AND click there so that I'm typing in an entirely different place than I thought I was."
And that's about it.