Closed GoogleCodeExporter closed 8 years ago
Please add information
Original comment by nintendo...@kaffeeschluerfer.com
on 22 Feb 2009 at 12:46
I'm not that into this, i´ve bought the wii chipped from china, but when i got
home
it isnt working, bought tons of games from the guy who also installed all the
shizzle
on the machine. Running the Softchip program as he advised, but as stated i get
the
DCI_read Error. I just saw that the cIOS is apparently sat on 249..... if that
makes
a difference
Original comment by Nicolai....@gmail.com
on 22 Feb 2009 at 1:05
On a chipped Wii the games HAVE TO run in the disc channel. And IOS36 is a
better
choice as IOS to use in SoftChip then. If you got ripped off, you need to check
if
your discs are DVD+R, if yes, they are most likely burnt the wrong way. Don't
ask
pirate questions here.
Original comment by nintendo...@kaffeeschluerfer.com
on 22 Feb 2009 at 1:51
Sorry for closing this, but without any additional information, it's not
possible to
solve the problem or even confirm there's a problem.
Original comment by nintendo...@kaffeeschluerfer.com
on 4 Mar 2009 at 12:55
1,select ios249
2,use -R disc
Original comment by kavidwf@gmail.com
on 4 Mar 2009 at 3:00
Let your Wii cool down a bit probably caused by overheating. Leave it
unplugged.
Play it later. Usually that error message disappears.
Original comment by retro...@gmail.com
on 30 Mar 2009 at 10:22
If it's an overheation problem, then disabling WiiConnect would help. If the
led of
your Wii is something else than RED it's running and heating. In WiiConnect
"standby"
the Wii is heating, but the fans are disabled, to me personally that's a good
reason
to avoid that mode. (the other reason is my electricity bill)
Original comment by nintendo...@kaffeeschluerfer.com
on 31 Mar 2009 at 6:10
If your Wii overheats and if you are using DVD-R you will get this loctl error.
Also, if you use DVD-RW you also get this same error message too. Softchip
will not
run DVD-RW.
Original comment by retro...@gmail.com
on 1 Apr 2009 at 1:50
Original issue reported on code.google.com by
Nicolai....@gmail.com
on 22 Feb 2009 at 12:24