Samba Shares Access Denied on USB Storage

[pew05]

Hello. I'm new to Retropie and so far I love it - it is the best emulation platform I have ever tried putting together, and is certainly working better than my converted OUYA!

However, I do have one nagging issue that I would like the community's opinion on - Samba shares for me are read-only following a config change to use USB storage. The USB drive I use is 64 GB so NTFS and exFat are my only options. I was able to mount the drive and copy things to it using ssh, but even after configuring Samba to point to the new roms dir I get access denied when trying to write into any of the roms folders via Samba from a Windows 10 machine. I have tried both authenticated (using Root and I know that's poor practice, also using pi user) and unauthenticated connections and both result in the same issue.

I have looked through similar posts from other users, and followed each of their resolutions. This includes the unmask= 000 setting in fstab when mounting the drive on boot, and a few settings in the smb.conf file under rom share config that you can see in the pastebin below.

Any input on how to resolve or work around this would be appreciated. Thanks for your time!

Pi Model: 3 B
RetroPie Version Used: 3.6.0
Built From: SD Image
USB Devices connected: Powered USB Hub, SanDisk 64 GB mini flash drive (directly connected, not hub'ed)
Controller used: Logitech f30
Error messages received: Access denied (On windows machine while in SAMBA share)
Guide used: http://mardell.me/blog/how-to-load-roms-from-a-usb-drive-on-retropie/
File: /etc/samba/smb.conf (Potentially???)
Emulator: NA
Attachment of config files:

1. FSTAB (Custom mount using exfat configured): http://pastebin.com/CwwFedtK
2. smb.conf (Share portion which shows roms share settings): http://pastebin.com/S6qZ20dV

How to replicate the problem: The retropie install is fully functional - I can copy roms to the USB and play them, however, if I connect via the samba share I get access denied in every rom folder when trying to write there.

[BuZz]

bad guide - you should mount the usb over the existing roms folder. symlinking it may also work (or do a bind mount from existing location).

Changing all the paths in es_systems.cfg is a bad idea.

you need to make sure you mount the drive so that the user pi can write them also. can use uid=1000,guid=1000 mount options for example.