Post by: ILLusions0fGrander on August 10, 2006, 08:40:00 PM
dunno, i havent used ripper in a while.
Post by: Gabbiani on August 11, 2006, 08:49:00 AM
Everyone uses a different method to make backups, so maybe merger isn't accounting for the different methods when it checks the md5. (I know it checks to know how to merge it all together though)
Post by: Nailed on August 11, 2006, 09:25:00 AM
QUOTE(Gabbiani @ Aug 11 2006, 02:56 PM) 
I wonder if this is related to having the SS md5 matching in SS merger?
I would suspect so. Especially if I had selected 'Fill In Zeros' in Isobuster when I got the data error.
Post by: lickwid on August 11, 2006, 11:49:00 AM
QUOTE(Nailed @ Aug 11 2006, 02:19 PM)
I figured out the difference (just needed a better hex editor... using 010 Editor now). The last FD90000 bytes of the wxripper image repeat at the end of the isobuster image. In other words, in the isobuster image, the ranges 1A3AF0000-1B3880000 and 1B3880000-1C3610000 are the same data.
When using isobuster, I got a data error at 96%. After hitting retry, isobuster continued on. I suspect it jumped back and re-read the same sectors over again.
The problem I'm having is that I never get the error prompt, so there is no way I can hit the retry button. Basically, it rips pretty steadily up to 96%, then stalls there for who knows how long, then eventually it'll be complete.