NTFSFileSystem and FATFileSystem on OS4 ?

@salas00

very well done !!! It works : I can use NTFileSystem on my IDE device without any problem !!!!

Excellent you got it working too!

interesting, it doesn't work in write-mode by chance this way?

No way it could write because its author did not write the corresponding code !

However I find quite strange it's working using USB without any patch.

Check this screenshot of NTFS if you don't believe me...

It's a Lacie Mobile 2.5 USB box, installed with a 10GB drive formatted just an hour ago in WinXP as NTFS. Then connected to my A1 frontpanel USB. Using giggledisk to find HIGH CYL as seen in screenshot,edited the mountfile as seen and mounted it with c:mount!

And it works!

Check grab...

www.haymigga.dk/ntfs_os4.png

just noticed that the 4.5GB debian ISO files are show as only 2GB, i guess this is Opus fault? or?

@abalaban

Quote:
The Sirion USB stack used in AmigaOS4 is, or at least was, available for AmigaOS 3.x as well and supported the obsolete TD64 commands for AmigaOS <= 3.1, but it was forgotten to disable them in the AmigaOS4 version. This bug was fixed a long time ago already in the AmigaOS4 version, but it seems it wasn't yet in the version included in Update4.

@abalaban

Thanks for testing this and reporting back. Since it works I think I can remove the untested alpha warning and do an upload to OS4Depot too.

@all

I have actively used and *read* a working NTFS Windows 2000 professional setup Harddisk using the NTFileSystem module from Aminet...

this was done on an AMIthlon setup

as for filesystem limitations... there are some quirks...

may be something to do with 32bit vs 64bit block addressing
for the filesystem...to with maximum HDD sizing and filesize limits

I think AFFS and FAT32 share the file size limit for the 32bit restricted versions...

I know I have had a larger filesize than that stored on SFS and NTFS between various setups

now I will go back to scrimping and saving for a Samantha
so I can put together some kind of development machine

@haymigga

I did not say I wasn't believing you, because I do believe you. Just I was finding it quite strange, but joerg stated what I was guessing from the begining : the USB device was supporting both NSD and TD64... At least until update 4 (means, you'll have to use the Salass00's patch with the next OS4 version...)

@Salass00

I've been using it for more than 1hour and a half yesterday to listen to MP3's to have a frequent read access and I did not experienced a single quirk Well done !

fantastic work!

Well, I have added TD64 to experimental versions of my drivers, for who'd like to test those filesystems without the patch.

It would probably require a pretty uptodate system though (like the current betatester's installation).

Regards,
--
St?phane

@ sg2
welcome to amigans good to see you here

abalaban: i like people believing in me ;)

I'will probably try this method of yours soon as well, one thing you could check is perhaps whether the display of my 4.5GB ISO's as 2.0GB in both AOS4 + DIR-OPUS has something to do with L:NTFSfilesystem or my OS4 installation?

edit: i guess this is some 32/64 bit limitation...so using TD64 will solve it?

@haymigga

Quote:

No. TD64 is just for the lowlevel device i/o, it knows nothing about files or directories itself. If there is a problem with big files then this needs to be fixed in the filesystem itself because that's where it is.

@Salass00

but maybe this is also DOpus that limits itself to display file size to 2GB ? Don't know I don't have such big files at hand, nor I have a known supporting Filesystem (SFS2 for example) to test DOpus display...

Someone with the SFS2, a >2GB file and able to test which size DOpus reports ??

@Salass00

very good job, I used it with ext2 filesystem from
my linux HD and it worked great.

Many thanks.

Regards,
Paolo

@abalaban

I missed that part of what he wrote (i.e. about using DOpus) but now you mention it I'd say it's likely part of the problem.

Anyway on OS3.x there isn't really any good way to find out the size of file that is bigger than 4GB. Seek()ing to the end of the file and back again doesn't work because the position you get is a 32-bit integer. ExamineFH() doesn't work either since the size field is also only 32-bit.

On OS4 there is GetFileSize() which returns the size of a file as 64-bit integer, and of course Change/GetFilePosition(), which are more or less 64-bit equivalents of the Seek() command.

The underlying filesystem will of course have to support the relevant 64-bit packets also for these to work...

In this case when 2GB+ files all show up as 2GB probably the filesystem is simply putting the biggest number that it can fit into a signed 32-bit. Probably a good idea too since a lot of programs will likely treat the filesize as signed.

I have added TD64 support in the drivers, and am now waiting for a betatester to confirm you can now directly use those filesystems.

Regards,
--
St?phane

@sg2

Any feedback?

@abalaban

is reading NTFS drives still working for you fine under OS4 final?

I tried to get it to work on IDE port today, but no luck. Perhaps you could give a hint?

@haymigga

first I launch the TD64patch (in the user-sequence) with something like this :
Quote:
a1ide.device is the device to patch (here internal A1 ide),
1 refers to the fact that I choosed to only patch the device for the unit I'll use for NTFS and that my PC HD is slave on the first port.

Then once it's okay I double click on the mountlist I defined using giggledisk (from the NTFS archive).

An it just worked.