Print

[Heimdall]

It won't be good enough...... you have to use XBPartitioner 1.1 to format any partition over 256GB, or to make both partitions equally sized and less than 256GB. At the moment you'll probably have F~129GB and G~360GB. The F will be fine, the G has the wrong size clusters so needs to be reformatted.

[xbnubi]

QUOTE(Heimdall @ Apr 7 2009, 06:10 PM)

SID 2.0 is a terrible softmod. Make your new disk with Kingroach NDURE 3.1 instead, and gain all the benefits of a recent, stable softmod.

Make sure that on your PC you have the following files easily to hand:
- the stock 5960 C dash files and folders from Slayers / AID / CASH
- a new set of Kingroach NDURE 3.1 C and E folders. Make these by running Kingroach NDURE 3.1 and simply selecting your Kernel version under "Kernel Selection" and "Create XBOXHDM Installer" - leave all other options at default.

Build your xboxhdm disc using the stock C from Slayers / AID, and the Kingroach NDURE 3.1 files you just made. Put the stock C in linux/C. Rename ndure.htm to ndure (no extension), and place it and the rest of the Kingroach 3.1 files in linux/ndure/, i.e. the Kingroach C and E directories should be in linux/ndure/C/ and linux/ndure/E/, with the ndure script named linux/ndure/ndure. Put eeprom.bin in /linux/eeprom/

Couple of things here (assuming that -all- you've got is a valid eeprom.bin file, and a new blank HD):  

- Is your original kernel relevant when creating C/E with Ndure 3.1, if you're going to be using the new kernel from Slayer's disc?  Should you not select kernel 5960 in Ndure to match Slayer's files?  (is there some sort of firmware issue with the kernel selection as well?)

- you say "...leave all other options at default." (during the Ndure 3.1 install)  The default "Ndure Retail" setting has NOTHING selected but "Core Files".  Is that what you mean, or should you select the other 4 install options as well? (i.e. check: softmod & nkpather options, UDDAE, xboxhdm installer, as well as the Kernel)

- as you corrected later, Slayer's 2.7 does not have an "aid" directory.  You might want to make your quick tip post a full tutorial referring to Slayer's 2.7, as this is the first comprehensive, and understandable, solution I've seen to re-build a new HD without your original backup.



Thanks.

[unmesh]

I'm jumping into this thread because some of the information may be helpful to me but I need further clarification.

I have a Xbox that was softmodded using Krayzie's Ndure installer. In the process of upgrading the hard drive, I copied the eeprom.bin file and the contents of the C and E drives to my PC, created a CD using xboxhdm, booted with it and created a new hard drive. Unfortunately, the Xbox with the newly created hard drive boots to the MS dash instead of the UnleashX dash as the original disk does.

Am I running into the "shadow" problem that was referenced earlier in the thread? If so, what do I do to get the new drive to work just the same as the old one?

Thanks.

[xbnubi]

QUOTE(xbnubi @ Jun 5 2009, 09:10 PM)

Couple of things here (assuming that -all- you've got is a valid eeprom.bin file, and a new blank HD):  

- Is your original kernel relevant when creating C/E with Ndure 3.1, if you're going to be using the new kernel from Slayer's disc?  Should you not select kernel 5960 in Ndure to match Slayer's files?  (is there some sort of firmware issue with the kernel selection as well?)

- you say "...leave all other options at default." (during the Ndure 3.1 install)  The default "Ndure Retail" setting has NOTHING selected but "Core Files".  Is that what you mean, or should you select the other 4 install options as well? (i.e. check: softmod & nkpather options, UDDAE, xboxhdm installer, as well as the Kernel)

- as you corrected later, Slayer's 2.7 does not have an "aid" directory.  You might want to make your quick tip post a full tutorial referring to Slayer's 2.7, as this is the first comprehensive, and understandable, solution I've seen to re-build a new HD without your original backup.
Thanks.

Another thing I noticed:

- The step: "...place it and the rest of the Kingroach 3.1 files in linux/ndure/, i.e. the Kingroach C and E directories should be in linux/ndure/C/ and linux/ndure/E/..." is a bit confusing, and unneeded, as Ndure will do all that for you if you simply point the installer to the: xboxhdm/linux folder.



Thanks again for a good solution.

[ldotsfan]

QUOTE(unmesh @ Jun 6 2009, 09:25 AM)

Am I running into the "shadow" problem that was referenced earlier in the thread? If so, what do I do to get the new drive to work just the same as the old one?

For Krayzie's Ndure, use Krayzie's Extras Professional Mode to ftp the real C drive contents over. Alternatively boot with Frosty's Xbox rescue disc and ftp the contents of C over when you are building the contents of C in xboxhdm iso.

[Bomb Bloke]

QUOTE(xbnubi @ Jun 6 2009, 09:10 AM)

- Is your original kernel relevant when creating C/E with Ndure 3.1, if you're going to be using the new kernel from Slayer's disc?  Should you not select kernel 5960 in Ndure to match Slayer's files?  (is there some sort of firmware issue with the kernel selection as well?)

There's no "kernel 5960". Your kernel version represents the BIOS that gets loaded out of your TSOP chip on the motherboard. Unless you're planning on flashing that TSOP or installing a modchip, your kernel cannot be changed - so the kernel the MS dash says it's using is the kernel you tell NDure you're using.

When installing NDure, you're best off to update your MS dash (which is something completely different) to 5960 before proceeding. Throw in a copy of Halo 2 then attempt to logon to Live. You don't need a network cable or Live account, it should just update the dash. A newer X-Box Live enabled game will also work.

QUOTE(xbnubi @ Jun 6 2009, 09:10 AM)

- you say "...leave all other options at default." (during the Ndure 3.1 install)  The default "Ndure Retail" setting has NOTHING selected but "Core Files".  Is that what you mean, or should you select the other 4 install options as well? (i.e. check: softmod & nkpather options, UDDAE, xboxhdm installer, as well as the Kernel)

Also select your kernel version, and if you're planning on using XBoxHDM... well, I'm sure you can guess what to tick for that. By all means tick the other options if you know what they do and want them, but otherwise leave them unticked.

[Bomb Bloke]

QUOTE(xbnubi @ Jun 6 2009, 11:33 AM)

But I guess the bottom line is that since kernel is related to on-board firmware (not R/W media of any sort), it's probably the best bet that you select the correct version, right?

Technically that firmware IS re-writable, but you need a working softmod to do that (though the softmod can be removed entirely afterwards). This is my preferred method of console modding.

But yes, while using the NDure softmod, it's a good idea to give it the correct firmware info.

QUOTE(xbnubi @ Jun 6 2009, 11:33 AM)

Anyhoo, did the clean HD install with Ndure 3.1 and Slayer's 2.7 and got it working, but I'm still a little fuzzy on whether or not you -need- any of the other Ndure options.  There are other tutorials (http://www.boards.ie/vbulletin/showthread.php?t=2055256404) that suggest you select everything in Ndure 3.1, but as I found out this is actually a bad idea!

The problem lies with inadvertently selecting the  "use Nkpatcher RGB" checkbox, which will seriously screw-up your component HD output!

You certainly do not need, nor usually want, to select all options.

RGB mode, for example, patches the system so that you can use a VGA out (and connect to a computer monitor, for example) - but is useless if you wish to use a TV. Stuff like the clock check is quite pointless due to XBMC/UnleashX's ability to set the time using an internet based server, and the NKPatcher settings regarding partitions layouts are all made redundant in that XBPartitioner overrides them anyway (and you need to use XBP for pretty much all decent sized drives).

There's a PDF file included with Kingroach's NDure 3.1 which explains the other options.

[unmesh]

QUOTE(ldotsfan @ Jun 5 2009, 06:34 PM)

For Krayzie's Ndure, use Krayzie's Extras Professional Mode to ftp the real C drive contents over. Alternatively boot with Frosty's Xbox rescue disc and ftp the contents of C over when you are building the contents of C in xboxhdm iso.

I have an earlier Xbox version with the Thompson optical drive and have not yet been able to get it to read anything from burned media, whether CD-R or DVD+R or DVD-R  

I have found the link for the Extras download and will try that out.

I might also try out the "Clone HD" function in xboxhdm

Thanks much.