Hacking WarioWare (PAL) problems with Cyclowiz

  • Thread starter Thread starter Nipi
  • Start date Start date
  • Views Views 5,841
  • Replies Replies 31
The unscrambler has a bug where it repeats the last 32KB - I doubt it'll make a difference either way however. If you're that worried, open it in Winhex or something, delete the last 32KB (8000 in hex) and save it - but personally I wouldn't bother.

If I do that, the game will be in raw format ?


As I understand it, if you delete the last 32k the game will be in 'proper' unscrambled format as opposed to 'buggy' unscrambled format, definitely not in raw format. What the practical difference between 'proper' and 'buggy' unscrambled format is, I don't know

QUOTE(LaGzoR @ Feb 12 2007, 08:05 AM)Who have already delete the last 32KB and tested the game ?
No other team unscrambler Wario PAL !
Thank you for your idea but i will waitÂ
wink.gif
I don't know the answers to your other questions.
 
Ok thank you !
I think the game we downloaded are only in raw format now !
That's why some people will not use unscrambler !
It's better
biggrin.gif
 
Madden NFL 07 (PAL) works perfect. I also tried Rayman, but there I received a DRE. Just ordered some Verbatim DVD-R's. Hopefully I can test those soon.

Other thing: Are some of you saying that the stuttering in WarioWare is caused by bad unscrambling?
 
Madden NFL 07 (PAL) works perfect. I also tried Rayman, but there I received a DRE. Just ordered some Verbatim DVD-R's. Hopefully I can test those soon.

Other thing: Are some of you saying that the stuttering in WarioWare is caused by bad unscrambling?

i testet rayman today in the morning
it gave me the same error as before
a dre right after the start from the wii menu

i dont know if its from bad unsambling.
would it be bad unscrambled the game would be playable
 
i also unscrambled my wwsm with unscrambler 0.4 and the size also was 4 700 012 544 bytes.

Then i unscrambled it again with the rawdump 2.0 software and then it was 4 699 979 776 bytes
smile.gif
Exactly, because Rawdump corrects the extra 32kb issue - if you removed 32KB from the end of the unscrambler 0.4 dump in a hex editor or something, it'd be exactly the same as the one unscrambled with Rawdump.
 
i also unscrambled my wwsm with unscrambler 0.4 and the size also was 4 700 012 544 bytes.

Then i unscrambled it again with the rawdump 2.0 software and then it was 4 699 979 776 bytes
smile.gif


Exactly, because Rawdump corrects the extra 32kb issue - if you removed 32KB from the end of the unscrambler 0.4 dump in a hex editor or something, it'd be exactly the same as the one unscrambled with Rawdump.
Just tested to take off the 32kb with winhex but it didnt help to the dre.
frown.gif
 
@Nipi:

i got the same problem with wwsm and thdj....
i've put a site online with some info: http://www.tyrant.de/cyclowiz.htm

@revilo; I noticed on your site you are flashing with firmware 111D, you should crossflash your pioneer to a 111L (auto bitsetting on single layer DVD+R's)

Copy & paste from other post:

To get +R media to work on the Wii you need to set the book type to DVD-ROM
The Pioneer 111D supports auto bitsetting of DVD+R DL, not single layer DVD+R

So you need to crossflash/update your firmware to 111L
this supports single layer +R auto bitsetting.

First download and downgrade to the TDB Pioneer 111 1.06* fimware
copykings.net/downloads/111_106.ZIP

To crossflash download the TDB Pioneer 111L 8.19* INT(Buffalo-Internal)
and the TDB Pioneer 111L 8.29 INT(Buffalo-Internal) firmwares.

copykings.net/downloads/111L_819.ZIP
copykings.net/downloads/111L_829.ZIP

First flash with the 111L 8.19* INT(Buffalo-Internal) firmware.
Restart your computer then flash with the 111L 8.29 INT(Buffalo-Internal) firmware.

All thanks go to the Dangerous Brothers for their fimware.
tdb.rpc1.org
 
Well, after hearing a lot of other experiences and reading some multiple fora, I think this problem stands loose from the type of media/burner/speed you use. It sounds just like a problem caused by the cyclowiz chip.
 
Well, after hearing a lot of other experiences and reading some multiple fora, I think this problem stands loose from the type of media/burner/speed you use. It sounds just like a problem caused by the cyclowiz chip.

or a problem caused by the game itself

the crews werent able to test their releases
 

Site & Scene News

Popular threads in this forum