Accessing your windows files

[oldcpu]

Also, if /windows/C .... etc exist, and you get the failure to mount (and it usually does fail the first time), then one can type the work around:

modprobe fuse

This is posted in my post #3 above. Please re-read that post and familiarize yourself with the details.

ntfs-3g driver has a very high data integrity quality, but it is still a beta release. IMHO it is still beta because it has some querks, when it comes to initial installation.

[mullet]

K i got that clear... but just want to make sure on something.

So the WIndows/E directories have to be put in this /etc/init.d/boot.local and /etc/init.d/halt.local directories? Correct?

[devils casper]

So the WIndows/E directories have to be put in this /etc/init.d/boot.local and /etc/init.d/halt.local directories? Correct?

No. just create these directories and execute 'chmod' command.
you can put this code in '/etc/init.d/boot.local'

modprobe fuse
ntfs-3g /dev/hdb1 /windows/E -o silent,umask=0,local=en_US.utf8

and this one in '/etc/init.d/halt.local'

fusermount -u /windows/E.

these codes are for /windows/E only. add lines for C and D too.



casper

[mullet]

I keep getting this error message
chicken:~ # ntfs-3g /dev/hdb1 /windows/E -o silent,umask=0,local=en_US.utf8
fusermount: bad mount point /windows//E: No such file or directory
fuse_mount failed.
Unmounting /dev/hdb1 (WinXP)

I'm sorry I tried following your posts and it still comes up with that error. I don't get how it doesn't work on this thing. I give up with it. Thanks for trying to help. I don't need it, if I desperately need to use my files, I'll just reboot into Windows. Cheers though.

[oldcpu]

I keep getting this error message
chicken:~ # ntfs-3g /dev/hdb1 /windows/E -o silent,umask=0,local=en_US.utf8
fusermount: bad mount point /windows//E: No such file or directory

This doesn't make sense. There should NOT be two slashes after windows (ie should not get /windows//). Did you make a typographical error? If you make even the slightest typographical error, this won't work. You have to be 100% exact in the syntax.

I'm sorry I tried following your posts and it still comes up with that error. I don't get how it doesn't work on this thing.

Do you have a directory called /windows/E, at the same level as /home, /etc, /var, /usr, etc ... ?

Please type: "cd /windows/E" and if that works, then type "dir" and tell me what you get.

[Arianyr]

Just to complete my contribution to this thread (apologies, .... I got lazy): On the suseforums site, the following was recommended to me, which works quite well for loading the ntfs-3g driver upon boot. First in a konsole (with root permissions) type:

modprobe fuse

Then edit the file /etc/sysconfig/kernel and modify the line that says:
MODULES_LOADED_ON_BOOT=""
to
MODULES_LOADED_ON_BOOT="fuse"

[I did this using YaST, as opposed to editting the file directly]

And finally I editted /etc/fstab to mount my ntfs partitions.
/dev/hdb1 /windows/e ntfs-3g silent,umask=0,locale=en_US.utf8 0 0

I had previously created the directory /windows/e with 775 permissions.

Hi!

I am trying to set this up. I can get it to work when already logged in and when i type in the command in a terminal.

However I am unsure how to set it up to boot. Following those instructions, i cant help but notice that 'MODULES_LOADED_ON_BOOT=""' isnt in my kernel file. I am using FC5

This is the content of my /etc/sysconfig/kernel

# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes

# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel

Is it safe to just add 'MODULES_LOADED_ON_BOOT="fuse"' to the end? Making it

# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes

# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel

MODULES_LOADED_ON_BOOT="fuse"

Eagerly awaiting a reply

[devils casper]

Is it safe to just add 'MODULES_LOADED_ON_BOOT="fuse"' to the end?

yeah ! add that line ...




casper