Topic: Disable Eject Fix For X2 Bios' (Read 632 times)

heinrich · « **Reply #60 on:** January 29, 2004, 06:36:00 PM »

QUOTE

How many of you are mad at EvoX for having such a crappy BIOS by today's standards? How many of you are mad at EvoX for not releasing M8 to include some of the advancements Xecuter has made with their BIOS?

I'm not.

QUOTE

Or how about this... let's get mad at Matrix for not having the foresight to see this coming and making such a ridiculous mechanism to disable their ancient chip.

You missed the code that xecuter released to do the SAME EXACT THING didn't you?

But see, I know the CHOICE of eject fix is important to a lot of people. As soon as the evox forums are back up, I'll take a screenshot of the thread where the m7 bios was released to beta testers. My first question was something to effect of "are you going to release a EF and non-EF version, a lot people like that choice".
And btw, m7 was hardly 'crappy' when it was released, it was the only bios that supported the focus chipset, and the only thing lacking was IGR, which is provided by the evox dash.
I don't have a matrix, and prefer eject fix - but does that mean others feel the same? no.

If it is as simple as for Ubergeek to comment out some code and recompile - yes, I feel people have the right to ask for a non-ef version. It seems that uber is just to damn lazy to do it, as he has the x3 chip/bios to work on (the one that was supposed to be released 6 months ago).

chelrob · « **Reply #61 on:** January 29, 2004, 07:54:00 PM »

QUOTE (heinrich @ Jan 29 2004, 08:36 PM)

QUOTE

How many of you are mad at EvoX for having such a crappy BIOS by today's standards? How many of you are mad at EvoX for not releasing M8 to include some of the advancements Xecuter has made with their BIOS?

I'm not.

QUOTE

Or how about this... let's get mad at Matrix for not having the foresight to see this coming and making such a ridiculous mechanism to disable their ancient chip.

You missed the code that xecuter released to do the SAME EXACT THING didn't you?

But see, I know the CHOICE of eject fix is important to a lot of people. As soon as the evox forums are back up, I'll take a screenshot of the thread where the m7 bios was released to beta testers. My first question was something to effect of "are you going to release a EF and non-EF version, a lot people like that choice".
And btw, m7 was hardly 'crappy' when it was released, it was the only bios that supported the focus chipset, and the only thing lacking was IGR, which is provided by the evox dash.
I don't have a matrix, and prefer eject fix - but does that mean others feel the same? no.

If it is as simple as for Ubergeek to comment out some code and recompile - yes, I feel people have the right to ask for a non-ef version. It seems that uber is just to damn lazy to do it, as he has the x3 chip/bios to work on (the one that was supposed to be released 6 months ago).

Yes, nobody is mad at EvoX, including me. That was my point. It would be ridiculous do be mad at them for being inferior to X2. But you're all mad at X2 for not providing NO EF, like M7 does.

You take things out of context. It's not fair to dissect my last post and reply to select lines because the meaning is now lost. I was purposely being outrageous to make my point. My questions were rhetorical at best. I was attempting to inspire critical thinking, outside of the box.

Lets just agree to disagree.

chelrob · « **Reply #62 on:** January 30, 2004, 10:24:00 AM »

QUOTE (NghtShd @ Jan 29 2004, 09:04 PM)

QUOTE (dee_ss @ Jan 29 2004, 09:54 PM)

is x2 4977 the same as x2 4976.02? if so, then this data should be different there. if only i knew where to start looking at...?

Probably at offsets 0x80031350 - 0x8003136B (4976.02) and 0x80031352 - 0x80031358 (4977).

Looks like that could be the spot (or at least a start).

CODE

4976_80031350:
cmp ebx, esi
jb short 0x80031333
push [ebp+arg_4]
call HalEnableTrayEjectRequiresReboot
test al, al
jz short 0x80031370
cmp byte ptr [ebp+arg_4], 0
jnz short 0x80031370

80031366:
mov edi, 0C000003Ah
jmp 0x800314E5

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

4977_80031352:

cmp ebx, esi
jb short 0x80031335
push 1
call HalEnableTrayEjectRequiresReboot

Can you take the last X2 release that had both EF and NO EF versions and dump, disassemble and compare the two for the difference in bits? Would that not give you the chunk of code causing the No Reset On Eject?

Or compare M7 EF and M7 NO EF.

heinrich · « **Reply #63 on:** January 30, 2004, 12:32:00 PM »

QUOTE

Can you take the last X2 release that had both EF and NO EF versions and dump, disassemble and compare the two for the difference in bits? Would that not give you the chunk of code causing the No Reset On Eject?

There was never such a release.
The only thing in the changelog from 4976.02 -> 4977 is eject fix, but there is quite a bit off extra code in 4977 to just be eject fix.

chelrob · « **Reply #64 on:** January 30, 2004, 12:58:00 PM »

How aboout M7 Vs. M7 EF?

NghtShd · « **Reply #65 on:** January 30, 2004, 01:31:00 PM »

X2 4981 reset on eject is working, too. Its doing a cold boot when you eject, though, which is why the tray goes back in. You can immediately press the button and get it back out, thoguh. It also reboots in the dash, which isn't exactly as planned. I'm not sure if these problems can be easily overcome, but I'm still twiddling bits.

simonx314 · « **Reply #66 on:** January 30, 2004, 01:46:00 PM »

QUOTE (NghtShd @ Jan 30 2004, 11:31 PM)

X2 4981 reset on eject is working, too. Its doing a cold boot when you eject, though, which is why the tray goes back in. You can immediately press the button and get it back out, thoguh. It also reboots in the dash, which isn't exactly as planned. I'm not sure if these problems can be easily overcome, but I'm still twiddling bits.

great progress, thanks for the hard work

heinrich · « **Reply #67 on:** January 30, 2004, 02:14:00 PM »

QUOTE (NghtShd @ Jan 30 2004, 06:31 PM)

X2 4981 reset on eject is working, too. Its doing a cold boot when you eject, though, which is why the tray goes back in. You can immediately press the button and get it back out, thoguh. It also reboots in the dash, which isn't exactly as planned. I'm not sure if these problems can be easily overcome, but I'm still twiddling bits.

woo hoo
great work

NghtShd · « **Reply #68 on:** January 30, 2004, 03:19:00 PM »

Update:

The cold boot issue is solved. The thing still reboots when you hit eject with the dash is running. I'm just wondering if this would be considered a serious problem. I'll keep looking at it, but if I don't fix that issue soon and people think this is good enough I'll go ahead and release it as is.

skorchir · « **Reply #69 on:** January 30, 2004, 03:58:00 PM »

NghtShd · « **Reply #70 on:** January 30, 2004, 04:11:00 PM »

There's a rather expensive dissasembler called IDA, but they also have a free version. I used nasm and it's companion dissassembler for the actual coding and hex workshop for hexing.

NghtShd · « **Reply #71 on:** January 30, 2004, 06:56:00 PM »

There's a new XBtool beta (1.0.18.b1) which will add reset on eject to 4981.xx kernels. I've tested it and not had any problems, but I'm calling it a beta release and I advise caution.

One thing to note, your xbox will reboot on eject even when the dash is loaded. I think matrix users want this for toggling the mod, so maybe that's not really a bad thing, I don't know.

dee_ss · « **Reply #72 on:** January 30, 2004, 07:11:00 PM »

awesome...

Memnock · « **Reply #73 on:** January 30, 2004, 09:42:00 PM »

QUOTE (NghtShd @ Jan 31 2004, 04:56 AM)

One thing to note, your xbox will reboot on eject even when the dash is loaded.

Yeah I noticed that and can't say I care for it. Is there any way of making it so that it resets on eject in a game, but not in the dashboard or XBMC/XBMP? Now it resets on eject whenever you press the button.. that kind of sucks. Had to roll back my bios.

Psilocybe · « **Reply #74 on:** January 30, 2004, 11:00:00 PM »

QUOTE (skorchir @ Jan 31 2004, 01:58 AM)

hey nghtshd just wondering what u used to decompile the kernel. you got any special tools or recommended apps for modding, debugging, and/or developing bios roms ? i take lots of interest

win32dasm isn't too shabby either

QUOTE

Yeah I noticed that and can't say I care for it. Is there any way of making it so that it resets on eject in a game, but not in the dashboard or XBMC/XBMP? Now it resets on eject whenever you press the button.. that kind of sucks. Had to roll back my bios

bitch for a reset on eject, then bitch once they get it, you really can't win

QUOTE

One thing to note, your xbox will reboot on eject even when the dash is loaded.

does this mean any prog or just the dashboards?
if any prog (including the ones that have the no reset on eject such as xbmp and pxhdd and such) does than this is almost pointless to have. if you put a disk in and turn on the system it will boot the disk. if you turn it on then try and put the disk in it will reset. since it's a cold boot it will then load up the disk. thus making it impossible to actually rip a game or play a cd or dvd.

Author Topic: Disable Eject Fix For X2 Bios' (Read 632 times)