NeeMeese / mplayer-ce

Automatically exported from code.google.com/p/mplayer-ce
0 stars 0 forks source link

MplayerCE freezes on startup #419

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Start mplayerCE 0.75

What is the expected output? What do you see instead?

Whenever I start mplayerCE it just says booting mplayerCE 0.75 and stays at 
that. I can see that the wiimote has connected because it flashes and then 
registers as controller 1. 

What version of the product are you using? On what operating system?

Wii 3.2E with mplayerCE 0.75

Do you have a modchip?

No

Please provide any additional information below.

I tried formating my wii and installing all the cios and all that stuff 
again as I suspected that some cios might have been damaged/changed and 
mplayerCE booted the first time I started it after the format. But when I 
turned my wii on the next day it just stayed at the first message "Booting 
mplayerCE 0.75" or just gives me a code dump. I also tried deleting the 
restore point file but no luck. MplayerWii 0.07 has the same problem, it 
just gives a code dump. However GeexBox still works... tough it's not as 
good as MplayerCE.

Original issue reported on code.google.com by nikoladu...@gmail.com on 9 Sep 2009 at 6:58

GoogleCodeExporter commented 9 years ago
This may be similar to issue 343. 

I have the same problem (HBC 1.0.1 on IOS36 v4.18.

Only mplayer v0.7 and above have this error for me. All older versions work.

Original comment by LoPresti...@gmail.com on 10 Sep 2009 at 3:18

GoogleCodeExporter commented 9 years ago
This could be the IOS reloading bug.  Do you have a newer Wii?

Original comment by agent...@gmail.com on 10 Sep 2009 at 11:13

GoogleCodeExporter commented 9 years ago
I found http://code.google.com/p/mplayer-ce/issues/detail?id=405&start=200 to be
helpful. I deleted cios 202 and it boots now. Haven't had time to test other 
player
to see if the problem remains in them but deleting cios 202 seems to fix my 
problem.
Will test some more later on today but so far so good.

Original comment by nikoladu...@gmail.com on 10 Sep 2009 at 7:24

GoogleCodeExporter commented 9 years ago
That suggests that it is the IOS reloading bug.  This bug should (hopefully) be 
fixed
in the next release.

Original comment by agent...@gmail.com on 10 Sep 2009 at 10:06