Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.acorn.programmer > #873 > unrolled thread

Filename length

Back to article view | Back to comp.sys.acorn.programmer

Contents

  Filename length Alan Wrigley <alan@alanwrigley.com> - 2011-10-14 12:47 +0100
    Re: Filename length Martin Wuerthner <spamtrap@mw-software.com> - 2011-10-14 16:28 +0200
      Re: Filename length Alan Wrigley <spamhater@keepyourfilthyspamtoyourself.co.uk> - 2011-10-14 16:00 +0100
        Re: Filename length Gazza <usenet@garethlock.com> - 2011-10-15 17:47 -0700
          Re: Filename length druck <news@druck.freeuk.com> - 2011-10-16 18:20 +0100
    Re: Filename length "David Holden" <SpamBin@apdl.co.uk> - 2011-10-14 14:49 +0000
      Re: Filename length Theo Markettos <theom+news@chiark.greenend.org.uk> - 2011-10-17 20:11 +0100

#873 — Filename length

It's been many a year since I last had a machine with restricted filename
length, so could someone please remind me what actually happens if you try
to create a directory (e.g. with OS_File 8) with a long filename. Does it
fail completely, or does it leave a directory in place with a truncated
name?

And if the latter, will OS_File 17 return 'not found' on the full name, or
will it match the first n characters and return 'directory found'?

Yes, there are still customers using old versions of RISC OS :(

Alan

[toc] | [next] | [standalone]

#874

In message <gemini.lt20rj006hph8013w.alan@alanwrigley.com>
          Alan Wrigley <alan@alanwrigley.com> wrote:

> It's been many a year since I last had a machine with restricted filename
> length, so could someone please remind me what actually happens if you try
> to create a directory (e.g. with OS_File 8) with a long filename. Does it
> fail completely, or does it leave a directory in place with a truncated
> name?

> And if the latter, will OS_File 17 return 'not found' on the full name, or
> will it match the first n characters and return 'directory found'?

> Yes, there are still customers using old versions of RISC OS :(

You do not need an old version of RISC OS to try that because the 
filename restriction is in the disc format, so you can enjoy 
restricted filename lengths even on your RISC OS 4+ system. All you 
need to do is to dig out an old floppy that was formatted with a 
pre-RO4 system or format a new floppy (or USB stick) to E/F format 
rather than E+/F+.

-- 
Martin
---------------------------------------------------------------------
Martin Wuerthner         MW Software      http://www.mw-software.com/
        RISC OS Software for Design, Printing and Publishing
---------------------------------------------------------------------

[toc] | [prev] | [next] | [standalone]

#876

Martin Wuerthner <spamtrap@mw-software.com> wrote:

> In message <gemini.lt20rj006hph8013w.alan@alanwrigley.com>
>           Alan Wrigley <alan@alanwrigley.com> wrote:
> 
> > It's been many a year since I last had a machine with restricted
filename
> > length, so could someone please remind me what actually happens if you
try
> > to create a directory (e.g. with OS_File 8) with a long filename.
> 
> All you 
> need to do is to dig out an old floppy that was formatted with a 
> pre-RO4 system

Heh! I never thought of that! It's been so long since I last used a floppy
that I'd forgotten they existed.

Alan

-- 
RISC OS - you know it makes cents

[toc] | [prev] | [next] | [standalone]

#880

IIRC filenames were restricted to 10 characters in old ADFS, and were
truncated if they were longer. E+/F+ permitted the use of long
filenames, although I don't think I ever found out how long they could
actually be.

[toc] | [prev] | [next] | [standalone]

#882

On 16 Oct 2011 Gazza <usenet@garethlock.com> wrote:
> IIRC filenames were restricted to 10 characters in old ADFS, and were
> truncated if they were longer. E+/F+ permitted the use of long
> filenames, although I don't think I ever found out how long they could
> actually be.

The disc format allows filenames up to 255 characters, but the total 
pathname must also be no longer than 255 characters, so you need to 
knock off at least 8 characters for ADFS::$. if it's in the root 
directory.

But then a 255 character pathname length can't be sent in a Wimp 
Message which has a limit of around 220 characters, making any such 
files inaccessible to the desktop.

So practically a filename in the root directory of an AFDS disc should 
not have a name longer than approx 200 characters.

Incidentally It is easy enough to create a pathname longer 256 
characters, so DiscKnight will attempt to truncate the filename to 
prevent files becoming inaccessible, from atleast the command line.

---druck

-- 
The ARM Club Free Software - http://www.armclub.org.uk/free/
32 bit Conversions Page    - http://www.armclub.org.uk/32bit/

[toc] | [prev] | [next] | [standalone]

#875

On 14-Oct-2011, Alan Wrigley <alan@alanwrigley.com> wrote:

> It's been many a year since I last had a machine with restricted filename
> length, so could someone please remind me what actually happens if you try
> to create a directory (e.g. with OS_File 8) with a long filename. Does it
> fail completely, or does it leave a directory in place with a truncated
> name?
>
It truncates the file or directory name to the maximum permitted length.

> And if the latter, will OS_File 17 return 'not found' on the full name, or
> will it match the first n characters and return 'directory found'?

No, it won't find it because it won't be there. In fact this is the simplest
way to find out if a disc is formatted in old or RO4 format.

The logic of this is that, even under RO 3.x, some filing systems could have
long file/directory names, eg. x-files, so the OS commands can cope, it's
the underlying filing systems that can't.

-- 
David Holden  -  APDL  -  <http://www.apdl.co.uk>

[toc] | [prev] | [next] | [standalone]

#884

David Holden <SpamBin@apdl.co.uk> wrote:
> 
> On 14-Oct-2011, Alan Wrigley <alan@alanwrigley.com> wrote:
> 
> > It's been many a year since I last had a machine with restricted filename
> > length, so could someone please remind me what actually happens if you try
> > to create a directory (e.g. with OS_File 8) with a long filename. Does it
> > fail completely, or does it leave a directory in place with a truncated
> > name?
> >
> It truncates the file or directory name to the maximum permitted length.

... if *Configure Truncate is set.  If it isn't, you get an error.  Most
machines have it set.

http://www.riscosopen.org/wiki/documentation/show/*Configure%20Truncate

Theo

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.acorn.programmer

csiph-web