xboxscene.org forums

Author Topic: Evox And Xblive  (Read 47 times)

lancerx

  • Archived User
  • Jr. Member
  • *
  • Posts: 90
Evox And Xblive
« on: May 19, 2004, 04:09:00 AM »
have you tried locking (unlocked before upgraging)the drive after upgraded with configmagic?, most of the errors are gone after locked and for error 21 in my own experience it was just renaming the xboxdash.xbe again, after you have installed evox have a look in c and tell me what are xbes files that you have.
Logged

mrRobinson

  • Archived User
  • Hero Member
  • *
  • Posts: 1321
Evox And Xblive
« Reply #1 on: May 19, 2004, 04:43:00 AM »
Well it needs to be locked so don't even try with it unlocked.
Logged

hack5t3r

  • Archived User
  • Newbie
  • *
  • Posts: 24
Evox And Xblive
« Reply #2 on: May 20, 2004, 01:38:00 AM »
Ive actually managed to get this working, I am going to have a bit more of a look at it to ensure it works with all versions (at least what I have here !)
Logged

necrodiety

  • Archived User
  • Newbie
  • *
  • Posts: 44
Evox And Xblive
« Reply #3 on: May 20, 2004, 03:01:00 AM »
I use the same thing with xblive.

My files look exactly the same....  but I locked my drive with config magic.

To play live, I just turn the chip off and boot.  msdash comes on and I play online with no probs.
Logged

Xtrem

  • Archived User
  • Hero Member
  • *
  • Posts: 764
Evox And Xblive
« Reply #4 on: May 20, 2004, 04:18:00 AM »
Thats What Happens When You Use Slayers You Don't Get Any Knowledge About Anything So You Get Stuck...

Please Play Safe Don't Use Slayers
Logged

Xtrem

  • Archived User
  • Hero Member
  • *
  • Posts: 764
Evox And Xblive
« Reply #5 on: May 25, 2004, 03:20:00 AM »
Happy For You ! Lol
Logged

lancerx

  • Archived User
  • Jr. Member
  • *
  • Posts: 90
Evox And Xblive
« Reply #6 on: May 25, 2004, 04:29:00 AM »
QUOTE (hack5t3r @ May 25 2004, 11:20 AM)
Dont get any knowledge about anything ?

First of all try learning the correct way to use the english language. Second, I quite clearly said that I use slayers for ease and speed. Third, maybe you should look into someones background before you comment, I work for the biggest games developer in the UK, I am a senior technician, I work on XB, XB2, PS2, GC, GBA, and PC. I use slayers because I have more important things to do than mess around with retail boxes. Maybe if you were surrounded with dev kits, test stations, dual xeon desktops, and G5 XB2 dev stations all day you would just use slayers ? eh ?

Finally, I also posted before I got any helpful answers that I had sorted the problem, so next time you want to start spouting flames at people, try it on someone who wont make you look like a complete tosser.

ouch!!
Logged

chris67rs

  • Archived User
  • Full Member
  • *
  • Posts: 110
Evox And Xblive
« Reply #7 on: May 26, 2004, 05:03:00 PM »
use config magic lock the hd, then choose the backup Eeprom option, go to c and ftp the   files eeprombeforebackup and eepromafterwhatever to your pc, that way you have the key files to fix it in the event your stuff ever totally dies ,

you need to lock any hd larger than stock, because the M$ dash looks for the retail locked drive, if it dont find one then you get an error code 6-13 i believe are all hdd related.

lock it and its good, msdash will load with chip off or on, good to have in case time needs to be set and your drive isnt locked.
Logged

hack5t3r

  • Archived User
  • Newbie
  • *
  • Posts: 24
Evox And Xblive
« Reply #8 on: May 26, 2004, 11:04:00 PM »
The error, I have found out, is because the kernel in the TSOP is the newest one, which wont boot older dashboards. If I replace all the M$ files on the c drive it works, have done this to about 5 boxes now and it works without fail. Slayers must install an older dashboard, funnily enough Firefuckers x-disk does not have this problem, maybe slayers will use the newer dash in the next release.
Logged