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 don't pass the -i option, and yet my original files get overwritten without my permission; it's bad program etiquette because I can't get the file back. This is not documented behaviour and really there's no reason it should be overwriting the .bin instead of just creating a new .iso file.
Maybe bin2iso is so fast because it rewrites only certain chunks in some file? In this case either overwriting the original .bin should not be the default (have an option --inplace that enables this behaviour) or the user should be given some confirmation question asking if the file may be overwritten.
.cue file
FILE "Usagi - Yasei no Touhai - Dramatic Mahjong (Japan).bin" BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
command line used & the screen output
$ bin2iso Usagi\ -\ Yasei\ no\ Touhai\ -\ Dramatic\ Mahjong\ \(Japan\).cue /run/media/danb/ps2_mx4iso/CD/
Aug 26 2021, 08:56:50
bin2iso V1.9b - Converts RAW format (.bin) files to ISO/WAV format
Bob Doiron, ICQ#280251
Check for updates at http://users.andara.com/~doiron
Note: Appending pregap data to end of audio tracks
Usagi - Yasei no Touhai - Dramatic Mahjong (Japan)-01.iso (425 Mb) - sectors 000000:189743 (offset 000000000:446277887)
Mode2/2352 single track bin file indicated by cue file
Usagi - Yasei no Touhai - Dramatic Mahjong (Japan).bin renamed to Usagi - Yasei no Touhai - Dramatic Mahjong (Japan)-01.iso
directory listing of source and files created (with sizes)
$ ls -al Usagi\ -\ Yasei\ no\ Touhai\ -\ Dramatic\ Mahjong\ \(Japan\)*
-rw-r--r-- 1 danb danb 446277888 Dec 24 1996 'Usagi - Yasei no Touhai - Dramatic Mahjong (Japan)-01.iso'
-rw-r--r-- 1 danb danb 116 Dec 24 1996 'Usagi - Yasei no Touhai - Dramatic Mahjong (Japan).cue'
The text was updated successfully, but these errors were encountered:
I don't pass the
-i
option, and yet my original files get overwritten without my permission; it's bad program etiquette because I can't get the file back. This is not documented behaviour and really there's no reason it should be overwriting the .bin instead of just creating a new .iso file.Maybe
bin2iso
is so fast because it rewrites only certain chunks in some file? In this case either overwriting the original .bin should not be the default (have an option--inplace
that enables this behaviour) or the user should be given some confirmation question asking if the file may be overwritten.The text was updated successfully, but these errors were encountered: