I learned that the ntfsprogs tools + ntfs-3g will be perfect.

Ntfs-3g is just a single mount cmd and ntfsprogs provide many useful tools for ntfs such as: ntfsresize,ntfsundelete,ntfsclone......

I said sorry before. And if you got the other solution than setuid,
please share your experience and that will be appreciate.

We should discuss something more useful than flame war.

Per Zhoun:
Yes, you did & I apologize for not acknowledging that.
Thanks, Zhoun. Your post (#16) got me to look at the packages for ntfsprogs & ntfs-3g. The lines in ntfsprogs doinst.sh that apply to mounting are:
The corresponding lines in the ntfs-3g
doinst.sh are:
So, both packages can be installed, without interference, & one driver or the other chosen when the filesystem is mounted. What I had previously read led me to believe that both could not be installed at the same time.
Also, I have not been able to find any other way to mount an ntfs filesystem, as a user, except by using set-uid-root. I guess that's the way I will go, even though it is contrary to my instincts.
Thanks again, all, for your input.
Regards,
Bill

From what I've seen, the difference hinges on whether the devices is classified as *removable* or not. For example, if you take thumb drive and format it with an ntfs filesystem, it mounts just fine as a normal user (with read/write permissions), just like any other removable device would do. However, if the device is not classified as removable, it doesn't. Unfortunately, most people's use cases are going to be with block devices similar to what you have, so that's definitely a problem. I didn't catch this in testing ntfsprogs, as I don't actually have anything set up to dual boot - I accidentally discovered it when doing some recovery work on a laptop hard drive that I'd put a usb adapter on and plugged into my -current laptop.

The reason that ntfsprogs was chosen instead of ntfs-3g is basically that ntfsprogs was already in /extra, so it seemed more appropriate to upgrade it to the latest version and move it into ap/ rather than removing it and adding ntfs-3g. With that said, I haven't had time to do any further research on how to make it behave as expected, so assuming it's possible, any information that you guys are able to find is welcome - you can mail me at rworkman AT slackware.com or post it here. I can't speak for Pat, but I personally would be very reluctant to "undo" the ntfsprogs addition unless it's simply not possible and/or bad from a security standpoint to do what we want it to do.

I finally got to spend some time today investigating the two ntfs drivers. Using set-uid-root is the only way I have been able to find to get a user permission to mount a filesystem under either one. The instructions that Zhoun gave worked perfectly for both ntfs-3g & ntfsmount. The only surprise was that "umount" did not work, but "fusermount -u /mnt/win2k" did. I will probably continue to use ntfsmount, just because that is what is included in -current, however I may not use it very long, now all of the programs that I need windows for work acceptably under wine, & I may be able to erase my win2k partition.
Edit: I have not been able to get the fuse.ntfs driver to work from fstab. This works for ntfs-3g:
but if I change the "ntfs-3g" to "fuse.ntfs", I get:
If I remove "users,", I get:
I finally wrote a short script to mount/unmount the partition.
Regards,
Bill