Closed GoogleCodeExporter closed 9 years ago
This is a known problem, we hope with the new path handling, witch is comming
up with
0.0.7, this will be history, feel free to test again when 0.0.7 is released.
This is rude, but please use a ftp client known to work with ftpii.
There is a list on http://www.wiibrew.org/wiki/Homebrew_apps/FTPii
Original comment by danieleh...@googlemail.com
on 23 Jun 2008 at 8:10
Hi James,
Thanks for the report. This is indeed the correct place to raise issues
regarding
client compatibility. The list at
http://www.wiibrew.org/wiki/Homebrew_apps/FTPii is
not regularly updated when new versions of ftpii are released, does not
generally
provide developers with enough information to be able to reproduce or fix a
problem,
and is usually just misleading. You are much better off using the issue tracker.
Clients "known not to work" with ftpii equate to bugs in our software (or very
buggy
clients...), and issues should be raised here.
Having said that, I see that the same problem you are having is also listed at
http://wiibrew.org/wiki/Homebrew_apps/FTPii, so either someone is having the
same
problem as you, or you added the problem there too ;-)
I have been developing almost solely using the OS X command-line ftp client,
and have
never seen the problem you describe. If there is a "client known to work with
ftpii", this is it. (Unfortunately, I am not sure how to figure out what
version of
ftp(1) I am actually using or I would post it here...all the usual suspects
like ftp
-v, ftp -h, ftp --version do not seem to work).
I assume this is the client you are referring to? Your step 2:
"2. Connect with Terminal (open IP)"
is slightly confusing, but I think you mean the Shell -> New Remote
Connection...
window (at least, that's how you get there in Leopard, or just type "ftp
ip.address"
in the Terminal...
I am interested to hear more about your issue. Perhaps Daniel knows something I
don't, but if this is a known problem I have no idea how to reproduce it.
What version(s) of ftpii have the problem?
Are you using SD-card or USB?
Is your filesystem FAT16 or FAT32?
What directory are you changing to?
What is the output of the "ls" command in the FTP client, in this directory?
What is the output of the "quote pwd" command in the FTP client?
What is the name and size of the file you are trying to upload?
(A copy/paste of the ftp session would answer most of these questions)
It is possible that the changes we have made to 0.0.7 (should be released in a
few
hours) will fix this problem by accident, please let us know!
Setting this to Priority-Low for now because there is not enough information to
investigate, and it Works For Me.
Ta,
Joe
Original comment by joe.goo...@psychlaw.com.au
on 23 Jun 2008 at 12:22
Furthermore, here is the output of your test case for me, using 0.0.6:
joe:ftpii joe$ ftp wii
Connected to wii.
220 ftpii
Name (wii:joe): foo
331 User name okay, need password.
Password:
230 User logged in, proceed.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd apps
250 CWD command successful.
ftp> put README.txt
local: README.txt remote: README.txt
502 Command not implemented.
227 Entering Passive Mode (192,168,1,3,4,0).
150 File status okay; reading data.
100%
|*******************************************************************************
**************************************************|
2581 133.35 KB/s 00:00 ETA
226 Closing data connection, transfer successful.
2581 bytes sent in 00:00 (4.56 KB/s)
ftp> del README.txt
250 File or directory removed.
ftp> bye
221 Service closing control connection.
joe:ftpii joe$
Original comment by joe.goo...@psychlaw.com.au
on 23 Jun 2008 at 12:57
Sorry. Before I posted that bug on the wiki, it said that Terminal DID work. I
was wondering if I was doing
something wrong. Glad to know it's not just me. Am now using Fetch 5.3 and it
works fine (added that to the
wiki too).
Your Q's:
Using FTPii 0.0.6, SD card,
I'm not sure but I think FAT16,
All directories,
It correctly displays the contents of all directories and furthermore is able
to make new ones using "mkdir"
It gives that error with all files I try to upload into any directory.
Will try and post a full log after work, depending on time. Mine is actually
different than joe's.
Original comment by James.W....@gmail.com
on 23 Jun 2008 at 2:53
Unable to reproduce. If there was an issue, it has likely been fixed since.
Original comment by joe.goo...@psychlaw.com.au
on 29 Jun 2008 at 8:43
Original comment by joe.goo...@psychlaw.com.au
on 25 Jul 2008 at 3:13
Original issue reported on code.google.com by
James.W....@gmail.com
on 22 Jun 2008 at 9:53