SMB v2 support
-
@substring what I need is to load the roms from my PC shares, so in this case the problem is with the recalbox smb client
-
@shira then please read the wiki, this has absolutely nothing to do with the protocol version
-
@substring it does, if my pc or nas has v1 removed then we need recalbox to be able to access smb v2 shares
-
# mount.cifs //192.168.0.2/RecalboxRoms /recalbox/share/roms -o username=roms,password=roms
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) -
@substring got it working, we simply have to add "vers=2.0" (or 2.1 / 3.0 /3.02) to the mount commands, i.e:
sharenetwork_smb1=ROMS@192.168.0.2:RecalboxRoms:username=roms,password=roms,vers=2.0
sharenetwork_smb2=SAVES@192.168.0.2:RecalboxSaves:username=roms,password=roms,vers=2.01.0: Win 2k/XP/Server 2003/Server 2003 R2
2.0: Vista SP1/Server 2008
2.1: Win7/Server 2008 R2
3.0: Win8/Server 2012 (w10?)
3.02: Win8.1/Server2012 (w10?) -
Edited the Wiki with these instructions:
https://github.com/recalbox/recalbox-os/wiki/Load-your-roms-from-a-network-shared-folder-(EN)
-
for KODI SMB2+: SMB v2 on KODI
-
@shira great job !
Still, it's a shame it can't properly "autodetect" the protocol version -
@shira Do you use Windows10? Does dosbox work with shared folder from Windows 10?
-
@toniosj Yes Win10. Dosbox?
-
@shira Since 17.12.2, dosbox doesnt detect my roms folder shared from Windows. All rest emulators work perfectly. And you?
-
@toniosj hm I don't have any dosbox games to test
-
@shira I've send you a chat.