Arlen Holder <
a%rlenh...@no.spam.net>
news:pq9v6c$ja9$
1...@news.mixmin.net Thu, 18 Oct 2018 12:43:57 GMT in
alt.comp.freeware, wrote:
> On Thu, 18 Oct 2018 10:46:25 +0100, p-0''0-h the cat (coder)
> wrote:
>
>> I think Dusty is talking about subst and net use. Neither of
>> which work with MTP.
>
> The good news, for freeware aficionados, is that we know the
> payware exists, which implies that freeware "could" exist.
NET use wasn't an original real DOS command. [g] But, I do find their
efforts to con me into giving it up just to prove I know about it and
for them to claim they did the whole time too, but were 'just
testing' me, isn't going to work this time around. And, they won't
make a sufficient distraction for you, either.
As you could see, of all the things I wrote and specific examples I
gave previously, disputing everything you wrote about rooting,
android version limitations, etc, pooh was silent on all of it. It's
above his paygrade. and, evidently, by your own thoughtful posts,
rofl, yours as well. He's taking a guess as to the command(s) I
hinted around about you using. Only, he didn't bother to double check
himself with the second one. Too much time being spoiled by network
aware editions of windows perhaps? :) Not much actual time with non
point and click OSes and network configuration.. rofl.
> We also know it works just fine on Linux (which uses libtmp, I
> think).
Ehm. Some of us know that later editions of Android, say, 5.1.1 work
just fine, without having to be rooted for internal and external
memory access; yes. So long as you're using a kernel that's okay with
it. if you aren't, it won't properly mount either internal or
external memory. Covered that in a previous reply, though. Another
example disputing your universal Android claim.
> If we can find a freeware solution, we'll have moved our tribal
> knowledge forward appreciably.
WHo's "we"? As I've told you before, some of us (except for pooh
rofl; he's always been a poseur though, so I'm not surprised) already
know what we're doing and don't require moving our ehm, tribal
knowledge anywhere. You certainly aren't moving our knowledge forward
when you post inaccurate information as you've done previously in
this thread.
Some examples of your inaccurate information:
You are correct that there are mixed results in the real world.
1. If you have _old_ Android (<4.3), you _can_ use "mass storage"
usb.
<
https://android.stackexchange.com/questions/190138/how-to-use-
usb-mass-storage-mode-on-android-4-3>
5. Everything that seems to work over usb, is _old_ or _rooted_.
<
https://www.google.com/search?
&q=android+windows+usb+mass+storage+mode+mount+drive+letter>
> I think there is a solution in "libtmp" but I don't know enough to
> make that solution work on Windows as I don't know what to do with
> libtmp.
Going by your own previous posts, it's evident that you don't know a
quarter of what people you've referred to as morons, amongst other
things, knows...
Someone who's used computers for as long as you've previously claimed
to have (20 years or more, right?), you have that newbie stench about
you. The condescending attitude doesn't really help you here, either.
If you want genuine discussion on freeware (that would be nice,
actually), lose the holier than thou I know more than you do, you're
a moron, etc, attitude you have with myself and other posters. Then,
perhaps several? of us can participate in a discussion that's
beneficial. Most likely wishful thinking on my part, but, I digress.
It's quite possible to pull off.
> On Linux, running commands on MTP "just works", where Linux seems
> to be using libtmp as the underlying code. So naturally, I tried
> the Windows libtmp port:
> <
https://sourceforge.net/projects/libmtp/>
Uhm...You need to learn to be specific when you mention linux and
what it does/doesn't use. Linux is the kernel. It's *NOT* the distro
with the pretty eye candy and a pile of apps, preinstalled ready to
run.
> But I don't have the knowledge required to figure out the steps to
> make it work to mount an Android MTP filesystem over USB as a
> drive letter.
I do. As do several other people. Infact, I know several different
ways of doing it. And so far, they ALL seem to allude you.
Serious question... Are you the same guy who was having trouble
printing various types of signs over the summer using a specific
font?
> This is the Windows libtmp port. But I don't know what to do with
> it.
libmtp...
You need to know more about libmtp and what it's actually for..,
here's a few educational urls about it:
https://github.com/mmalecki/libmtp
Pay close attention to the FAQ a ways down the page. It goes into
some detail (provides an example or two infact) of various Android
devices that do exactly what I told you from the get go they'd do;
not play nicely and follow the damn established rules.
> <
https://iweb.dl.sourceforge.net/project/libmtp/libmtp-win32/0.3.5
> -win32-1/libmtp-0.3.5-win32-bin.zip>
Not complete as is. inside is a spiffy file called
README.windows.txt... inside this file are the following nifty words
(educational value they be):
Libraries:
LibMTP currently depends on LibUSB and libiconv. There are currently
projects that port both of these libraries to Windows. Binary files
can be obtained from:
LibUSB Win32 -
http://libusb-win32.sourceforge.net/
LibIconv -
http://gnuwin32.sourceforge.net/packages/libiconv.htm
Also a note you might want to pay close attention to...:
2.0 LibUSB and Driver Issues for Windows
----------------------------------------------
Unfortunately, Windows does not have abstract USB support and depends
upon specific drivers for each and every device you use. Fortunately,
LibUSB-Win32 provide a solution to this problem. LibMTP takes
advantage of the LibUSB-Win32 Device Driver package.
1. Download the latest device driver binary package (libusb-win32-
device-bin-x.x.x.x.tar.gz) from
http://sourceforge.net/project/showfiles.php?group_id=78138
2. Upon extraction, plug in your music device and run bin/inf-
wizard.exe. Selecting your device and saving the inf file in the
project root directory.
3. Copy the files "bin/libusb0.dll" and "libusb0.sys" or "libusb0
_x64.dll" and "libusb0_x64.sys" for 32-bit or 64-bit operating
systems respectively.
4. Goto Start -> Run, type "devmgmt.msc" and press "ok".
5. Select your music device from the list and click Action -> Update
Driver, Choose "No, not this time" if prompted to connect to
microsoft.
6. Choose "Install from a list or specific location".
7. Choose "Don't search, I will choose the driver to install
8. Click the "Have Disk..." button in the bottom right corner of the
prompt
9. Browse to your .inf file and select it. Press Ok
10. The name of your music device should appear in the prompt, click
it and click "Next>" (Ignore any prompts about Driver Signing,
continuing
installation of the selected driver).
11. Click finish to end the driver install process.
To get your old driver back:
1. Goto Start -> Run, type "devmgmt.msc" and press "ok".
2. Select your music device, right click on it and click "Properties"
3. Go to the "Driver" pane and select "Roll Back Driver".
You've been missing a few steps and software packages, Arlen.
Oh, btw, before you go through all that hassle expecting a universal
method of accessing ANY android device in the manner in which you'd
like, don't waste your time. It WILL NOT presently, happen. It's
*NOT* universal. It will NOT work with all Android devices. Various
people, including myself, have tried to tell you this on several
occasions. You refused to listen to us, you incorrectly thought you
knew better than any of the rest of us who wasted time responding to
you.
Incidently.. I forgot (completely) to mention yet another option you
have for a single workstation scenario. I notice pooh didn't mention
it either. alas. Anyways, you use a vm and appropriate OS that's your
android device friendly. Set appropriate permissions and
configuration options for the vm to be able to interact with the
'real' network outside of it and 'share' the memory
(internal/external) as you see fit. I didn't provide step by step
instructions Arlen. I know better, but, I'm assuming you aren't as
much of a newbie as I suspect you to be. :)
A newbie would need his/her hand held for each step. I'd have to
detail every single step and make sure I didn't accidently leave
something out. I'm going to assume (again, bad idea on my part; I
know better than to do this with you) that you understand what I mean
by vm, know how to select the appropriate guest os and make the
necessary configuration changes to the guest os and vm software to
grant it required permissions.
OTH, If you'd like to concede in front of the audience that you don't
know nearly as much as you thought you did and apologize for your
erroneous moron comments to myself as well as others involved in a
previous thread, and, I'll do you a solid and hold your hand on this.
I'm going to gloat quite a bit as I do so, but, I'll do that if
you're willing to admit, and swallow some pride in front of us all.
So, what say you Arlen? Have you had enough getting your technical
arse kicked? It didn't take any real effort on my part. years of
first hand experience did the 'real work' for me. I knew you were
wrong from the first post on the subject of Android. In actuality,
Android devices have little in common with one another. And, you
can't even get sound/reliable information on them, based on the urls
you've shared previously, boldly (yet, incorrectly) making the
following claims:
1. If you have _old_ Android (<4.3), you _can_ use "mass storage"
usb.
<
https://android.stackexchange.com/questions/190138/how-to-use-
usb-mass-storage-mode-on-android-4-3>
5. Everything that seems to work over usb, is _old_ or _rooted_.
<
https://www.google.com/search?
&q=android+windows+usb+mass+storage+mode+mount+drive+letter>
Either those urls really provide that totally bullshit information (I
haven't checked any of them), or, you misunderstood what you were
reading.I told you when you brought up the entire Android file
sliding nonsense that it wasn't universal - Differences do exist in
Android versions, Windows versions, linux (kernel and support
applications depending on distro you go with), etc. It's NOT
universal. One size won't fit all.
I previously mentioned XP not properly mounting some versions of
Android while properly accessing other Android devices. I also wrote
about a particular linux distro I use that does the same thing as
well as another distro that's okay with the devices the XP and other
distro machines aren't. You'll run into this issue with Windows 7, 8,
even Windows 10. It's more about the Android device than it is the OS
you're using. Like I told you, several times now, they don't all play
the same, they don't all follow the so called comms rules to chat
and/or properly enable MTP.
You can't tell me that Windows 10 isn't relevant today, it's the
latest (before MS switches you loyal suckers, i mean, customers over
to subscription and bring back the so called dumb terminals). It's
already happening, and suckers, er, I mean loyal customers are
lapping it up and asking for more. A couple of abilities of cloud
computing; offsite data storage. offsite data processing, etc. the
dumb terminal is making a comeback! And it's going to make a lovely
cash cow for some companies.
I salivate at the sight of mittens.