xboxscene.org forums

OG Xbox Forums => Modchip Forums => Team Omega Chips (DuoX) => Topic started by: gjm on February 28, 2006, 11:27:00 AM

Title: Duo X2 Not Booting To Ms Dash
Post by: gjm on February 28, 2006, 11:27:00 AM

You will not be able to boot the retail BIOS unless you have locked your hard disk. Have you locked it?

Some BIOSes assign the first 137gig to F, and the rest to G. This is probably what has happened in your case - have you formatted G?

Title: Duo X2 Not Booting To Ms Dash
Post by: Julius Pleaser on February 28, 2006, 11:33:00 AM

Gjm nailed it.

Until you lock the HD, your Xbox will not boot with the chip off.  And depending on the bios, you either need to format G to get the rest, upgrade the bios if it is old (unlikely), or edit the bios to tell it not to use the G drive (ie put all to F) as some will allow.

Title: Duo X2 Not Booting To Ms Dash
Post by: gjm on February 28, 2006, 06:28:00 PM

Can you verify the files are intact on the C drive for the MS dashboard? Perhaps you can compare against the backup you took of your original HD's C drive. Look for xboxdash.xbe amongst others.

Not sure other than that..

Title: Duo X2 Not Booting To Ms Dash
Post by: Julius Pleaser on February 28, 2006, 08:17:00 PM

that is your problem there.   you renamed evoxdash.xbe to xboxdash.xbe.  So it is trying to load EvoX when you boot with the chip disabled..... and EvoX is unsigned code.  I would suggest using either SLayers or AID to just rebuild the MS dash.

Title: Duo X2 Not Booting To Ms Dash
Post by: gjm on March 01, 2006, 04:27:00 AM

Yeah, there was no need to rename evoxdash.xbe - the hacked BIOSes will try to run evoxdash.xbe before they try xboxdash.xbe anyway. Xboxdash.xbe must be the unmodified MS dash if you want the retail BIOS to boot it.