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
If an mds file specifies an extension that isn't mdf, aaru will fail to handle the image and close with ENOENT, regardless of whether you give the image file the extension the MDS specifies, or whether you give it the extension MDF.
Exact command line used
aaru i info [name].mds
Expected behavior
For this specific command, I expected aaru to retrieve image information.
There are 3 ways I'd imagine approaching this.
Giving an error that the format specified in the MDS is wrong, and that the user should change it to mdf themselves.
Checking for *.mdf regardless of what the mds file specifies.
Using the extension specified in the mds file
Personally, I'd lean towards 3, as even if a120 doesn't dump to that format, it will still happily mount images based on the extension specified in the mds, and, presumably the extension is specified there for a reason anyways.
Regardless, I'd be ok with any of the options, though.
Actual behavior
Image format identified by Alcohol 120% Media Descriptor Structure
(a78fbeba-0307-4915-bde3-b8a3b57f843f).
Cannot open data file
Unable to open image format
Error: ENOENT
Uploading statistics
Output of command execution with debug output enabled
Version
Development commit
Commit hash
f061e8b
Tested debug version?
Which operating systems have you used?
What is the architectural bit size you're using?
What processor are you using?
Image format
MDS
Application that created the image
Alcohol 120%
What were you doing when it failed?
Destination image format
No response
Filesystem
No response
Description
If an mds file specifies an extension that isn't mdf, aaru will fail to handle the image and close with ENOENT, regardless of whether you give the image file the extension the MDS specifies, or whether you give it the extension MDF.
Exact command line used
aaru i info [name].mds
Expected behavior
For this specific command, I expected aaru to retrieve image information.
There are 3 ways I'd imagine approaching this.
Personally, I'd lean towards 3, as even if a120 doesn't dump to that format, it will still happily mount images based on the extension specified in the mds, and, presumably the extension is specified there for a reason anyways.
Regardless, I'd be ok with any of the options, though.
Actual behavior
Output of command execution with debug output enabled
Affected image
Any MDS specifying something besides *.mdf is affected. So far I've seen *.bin, *.iso, and *.img. (For both single and double byte, obviously).
Mofamen Xilie Zhi Yingxiong Wudi III - Mori Zhi Ren (China).mds.zip
The text was updated successfully, but these errors were encountered: