Is DOS 64 going to be part of MOS 1.5? The 2 gig barrier for dos.library is quite a pain...

[ Edited by matt3 on 2005/8/17 17:33 ]

Can anyone *not* agree to this?

here is one better. has anyone using MOS ever needed even close to 2 gigs of memory

Not memory, no, but files could be handy...

Even if DOS would be 64 bit there would still be a need to have 64 bit support in SFS aswell. Fixing DOS would just move the limit from 2 GB to 4 GB files.

Bounty SFS 64 bit anyone ?

DOS 64 belongs to a special kind of reality, so called "1.5 reality", which is a reality only in some exclusive portions of the space .

I think MOS need support for Files larger then 4Gigs and larger then 16Gigs. You ask why!?!
I say BlueRay and HD-DVD and HDTV, for this kind of media files with maximum 4Gig size are a bit small.
When the MOS Dev team will brake the 2 Gig Barriere why only expand to 4Gig.
Why not built something for the future a filesystem and dos.lib with support for files larger then 32Gig?

Quote:

Better than nothing for a start...

You can have "poor mans" 64 bit dos easily, we just don't know if relevant 64bit functions are created in mythical 1.5 =)

Why not add to asyncio.library relevant 64bit functions ? asyncio would then create a pile of 2GB-1byte files and present them as one to calling program. You just need to promote these functions and present proper API extensions to developers. The good thing is, when such functionality would be available in real dos.library, you could just wrap asyncio.library around new functions, so that old programs (written for updated asyncio.library) automagicaly would use new OS functions.

The real problem is to make relevant programs use these new functions and not custom sollutions

Is this idea usefull ?

Initially instead of sfs we could use ext2fs which will give us 4 tb's until sfs is 64 bit...

I went to the sourceforge mos site and didn't find a dos library improvement. Is that something we should add there?


Matt