This is why is not a good ideea, because ntfs write access is not fully stable, and you may end up with corrupt data on your ntfs partition. do you want to take the risk of loosing everything ? it doesn't matter if you use a third party ntfs driver under my opinion is still risky. And the reasons why ntfs access is not complete you got the answer from gbonvehi in the quote above, so this question would best fit to micro$oft.

As gbonvehi said, Microsoft has kept the NTFS specs kindof secret. There have also been several revisions since it first appeared in Windows NT (hint: NT File System). It takes time and effort to learn the secrets of NTFS partitions, and most kernel hackers have other things on their minds also.

ok i will switch back to my fat32
but how can i configure slack to use my drivers as fat32 not as ntfs????

because it is not done yet. It is still in development stage.
At this stage, massive data corruption was observed in several cases.

What on Earth do you mean?

If you mean, you want to use fat32 partitions, and if isn't already enabled, then you must recompile your kernel , unde File systems , enable DOS FAT fs support, then enable VFAT (Windows-95) fs support .

Also, if the partitions are formatted NTFS, you'll have to reformat them as FAT 32 before using them as such, surely..

i mean that i have mounted my ntfs drives on slack
now i will chang them from ntfs to fat32
then i must remount them
can any body help me?

ok, then change them from ntfs to fat using partition magic under window$ or whatever software you want, then return to Linux, make sure you have DOS FAT fs support and VFAT (Windows-95) fs support enabled in your kernel config, either as module or built-in drivers. Then mount them by either adding a line in /etc/fstab for them, or from the command prompt as follows: mount -t vfat /dev/hdXy /mnt/mountpoint (replace X and y with your config), for example if you want to mount first partition on the primary master disk (your C: drive that would be) the command should look like: mount -t vfat /dev/hda1 /mnt/mountpoint . Make sure the directory /mnt/mountpoint exists before trying to mount it.

what do you mean by "compiling kernal" which kernal do u mean my 2.4 or compile a new one 2.6???
and how can be sure to have DOS FAT fs support and VFAT (Windows-95) fs support enabled in my kernel config?????

Ok, I see we have really big problems communicating, and also seen that you open numerous threads when you could had just state all your problems in one, anyway... I will ask some questions and you read them carefully, understand them carefully and most important answer them carefully. They will include all problems from all your threads in this one, cause as I've seen all are kernel related, meaning you must mingle with the kernel in a way or another.
You stated that you are running kernel 2.4.31 somewhere in a thread, you can either keep this one, or install (compile) a new 2.6.x kernel, think about it and let me know in the post you are going to reply so we know what to do.

In this thread you ask help (lately) to mount your fat32 partitions (assuming you already have them, or converted them from ntfs to fat32 from within window$ with Partition Magic as you've mentioned before). Now, I need you to be booted in Linux, execute the following commands, copy the output you get after issuing them, and paste them here so we can check them. Open a terminal emulator (ex. Konsole, xterm, rxvt, etc.) and:
1. fdisk -l
2. df -ha
3. cat /etc/fstab
Again, copy all the output of these commands and paste them here.

In another thread you complain that your Realtek RTL-8139 PCI Fast Ethernet Adapter doesn't work, that drivers for it don't exist and things like that. You're wrong, the only way it could not work is if your network card is broke, because drivers for this kind of card exist in the kernel (both 2.4.x and 2.6.x have it). This we will set up later, after you decide on what kernel version you want and finish with your fat32 partitions problem.

This is my last effort in helping you, cause sometimes I get the feeling you don't give too much, so if you really want this to work out, fast and quiet, just answer my questions and follow my lead. Waiting for replay.

PS: about your spelling.... I'm not from US neither, I didn't come from academy or very high schools, but you could at least try using the spell checker existing here. That means if you write a word incorrectly, that word will have a red color, so you can review it until you get it right... just so we can understand each other better.

I just hate that windoze doesn't like to format FAT32 partitions bigger than 32 gigs, that was implemented to force the users to use NTFS on their drives; however you can format your smaller-than-32-gigs partition as FAT32 and latter resize it with parted, Partition Magic or any other software.

kind of offtopic but I wanted to share that link

you could read here:
http://www.linux-ntfs.org/

and also /Documentation/filesystems/ntfs.txt
in the Kernel tree if you have downloaded a kernel from http://www.kernel.org/

tobyl

here you are
root@host:~# fdisk -l

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 894 7181023+ 7 HPFS/NTFS
/dev/hda2 895 9729 70967137+ f W95 Ext'd (LBA)
/dev/hda5 895 3104 17751793+ 7 HPFS/NTFS
/dev/hda6 3105 5314 17751793+ 7 HPFS/NTFS
/dev/hda7 5315 7524 17751793+ 7 HPFS/NTFS
/dev/hda8 7525 8829 10482381 7 HPFS/NTFS
/dev/hda9 8830 8892 506016 82 Linux swap
/dev/hda10 8893 9729 6723171 83 Linux
root@host:~# df -ha
Filesystem Size Used Avail Use% Mounted on
/dev/hda10 6.3G 2.9G 3.1G 48% /
proc 0 0 0 - /proc
/dev/hda1 6.9G 4.9G 2.1G 71% /mnt/win_C
/dev/hda5 17G 14G 3.1G 82% /mnt/win_D
/dev/hda6 17G 16G 1.4G 93% /mnt/win_E
/dev/hda7 17G 14G 3.7G 79% /mnt/win_F
/dev/hda8 10G 7.0G 3.1G 70% /mnt/win_G
devpts 0 0 0 - /dev/pts
usbfs
root@host:~# cat /etc/fstab
/dev/hda9 swap swap defaults 0 0
/dev/hda10 / ext3 defaults 1 1
/dev/hda1 /mnt/win_C ntfs ro 1 0
/dev/hda5 /mnt/win_D ntfs ro 1 0
/dev/hda6 /mnt/win_E ntfs ro 1 0
/dev/hda7 /mnt/win_F ntfs ro 1 0
/dev/hda8 /mnt/win_G ntfs ro 1 0
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0

Speaking about this subject, just right on news headers: http://sourceforge.net/mailarchive/f...&forum_id=2697