CleanRip v1.0.2

Release threads for homebrew & utilities only
Post Reply
User avatar
emu_kidid
Site Admin
Posts: 4575
Joined: Mon Mar 29, 2010 10:06 am
Location: Australia
Contact:

CleanRip v1.0.2

Post by emu_kidid » Sat Sep 18, 2010 4:41 pm

CleanRip
Author: emu_kidid
(taken from http://code.google.com/p/cleanrip/)

Create 1:1 backups of your GC/Wii discs for archival purposes without any requirements for custom IOS (cIOS).

Whatsnew in 1.0.2:
* Added redump.org in-program verification (see FAQ section)
* Added auto file splitting (i.e. ripping a Wii disc to a large FAT32 hdd)
* Fixed BCA dumping (GC & Wii disc)
* Fixed Multi-Disc rip file names
* Fixed Crashes on disc init

Features:
* FAT32 / NTFS file system support
* USB 2.0 support
* Front SD Support
* Gamecube / Wii / Wii Dual layer disc dumping
* BCA ripping to disk
* File Splitting (1,2,3GB (or Maximum file size - only on NTFS))
* MD5 sum is saved to disk
* Redump.org in-program verification for known rips

Image
Web site:
http://code.google.com/p/cleanrip/

Cleanrip current version - Download
http://code.google.com/p/cleanrip/downloads/list
Image
YuanZ
Posts: 15
Joined: Sat Aug 28, 2010 4:29 pm

Re: CleanRip v1.0.2

Post by YuanZ » Sat Sep 18, 2010 4:56 pm

Excellent :)
buckeye
Posts: 7
Joined: Tue Sep 14, 2010 3:24 am

Re: CleanRip v1.0.2

Post by buckeye » Sat Sep 18, 2010 7:51 pm

Something broke with NTFS in 1.0.2. Selecting USB, NTFS, drive and game get mounted, DL=no, chunk size = max (tried other settings also), new device per chunk = no, and get the following:

ntfs0:/chunk0.bin
failed to create file!

Then the application exits.

Also, might be better to maybe grey out or hide the new device per chunk option when chunk size = max is selected, since you wouldn't be changing the device anway when set to max.
ksadex
Posts: 3
Joined: Sat Sep 18, 2010 10:08 pm

Re: CleanRip v1.0.2

Post by ksadex » Sat Sep 18, 2010 10:12 pm

I'm getting same error like buckeye.

1.0.1 was working fine with exact same setup, ripped 2 discs today.

Edit: The reason i'm reriping again with new version is to rip correct bca files. While at it, maybe an option to rip bca only could be useful :)
User avatar
emu_kidid
Site Admin
Posts: 4575
Joined: Mon Mar 29, 2010 10:06 am
Location: Australia
Contact:

Re: CleanRip v1.0.2

Post by emu_kidid » Sun Sep 19, 2010 12:23 am

Nothing changed with the NTFS code, that's pretty strange..
Image
User avatar
emu_kidid
Site Admin
Posts: 4575
Joined: Mon Mar 29, 2010 10:06 am
Location: Australia
Contact:

Re: CleanRip v1.0.2

Post by emu_kidid » Sun Sep 19, 2010 3:47 am

There is a bug with redump verification in which it'll fail on the second and subsequent discs. I'll fix it for 1.0.3.
Image
Sintendo
Posts: 60
Joined: Tue Sep 14, 2010 1:39 pm
Location: Belgium

Re: CleanRip v1.0.2

Post by Sintendo » Sun Sep 19, 2010 9:39 am

I've been having crashes right after pushing A to resume the ripping after inserting the second USB device.

Image

Code: Select all

Exception (DSI) occurred!
GPR00 800678E8 GPR08 00800080 GPR16 00000000 GPR24 801C24C9
GPR01 802C4AF8 GPR09 53423450 GPR17 00000000 GPR25 801C24C3
GPR02 801C84E0 GPR10 FF800080 GPR18 00000000 GPR26 80067940
GPR03 801C24D0 GPR11 00000000 GPR19 00000000 GPR27 800678E8
GPR04 00800080 GPR12 801C27CC GPR20 802C6240 GPR28 801C24D0
GPR05 00000010 GPR13 801CAB40 GPR21 801BA33C GPR29 802C5A20
GPR06 00000000 GPR14 0000000A GPR22 801BA35C GPR30 00000008
GPR07 0000FF00 GPR15 277052B2 GPR23 801C24CD GPR31 802C4B30
LR 800678E8 SRR0 80067940 SRR1 00002030 MSR 00000000
DAR 53423454 DSISR 04000000

STACK DUMP:
80067940 --> 800678e8 --> 80005860 --> 800678e8 -->
80005860 --> 800678e8 --> 80005860 --> 8006794c -->
80005860

CODE DUMP:
80067940: 80890004 4CC63182 48003131 2F9E0008
80067950: 83BD0000 3BDE0001 419E0001 801D0000
80067960: 2F800000 409EFF64 801F0000 2F800002
I hope I didn't make any mistakes while transcribing the error screen.
User avatar
emu_kidid
Site Admin
Posts: 4575
Joined: Mon Mar 29, 2010 10:06 am
Location: Australia
Contact:

Re: CleanRip v1.0.2

Post by emu_kidid » Sun Sep 19, 2010 9:52 am

Sintendo, unfortunately that error is coming from the usb code in libOGC. There was a new change made so the next version will be compiled with that.
Image
Post Reply