Topic: 10-13 Cvs Release Problems (Read 50 times)

Soulja221 · « **on:** October 22, 2003, 06:02:00 PM »

Who, besides myself has problems with the 10-13-03 CVS release of Media Player?

I cant get it to boot at all...never, not once has it not frozen at the loading screen and I do believe I've tried everything. Now I want to see what is common between all of the people with problems....

82ross · « **Reply #1 on:** October 22, 2003, 11:00:00 PM »

Upgrading wasnt any different than any other CVS. Im not sure why people are having problems. But if nothing else works:

Delete you xbmp folder inc config.xml
Delete the 0face007 folder in T/UDATA.

And start again. The only thing i wouls usggest is not setting it up as a dash untill youve tested it a lot as just a media player.

82ross · « **Reply #2 on:** October 23, 2003, 12:29:00 AM »

Yup i know, but its easier for me to ftp instead of launching the xbox dash.

jmarshall · « **Reply #3 on:** October 23, 2003, 04:57:00 PM »

There is a bug in the 10/13 release that means it may not boot unless there is a

<autolaunchvideo>false</autolaunchvideo>

tag present in the config.xml file.

If you want the autolaunchvideo feature, just set the tag to true.

The key thing is that the tag should be present in order to guarantee that you'll avoid problems. If you use the config.xml file that was distributed with the 10/13 release, you'll be fine, as this has the required tag. It's only those people who are using old config.xml files that are having problems.

This bug has been fixed for over a week.

jmarshall · « **Reply #4 on:** October 23, 2003, 05:00:00 PM »

Also note that for quite a while (at least since August) XBMP has had version numbering on it's system.bin file, so you shouldn't have to delete it when you upgrade. The worse that can happen is all the settings will be screwed up, and this will only happen if someone changes the format (adds stuff) and doesn't increment the version number, which is unlikely.

Tethra · « **Reply #5 on:** October 24, 2003, 01:12:00 PM »

Hi,

I had problems getting it to start on my XBOX also. Chip is an Xecuter 1.

I deleted the 0face007 folders in TDATA and UDATA and still couldn't get it to start.

Finally remembered the dev kit to retail patch and that got it working for me.

Good luck,

Tethra

Author Topic: 10-13 Cvs Release Problems (Read 50 times)