On 19 Oct 2018 13:46:48 GMT, Frank Slootweg wrote:
Moral: It seems from these threads that Windows 10 users get each and
every problem they deserve! :-) I.e. everything works fine on older
Windows versions or/and with older versions of the tools, but not with
the latest-and-(not-)greatest! :-)
Hi Frank,
Here is my detailed response to your purposefully helpful FTP suggestions.
Thanks for the FTPUse suggestions, where, as I recall, it used to work for
me but no longer does - but - I'm not too worried for two reasons:
a. I found a method that did work for me with FTP over Wi-Fi, and,
b. Even if I hadn't found that method that worked, USB is the main goal.
For this post, we aren't discussing USB.
For this post, we're only discussing WiFi.
And, for this post, we're not discussing any other server other than FTP.
(For example, we're not discussing WebDAV, which always worked just fine.)
What we want, for this post, is a *drive letter*.
We never had problems with a "network location".
What else, we want for this post, is a *universal solution*.
That means anyone can do it (not just you and me, Frank).
In general, that means freeware.
I think we have that solution below using DND freeware.
o DirectNet-Drive created a drive letter of a WiFi FTP network location
But I acknowledge that _other_ freeware should have worked for me.
o FTPUse should have worked (and I think it did work, in the past, for me)
https://www.ferrobackup.com/download/FtpUseInst.exe
o SFTP Net Drive should have worked (but it also failed for me)
https://www.nsoftware.com/sftp/netdrive/ (it took a bogus name & email)
What worked for me the very first time, was this combination:
1. Android freeware FTP Server:
https://play.google.com/store/apps/details?id=com.theolivetree.ftpserver
2. Windows freeware map of "network location" to a "removable drive":
http://www.directnet-drive.net/
Here is a screenshot of the FTP WiFi connection as a drive letter (R
http://www.bild.me/bild.php?file=4731516dir011.jpg
And here is a screenshot showing that I can run DOS commands on Android:
http://www.bild.me/bild.php?file=6340420dir012.jpg
Where both those connections are made using the Olive Tree FTP server
on my Windows 10 desktop connected to Android 7.0 Nougat.
For whatever reasons, on my Windows 10 system, FTPUse failed under exactly
the same circumstances (both as a password user & as anonymous):
FTPUse failing with the "Olive Tree" FTP server as user "francis":
http://www.bild.me/bild.php?file=7355568dir09.jpg
FTPUse failing under the same FTP server as user "anonymous":
http://www.bild.me/bild.php?file=4223201dir010.jpg
As you know, FTPUse also failed when I used F-Droid "FTP Server (Free)":
https://f-droid.org/en/packages/be.ppareit.swiftp_free/
Where these screenshots are from a few days ago when I ran those tests:
http://www.bild.me/bild.php?file=7687244dir06.jpg
http://www.bild.me/bild.php?file=7075400dir07.jpg
http://www.bild.me/bild.php?file=3316456dir08.jpg
SFTPNetDrive freeware also failed today with the "Olive Tree" server where
SFTP NetDrive simply failed to connect whether using user "francis" or
"anonymous".
In summary, I was never worried about FTPUse not working on Windows 10 for
me since I prefer USB and since I found (by trial and error) an WiFi FTP
solution that works as a general freeware solution for everyone, which is
"DirectNet-Drive".
If we still wish to move the ball forward, we should ask another Windows 10
user to see if FTPUse or SFTP NetDrive works for _them_.
All I can tell people here is that my empirical results are the following:
o Using multiple FTP servers on non-root Android 7.0 Nougat...
o DirectNetDrive Windows 10 network-location-to-drive-letter worked!
o But both FTPUse & SFTP NetDrive failed (under the same conditions).
Why?
I don't know why.
If another Windows 10 user can test either of those two failed solutions,
we will get a better idea if it's Windows 10, or if it's just me.
--
As always, the Usenet goal is for all to help everyone with their efforts.