I'm confused...why are you renaming the DVV files to .BAK? What ever gave you the idea to do that? Are you using the same USB drive for the broken Wii?Quote:
Originally Posted by lemusmar
If you're using the same SD and USB devices between both Wii's and it is asking you to reverify the games then something with Devolution must have changed, cause I swear when my drive was broken I was able to verify my games on a friends Wii with my own SD and USB.
This would all be considerably easier to "interpret" if Devolution AND the games were being run from a single USB device without any inclusion of an SD card...
Yes, I agree. If I had a 2nd Wii I would test this out again and detail the exact process.
I'm looking for other ideas since the verify did not stop the 2nd broken wii from requesting for me to insert the disk again. In my reply I stated "But still, whenever I plug in the broken drive wii, using the sd card, I still get the blinking twice deal." Also, someone game me the idea that what was really happening with the "verify" was that devolution was creating/updating the GameID.DVV file with a "unique" id number, which is true... Agree? Anyway, since I can't again, re-verify the disk on my broken wii, how about if I trick the system into thinking it has the right GameID.DVV file already? It appears that the GameID.DVV file contains some encryption that physically and logically links the GameID, to the wii serial#, and the iso file.
So it sounds like the anti-piracy has been improved and now ties the verification to a single console.
Replacing the drive in the broken Wii is a pretty easy thing to do. I fixed mine with a replacement drive from amazon that cost around $20-25 and it took me around 15 minutes to swap it out following some guide I found on this site.
So many people have tried to do that and failed, it seems that if your drive is broken and you can't verify on a 2nd system without being asked to verify again on yours then your only choices are as follows:Quote:
Originally Posted by lemusmar
1) Get your broken drive fixed
2) Keep trying to verify on your Wii and hope you get lucky, it's possible...I did verify 2 or 3 of my games with my dying drive (the rest on a friends Wii).
My thoughts exactly, cause I know for a fact it worked when I did it with Devolution r159 basic loader. It sucks though cause now when Devolution gets Classic Con support for Wii U compatibility how the hell are we gonna verify our discs? A mini-standard disc adapter? Would that even work?Quote:
Originally Posted by blaisedinsd
The verify process works fine on the working wii; yes, a GameID.DVV files is created, unique for each game, and must have some proprietary/unique identification that physically/logically ties that .DVV file to the wii and the iso. I am not sure if this was working before or not. I can briefly discuss the steps I performed... On working drive wii: (1) CleanRip gamecube disk; (2) copy iso's to usb1:games and folder named using the gameid; (3) Use usbloader gx to run game on working wii; wii blinks twice continuously, so I insert disk to perform the "verify", then eject disk, then try game without disk, all working ok. On broken drive wii: (1) Disconnect working wii and remove sd card and usb drive. (2) Connect broken drive wii with original sd card and usb drive; (3) Use usbloader gx to run game without disk, game attempts to start then screen goes black and wii blinks twice continuously, apparently awaiting the disk to do the verify yet again. (4) Can't do the verify on the broken wii.
I only brought up the idea about the .DVV files because if I knew how the unique .DVV files were generated, I could recreate those somehow and copy them to the sd card and not have to do the verify again. I'm not sure what is driving the verify again. I believe that devolution must have something going on with generating the unique contents of the .DVV files that is tied to the serial number of the wii. Not sure.
Any ideas are appreciated. Thanks for being patient with me.
If you have a link you can send me on that exact drive you purchased, I will probably do that.
Use the Edit button please ~ SNES_Master
USB Loader GX? You really should be testing this stuff with the sample loader... and again, with it on the same USB/SD device as the games.
EDIT: To clarify, you want to minimize the amount of variables as much as possible.
@lemusmar: Soon as you copy (or do just about anything with) those .DVV files they become corrupt and you'll be forced to reverify...once they are auto-generated they should be left alone.
I hope you haven't been doing anything to the DVV files as that could be the cause of Devo asking you to reverify.
That's how I did it...could've sworn I explained it that way too, if not sorry. I was playing Zelda Minish Cap while posting lol.Quote:
Originally Posted by Nintendo Maniac 64