English Amiga Board


Go Back   English Amiga Board > Support > support.WinUAE

 
 
Thread Tools
Old 24 January 2013, 15:35   #1
mark_k
Registered User
 
Join Date: Aug 2004
Location:
Posts: 3,203
Unusual characters in filenames and shared folders

I was experimenting with creating files with unusual characters in their names, and seeing how those characters map to the filenames WinUAE creates in the host shared folder. (Some characters are shown differently, I'll post about that later.)

There are some issues with the º character (hex $BA). I can't reproduce that character properly typing here, but it looks like a superscript o with an underline below it. Pressing Alt-B with the Amiga GB keymap types it. Whether or not that character is legal in filenames varies:
  • Kickstart 1.x ROM filesystem: illegal
  • Kickstart 1.x RAM-handler: illegal
  • Kickstart 2.x, 3.x ROM filesystem: illegal
  • Kickstart 2.x, 3.x RAM handler: legal
  • FFS 40.1 (probably all earlier versions too): illegal
  • FFS 45.13: legal
  • WinUAE shared folder: legal
If you try to copy a file with that character in its name to an FFS pre-v45 partition or RAM: under Kickstart 1.x you'll get an error 210, object name invalid. Because of that it might be a good idea to make the º character illegal for WinUAE shared folders. Or at least, disallow creation of files with that character. (On the other hand, maybe those characters are supposed to be legal but were incorrectly rejected by the 1.x RAM-handler and earlier FFS versions?)

The same issue seems to apply to the ¯ character (hex $AF, Shift-Alt-N in the GB keymap).

Last edited by mark_k; 24 January 2013 at 16:59.
mark_k is offline  
Old 24 January 2013, 17:26   #2
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 46
Posts: 24,999
Because this is AmigaOS filesystem specific limit, not AmigaDOS limit, I don't see any reason for restrictions. Different filesystems can have different limits.
Toni Wilen is offline  
Old 29 January 2013, 15:20   #3
mark_k
Registered User
 
Join Date: Aug 2004
Location:
Posts: 3,203
That makes sense.

I wonder why only $AF and $BA are not allowed. Hopefully I'll get around to looking at the FFS code to see why some time.
mark_k is offline  
Old 03 February 2013, 19:50   #4
mark_k
Registered User
 
Join Date: Aug 2004
Location:
Posts: 3,203
If anyone's interested in checking how various Kickstart and/or filesystem versions handle filenames with those characters in, here's a test ADF. I created it using a 901120-byte HDF with FFS 45.13 in WinUAE. The ROM filesystem 40.1 won't allow files with those characters in their names to be created, but you can open and write to existing files.
Attached Files
File Type: 7z StrangeNameTest.adf.7z (979 Bytes, 121 views)
mark_k is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
File timestamps lose precision in shared folders mark_k support.WinUAE 9 06 February 2013 16:25
File comments and shared folders mark_k support.WinUAE 2 06 December 2012 10:15
Bug: Filenames containing national characters in Windows Directories arnljot support.WinUAE 17 17 December 2009 12:19
How do i Get Miami to mount shared folders Rogueraven support.Hardware 6 13 March 2008 11:57
CD rom with unusual interface Magno Boots support.Hardware 9 25 August 2007 22:01

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 15:22.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.
Page generated in 0.09048 seconds with 14 queries