How to reach information of a CDROM after apparent EOF?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
How to reach information of a CDROM after apparent EOF?
Hello!
I have in my hand a CDROM with photos created by some greedy photographer. When I mount it I can see two files in there, two .exe executables about 7.7 MBs in size each. When I try to create an ISO of the cdrom, I get an IO error and only 16 MBs end up at the file.... so I would expect the photo files after the apparent EOF of the device (or whatever it's called in CDROM jargon).
Is there a way to get past this point so that I could run magicrescue on the rest of the CD so that i can get the rest of the files?
Or are there other handson hacky methods to get to that data?
I have in my hand a CDROM with photos created by some greedy photographer.
Proprietary?
Quote:
Originally Posted by eantoranz
When I mount it I can see two files in there, two .exe executables about 7.7 MBs in size each. When I try to create an ISO of the cdrom, I get an IO error and only 16 MBs end up at the file.... so I would expect the photo files after the apparent EOF of the device (or whatever it's called in CDROM jargon).
Is there a way to get past this point so that I could run magicrescue on the rest of the CD so that i can get the rest of the files?
Or are there other handson hacky methods to get to that data?
Thanks in advance.
I believe your asking us to aid in cracking a piece of protected information by providing methods to circumvent the encryption by the original author. This would violate the LQ Rules.
Posting exact commands and error messages, running 'file' on the executables and running verbose 'fdisk -l', isoinfo, running 'find' on the ISO image (or whatever else diagnostics you can think of) could come in handy as basically any info like jewelcase inlay, disk creator, write type, session and TOC nfo may be interesting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.