Search the Community
Showing results for tags 'thread)'.
I'm moving this topic from: I would do it in a more polished fashion, but I'm not a moderator and don't have the means to do so. ----------------------------------------------------------------- Post 1: In response to what dash I was using. Old ass xbmc 1.1 dude. I actually want to change to evox or maybe xbmc 3.5.3 but I don't know what the previous owner did for the installation on this particular box and i don't want to de-stabilize anything. The dash boots from a mounted (I'm assuming it's mounted) q: partition. X3cl is configured to boot the dash from f:, but the only files present in the root directory are evoxdash.xbe.old and evox.ini... What the fuck? How is this thing even booting? What the hell is going on? I would just do a clean install but i won't have direct pc access for another month or so, so i can't back up. I do have slayer 2.7 and ogxbox 2021 discs. Can i pull it off with those?... Assuming that's even enough info for you to assess the situation! Post 2: Basically, when asked to clarify and provide more details. Kaos, the two files I listed (an .ini and an .old) are literally the only 2 files in the root of f:. There are no valid executables there so i have no idea what the x3 is booting to get me into xbmc. That's my main point of confusion - If the X3 is set to boot the dash from the root of F: and there's no dash executable located there, then how the FUCK is my Xbox booting at all? How can my bios launch a dashboard (the XBMC 1.1.0 I mentioned) that, by all available and tangible evidence, doesn't fucking exist? but it loads, so obviously it exists somewhere) but can't even load a I'll check the logs. The dash priority list in configlive is the default list. When I change to boot from E: a bare unleashx loads with no menu entries (games and emulators are empty) and is useless except for the file browser. Booting from c partition results in a boot loop, even though there is an evoxdash.xbe in the root, which I'm assuming was created as an old shortcut because there are no resource files/folders and trying to load it manually results in a dash restart... This thing reminds me of the house from poltergeist - full of randomness and wormholes and shit. Dave, thank you for confirming. Is it possible that the bios is just resetting the time every time I try to set it with the dash? Edit: Oh for fuck's sake. I can't open the .log file in unleashx because q: is only present when xbmc is running. And when I try to copy the log file from q: to any other partition so I can view it in unleash, xbmc just refuses to do it. For the life of me, I can NOT find the folder that is being mounted to q:, either. My xbox is a fucking sociopath. What the CHRIST? Edit 2: i found softmod install files in udata and some evox dash files in a subfolder of 41560017. So this thing was softmodded at some point in its life. No wonder it's such a mess. Still can't find the real q: directory... Edit 3: I'm able to get UnleashX to boot if I copy the files from the slayer's 2.7 disc to, say, the root of E:. But if I try to get EvolutionX to run by copying files from the same method, it fails to load and triggers a bios default-dash restart. Does the Evox dash have to be run/setup/installed a certain way, or something? I'm able to load any other dash like Avalaunch or XBMC 3.5.3 (if run as an application from a default.xbe). EvolutionX seems to be really touchy in that respect. Ironically, I was able to get the Evox menu from OGXbox (or slayer's, I can't remember now) actual installer to run from the root of E:, but not the one from the Dashes folder of Slayers. Wow. That makes no sense to me. ----------------------------------------------------- SS_Dave's responses to my time issue: -I tested this with a X3cp with the X3 bios and yes the date gets scrambled on each boot where the X2-5035 and Ind 5004 bios didn't reset the date/time I haven't noticed it before as my Xbox's are connected to the home network and the date/time is set automatically. -I tested that with 2 different Xbox's (1.6 and 1.1) and it did the same when booting direct to the dash and not loading the X3 menu 1st and the clock gets scrambled every time but not with the X2 or Ind on the 1.1, The 1.6 gets reset to 1/1/1900 on the Evox dash and 1/1/2000 in the M$ dash every time you power cycle it. It made no difference if the clock as set via the net then unplug the network cable and power cycle then the clock was scrambled or the clock setting in the M$ dash it did the same. When I get bit more time I will test the older versions of X3 bios. My Reply: So my problem is reproducing when you mimic my setup? Glad to know it's not just me. Definitely let me know when you get some time and are able to experiment further. I appreciate it, buddy. Do you have any insight into my dashboard clusterfuck, by chance? I'd appreciate your input on that, if you don't mind.
Board Life Status
Board startup date: April 23, 2017 12:45:48