Hi everybody,

Has SFS a 4GB filesize limit?
Atleast I could't copy a file of 4.3GB to my harddrive (I got a negative remaining HD space during the copy-process ).

Is it possible to have >4GB files with the Peg?

Thanks,

Spidey

It is possible... but most program can't handle sizes over 4GB. SO i suggest you try to avoid such big files.

regards,
tokai

Well thats not good! What if you want to make some DVD-R movies or data when the time comes that MOS can support that?

dont worry , Burnit is already able to handle such files.

Will BurnIT Support Dual Layer DVDs?

It should read them, but nothing writes to them ATM.

The problems is not SFS, but all old programs (68k mainly).
Anyway both DVD-R morphos future software support filesize bigger then 4GB.

And what about the well-known ~2GB filesize limit in dos.library? Or does MorphOS have some new API available in its dos.library (eg. parts of QBox API?) for DVD-R software developers which allow to work around this problem?

AFAIK this annoying 2GB file limit is in the MOS dos.library, too.

I think that both BurnIT 3 and FryingPan will handle this problem by splittig the DVD image files into chunks of less than 2 GB of size.

dvdrecord would be able to burn DVDs which contain more than 2 GB if there wouldnt be this 2 GB file size problem of dos.library, but currently I am not really motivated to change this in dvdrecord as BurnIT 3 will appear soon.

Hello,

i think, there is one problem more.
When i'll playing some MEPG-videos from
DVD-R media, the Mplayer has a problem with
files, there sectors was saved over 4GB!
With other words, Mplayer played files till 4096MB correctly and suddenly the first file (data-sector 0)
was played. This problem is with all my DVD-R medias (written with PC).
A copy back to HDD has the some problem!

Hey, any ideas???

(used on Peg1/April1 and DVD-ROM+CD-RW combo from Philips and MOS 1.4)

SFS has no such limitation, but dos.library does. There are some extensions planned for 64bit file access which will solve this *for apps that utilise them*.

As for having "negative remaining HD space", I suspect that's a cosmetic bug regarding the tools that calculate the remaining HD space.

Neko

Hello Neko (and all other replyers ),

Well, that cosmetic negative HD space I got from DirOpus, but:

I was copying that file (4.3GB size) from my pc to my PegII (network with Samba). So, I never used an Amiga-prog to copy it.
When the error occured I looked at DirOpus and saw that negative figure.

I checked SFS documentation (from the internet) and read the biggest supported filesize was just below the 4GB.

If I have it right, we'll get an update that will solve this "problem"? Nice!
(I dare not to ask "when", I'm just glad the problem is being taken care of )

Bye,

Spidey

FryingPan supports ISO-on-the-fly, so don't worry about the file sizes. And iirc, all the DVDs has it's movie files separated to 1 gig chunks, so there is no file bigger, than 2 gigs at all.

Bye, MarK.

That is correct - I have never seen any vob-files larger than 1024MB.

Well, it's OK, that the files on the DVD are splitted into 1GB parts, but what happens if you have a DVD ISO image? It's 4.7 GB in size!

Quote:
You'll probably say some bad words...

DOpus will give you freaky figures.. please don't expect this is a bug in MorphOS.

>by GK_LKA on 2004/5/28 22:59:39

>Well, it's OK, that the files on the DVD are
>splitted into 1GB parts, but what happens if you
>have a DVD ISO image? It's 4.7 GB in size!

Yeah, you are right.

To be able to burn that kind of DVDs there would be two solutions:

1. burn DVDs from a given path containing all the data on-the-fly without creating a ISO image first

2. create a ISO image which is splitted in chunks of less than 2 GB size; these chunks will have to be put together again by the burning application.