Shortcut Install Blues

  • the instructions make it sound very straightforward, but to my considerable frustration, i cannot get it to work.

    i renamed the shortcut.xbe file to xboxdash.xbe, the shortcut.cfg file to xboxdash.cfg, and placed them both in the root of the c drive. the cfg file contained only the text "e:\apps\xbmc\default.xbe" which is appropriate for my install. when i booted the xbox, after the flubber animation, the screen went black and stayed black.

    i booted into my chip's os and used the embedded ftp server to examine the disks. i saw a new file - xboxdash.log - in the root of the c drive. it said:


    info - mounting d: to \device\harddisk0\partition2
    info - launching cutfile: d:\xboxdash.cfg
    info - openening cutfile: d:\xboxdash.cfg
    info - launching xbe: e:\apps\xbmc\default.xbe


    yet i couldn't find a logfile from xbmc anywhere, and the 0face008 folders didn't reappear in tdata or udata. i added an advancedsettings.xml file to xbmc's userdata folder so as to increase the logging level, but still no log was written.

    it doesn't seem as if xbmc's xbe is actually being executed.

    i experienced this problem not only with today's build, but with the 5/28 build as well.

    i've installed both the 5/28 build and today's build several times, overwriting everything. i've cleared out the x, y and z drives as well as the 0face008 folders. i've reverted to a "stock" xboxmediacenter.xml file.

    for experimentation purposes, i changed the shortcut.cfg file to point to a different xbe file altogether - a well-tested emulator whose install hasn't been disturbed. i figured this would cause the xbox to boot directly into the emulator rather than a dashboard. instead, i got a black screen after the flubber animation, just like when i was trying to load xbmc. the resultant log looks the same - it reports that it's loaded the xbe from the correct path, but it doesn't seem as if it's actually doing so.

    i downloaded the sourceforge opensdk version of shortcut.xbe and tried it, as well - the opensdk logo is superimposed on the splash screen, so clearly it's being loaded, but you wind up with a black screen. the log file looks exactly the same as noted above.

    i feel like there is something basic about the new shortcut method i'm just not getting, but i've no idea what. i've scoured all the documentation i could find.

    please help..?


  • Well, the newest build didnt work for me, i still get the black screen. I am fresh out of ideas.


  • devs, aren't most of these issues the result of BIOS incompatiblity?


  • yeah, i tried that... i was wondering if the xbmc build was faulty in some way. i do get the fatal error handler. the log says


    03:35:26 m: 53747712 notice: -----------------------------------------------------------------------
    03:35:26 m: 53727232 notice: starting xboxmediacenter. built on jun 6 2006
    03:35:26 m: 53727232 notice: q is mapped to: harddisk0\partition2
    03:35:26 m: 53727232 notice: log file is located: q:\xbmc.log
    03:35:26 m: 53727232 notice: -----------------------------------------------------------------------
    03:35:26 m: 53727232 notice: setup directx
    03:35:26 m: 53706752 notice: load settings...
    03:35:26 m: 53706752 notice: loading q:\userdata\guisettings.xml
    03:35:26 m: 53706752 error: unable to load q:\userdata\guisettings.xml, creating new q:\userdata\guisettings.xml with default values
    03:35:26 m: 53678080 error: unable to save settings to q:\userdata\guisettings.xml
    03:35:26 m: 53678080 error: unable to save settings to q:\userdata\guisettings.xml
    03:35:26 m: 53678080 warning: emergency recovery console starting...
    03:35:26 m: 53678080 error: the screen resolution requested is not valid, resetting to a valid mode
    03:35:26 m: 53678080 error: resetting to mode pal 4:3
    03:35:26 m: 53678080 error: done reset
    03:35:26 m: 50114560 fatal: xbmc fatal error:
    03:35:26 m: 50114560 fatal: q:\userdata\guisettings.xml, line 0
    03:35:26 m: 50114560 fatal: failed to open file
    03:35:26 m: 50114560 fatal: init network using dash settings...
    03:35:27 m: 50114560 warning: use dashboard
    03:35:27 m: 49803264 fatal: ip address: 192.168.1.12
    03:35:27 m: 49803264 fatal: starting ftp server...
    03:35:27 m: 47706112 fatal: ftp server running on port 21, login: xbox/xbox

    which seems like what you'd expect, right?


  • i created a custom shortcut using the uix shortcut creator thingy. it worked the same as the pre-made uix shortcut - the xbox froze on the xbox logo / "microsoft" text.


  • I have a xenium ice and am also suffering this problem.

    I have tried all three shortcut methods on both the x2 bios and the ind-bios.

    any workarounds?


  • i'll try to obtain another bios and try it out.

    for what it's worth, here (http://forums.xbox-scene.com/index.php?showtopic=518742) is a relevant thread on the xbox-scene xboxmediacenter forum. several people have this problem. one fellow reports that he's using an (older) x2 bios.


  • generally yes so is the case. but since the shortcut loads in this case, there must be something wrong in how we call on the next xbe. it's very hard to debug thou.


  • Still have not got it to work. I am going to try it right on the C: drive and see if that works. I have put an older version on with the .xml, and that works just fine.


  • if u can, try a proper bios instead.

    i'd recommend anything x2/x3.


  • sounds to me like you have the wrong xbe name then. make sure that it's renamed correctly, i.e. it's the xbe your bios loads.


  • no log file is being written - that's one source of my confusion.

    and i, too, thought the xbe must be corrupted... but yet, when i name it "xboxdash.xbe" and place it on the c drive, it loads. (i get the emergency recovery console thingy, of course, but it does load.)


  • http://www.skinjob.net/tsp/xbox%20boot%20stuff.htm
    maybe this will help explain some stuff?
    all i can contribute is that shortcut xbes made with team uix's shortcut maker (with the hardcoded path and no config file of any kind) have always worked for me, no problems, so i reccomend using them, just test them before you boot from them to make sure that a given xbe will in fact launch what you want it to launch.


  • join the club!! i think it may be something to do with the python folder - it seems as though when i deleted xbmc a file remained and i couldn't delete it.


  • hmmm, this stuff:

    03:35:26 m: 53678080 error: the screen resolution requested is not valid, resetting to a valid mode
    03:35:26 m: 53678080 error: resetting to mode pal 4:3
    03:35:26 m: 53678080 error: done reset

    doesn't look too good - you get the red writing on screen and everything though?

    if so, that confirms that things are working correctly as far as your xbox goes.

    what bios/modchip combination do you use? would be nice to track down as to whether that has any influence.

    the only other thing i can suggest for now is editing your bios to point directly to the xbmc xbe.

    cheers,
    jonathan


  • i do get the red writing on the screen... it looks fine, as far as error messages go.

    my modchip is a xenium ice. i tried this stuff with both evolution-x m8 and m8plus16 (my usual bios).

    i'm a little wary of the bios editing stuff, but i guess i'll try that tomorrow.


  • just for kicks, dump xbmc's xbe (or anything else that does not require any additional files to do something interesting) in place of xboxdash.xbe.

    you should at least get the fatalerrorhandler. if you don't, then there's something more wrong with your xbox.


  • I now have mine working. Last night I thought i had the latest version, but there was one newer. so I deleted the whole xbmc folder from unleashX (including that python folder which would not delete from ftp) and now it works.

    So I guess, just make sure you DO have the latest release, and if you were also unable to delete the python folder from FTP, try doing it using another dash.
    thanks guys.


  • afternoon

    any more progress on this guys? i seem to have the exact same situation, except i have an older modchip: an executer 1 with original bios (ie the xbox can only boot an .xbe named xboxdash.xbe)

    normally i boot straight into xbmc ie. the xbmc xbe was renamed and placed on c with the xboxmediacenter.xml.

    using the shortcuts (or making my own), pointed to the right path, the xbox boot stops half way through the boot anim, and i can get no further.

    following another post i've reformated the whole drive, lost 120 gigs of good stuff and have no improvement.

    i'm stumped and dont know what to do now.

    cheers all


  • thanks for the suggestion. when i use that version, things don't get as far - the screen never goes black, just hangs at the last frame of the splash sequence. no log file is written - i don't know if it is supposed to write one or not.


  • i understand - i've been using xbmc as my dash for a couple of years, i guess. the bios i've been using - m8plus16 - tries two filenames: evox.xbe (i believe) and xboxdash.xbe (which is what i've been using this whole time).

    i've gotten the x2 5035 v16plus and installed it in a spare bank on my xenium ice modchip. i've not had time to conduct *all* of my tests over yet, but so far, it's behaving just the same as i've described with the m8plus16 bios.

    this evening i installed evolution x as my dash (by dropping it in c:\ and naming it xboxdash.xbe, just as i've been doing with xbmc). it loaded fine with all three bioses i've got installed. using it, i was able to load emulators and such from the e drive - no problems. when i use it to load xbmc, the screen goes black for an instant, then the xbox reboots. it does this consistently and with all three bioses. no log file is written and the udata and tdata directories still lack a 0face008 folder.

    i'm so very, very confused...


  • and let's get this straight: you are running xbmc as an app from evox and it doesn't work?


  • I wish it would create a XBMC log file, then at least I could find the problem. If I use the pre compiled shortcut with the .cfg file, I get an evoxdash log since that is what I named them. The funny thing is the log shows that it is linking to E:APPSXBMCdefault.xbe no problem, yet it never loads. Older builds that use the .xml file load up no problem.


  • there is no log created, at least in my case.


  • yea, I know its not the bios because I have tried just about all of them with the same results.


  • i'm afraid i have exactly the same problem - i've tried both shortcut methods and the screen either hangs after the flubber or goes black depending on which method i use.

    strangely, if i take out the file (avalaunch.xbe which is the path it boots to) the xecuter dashboard boots instead - which it will do as that is loaded on.

    seems the problem is with the xbmc boot but i can't get it to work. can anyone help as this is very frustrating.

    thanks


  • it you are running xbmc from evox and it's not working then i suspect the xbe of xbmc is corrupt or not present. one of the first things it does is open the log file.


  • try the one that used to come with t3ch (not sure if it still does) - the one that didn't require the .cfg file.

    it's built with the xdk so may be more reliable (it may be a bios related issue)


  • i'm just wondering if any of you checked the logfile that should be genereted when using xbmc's shortcut. or is that not even created?


  • I have been having the exact same problem. I have tried everything, including about 10 different bios. Always the same. I belive it might be the xenium ice modchip that is conflicting with the new shortcut method, because I too have xenium ice modchip and have the same problem.







  • #If you have any other info about this subject , Please add it free.#
    Your name:
    E-mail:
    Telphone:

    Your comments:


    If you have any other info about Shortcut Install Blues , Please add it free.

    Jonas Brothers cd or what? Who's better for Nick Jonas - Miley Cyrus or Selena Gomez?