| QUOTE (bullsh1t @ Dec 3 2004, 08:07 AM) |
the name of the file is boot.cfg, it should be in the root of C or E, and the line you want to take out looks like this
AltRomfile "The name of your bios here"
you want to make it look like this,
# AltRomfile "The name of your bios here" |
It already looks like this???
#AltRomfile xboxrom2.bin
| QUOTE (krayzie @ Dec 4 2004, 09:48 AM) |
| I think you problem might be that you used ltools on your virgin xbox and you only copied your c over to the new drive so therefore when you try to boot with eject it loads an error 21. You can just copy over the ltools gamesave and the error will probably dissapear. |
What is the itools gavesave?
I did copy over C and E.
Any other suggestions?
The "ltools" gamesave is the contents of your original hdd's E:\UDATA\4d530017 folder...the ltools dash (set up as the dual boot dash used when dvd tray is open) is in there. If your new hdd boots to EvoX fine, it shouldn't have a problem booting to the ltools menu as long as it can find the files. Try throwing in your old hard drive and see if it boots to the ltools menu with the tray open. If not, you don't have the gamesave files you need. You can get them in "the usual places". Once you have the UDATA files you are looking for, ftp them to the UDATA folder in E on your new hdd. Reboot with tray open. ltools menu should load.
I get the same Service error screen (21) after an hdd upgrade. Some info:
- version 1.1 box
- K:5838.01, D:5659.03
- Softmod: MA ltools 1.7.5 install, UDE2, PBL-Metoo, EvoX M8
- hdd upgrade to 160gb using http://www.xbox-scene.com/articles/no-modchip-hdd-swap.php (I know, there's probably a better version, I just haven't had time to look around)
- new hdd = Seagate ST3160023A ATA/100
- have full original backups of C and E
- have full modded backups of C and E
- am 100% certain correct hdd lock password was used
- original drive still boots Evox fine
- have tried CS and MSTR jumper settings on new hdd
- have tried diff IDE cable from diff Xbox
- do not have modchip to try (Xenium ICE arriving in 2 days for diff Xbox)
I can't figure out why this isn't working. I've done this on over a dozen Xbox's in the last month. This isn't the first v1.1 I've run into. All of the other's worked like a charm. This one did have a much higher dash version than the rest, but the UDE install breezed through on the original hdd so I don't think that's an issue. I had to go with UDE2 because of the kernel version but that shouldn't matter as I've used it many times. This is the exact same hdd I've used those times and it's never been a problem. Nothing went different at all compared to the other mods.
Some thoughts/possibilities (if you know an answer, please chime in :) ):
- fdisk new hdd and start completely over (or did hex editing the drive muck that up)?
- try a diff hdd (possible, but it takes a few days to get one)? I don't think the hdd is the issue though.
- try Norton Ghost to copy old hdd to new hdd and relock new hdd?
Anyone have any ideas? ThanQ.
| QUOTE (BigDog67202 @ Dec 8 2004, 07:52 AM) |
The "ltools" gamesave is the contents of your original hdd's E:\UDATA\4d530017 folder...the ltools dash (set up as the dual boot dash used when dvd tray is open) is in there. If your new hdd boots to EvoX fine, it shouldn't have a problem booting to the ltools menu as long as it can find the files. Try throwing in your old hard drive and see if it boots to the ltools menu with the tray open. If not, you don't have the gamesave files you need. You can get them in "the usual places". Once you have the UDATA files you are looking for, ftp them to the UDATA folder in E on your new hdd. Reboot with tray open. ltools menu should load.
I get the same Service error screen (21) after an hdd upgrade. Some info:
- version 1.1 box - K:5838.01, D:5659.03 - Softmod: MA ltools 1.7.5 install, UDE2, PBL-Metoo, EvoX M8 - hdd upgrade to 160gb using http://www.xbox-scen...ip-hdd-swap.php (I know, there's probably a better version, I just haven't had time to look around) - new hdd = Seagate ST3160023A ATA/100 - have full original backups of C and E - have full modded backups of C and E - am 100% certain correct hdd lock password was used - original drive still boots Evox fine - have tried CS and MSTR jumper settings on new hdd - have tried diff IDE cable from diff Xbox - do not have modchip to try (Xenium ICE arriving in 2 days for diff Xbox)
I can't figure out why this isn't working. I've done this on over a dozen Xbox's in the last month. This isn't the first v1.1 I've run into. All of the other's worked like a charm. This one did have a much higher dash version than the rest, but the UDE install breezed through on the original hdd so I don't think that's an issue. I had to go with UDE2 because of the kernel version but that shouldn't matter as I've used it many times. This is the exact same hdd I've used those times and it's never been a problem. Nothing went different at all compared to the other mods.
Some thoughts/possibilities (if you know an answer, please chime in ): - fdisk new hdd and start completely over (or did hex editing the drive muck that up)? - try a diff hdd (possible, but it takes a few days to get one)? I don't think the hdd is the issue though. - try Norton Ghost to copy old hdd to new hdd and relock new hdd?
Anyone have any ideas? ThanQ. |
E:\UDATA\4d530017
I don't have this directory in E:\UDATA...
All I have is the following directories:
00004321
00170015
4d530028
Do you think this is why I'm receiving the error message? and is this folder available at the "usual place"?
Thanks
Yes, I would say that's why you're receiving the error message. The file is available in "the usual places" (I think under Operating Systems\Linux\...). It's "ltools_v_1_7_5.zip" or something like that. There is one for 007 and one for MA. I used MA to do the UDE install. Choose whichever one you need. Unzip, open UDATA, there's 4d530017 (for MA...007 UDATA folder will be a different name but have the same files). If you already have a UDATA folder named the same as what is in the 007 ltools package, check your hdd to see if the files on there are the same as the files in the package. If not, use the files in the package (ftp to hdd). If you have to, re-run your UDE installer (pop in 007 or MA, run Campaign -> Run Linux) and you should be good to go for dual booting.
| QUOTE (BigDog67202 @ Dec 8 2004, 08:54 AM) |
| Yes, I would say that's why you're receiving the error message. The file is available in "the usual places" (I think under Operating Systems\Linux\...). It's "ltools_v_1_7_5.zip" or something like that. There is one for 007 and one for MA. I used MA to do the UDE install. Choose whichever one you need. Unzip, open UDATA, there's 4d530017 (for MA...007 UDATA folder will be a different name but have the same files). If you already have a UDATA folder named the same as what is in the 007 ltools package, check your hdd to see if the files on there are the same as the files in the package. If not, use the files in the package (ftp to hdd). If you have to, re-run your UDE installer (pop in 007 or MA, run Campaign -> Run Linux) and you should be good to go for dual booting. |
This worked perfectly!!!!! Thanks for your help!!!!
Excellent. Glad to hear it. I got mine fixed as well. Just popped in the SlaYer's 2.6 Auto Installer, ran the Full Install to Retail option, re-did the UDE, re-ran the No Modchip Hdd Replacement tut, popped the new hdd in and walla(!) it booted up.
Now, if only I can get my dead box that I tried to solder on working with the Xenium ICE when it arrives...