Problem with filename lenght

Hello everyone,

i'm having problem with the lenght of a filename. What the maximum lenght of a filename for AmigaOS?

When i extract files from certain archives i see that filename are truncated.

Any hint?

thank you

@AmigaBlitter

Sigh.

There a way to change the partition type? I mean convert to another filesystem?

@AmigaBlitter

Backup your files, change the filesystem for the partition in Media Toolbox, reboot, format, and restore your files from the backup.

Best regards,

Niels

Don't tell me: i have to format :P

I can't backup all file, can i?

There is a tool for this?
Just copying the file doesn't works, cause some files return an error (i guess is a FS limit)

@AmigaBlitter
If you read the chart you will see that the only filesystem that has filenames with less than 107 characters is the old OS3 filesystem. Unless you intentionally formatted all your partitions with the old filesystem, you shouldn't need to change filesystems. I don't know of anyone using the old FFS filesystem with OS4.

Your problem is more likely with the archiver used to create the archive or the program you used to extract the archive. There's also the possibility of a corrupted archive.

@xenic

I unintentionally formatted with old filesystem.

Now i realized....

Formatting...

thank you all for the help

@AmigaBlitter

Quote:

How did you manage that? "Long names" is ticked by default, I think, in both MediaToolbox and Format (and I believe you can still format with long names even if you selected the wrong FFS subtype in MediaToolbox, although I've never tried, the format req certainly allows for this possibility)

@AmigaBlitter

You will also get this problem with filenames longer than 107 characters (windows) the only way I found round the problem is to rename them is with filer.

@Severin

Windows has a different problem. If the entire filename and path is longer than 256 characters trouble ensues. You can get around it by renaming any directories it is in until the length is down enough.

@chris
My mistake. Don't know what i've done. I was sure convinced that FS was SFS2. I noticed only when some source file name were truncated.
107 chars will suffice, i guess.

@Chris

I meant files created on wundows and downloaded via the internet, I sometimes get filenames longer than 107 xharacters. filer is the only program I have found that will rename them so everything else can use them..

@Severin

Quote:

Programs that use the old FileInfoBlock based examine APIs have problems with file names longer than 107 characters.

Workbench uses FileInfoBlock structures internally for some things so that's probably why it has problems with longer file names.

@Severin
I was also able to rename a file to 120 characters with Dopus4 and then rename it back to a name with 10 characters. However, Dopus4 will only copy 107 characters. If the filename is longer than 107 chars, Dopus4 copy will truncate the name.

EDIT: I was also able to rename a file with 120 character filename to 10 characters with the C:Rename command. The problem is knowing the entire 120 character name to start with. Neither C:List or C:Dir will list more than 107 characters of the filename.

EDIT2: It appears that ram: is the only device that handles filenames greater than 107 characters. My SFS2 partitions seem to be limited to 107 characters (as listed in Raziel's chart).

@salass00
I did some testing and found that ram: is the only media device that handles filenames longer than 107 characters. I tested some AmigaDOS commands on files with 120 character filenames in ram: and the C:List & C:Dir commands will only display 107 characters of the 120 character filenames.

@xenic

Quote:

Not quite true on two levels.

1. The critical thing isn't the ram: device but the ram-handler file system.
2. There is at least one more that does ie env-handler and perhaps fuse based filesystems and one other....

command line tools do seeme to limited to 107 at the moment, eg RENAME COPY LIST etc though the shell will auto-complete the full file name and GETENV willl extract the varaible with full name length.

@xenic

Quote:

Neither rename nor copy wil work with over 107 files here

13.RAM Disk:> rename foo-1-1234567890-2-1234567890-3-1234567890-4-12345678890-5-1234567890-6-1234567890-7-1234567890-8-1234567890-9-1234567890-10-1234567890-11-1234567890-12 foo
RENAME: Can't rename "foo-1-1234567890-2-1234567890-3-1234567890-4-12345678890-5-1234567890-6-1234567890-7-1234567890-8-1234567890-9-1234567890-10-1234567890-11-1234567890-12" as "foo" because
RENAME: object not found
13.RAM Disk:> copy foo-1-1234567890-2-1234567890-3-1234567890-4-12345678890-5-1234567890-6-1234567890-7-1234567890-8-1234567890-9-1234567890-10-1234567890-11-1234567890-12 foo
Cannot open "foo-1-1234567890-2-1234567890-3-1234567890-4-12345678890-5-1234567890-6-1234567890-7-1234567890-8-123456789" for input - COPY: object not found
13.RAM Disk:> which rename
NGFSBoot:C/Rename
13.RAM Disk:> version rename
Rename 53.4
13.RAM Disk:>

The posix tools from the SDK can cope with arbitrary name lengths.

mv, cp etc