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
I've been trying out lr-puae on the Retroid Pocket 5. Good performance for running games, but i am looking to have an amiga development setup on there too, since its a great portable device that can be easily plugged into a screen, or mouse/keyboard added.
I had issues getting my System (ClassicWB) folder mounted as DH0: ... when booting it seemed not to perform properly. I then added it to an HDF and mounted that (using a .uae config file) . This loaded ok , but is there any reason why it has forced it to be read-only, despite setting the option as 'rw' ? Is this intended behaviour, and if so can that be overridden?
I then added the areas i needed to be writable to a folder mounted as DH1: but this seems to be throwing up issues also and not being correctly read either.... in particular not performing the same on the lr-puae setup as it has on fs-uae where i tested it... resulting in AMOS refusing to read its own APSystem folder correctly.
Any comments on this that might rectify the issues welcomed,
Thanks
The text was updated successfully, but these errors were encountered:
Never seen any of those. Try consulting the log, even though it still won't give any reason why it resorts to mounting read-only. Something up with the device permissions perhaps.
Hi
I've been trying out lr-puae on the Retroid Pocket 5. Good performance for running games, but i am looking to have an amiga development setup on there too, since its a great portable device that can be easily plugged into a screen, or mouse/keyboard added.
I had issues getting my System (ClassicWB) folder mounted as DH0: ... when booting it seemed not to perform properly. I then added it to an HDF and mounted that (using a .uae config file) . This loaded ok , but is there any reason why it has forced it to be read-only, despite setting the option as 'rw' ? Is this intended behaviour, and if so can that be overridden?
I then added the areas i needed to be writable to a folder mounted as DH1: but this seems to be throwing up issues also and not being correctly read either.... in particular not performing the same on the lr-puae setup as it has on fs-uae where i tested it... resulting in AMOS refusing to read its own APSystem folder correctly.
Any comments on this that might rectify the issues welcomed,
Thanks
The text was updated successfully, but these errors were encountered: