Mark Brinicombe wrote:

> Hmm 64bits addresses more that take doesn't it ?

A daddr_t is a signed 32-bit number (negative used to access indirect
blocks via vnode). This is probably the limiting factor; with a 1KB
fragment size as is common on most discs, 2 gig * 1024 = about two
terrabytes...

> Actaully will RiscOS have a problem with it ? Certain putting filecore on
> it may be more of a problem. If it is not the only disk on the system then
> it does not even need to be configured under RiscOS.

If it's two terrabytes, almost certainly :-)

For 5.1gig, as long as the 'new filecore' is used, it'll be file albeit
the LFAU will be pretty big.

	Neil

-- 
Neil A. Carson