You are not logged in. Please login or register.
Redump Forum → Posts by ssjkakaroto
I don't have any cd drive except plextor now, so I can't support now.
sarami, I think you can test this with plextor drives also. Just don't read the disc in scrambled mode.
This is what already happens when you use DIC with the "data" and "audio" options. We're only missing the option of reading a mixed-mode disc.
Small bug using data mode:
E:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe data i "Unreal Mission Pack I - Return to Na Pali" 16 0 331789 /c2
(...)
Allocating packed memory for C2 errors: 8192
Set read command: 0xbe, subcode reading mode: Raw
Checking SubQ ctl (Track) 1/ 1
Creating bin from 0 to 331789 (LBA) 331788
No C2 errors
Exec ""E:\DiscImageCreator\Release_ANSI\EccEdc.exe" check "E:\DiscImageCreator\Release_ANSI\Unreal Mission Pack I - Return to Na Pali""
[F:main][L:690] GetLastError: 2, The system cannot find the file specified.
Freeing allocated memory for C2 errors: 8192
End time: 2016-08-02(Tue) 20:47:08DIC forgets to add .bin to the EccEdc command line.
Manually running
EccEdc.exe check "Unreal Mission Pack I - Return to Na Pali.bin"works
No rush sarami. I'm glad you consider it, thanks.
Sorry for the necromancy, but I would also like to request the RedumpOrgToCloneCD function. Virtual Clone Drive doesn't accept cue files, but it does accept ccd files.
This function would make it very convenient to play games with multiple tracks.
Unless you have another disc to verify or someone else dumps it and gets the same results as you, it won't be verified.
There are tons of discs in this situation, don't worry about it.
Here's one that I'm 99% sure won't ever be verified, but I'm sure my dump is good: http://redump.org/disc/9470/
Whatsnew in 1.0.4:
* Added redump.org DAT file downloading
* Added more info to the dumpinfo.txt
* Fixed rip completion time not showing up
* Fixed NTFS issues (failed to create file/etc)
Whatsnew in 1.0.3:
* Added SHA-1 and CRC32 calculation (all saved to disk)
* Fixed redump.org verification on second and subsequent files
* Compiled with the latest libFAT & libOGC
Example of dump information provided as of 1.0.3:
--File Generated by CleanRip v1.0.3--
Filename: GHSP69
MD5: 2E0DF737435BEB701C77672D7E80E113
SHA-1: 92C7119517CD53C75A7C13F302951B53810E2C2C
CRC32: 97D0FBB3
Version: 1.00
Change log (v1.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
Change log (v1.0.1):
- Added experimental BCA dumping (Wii disc only)
- Added MD5 sum saving
- Fixed Speed/ETA calculation
- Fixed file split issues
- Fixed SD/USB re-init issues
- Hopefully random code dumps with Wiimote are gone
I just looked at the 15 pages of the Superdump thread in gbatemp (which was the only one that I posted).
http://gbatemp.net/index.php?showtopic= … =superdump
Noone talks about uninstalling the cIOS, people that had the 99% error, the one you talk about, said the problem was with their modchip (page 7).
On the last page there is someone that get the error again, but he doesn't even know if he is actually using rev13b, he doesn't say if he has a modchip and he doesn't say he solved it.
All the others that report the 99% error are talking about the refresh problem.
Some other people get and error reading from their USB devices, which is solved in a completely different way.
Now Rimmer said
If I'm not mistaken, the dumps is 99% correct, only like the first 1% is kinda not good, something around boot sectors maybe?
He didn't say he got any error in Superdump, also the bad sector are at the beginning of the disc, not the end, which looks like a completely new error.
He needs to provide a more detailed report of what exactly he is doing and if he has a modchip.
Again, where did you come with this uninstall/install thing?
The problem is this Rocknroms:
I repeat again with other words, some people still get the 99% error after downgrading cIOS but they solved it unistalling rev 14/15 and then reinstalling rev 13b.
Where the hell did you come up with this? It makes absolutely no sense. The error must have come from something else, not the cIOS.
The procedure
(Wii with cIOS 14/15/16) -> (Install cIOS 13b) -> (Dump the game with Superdump)
cannot lead to different results than
(Wii with cIOS 14/15/16) -> (Uninstall cIOS 14/15/16) -> (Install cIOS 13b) -> (Dump the game with Superdump)
I repeat again with other words, some people still get the 99% error after downgrading cIOS but they solved it unistalling rev 14/15 and then reinstalling rev 13b.
This is completely FUD. The error occurs with any cIOS and is not consistent. It doesn't matter if you uninstalled or overwrote it.
If you think everyone needs to keep the hacked/vulnerable IOS for all eternity without updating, even though they already got cIOS, then your/Pikmin guide is probably right.
This is what you said:
I know you can make mistakes unistalling iOS, but many people had problems downgrading iOS without disinstalling old one.
There is absolutely NO problem to downgrade a cIOS, you probably did something awfully wrong for that to happen.
So, as I never hear about bricking for unistalling and reistalling cIOS, I don't understand the real meaning of your first post
I never said anything about a brick for unistalling and reistalling cIOS. You're misunderstanding. Waninkoko's cIOS installs as IOS 249, which is currently not in use by the Wii, so you can mess around with it without problems. The brick comes if you do something wrong with regular IOS (note that there's no c there) (e.g. IOS 61, 70)
but as I said it's better to delete cIOS (rev. 14/15/16 **) and then install rev.13b. Again, it cannot damage anything in your system (even if you got a brick, which never happened as long as I know, you can still start wii via bootmii or preloader and fix everything), but some people have problems with superdump and a downgrading cIOS (for example I had problem the first time).
It's not better. It won't damage your Wii, but if for some reason someone that had cIOS (as IOS 249) and after that updated the Wii's regular IOS's and did not leave a vulnerable IOS besides the cIOS, that person would have to run TBR again if he/she uninstalled the cIOS. This isn't a brick, just a unnecessary annoyance, that could have been avoided if the person had just overwritten the cIOS with the previous version. This scenario might not happen to many people, but it is possible.
but many people had problems downgrading iOS without disinstalling old one.
What problems? Seriously. This was the first time I heard this. What cIOS did you have before you installed rev 13b.
I've done this procedure tons of times with all revisions of Waninkoko's cIOS's without a single problem.
If you're talking about the 99% issue with Superdump, this has got nothing to do with installing an older version over a newer one. This happens with all versions of cIOS. You can ask kiczek about it.
I meant cIOS38 (IOS249), I never read about any wii brick problem on downgrading this IOS
Of course not, that's exactly what I said in my previous post. Install cIOS rev 13b (IOS 249) over the currently installed cIOS rev 14/15/16 (also IOS 249). After you dump the game just reinstall cIOS 14/15/16 (IOS 249) over the currently installed cIOS rev 13b. There won't be any brick with this procedure and you won't need to uninstall anything.
You can only brick your wii if you install cIOS38 with a clean IOS36 or maybe if you install it using a different IOS than 36, but this could happen even if you overwrite it.
LOL, you won't be even able to install the cIOS if you don't have a vulnerable IOS. That's exactly why you use TBR.
Rocknroms, by what you wrote, I think you understand what I posted earlier (install a cIOS over another one). You probably just didn't read it correctly 
Who said anything about downgrading a IOS? Read carefully.
I was talking about downgrading a cIOS, which is completely different.
There may be cases where after uninstalling the cIOS you'd have to softmod your Wii all over again since you wouldn't have a hacked IOS to install stuff. So it's not recommended to do that.
But even if you want to "clean" your Wii (e.g. when you have CIOSCORP installed) it's always recommended to overwrite the IOS's (with non stub versions, of course), uninstalling some IOS's could lead to a really bad brick.
3. If you have cIOS v1.4 or v1.5 uninstall it with the unistaller and then install v1.3b to have a clean system
You don't need to do that, just overwrite the currently installed cIOS with 13b (not 1.x). Never delete any IOS, always overwrite them, it's a lot safer.
After you dump, you can go back to rev 14, 15 or 16.
F1ReB4LL do we just use the drive's offset in EAC when dumping audio cds or do we use the same procedure as data+audio discs (combined offset)?
...Audio CD section was also created, btw, for various game-related CDDAs (not the bonus ones) - OSTs, promos, etc.
Where is it?
IIUC the year will be just a tag in the dat file, there will be no change in the naming convention. You can add infinite tags in the dat without changing the file name.
In the case of multiple games the No-Intro guys use: X Games in 1: Game1 + Game2 + ... + GameX (Region) (Languages)
Here's a example that I have: http://redump.org/disc/2939/
I'd like to try PSX ROMid, but I'm just too lazy to unbox my PS1 and set it up 
Probably many discs will match but many will need patching.
A few years back I got to extracting a few FMV from PSX and Saturn games, there were some very cool openings (Eretzvaju for example), but the hassle of ripping/converting on the slow PC I had at the time made me stop 
.
It would be so much better if those codecs were supported in ffmpeg/mplayer/etc, so we could just copy the video file and play it.
Did anyone get to fixing the PRE/DCP flag issue when generating the cuesheet?
Redump Forum → Posts by ssjkakaroto
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.