Search the Community
Showing results for tags 'date'.
Found 3 results
Date Settings Reset ProblemHi, I soft-modded my Xbox (1.6) some years ago (I think 5) with SID 12. The soft-mod main dashboard is UnleashX. I moved it (the 3 files) from E:\ to E:\Apps and installed XBMC4XBOX in E:\ making it as my main dash (with a shorcut.xbe). On the HW side I replaced the IDE cable with a 80 wires one and installed a SATA III 2,5" Barracuda HDD (connected with the Sabrent ide to sata board. HDD blocked with a 2,5" to 3,5" mount) I installed a lot of Xbox games and emulators, never had a single problem but this one: Since the beginning it keeps resetting the time zone (it happened very often). I always set it again, in all 3 dashboards (UnleashX, XBMC and the original Dash) but it keep resetting. I remember when updating to the last XBMC version, it seemed to reset less often, but i can't tell for sure. I was some good amount of months (maybe a year) without using the Xbox and when I came back to use it I noticed the problem is changed. Now it reset all the date settings to 1 January 2007 (ironically the time zone seems to keep the settings now). The Xbox is always connected to the A/C power. I think it's a software related problem, because it seems to reset depending on the date. I gave up on manually re-setting the correct date and leaved it as it was. It never reset anymore. It started on 1/1/2007. It's been a months now and date keeps going corectly (If I set the actual current date, after one or two rebooting at max, it resets). For curiosity I checked the last @Rocky5 installer to see what has changed in the last 5 years (I have a lot of installers, old stuff though). I noticed this note about main Features: Clock auto set to 01/01/2019 (No more clock loops) It can be something related to my problem?? I want to specify that I'm really good with my old SID 12 softmod, everything works 100% perfectly aside the above mentioned issue and i'm not even sure it is related to the soft-mod or to the fact I moved UnleashX files or something else. So, there's a way to solve it, maybe changing some settings, replacing files?? Otherwise, if it's a issue not solvable on my old soft-mod, I could consider to update it with the new 1.1.7 installer (hoping to not damage anything). If you need more infos just ask, thank you and sorry for the bad english.
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.
1.6 XBox Not Keeping Date and Time?
Hector Hidalgo posted a topic in RepairSo yes guys, that is my question. What's up with my Xbox? It is not keeping the time and date, not only if I unplug it, but only if I turn it off and then on again, it goes back to 2004 Things is, I have a 1.6 version of the Xbox, with Hynix Ram, softmodded. And I looked for any battery and there is no battery, it has a yellow capacitor that it supposed to keep the date and time. And it is in great looking condition, but what's wrong? Why is not keeping the time? Could I fix it? I am leaving a picture of my motherboard. Thanks for any feedback!
Board Life Status
Board startup date: April 23, 2017 12:45:48