| 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!!
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.
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.