You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am wondering if there is the possibility for the cartridge to interface with the controller pak in order to copy the contents of the memory card onto the SD card, and vice-versa. I have seen that the EverDrive has this functionality. Would be useful to avoid needing multiple controller paks.
How to solve the problem
I think this could be solved by having a menu with an option that essentially backs up the entire content of the Controller pak to a file, as well as an option to transfer the same file back. That is if this functionality is technically possible.
Describe alternatives you've considered
Main point of reference is the Everdrive implementation:
Additional context
No response
The text was updated successfully, but these errors were encountered:
Having a mechanism to back up an old card entirely would be really appreciated for folks who have old and aging cards that they want to save or move to something like a foreverpak. Being able to split it is of course great, but there is definitely a strong case for grabbing the whole card like everdrive 64 x7 does.
Description
Hi, I am wondering if there is the possibility for the cartridge to interface with the controller pak in order to copy the contents of the memory card onto the SD card, and vice-versa. I have seen that the EverDrive has this functionality. Would be useful to avoid needing multiple controller paks.
How to solve the problem
I think this could be solved by having a menu with an option that essentially backs up the entire content of the Controller pak to a file, as well as an option to transfer the same file back. That is if this functionality is technically possible.
Describe alternatives you've considered
Main point of reference is the Everdrive implementation:
Additional context
No response
The text was updated successfully, but these errors were encountered: