xboxscene.org forums

Author Topic: Problem  (Read 68 times)

danania1

  • Archived User
  • Newbie
  • *
  • Posts: 35
Problem
« on: August 01, 2004, 12:31:00 AM »

I recently installed a 160 gig harddrive in an xbox, booted up with the slayers cd (using a matrix chip), and had no problems, formatted the drive and installed evox and everything went smoothly.  now when i try to boot up the xbox without the modchip in, i get error 5 (hdd unlocked). which is normal, i know i need to lock the harddrive in order to boot to the MSDash.  However, this is the problem.  I can boot to the MSdash when the modchip is in.  I am positive that it loads the matrix bios for 2 reasons... The X logo is blue and if it wasnt loading the matrix bios then the xbox wouldnt boot because the hdd is not locked.  Now my question is this, why does it load to the MSDash and not EvoX? And how can I fix this so I can launch Evox?  What I think is happening is that it is booting MSDash instead of evoxdash, but even so, how will i get about to fixing this? It refuses to launch the slayers cd for some unknown reason.  It just says its an invalid disk within the MSDash is booted up.  So if I cannot use my slayers CD to access my hdd via FTP to fix the booting problem, and I cannot use the slayers cd to reformat the hdd, then what am I to do?  Any help woudl be most appreciated.  The only other thing that I can think of is because im not using a 137gb+ bios.  But wouldnt this just limit the 160 gig to 137 gig? It wouldnt reject it from booting up all together would it?  Thanks.
Logged

Exzir

  • Archived User
  • Full Member
  • *
  • Posts: 248
Problem
« Reply #1 on: August 02, 2004, 05:12:00 PM »

Hey,

I think that the bios was programed wrong or the evoxdash was named wrongly.  

First off check the saves or memory area delete anything that might seem odd.  Secoundly if you can not boot the slayer disk from boot (before entering into the msdash) then remake the disk incase it is a none reading disk error.  I have had plenty of thouse with dvd+r disks.  If this still fails then get an exploit like the Mech Ass.  one and use that to ftp into your xbox to corect the evoxdash nameing.

Get a program to break the bios down and see what boot order everything is.  Insure the evoxdash xbe is correcly choosen.

Also last but not lease since the drive is not locked you can hook it up to a computer and get a program that will access it in the os and correct it from there.
Logged