-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Add the ablity to mount disc image files #7880
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
Comments
Are we talking about ".ISO" files? |
yes |
Also TRY to add support for The following file extensions |
Iso images (and vhds) open fine in Files for me, so bug. Could you upload the app's log files? |
Yea.... the log files are not showing anything |
So... this is a bug AND a feature request? |
I found a lot of helpful links here |
@Advik-B could you check what happens if you right-click an ISO file and choose "Mount" instead of double-clicking it? |
No it does not work |
What happens instead? You don't have a mount option? You get a request for administrator but the iso is not mounted? |
Yes, also I don’t need admin to mount drive in windows explorer
|
Would there be any point to mounting it as a drive when #8232 is implemented? |
If we want to replicate Windows File Explorer functionality as closely as possible (since this is supposed to be an alternative), native mounting support would be ideal rather than extract the ISO via 7zip. |
You wouldn't need to extract it to view it would just act like a folder. |
Asking @yaichenbaum for approval. |
What's the Problem?
When you double click on a disc image file, the following happens:
Windows Explorer
will mount the file and display it as a drive
Files
nothing happens
Solution/Idea
Add the ablity to mount disc image files, or ... at least use windows explorer to mount it, then show it as a drive
Alternatives
hard-code it yourself, or use this library
Priorities
Files Version
Version: 2.1.2.0
OS Version: 10.0.22000.434
Windows Version
Windows 11 Pro 22000.434
Comments
Windows Specs:
Device Specs:
The text was updated successfully, but these errors were encountered: