From Newsgroup: comp.sys.acorn.hardware

I have a 1TB HDD which according to my PC is FAT32 but if I connect it to
my ARMX6, via a USB KVM switch, it sees nothing. When switched to the PC
it is seen fine. The ARMX6 is RO5.3.

Why?

I thought that the latest versions of RO could work with larger drives
--
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.hardware

In message <5bab2e103fSpambin@argonet.co.uk>
Stuart <Spambin@argonet.co.uk> wrote:

I have a 1TB HDD which according to my PC is FAT32 but if I connect it to
my ARMX6, via a USB KVM switch, it sees nothing. When switched to the PC
it is seen fine. The ARMX6 is RO5.3.

Why?

Do you have the FAT32FS module loaded on RISC OS ?
--
Chris Hughes
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.hardware

In article <812a30ab5b.chris@mytardis>,
Chris Hughes <lists@noonehere.co.uk> wrote:

In message <5bab2e103fSpambin@argonet.co.uk>
Stuart <Spambin@argonet.co.uk> wrote:

I have a 1TB HDD which according to my PC is FAT32 but if I connect it to my ARMX6, via a USB KVM switch, it sees nothing. When switched to the PC
it is seen fine. The ARMX6 is RO5.3.

Why?

Do you have the FAT32FS module loaded on RISC OS ?

It seems to have no trouble with memory sticks or the FAT32 partition on a drive I was checking out for friend. It was recovered from an old PC in
2008, and had two partitions, a 32G FAT32 and the 2nd partition, of the
120G drive, was NTFS.

Both partitions were deleted using my PC, and the whole the reformatted to
RISC OS using the ARMX6
--
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.hardware

On 6 Oct, Stuart wrote in message
<5babc790acSpambin@argonet.co.uk>:

In article <812a30ab5b.chris@mytardis>,
Chris Hughes <lists@noonehere.co.uk> wrote:

Do you have the FAT32FS module loaded on RISC OS ?

It seems to have no trouble with memory sticks or the FAT32 partition on a drive I was checking out for friend. It was recovered from an old PC in
2008, and had two partitions, a 32G FAT32 and the 2nd partition, of the
120G drive, was NTFS.

DOSFS has a size limit, IIRC -- presumably it stops at one of the extensions
of the FAT standard. 32G sounds as if it would be within the capabilities of DOSFS, while 1TB sounds as if it might not.

As Chris says, install Fat32FS if you haven't already.
--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.hardware

Steve Fryatt <news@stevefryatt.org.uk> wrote:

On 6 Oct, Stuart wrote in message
<5babc790acSpambin@argonet.co.uk>:

In article <812a30ab5b.chris@mytardis>,
Chris Hughes <lists@noonehere.co.uk> wrote:

Do you have the FAT32FS module loaded on RISC OS ?

It seems to have no trouble with memory sticks or the FAT32 partition on a drive I was checking out for friend. It was recovered from an old PC in 2008, and had two partitions, a 32G FAT32 and the 2nd partition, of the 120G drive, was NTFS.

DOSFS has a size limit, IIRC -- presumably it stops at one of the extensions of the FAT standard. 32G sounds as if it would be within the capabilities of DOSFS, while 1TB sounds as if it might not.

IIRC DOSFS stops at 2GB because it uses image files, and file sizes are
limited to 2GB on RISC OS. Not sure if recent work on making every file
offset be unsigned has bumped that limit to 4GB, but it can't go higher
without a 64 bit file API.

FAT32FS uses the ADFS/SCSIFS/etc block interface which isn't subject to the image file limit.

Theo
--- Synchronet 3.21d-Linux NewsLink 1.2