Print

[Yuyu]

[BenJeremy]

Interesting.... must be a weird thing with the way the Matrix works.

Cool, though!

[nObedienz]

[Xeero]

QUOTE (BenJeremy @ Jul 30 2003, 08:41 PM)

Interesting.... must be a weird thing with the way the Matrix works. Cool, though!

I wonder if the soft eject triggers the Matrix to load the MS BIOS, which in turn doesn't allow the unsighed eject.xbe (or whatever the filename is) to finish executing.

[BenJeremy]

QUOTE (Xeero @ Jul 30 2003, 10:02 PM)

QUOTE (BenJeremy @ Jul 30 2003, 08:41 PM) Interesting.... must be a weird thing with the way the Matrix works. Cool, though! I wonder if the soft eject triggers the Matrix to load the MS BIOS, which in turn doesn't allow the unsighed eject.xbe (or whatever the filename is) to finish executing.

Well, "eject.xbe" would be MXM, in this case, but no, there shouldn't be a BIOS change in midstream.

[Xeero]

QUOTE (BenJeremy @ Jul 30 2003, 10:12 PM)

QUOTE (Xeero @ Jul 30 2003, 10:02 PM) QUOTE (BenJeremy @ Jul 30 2003, 08:41 PM) Interesting.... must be a weird thing with the way the Matrix works. Cool, though! I wonder if the soft eject triggers the Matrix to load the MS BIOS, which in turn doesn't allow the unsighed eject.xbe (or whatever the filename is) to finish executing. Well, "eject.xbe" would be MXM, in this case, but no, there shouldn't be a BIOS change in midstream.

Well, what I meant was perhaps it momentarily cycles the power (that's how the Matrix's eject trick has always switched BIOSes), which doesn't allow eject.xbe to finish.

[BenJeremy]

QUOTE (Xeero @ Jul 30 2003, 10:14 PM)

QUOTE (BenJeremy @ Jul 30 2003, 10:12 PM) QUOTE (Xeero @ Jul 30 2003, 10:02 PM) QUOTE (BenJeremy @ Jul 30 2003, 08:41 PM) Interesting.... must be a weird thing with the way the Matrix works. Cool, though! I wonder if the soft eject triggers the Matrix to load the MS BIOS, which in turn doesn't allow the unsighed eject.xbe (or whatever the filename is) to finish executing. Well, "eject.xbe" would be MXM, in this case, but no, there shouldn't be a BIOS change in midstream. Well, what I meant was perhaps it momentarily cycles the power (that's how the Matrix's eject trick has always switched BIOSes), which doesn't allow eject.xbe to finish.

OK, yeah, some sort of power cycle (required to cause a Flash reload), but th einterruption is because of the reboot, not really the lack of a valid signature on the part of the app running at the time of the reboot.  

[Xeero]

QUOTE (BenJeremy @ Jul 30 2003, 10:22 PM)

QUOTE (Xeero @ Jul 30 2003, 10:14 PM) QUOTE (BenJeremy @ Jul 30 2003, 10:12 PM) QUOTE (Xeero @ Jul 30 2003, 10:02 PM) QUOTE (BenJeremy @ Jul 30 2003, 08:41 PM) Interesting.... must be a weird thing with the way the Matrix works. Cool, though! I wonder if the soft eject triggers the Matrix to load the MS BIOS, which in turn doesn't allow the unsighed eject.xbe (or whatever the filename is) to finish executing. Well, "eject.xbe" would be MXM, in this case, but no, there shouldn't be a BIOS change in midstream. Well, what I meant was perhaps it momentarily cycles the power (that's how the Matrix's eject trick has always switched BIOSes), which doesn't allow eject.xbe to finish. OK, yeah, some sort of power cycle (required to cause a Flash reload), but th einterruption is because of the reboot, not really the lack of a valid signature on the part of the app running at the time of the reboot.

Yeah, I kind of changed theories "midstream".  

[BenJeremy]

QUOTE (Xeero @ Jul 30 2003, 10:23 PM)

QUOTE (BenJeremy @ Jul 30 2003, 10:22 PM) QUOTE (Xeero @ Jul 30 2003, 10:14 PM) QUOTE (BenJeremy @ Jul 30 2003, 10:12 PM) QUOTE (Xeero @ Jul 30 2003, 10:02 PM) QUOTE (BenJeremy @ Jul 30 2003, 08:41 PM) Interesting.... must be a weird thing with the way the Matrix works. Cool, though! I wonder if the soft eject triggers the Matrix to load the MS BIOS, which in turn doesn't allow the unsighed eject.xbe (or whatever the filename is) to finish executing. Well, "eject.xbe" would be MXM, in this case, but no, there shouldn't be a BIOS change in midstream. Well, what I meant was perhaps it momentarily cycles the power (that's how the Matrix's eject trick has always switched BIOSes), which doesn't allow eject.xbe to finish. OK, yeah, some sort of power cycle (required to cause a Flash reload), but th einterruption is because of the reboot, not really the lack of a valid signature on the part of the app running at the time of the reboot.   Yeah, I kind of changed theories "midstream".

I think you just want to up your post count to hit 6000+