Topic: I Found At Least 1 Of The 3921 Ftp Problems... (Read 22 times)

moonface · « **on:** November 28, 2003, 04:38:00 PM »

Scratch that - dashes are OK, the following characters are not:

!
(
)
[
]

Also, any file name with more than 40 characters, including spaces will fail to upload. This does NOT include the file extension.

Large Dopant white · « **Reply #1 on:** November 28, 2003, 05:03:00 PM »

Yeah, 3921 has been buggy FTP wise for a long time. It's amazing that, for the multitude of times that it has been mentioned, it hasn't been pinned. I can personally attest to the fact that the FTP is broken regardless of client and OS (FlashFXP, WS FTP, CuteFTP, etc... on the OS side, a bunch of *nix distros, Windows 98/ME/XP, and OS 9 & X... all I have tested, and all fail). I've had to tell many users about the bug, as it's practically unknown. Strange, indeed.

heinrich · « **Reply #2 on:** November 29, 2003, 12:18:00 AM »

QUOTE

Maximum File Length: 42 Characters

The following characters are permitted:
   ! # $ % & ' ( ) - . @ [ ] ^ _ ` { } ~
   Numerals 0 through 9
   Upper and lower-case letters A through Z

The following characters cannot be used:
   < > = ? : ; " * + , / |
   Characters values 0 through 31 and 128 through 255.

Filenames are not case sensitive. XBOX, Xbox, and xbox are all the same.

mrRobinson · « **Reply #3 on:** November 29, 2003, 04:26:00 AM »

and just to be clear, those things heinrich mentions are NOT bugs with evox ftp they are limitations of the filesystem the xbox uses.

Serious Sam · « **Reply #4 on:** November 29, 2003, 04:39:00 AM »

Yep those are Xbox limitations not dashboard. I've been using Evox 3921 with no issues at all

Large Dopant white · « **Reply #5 on:** November 29, 2003, 09:07:00 AM »

Yes, I've read the pinned topics. I'm aware of the filename limitation. However, 3921 will fail to transfer files that even have a valid filename. Try it out sometime, and I assure you that you'll run into the same problems- directories failing to list, files failing to transfer completely or at all, etc.

heinrich · « **Reply #6 on:** November 29, 2003, 09:55:00 AM »

moonface · « **Reply #7 on:** November 29, 2003, 08:03:00 PM »

QUOTE (mrRobinson @ Nov 29 2003, 02:26 PM)

and just to be clear, those things heinrich mentions are NOT bugs with evox ftp they are limitations of the filesystem the xbox uses.

mrRobinson,

Thanks for the reply. I understand how a file system's structure influences what characters are legal and illegal in a filename. But, all of the characters that I mention having problems with are supposed to be legal characters in the xbox FS. As such, I do believe there might be a bug 3921. Not necessarily with the FTP server.

bakin1 · « **Reply #8 on:** November 29, 2003, 08:19:00 PM »

I tried using xtoolbox after upgrading to 3921 and it didnt work at all. I could connect fine, but other then that, nothing worked right, and it wouldn't transfer at all. switched back to3752 and everything works again.

heinrich · « **Reply #9 on:** November 30, 2003, 02:00:00 AM »

QUOTE (moonface @ Nov 29 2003, 11:52 PM)

Read my posts heinrich....EVERY SINGLE character that said was not transfering are LEGAL according to your quote. Please believe that I absolutely know what I am doing. I have been mod-ing consoles for 10 years and working as a network engineer for 12. I always read everything very carefully and I know FTP in my sleep.

QUOTE

File Name Conventions
The FATX file system used for the console hard disk supports file names up to 42 characters long. The UDFX file system used for the DVD player supports file names up to 255 characters long (also known as "long" file names).

Although each file system can have specific rules about the formation of individual components in a directory or file name, file systems on the Xbox follow some common general conventions.

Both file systems use the backslash (\) character to separate directory names and the file name when forming a path.

General rules for applications creating names for directories and files or processing names supplied by the user include the following:

In general, use only printable characters in a file name. Do not use a path separator, a character in the range 0 through 31, or any character explicitly disallowed by the file system. A specific file system may allow only a certain set of characters in a file name. The FATX file system used for the console hard disk supports the following characters in file names:
! # $ % & ' ( ) - . @ [ ] ^ _ ` { } ~
Numerals 0 through 9
Uppercase and lowercase letters A through Z
Use the backslash (\) to separate components in a path. No other character is acceptable as a path separator.
UNC names are not supported. UNC names are of the form \\server\share.
Neither the use of a period (.) as a directory component in a path to represent the current directory, nor two consecutive periods (..) to represent the parent of the current directory, are supported.
Use a period (.) to separate the base file name from the extension in a directory name or file name.
Do not use the following characters in directory names or file names, because they are reserved:
< > = ? : ; " * + , / \ |

Do not use characters values 128 through 255.
All paths must be specified as fully-qualified path names beginning at the root of a drive and including the drive letter, directories, and file name. For example, "Z:\ai\search.ait". There are no current directory or current drive defaults.
Process a path as a null-terminated string. The maximum length for a FATX full path (directories and file name), including a trailing backslash, is given by MAX_PATH. A UDFX full path can be greater than MAX_PATH, but each component (directory or file name) will be MAX_PATH characters or less.
Do not assume case sensitivity. Consider names such as OSCAR, Oscar, and oscar to be the same.
By following the rules listed in this section, an application can create valid names for files and directories regardless of the file system in use.

Backslashes (\) are used as element dividers in paths (dividing the file name from the path to it, or directories from one another in a path). You cannot use them in file or directory names. They may be required as part of volume names (for example, "T:\").

No one is doubting your experience or intelligence, but when you make statements like "some files would fail, while others do not. It seems to be based on certain characters in the file names." Yes, we all know this, and we know what the characters are.

dapht_punk · « **Reply #10 on:** November 30, 2003, 07:49:00 PM »

). And it shows you what it will rename it too so it is FATX compliant.

Author Topic: I Found At Least 1 Of The 3921 Ftp Problems... (Read 22 times)