search

smurk-too / cleanrip

Automatically exported from code.google.com/p/cleanrip
0 stars 0 forks source link

Disc type and dumping media autodetection #8

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
First, thank you very much for this awesome dumper.  I've been waiting for a 
long time to get rid of cIOS for good, the only homebrew I use are dumpers.

Since I don't rip games that often it's not urgent.  And it's only a feature 
request.

I would like the program to detect on its own what disc is in the drive (GC / 
Wii / Wii DL) and also where to dump (if there's a USB drive just assume it'll 
be there, or make a config file so the user can change this setting one time 
and not each time we have to dump.  Then detect what type of FS, etc that drive 
uses, FAT32, NTFS, etc.

It would be awesome if we could just start the program via HBC, insert a disc, 
press A to dump, and then A again to dump another game when it's finished, and 
then A again, etc.

Would be really awesome.

Thanks!

Original issue reported on code.google.com by dominicp...@gmail.com on 15 Sep 2010 at 2:31

GoogleCodeExporter commented 8 years ago 
Oh, didn't see we could change the settings at the left.  Change to enhancement 
and low priority or whatever you think is right.  :)

Original comment by dominicp...@gmail.com on 15 Sep 2010 at 2:33

GoogleCodeExporter commented 8 years ago 
Oh, and by the way Configurable USB Loader seems pretty good at doing many of 
those (detecting disc type, FS, config file, etc.) maybe you can use part of 
their code.

Original comment by dominicp...@gmail.com on 15 Sep 2010 at 2:46

GoogleCodeExporter commented 8 years ago 
Main difference: they use cIOS.
It's not really that much of a pain to set the very few setting each time the 
program starts.
I think emukidid will mark this Invalid.

Original comment by school.p...@gmail.com on 15 Sep 2010 at 10:28

GoogleCodeExporter commented 8 years ago 
If the user doesn't specify things like whether the disc is a dual layer, chunk 
size, device type (sd, usb), filesystem type (fat, ntfs), etc, there's a lot 
more that can go wrong.

I will add in Dual Layer detection though, that one is easy.

Original comment by emuki...@gmail.com on 16 Sep 2010 at 1:50

GoogleCodeExporter commented 8 years ago 
Awesome, I think detecting DL is the most important one.  The others the user 
knows, but DL there's no easy way.

Thanks!

Original comment by dominicp...@gmail.com on 16 Sep 2010 at 1:11

GoogleCodeExporter commented 8 years ago 
Turns out this has more issues than I'd thought. It's best to leave it out for 
now :(

Original comment by emuki...@gmail.com on 19 Sep 2010 at 1:12

GoogleCodeExporter commented 8 years ago

Original comment by emuki...@gmail.com on 19 Sep 2010 at 2:34

GoogleCodeExporter commented 8 years ago 
if you have troubke writting solid detection code you might want to look at my 
code in SNEEK: http://code.google.com/p/sneek/source/browse/trunk/es/SMenu.c#387

Original comment by urt...@gmail.com on 25 Sep 2010 at 1:52