[quote=malkierian post_id=452814 time=1543444838 user_id=90301]
Thank you so much for getting this figured out.
[/quote]

Thank YOU so much for the patience. Your activity helped us to find a regression/issue in MM5 that we would hardly find otherwise (without YOU being involved) ;-)

Huzzah! We finally got it.

Don't see a need to have the log now that it's fixed, but here you go anyway.

https://www.dropbox.com/s/oidxlc61kts3vvq/LATIPENNATE6.LOG?dl=0

Thank you so much for getting this figured out.

OK, I finally got it and also have been able to simulate.

The 'N:\' is also name of the flash drive. And MM5 (unlike MM4) uses the name in cache path when caching the storageInfo.xml to the temporary directory. And because chars like ':' are not allowed in filename then the MTP error 8007007B appears while trying to transfer storageInfo.xml to the temporary directory.

I have fixed it and the new DLL is here again: https://www.dropbox.com/sh/1adyja3lz4o3pjx/AACq_fOAbsgZLMo-jvld4lqQa?dl=0

So please do one more test and attach debug log, this time it will read the storageInfo.xml and should recognize each flash drive as different profile finally.
Thanks!

Yes, that's what I'm saying. Those are plugged in the entire time. N:\ is where the flash drives are supposed to be (which is actually shown with the third device in your last code block; that's its drive letter, not its name).

And don't worry about it, I'm not particularly in a rush.

Nirvana, G:\, disk space: 8001427599360

Foolishness, L:\, disk space: 999500541952

00068889	82.06127930	[3452] WMDM: Is Inserted: Nirvana, 0:NA8X60V4!USB@\\?\swd#wpdbusenum#{7690a3cf-54b0-11e8-8f2b-d05099651649}#0000000008100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0, \\?\swd#wpdbusenum#{7690a3cf-54b0-11e8-8f2b-d05099651649}#0000000008100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0	
00068890	82.06250763	[3452] WMDM: Is Inserted: Foolishness, 0:WCAV55626674    !USB@\\?\swd#wpdbusenum#{214c543f-5b4c-11e8-8f31-5cf370712185}#0000000000100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0, \\?\swd#wpdbusenum#{214c543f-5b4c-11e8-8f31-5cf370712185}#0000000000100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0	
00068891	82.06443024	[3452] WMDM: Is Inserted: N:\, 0: :\\?\SWD#WPDBUSENUM#{c0b104ac-e93a-11e8-8ca1-5cf370712185}#0000000000000000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0!USB@\\?\SWD#WPDBUSENUM#{c0b104ac-e93a-11e8-8ca1-5cf370712185}#0000000000000000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0, \\?\SWD#WPDBUSENUM#{c0b104ac-e93a-11e8-8ca1-5cf370712185}#0000000000000000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0

Are you saying that
[code]Nirvana, G:\, disk space: 8001427599360[/code]
and
[code]Foolishness, L:\, disk space: 999500541952[/code]
are not the discs that you inserted into N:\ ?

BTW: later in the log I see actually three devices inserted:
[code]
00068889 82.06127930 [3452] WMDM: Is Inserted: Nirvana, 0:NA8X60V4!USB@\\?\swd#wpdbusenum#{7690a3cf-54b0-11e8-8f2b-d05099651649}#0000000008100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0, \\?\swd#wpdbusenum#{7690a3cf-54b0-11e8-8f2b-d05099651649}#0000000008100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
00068890 82.06250763 [3452] WMDM: Is Inserted: Foolishness, 0:WCAV55626674 !USB@\\?\swd#wpdbusenum#{214c543f-5b4c-11e8-8f31-5cf370712185}#0000000000100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0, \\?\swd#wpdbusenum#{214c543f-5b4c-11e8-8f31-5cf370712185}#0000000000100000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
00068891 82.06443024 [3452] WMDM: Is Inserted: N:\, 0: :\\?\SWD#WPDBUSENUM#{c0b104ac-e93a-11e8-8ca1-5cf370712185}#0000000000000000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0!USB@\\?\SWD#WPDBUSENUM#{c0b104ac-e93a-11e8-8ca1-5cf370712185}#0000000000000000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0, \\?\SWD#WPDBUSENUM#{c0b104ac-e93a-11e8-8ca1-5cf370712185}#0000000000000000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
[/code]
but none gets drive letter and there is MTP error 8007007B when reading the storageInfo.xml

FYI: I haven't had time (because of other issues) to look into it today, but going to test this on Windows 10 + external HDDs tomorrow to understand what is going on and to try to find a better way how to pair external HDD recognized as MTP(WMDM) device with its drive letter.

By the way, I just wanted to make it clear, Foolishness (G:) and Nirvana (L:) are not the two flash drives I've been using to test this out, they're unrelated. N: is the drive letter assigned to them as I swapped them out with each other.

Would the failure to read from the two hard drives affect the recognition of a different drive?

Hmm, I can confirm that based on the log MM has still trouble to read the storageInfo.xml from your HDDs -- Foolishness (L:\), Nirvana (G:\)
I re-opened #14982, I need to rework something and will get back here with new stuff later...

Nope, it's still recognizing each drive as the previously set device. It looks like it's reading storageinfo.xml now, but it's still not associating the info from the that file with what it displays. Maybe it's not that the process is bad, but that it's not updating the display variables properly? I tried watching in the log, but I couldn't figure out exactly where it was loading the info.

https://www.dropbox.com/s/6mxxotgmk4x32bt/LATIPENNATE4.LOG?dl=0

It is fixed with this d_WMDM.dll : https://www.dropbox.com/sh/1adyja3lz4o3pjx/AACq_fOAbsgZLMo-jvld4lqQa?dl=0
Could you please do one more test with the DLL and confirm the fix + generate new log (just to be sure that it is working correctly finally) ?

Thanks!

Thanks for the log,
I finally understand the difference, I have been testing with SD cards and flash disc that gets drive letter directly in d_WMDM.dll plugin, but you have been testing with external HDDs that are (starting from Windows 10) recognized as MTP devices by d_WMDM.dll without drive letter - and I supply the drive letter externally in the course of https://www.ventismedia.com/mantis/view.php?id=14982 - item 2c
But found that for the storageInfo.xml reading the MTP protocol is still used -- and it gets error 8007007B on your PC
The solution is to _always_ use the drive letter for any file access.

So I re-opened https://www.ventismedia.com/mantis/view.php?id=14982 to fix it as 2c properly

Here you go.

https://www.dropbox.com/s/mplplwgws6czi6u/LATIPENNATE.LOG?dl=0

Hi,
thanks for the new log.

In the log I see that MM was trying to read the storageInfo.xml from the device, but got an error while trying to read it.
But the log is missing some debug lines to see the exact error number, this mostly happens when DbgView is started after MM start,
could you please generate one more log using this d_WMDM.dll (I uploaded new) : https://www.dropbox.com/sh/1adyja3lz4o3pjx/AACq_fOAbsgZLMo-jvld4lqQa?dl=0
but be sure that DbgView is started prior to MM?

Thanks!

Alright, that driver made it start writing the storageinfo.xml file again, but it's still not recognizing and using the ID. I plugged in one of the drives, named it "First", hit apply, unplugged it, plugged in the other one, named it "Second", hit apply, unplugged it, plugged in "First" again, and MM said "Second" was plugged in.

Here's the log for that process:
https://www.dropbox.com/s/d6el3tt2yewpsup/LATIPENNATE.LOG?dl=0

Even when plugging in "Second", before modifying the settings, MM assumed it was "First", so there should be two instances of mis-identification in that log.

Hi, thx, I can confirm (based on the log) that the storageInfo.xml really wasn't written to your devices.

Could you please replace your current /plugins/d_WMDM.dll by this d_WMDM.dll : https://www.dropbox.com/sh/1adyja3lz4o3pjx/AACq_fOAbsgZLMo-jvld4lqQa?dl=0
and try whether it fixes the issue + generate one more debug log ?

Thanks!