xboxscene.org forums

Author Topic: Question About Dualboot.xbe  (Read 84 times)

slumberpod77

  • Archived User
  • Hero Member
  • *
  • Posts: 523
Question About Dualboot.xbe
« on: December 24, 2004, 11:19:00 AM »

yo,
I used the NTSC Splinter Cell exploit to get started on a virgin 1.6 box. Everything works well, I just had a question about something.

If I understand correctly the nature of the ltools package, my Xbox is hitting the exploited fonts, which is causing C:\dualboot.xbe to run. from what I can make out via hex viewing, this program checks the DVD drive tray status and runs either

\Device\Harddisk0\Partition1\BiosLD\default.xbe (Tray Closed) or
\Device\Harddisk0\Partition1\UDATA\21585554\000000000000\install.xbe (Tray Open)

Normally for me, the BIOS loader then kicks in and in a few seconds i'm looking at my dashboard. However, I can't manage to get the Xbox to boot with the tray open. I have checked using my launcher to ensure that install.xbe is properly executeable by the system (it is). Even so, booting with the tray open throws me an Error 21 page.

can anybody help me out with understanding this behavior?
Logged

slumberpod77

  • Archived User
  • Hero Member
  • *
  • Posts: 523
Question About Dualboot.xbe
« Reply #1 on: December 26, 2004, 11:14:00 AM »

Whoops. I forgot to specify, I used the ltools package to install UDE2.
Logged

slumberpod77

  • Archived User
  • Hero Member
  • *
  • Posts: 523
Question About Dualboot.xbe
« Reply #2 on: December 31, 2004, 02:28:00 PM »

I solved the issue myself.
In retrospect it was kindof obvious.
My theories seem to be supported by experimentation, so here's what happens during bootup on a softmodded Xbox which has been set up using ltools' UDE2:
-the first executable run by the system is C:\dualboot.xbe
-the program dualboot.xbe looks at the DVD tray status.
if the tray is closed, it executes E:\BIOSLD\default.xbe.
if the tray is open, it executes E:UDATA\21585554\000000000000\install.xbe.
either way, at this point in time the normal Xbox BIOS is running, and thus all xbe files must be properly signed to be executed. attempting to run unsigned executables using dualboot.xbe will cause an Error 21. i had forgotten this crucial detail and was trying to get dualboot to directly run my dashboards.
my solution was to place a copy of the PBL Metoo BIOS loader at both locations. This allows you to test out different BIOS images safely and also you can idiot-proof your Xbox.
This whole thing started when my roommate couldn't figure out how to properly turn on the Xbox. He kept hitting the big Eject button, which caused the box to throw an Error 21 screen every time.
Logged