hm...
It doesn't use wine. It uses the wine idea (that is what it says on their homepage) and not wine itself.
At least it works on my linux without having wine installed. Has your knoppix write support on NTFS?
Because that is very constrained...

I don't see any problem in people having to use files from an existing windows installation, because who would try to use ntfs when he doesn't have NT/2K/XP at all? ;)

I think that is the most easy thing to do and it is indeed the most secure one!

greetings moses

ok, but it uses wine and the m$ driver...
i got knoppix, not the driver...it cames with write/read enable and no warning! dunno where they got it but its there!
regards,

Even the very latest NTFS support for Linux is beta. They don't guarantee it will write. In fact, they guarantee that it WILL eventually corrupt your NTFS partition. They recommend you use it as read-only.

There is a driver you can get that allows Linux to use the Windows NTFS driver. This works well in Linux without worry of corruption.

http://www.jankratochvil.net/project/captive/

You can get the source there as well. It's probably the best bet for NTFS on AROS.

well,
i do use knoppix and it has ntfs (module) support!

this has gone a bit off topic ... probably better suited for one of the bounty suggestion threads under development.

NoctReX:

Captive sounds great for linux users but i cant see it being of much use in our instance. firstly we would need to have an AROS "wine" environment, and then everyone would need the microsoft ntfs driver files.

Sounds like its based loosely on the old MSDOS ntfs drivers which did the same thing - just acted as a bridge to the proper code.

However - NTFS would be my prefered choice for a Filesystem to use.

there is a new filesystem for linux, it`s called captive, and this thingy enables full windows NTFS read/write access!
http://www.jankratochvil.net/project/captive/

I don`t know if it`s possible to make it work for AROS, but at least there is a free NTFS filesystem implementation out there...

Also a great filesystem for native AROS partition would by ReiserFS 4. It`s in the final testing stages, and so far it`s the best!
http://www.namesys.com/

- Reiser4 is an atomic filesystem, which means that your filesystem operations either entirely occur, or they entirely don't, and they don't corrupt due to half occuring. We do this without significant performance losses, because we invented algorithms to do it without copying the data twice.
- Reiser4 uses dancing trees, which obsolete the balanced tree algorithms used in databases (see farther down). This makes Reiser4 more space efficient than other filesystems because we squish small files together rather than wasting space due to block alignment like they do. It also means that Reiser4 scales better than any other filesystem. Do you want a million files in a directory, and want to create them fast? No problem.
- Reiser4 is based on plugins, which means that it will attract many outside contributors, and you'll be able to upgrade to their innovations without reformatting your disk. If you like to code, you'll really like plugins....
- Reiser4 is architected for military grade security. You'll find it is easy to audit the code, and that assertions guard the entrance to every function.

looks nice!!!

and sfs?
and some fs with balanced*tree? (i saw that on beos or qnx fs...dont remember)
ahh...and the ffs2?!?!? (used by morphos and amigaos4, (i am not sure))

PS: i am having problem with very long filename of jamiga...anyone notice this problem?
PS2: what is the difference between ffs and intl-ffs? (hd-toolbox)

The better choice would be probably Berkeley FFS used by BSD systems. Its advantages are:

1) doesn't get fragmented

2) supports background fsck (you can mount disk while fsck runs, like disk-validator on Amiga)

After FAT32 support is done, what do you think should be the next file system? I wouldn't mind seeing ext2/3.

Dammy
TeamAROS

Don't expect Mt. Rainier support anytime soon - that is a patented format with rabid lawyers. Any implementation to appear would precipitate calls from their lawyers to pay royalties. Negotiations on fees for Mt. Rainier is one of the things that delayed the launch of Windows XP originally.