Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDF / Harddrive Folder issues #684

Open
HoraceAndTheSpider opened this issue Jan 4, 2025 · 1 comment
Open

HDF / Harddrive Folder issues #684

HoraceAndTheSpider opened this issue Jan 4, 2025 · 1 comment

Comments

@HoraceAndTheSpider
Copy link

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

@sonninnos
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants