• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

unable to access genesis share

Scheduled Pinned Locked Moved Help and Support
genesisshareerror
7 Posts 3 Posters 5.4k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F
    flagrant99
    last edited by 11 Oct 2017, 00:34

    So I followed the steps here
    https://github.com/retropie/retropie-setup/wiki/Genesis-Megadrive
    To make it display sega genesis instead of sega megadrive in emulationstation menu. After updating it does now display sega genesis. :)

    But now the genesis share \retropie\genesis is unreadable. It still displays but I cannot access. I get the directory name is invalid. Before following the steps I could access genesis or megadrive. It's not that big of a deal, but curious. Is there some reason I can only write to megadrive when I would like to display genesis? Before this step I could read and write fine from either subfolder. Is there something wrong with permissions? I think I am on 4.3 but can't figure out how to check. I did just update in the last couple days.

    M 1 Reply Last reply 11 Oct 2017, 04:25 Reply Quote 0
    • M
      mitu Global Moderator @flagrant99
      last edited by 11 Oct 2017, 04:25

      @flagrant99 The genesis folder is just a shortcut (symlink) to the megadrive folder, so you can just copy ROMs in the megadrive and they'll show up under the genesis in the RetroPie interface.

      1 Reply Last reply Reply Quote 1
      • F
        flagrant99
        last edited by 12 Oct 2017, 00:31

        right. I understand that if I write to the megadrive folder they show up under genesis in the front end. Was just wondering if I screwed something up or this was by design. Just thought it odd that when I display megadrive I can write to genesis or megadrive. But when I display genesis I have to write to megadrive. Honestly the most annoying thing about it is I like to sync files from the roms share but I can't even read from the visible genesis sub folder. So I have to sync each subfolder independently. Like I said when ever I click on the genesis subfolder over samba I get the directory name is invalid errors. If the symlink worked like before I should have been able to read from it right?

        S 1 Reply Last reply 14 Oct 2017, 20:26 Reply Quote 0
        • S
          spinmaster7 @flagrant99
          last edited by 14 Oct 2017, 20:26

          @flagrant99 I have the same issue. It was fine before I upgraded to 4.3 recently. I hope to find what I need to type in the command line to remove this read protection. If I find it I will post back.

          S 1 Reply Last reply 14 Oct 2017, 21:29 Reply Quote 0
          • S
            spinmaster7 @spinmaster7
            last edited by 14 Oct 2017, 21:29

            ok, I should have paid better attention to the post above. Its a virtual/share folder, not sure why no after update but yeah, copy .md files to megadrive not genesis. Whats strange is after the update to 4.3 I lost all of the .md's I had on the SD card.

            1 Reply Last reply Reply Quote 0
            • F
              flagrant99
              last edited by 16 Oct 2017, 01:32

              Ok thx spinmaster. This means this had more to do with the upgrade to 4.3. I just happened to update to 4.3 while changing the logo. Probably the best solution is to just kill the symlink. If I ever figure it out I will post here.

              M 1 Reply Last reply 16 Oct 2017, 03:52 Reply Quote 0
              • M
                mitu Global Moderator @flagrant99
                last edited by 16 Oct 2017, 03:52

                @flagrant99 I doubt it has anything to do with the 4.3 upgrade, I've seen the same behavior before and there are a few posts in the forum asking the same thing.
                The symlink support in Samba - the application that's responsible for the file sharing - has changed a long time ago due to the https://www.samba.org/samba/news/symlink_attack.html .
                If you want to enable it again, then you'll need to modify the configuration file just like it's described here - https://unix.stackexchange.com/questions/5120/how-do-you-make-samba-follow-symlink-outside-the-shared-path .

                1 Reply Last reply Reply Quote 0
                6 out of 7
                • First post
                  6/7
                  Last post

                Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.

                  This community forum collects and processes your personal information.
                  consent.not_received