I've installed ntfs-3g using apt. I added my user to the fuse group as the installer told me to.
Whenever I try to access a ntfs partition using KDE (I can see the partitions) I get the error:
How to solve this?

Regards

Is the NTFS partition represented in the /etc/fstab file?

Ah, forgot about that...I'll add it.

Thanx

I've been working on this one for a wile, and I've searched the forums for a solution. I've found:
su
[root password]
vi /etc/fstab
and I get something I can't use

I'm not sure but I think once I get into a place where I can put in he proper file it will go something like this:
/dev/hda1/ /windows /NTFS default 0 0

I'm currently logged into startx as root, and I'm going to try it like a newb, with the GUI's assistance.

Now it's gone to permissions denied...
I'll try rebooting.

Could anyone tell me the mount point? It's not /windows, I'm going to try /home.

I suggest nano instead of vi(m). It has the advantage that the key combinations are visable below the entry field.

Nano? I was hoping my newb trick of editing it as root logged into the KDE desktop would solve the editor issue. Is that whats causing it to forget what the NTFS file system is?

Nice, it kind of worked! Now I'm encountering another problem. It won't let my user level log in.
It's giving me many authority errors.

The exact error it's giving me on startup is "Could not start up kstartupconfig. Check you installation."

I went in and changed NTFS to ntfs, and changed the permissions to 0 and 0. I'll go back and try changing them back.

Logging in as root into a GUI is considered "Bad Practice" (TM) by more advanced users (like sys-admins and such ) Don't use the Powers of Root in vain! It'll haunt you one day... Use the su command (I hate sudo) in a terminal. You can invoke your editor of choice then and there. I know Gedit does Anyway, nano isn't that hard to understand, even for new users.

Oh, btw: lose the slash on the filesystem type, and put that in lowercase: ntfs, not NTFS

I'm starting to see that. It won't let me log in as anything else now! What do I do to undo a change I made that caused this type of error?

Depends on how much you'll loose when re-installing the lot. I know, it shouldn't be needed, but it could well be the quickest and easiest way out... Especially for inexperienced users

If you want to try it, open Synaptic, select the base-system group and mark all installed packages in that group for re-installation. Also, do likewise with the KDE packages. If unsure, do all packages (but that's gonna be very similar to re-installing from scratch ) Best of luck! (you're gonna need it. in plentiful quantities )

This is a fresh install; I must admit that I feel a little like Mikey Mouse in fantasia. Where he used the master broom wile he was away, and had to hand it back. I'm new to this, but certainly not lacking in brains; there has to be another answer. Stepping back from the notebook, and reassessing the situation I will admit I was a little hurried in finding a solution, but reinstalling again is very extreme. I'm so sorry I used the power of root in vane! Please offer me a better way!!!

btw where do I find synaptic, I ran a search for it, and all that came up were the mouse drivers.

TryThis will take quite some time, but it should give you a clean sheet to start from. You may need to add the --force option, but do so only when you're prepared to re-install from scratch if it fails!

If you are running kde, you could run "kdesu kate /etc/fstab".

You will just be running kate as root in this case. You can also use "gnomesu" if you use gnome.

It would be a good idea to learn vim. If you need to use a rescue disk, it probably has vim-minimal installed. Also, to edit /etc/sudoers, you should use "visudo".

For simple editing, it isn't that hard. Just hit the "i" key to start editing. When finished, press the "ESC" key, and then ":wq" to write and 'quit.

Logged out, to console. running code, this is fascinating. The power, the raw power! It's letting me change everything! Awesome learning experience thus far, I'm going to have to get a Debian KDE dpkg manual, just in case I want to do any of these later on. I like how it explains what each thing does...

lol, it just told me to restart iceweasels! That hilarious!

It's looking like it's having issues with frontend KDE =\
It locked up... That's depressing. I'll try again from recovery mode.

grrr... I'm really getting tired of installing this OS, I think this is lucky number 13 =\.

In recovery mode I'm getting:
xauth: timeout in locking authority file //.serverauth.2406
xauth: timeout in locking authority file //.Xauthority
xauth: timeout in locking authority file //.Xauthority
xauth: timeout in locking authority file //.Xauthority
X: user not authorized to run X server, aborting.
xinit: Server error
xauth: timeout in locking authority file //.Xauthority
*sighs*