Post by: luther349 on July 09, 2003, 05:59:00 PM
Post by: Cain on July 09, 2003, 06:13:00 PM
If we find out what its supposed to do when the battery dies it will be easier to find out what exactly is causing the problem and fix it.
I would do it myself but if someone else is willing to do it i wont have to remove the files to return it to normal, test, then go through the hastle of putting it back on again.
Post by: Machster73 on July 09, 2003, 07:02:00 PM
I can do that. I'll reply here in the morning. Hope it helps.
Post by: afon on July 09, 2003, 07:11:00 PM
Post by: JacksRagingBileDuct on July 10, 2003, 07:57:00 AM
works with the exploit. I regularly have this happen (past two nights in
a row). RonJeremey speculated it had to do with leaving the unit on (while
trying to reboot) until a minute passed such that the time was no longer
the reset time (e.g. 12:01 to 12:00). I tested this this morning, watched my
watch and, sure enough, in a minute and change, I was no longer cycling and
sitting in the Complex!Loader menu.
Instead of going into Evox (which synchs time from SNTP) I rebooted and
this is weird, I was back in the xbox-cycle loop. Oddly, after a minute of
rebooting, it was okay again. Something about Complex!Loader must
drop the time if it isn't set? Not sure, but whatever it is, it's far from fatal.
You just need patience on your first boot.
With ComplexLoader 1.1 fixing the DVD-ROM/reset issue (tested and confirmed)
this is a really great solution if you have kernel 4034
Post by: Machster73 on July 10, 2003, 08:12:00 AM
So you think that Complex Loader has fixed the clock reset problem? Is this true? I know there are still alot of people whose XBOXs just stay in the continuous loop.
I guess since the time never went to 12:01 for me (on my virgin XBOX) then it would be fair to say that it MIGHT be something written into the Complex!Loader code?
Quick Poll: Of everyone out there whose XBOX has been caught in the loop, How many used Complex!Loader, and how many didnt? Of those who used Complex Loader, How many can remedy the problem by simply letting it reboot until it comes up?
Post by: JacksRagingBileDuct on July 10, 2003, 08:34:00 AM
I do *not* think that complex fixed the problem. I'm of the opinion that
the "problem" fixes itself if you let the box keep trying to boot for a minute
no matter which hack you're using.
Post by: Machster73 on July 10, 2003, 08:39:00 AM
Post by: JacksRagingBileDuct on July 10, 2003, 09:10:00 AM
to test that pretty easy.
Post by: Cain on July 10, 2003, 09:12:00 AM
I think this prooves what i feared.
The clock doesnt get set to a default value, not by the BIOS or the dashboard.
The only way the clock gets set is when you enter the time from the dash.
When the power is off the clock still ticks meaning that if it did get set to a time which triggers the "set clock" screen when its plugged in, in one minute it would no longer be at that invalid time
Hopefully when BenJeremy and Cherry have looked at the kernel they can say conclusively whether the dash HAS to be launced prior to any xbe being launched if the time is not set.
I no longer think this is the case considering the clock is not set to a default value it can hardly progress to a later time. So something else must be happenning to kick people out of the loop (or the loop is caused by something else).
JacksRagingBileDuct: when you get kicked out of a loop what time does box say it is?
I think its more likely that when a program asks for the time and it is not set the kernel tells the dash to load so the time can be set. And the loop is occurring because of a (possibly related but) different problem.
I've been using the font exploit since it was released and regularly have problems booting it, sometimes it just hangs at the mesh from the original dash, sometimes it doesnt get that far sometimes it goes on a reboot cycle (which only lasts a couple of boots before working). When i turn it on with the eject button it works most of the time.
The continual rebooting may just be due to having EvoX launch the dash when the time needs resetting, if you launch any other program on boot (that doesnt try to set the time via the dash or if you set EvoX to not launch the dash) e.g. Complex !Loader then the problem may be avoided.
I think the hack just needs a little refinement, as has been said it is just a proof of concept at the moment and will improve, a bit of documentation would have been useful but i'm sure people are managing without it.
But this little test and the fact that people have managed to escape the loop makes me think the time reset "bug" isnt such an issue.
Still it needs more investigation.
Edit: You're right Machster73 a poll would be a good idea. It needs to be known what is causing ths behavior.
Post by: JacksRagingBileDuct on July 10, 2003, 09:18:00 AM
I wonder if this "bug" was fixed in later bios versions . . .
Post by: Machster73 on July 10, 2003, 09:18:00 AM
Good point Jack, what version is yours? Mine is a v1, 4043.
Post by: Cain on July 10, 2003, 09:34:00 AM
| QUOTE (JacksRagingBileDuct @ Jul 10 2003, 05:18 PM) |
| 12:01am |
what app are you using to tell the time?
are you going by what !Loader says or launching something else.
Post by: ylsf on July 10, 2003, 10:38:00 AM
Will post my results tommorow
Post by: Machster73 on July 10, 2003, 11:33:00 AM
Anybody else wanna try?
Post by: spIdeZ on July 10, 2003, 01:20:00 PM
