2021-01-03, 04:04
Hello All,
Recently took advantage of a 1tb cloud storage offer from ASUS WebStorage, with the intention of setting it up to use for media in KODI.
I thought it would be as simple as assigning the drive letter, using their RemoteDrive utility, and then setting up the sources in KODI, but, unfortunately, the drive letter I've assigned ( W: ) is not being seen by KODI. I've also tried O:, but with similar results.
I originally ran into a similar issue, after switching to Windows 10, where KODI was unable to see the drives mapped to my server (QNAP NAS), via "NET USE", or virtual drives, using the "SUBST" command, but corrected it with the following registry entry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLinkedConnections"=dword:00000001
So, that's not the problem this time.
Is there another limitation of which I am unaware that would prevent the drive from being seen? Does anyone have a suggestion of a work-around?
I did attempt to SUBST to the virtual drive, but the subst drive was not recognized by KODI either.
As an aside, I did manage to get the GoogleDrive addon setup using the STRM function, and it works great... but it's only 15gb, and I've got this whole TB sitting out there, not being used.
Thanks for any help or suggestions.
My best to you and yours in the coming year!
Recently took advantage of a 1tb cloud storage offer from ASUS WebStorage, with the intention of setting it up to use for media in KODI.
I thought it would be as simple as assigning the drive letter, using their RemoteDrive utility, and then setting up the sources in KODI, but, unfortunately, the drive letter I've assigned ( W: ) is not being seen by KODI. I've also tried O:, but with similar results.
I originally ran into a similar issue, after switching to Windows 10, where KODI was unable to see the drives mapped to my server (QNAP NAS), via "NET USE", or virtual drives, using the "SUBST" command, but corrected it with the following registry entry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLinkedConnections"=dword:00000001
So, that's not the problem this time.
Is there another limitation of which I am unaware that would prevent the drive from being seen? Does anyone have a suggestion of a work-around?
I did attempt to SUBST to the virtual drive, but the subst drive was not recognized by KODI either.
As an aside, I did manage to get the GoogleDrive addon setup using the STRM function, and it works great... but it's only 15gb, and I've got this whole TB sitting out there, not being used.
Thanks for any help or suggestions.
My best to you and yours in the coming year!