Be aware that if you are using Windows 10 Fall update you must type the path in the address into the file explorer address bar. Like \\192.168.1.87.
For reasons I don't understand I don't have to type the url on one of my updated Windows machines.
However, there should be no need to share any files that are not included in the default samba. You can get to the config files and userdata with it.
It appears the spelling without the "e" is favoured by US English, which may explain the dual support.
I don't know about that; I am US never seen it without the e. Maybe it is "acceptable" because we tend to accept illiteracy.
I just found this today in libreelec 8.2.2 RPi.arm the samba.conf.example has typos that prevent it from working.
browseable and writeable are missing the "e". So if you follow directions and edit it to be /storage/.config/samba.conf samba will not work unless you add those "e"s.
One thing that keeps being forgotten is that in windows file explorer you must type "\\libreelec" or whatever your url is into the address bar. Then as if by magic ........
LibreELEC 8.2.2 RPi.arm
Are "browsable" and "writable" misspelled on purpose in the samba.conf.sample? Every other system I've seen has the missing e.
Is that why I can't seem to get it to work, I do understand the new samba 3/4 thing, that has been learned on the other RPi running Raspbian.
I do know that you must type the url into the windows file explorer like this "\\libreelec" or "\\192.168.1.xxx" to make it show on the network browser.
AhHa! yes, that is the problem. Hope this helps everyone trying to make it work!
I bet it has something to do with the way 8.2 does lirc.
Add the source by typing the network path then provide user name and password. Samba browser is gone in the new version.
That is in the release notes.
You can't browse the windows network anymore. You have to add the source by typing the path then adding user and password. After that you can browse in the source i.e,: //192.168.0.1/News if you try to browse the windows network you can only get to //windows network/.., where you used get to //windows network/workgroup/News.
On further review; it seems to have suddenly started working. The only thing I did was load the cfg file into notepad++ and re save it.
Here are the oddities:
I had a USB vista MCE remote plugged in and both worked, contrary to the wiki.
Both remotes work whether lirc is turned on or not, contrary to the wiki.
It is good when things fix themselves just from pulling your hare out. This is the second thing to do it on this try with LE.
The word that describes what grows out the top of your head is censored!!!!!?
Did you triple check the caps in the paths?
That is an entirely different question. Mine did that, then suddenly they popped up in file explorer when I was starting to search here. I think it has something to do with which machine gets elected master. Try rebooting everything in a different order.
I don't know why you would try to disable samba 1, the creator update did that.
I have a pi 1B with a gpio IR receiver. I just deciphered the wiki notes.
Added the dtoverlay=gpio-ir line to config.txt, enabled lirc in LE settings, added "** hauppauge" to a new file /storage/.config/rc_maps.cfg.
My problem is that is not permanent. I have to do
ir-keytable -a /storage/.config/rc_maps.cfgevery reboot.
Any idea what the problem is?
If I understood blueribb's plight correctly you did not want to password protect your admin account because you wanted to reboot Windows without having to enter a password?
That is solved by netplwiz and having just one (admin) account.
Linux people are obsessed with accounts and passwords for security, they don't understand that most home users don't care about security; Windows has ways to get around that stuff, for now.
You described the samba wizard in post #27.
That is the part about typing the path then entering the user and password in sources.
What is confusing is they still include the "browse" option that does not work anymore. I guess they could modify that to "type the network address here, they follow the directions".
I had to read this thread and your post #27 to understand it, but it is easy.
That is not the suggestion.
The new Windows samba does not allow BROWSING to the path, so you have to type the actual path.
You used to be able to browse the windows network to find the path. Now you can't get farther than smb//windows network/...
The solution is to type the path and add your credential.
In my case; all of my shares are owned by the admin account and they are shared to "everyone". The account must have a password.
In windows 10 you don't have to login in at every boot; if you run>netplwiz uncheck the "users must enter name an password" box, if you have more than one account you can add them in the box; click save. done.
I am the only one in my house with access to the computers so I try to disable as much security as I can.
A very easy solution is to install Plex server on you windows server machine, then you can share via UpnP automagically. Add the Plex app to Kodi and it takes a step away.
That's what I've been doing until I get around to fixing samba.
VNC is your easier bet. It works fine for me on my Windows 10 machine, if I ever wanted to do it,
I don't know why I would. WinSCP/PuTTY works fine for transferring and editing files remotely.
Ever heard of "routine site maintenance"?
And the Buffalo Bills traded their entire team and all of their draft picks for the next 5 years for Tom Brady! They have decided to go the 1 man team route and save lots of money.