Mac users with config/SRAM writing issues?

I am currently investigating a case where the Retrode doesn’t seem to work the way it should. In particular, it appears as if under MacOS, write accesses to the Retrode (config file, SRAM) are sometimes ignored and the files are not written correctly. For instance, after saving the config file from a text editor and resetting the Retrode, the file would contain the old data again. Needless to say, this is quite an annoyance, and the problem has been haunting me for some while now.

The good news is: I have come up with a possible solution. However, since I do not have a Mac, I cannot test it myself. Therefore, I would appreciate if someone could help me out with some testing. If you are a Mac user and you think you are affected by this problem, please report to me and you can contribute to the further improvement of the firmware.

2 comments to Mac users with config/SRAM writing issues?

  • Chris White

    This sounds like write buffering, which is a feature where the operating improves safety and performance of external storage by storing written data in computer RAM first until it has a nice big chunk to save, and THEN it writes to the external storage. This means that you are never guaranteed that it writes ANYTHING immediately.

    The way to test if this is the case, and indeed the SOLUTION if it is the case, is for affected users to right click the mounted “virtual disk” of the retrode and select “Eject” in the menu.

    This means the Mac will flush (write) any remaining unwritten data and then disconnect the virtual disk.

    Let’s hear if this worked,

    • The Retrode identifies itself as “removable device”, which should tell the OS to disable write buffering. On Windows, I see no “eject” icon so it seems to work.