Notifications
Clear all

Flashair: Mounting root directory in Windows 10  

  RSS
jweaver
(@jweaver)
Honorable Member
Flashair: Mounting root directory in Windows 10

I had my Flashair working nicely in Windows 7.. I just mapped \\192.168.1.120 as a network drive and could see it like a hard-drive.

I have just changed the computer and started with a fresh build of Windows10 and I can no longer mount the card.

What I have found is that I can mount directories on the card, for example \\192.168.1.20\gcode.

Its no big deal as I can just move everything down one folder and mount that.. I assume this is a Windows thing and there is a change between Win7 and Win10.. But I am curious to understand why in Win7 I can mount my card using \\192.168.1.120 and in Win10 I have to address a folder (\\192.168.1.120\<folder>)

 

Does anyone have any windows knowledge that can explain this?

Jon

Napsal : 30/04/2020 2:43 pm
Area51
(@area51)
Member
RE: Flashair: Mounting root directory in Windows 10

Have you tried running: \\192.168.1.120\DavWWWRoot ?

It works my Windows 10 x64.

Have a look at my models on Printables.com 😉

Napsal : 30/04/2020 4:58 pm
jweaver
(@jweaver)
Honorable Member
Topic starter answered:
RE: Flashair: Mounting root directory in Windows 10
Posted by: @area51

Have you tried running: \\192.168.1.120\DavWWWRoot ?

It works my Windows 10 x64.

That worked.. I am 99% sure that I used to just mount \\192.168.1.120 on Win7, but I could be wrong.

But it doesn't matter.. That fixed it... Thanks for the tip..

Napsal : 30/04/2020 5:08 pm
Area51
(@area51)
Member
RE: Flashair: Mounting root directory in Windows 10

I did struggle with it too when using Windows. As I remember it \\192.168.1.120 worked in the explorer, but a shortcut needed the full path \\192.168.1.120\DavWWWRoot to work.

Have a look at my models on Printables.com 😉

Napsal : 30/04/2020 9:36 pm
jweaver
(@jweaver)
Honorable Member
Topic starter answered:
RE: Flashair: Mounting root directory in Windows 10
Posted by: @area51

I did struggle with it too when using Windows. As I remember it \\192.168.1.120 worked in the explorer, but a shortcut needed the full path \\192.168.1.120\DavWWWRoot to work.

It is very odd.. On my old PC (Win7), I just have \\192.168.1.120 mounted.. But on Win10, I have to mount of fold (or use your DavWWWRoot workaround)...

But its such a non-issue.. Its working now, and thats all that matters, so I am happy.

Thanks again for your help

Jon

 

Napsal : 30/04/2020 10:30 pm
Share: