Print

[ldotsfan]

QUOTE(ldotsfan @ Jun 28 2008, 11:43 AM)

I'll need to see if the master password can unlock the hdd.

1. It's true when you lock your hdd with EvoX, it also sets the master password to TEAMASSEMBLY.
2. I was unable to use xboxhdm option 3 to recover as that expects a hexadecimal password.
3. Xboxhdm option 4 didn't work for me as somehow ATAPWD couldn't detect the hdd.
4. In the end I use MHDD to unlock the hdd with the master password successfully.

Back to my experiments:

1. I replaced EvoX with ConfigMagic and was successful in locking the new hdd.
2. The timer.xbe wasn't necessary as long as you let the new hdd boot up to an error 5 first to get it ready and then keep the power on.
3. The BFM bios xbe or vanilla unleashx.xbe also didn't seem to matter.

In other words, we have a working boot disc for softmods to do hdd upgrades - but it requires additional equipment (the hdd power source). I'll try to document all the steps in a separate thread now so that somebody else can check my work and verify it really works.

[Bomb Bloke]

Awesome! So the problem wasn't the console expecting the old drive to be plugged in, it was the new drive not receiving any "wake up" messages since it wasn't present for the boot process. I didn't figure out what you meant when you first described what you were gonna test.

Well done!  

QUOTE(ldotsfan @ Jun 29 2008, 01:57 AM)

1. It's true when you lock your hdd with EvoX, it also sets the master password to TEAMASSEMBLY.

I gather that older versions don't use the password. I have no idea as to which will and which won't, let alone how many old versions are floating around with for eg. softmod installers.

[ldotsfan]

QUOTE(Bomb Bloke @ Jun 29 2008, 09:58 PM)

Awesome! So the problem wasn't the console expecting the old drive to be plugged in, it was the new drive not receiving any "wake up" messages since it wasn't present for the boot process. I didn't figure out what you meant when you first described what you were gonna test.

Well done!  

Thanks..I finally figured out the code to do the 'wake up' call for the new hdd:

CODE

MOV DX, 1F7h;status register
LOOP1:
IN AL, DX;sets AL to status register (which is 8 bits)

;If the first bit of the status register (BUSY) isn't 0, the device is busy,
;so keep looping until it isn't.

AND AL, 10000000b
JNE LOOP1

MOV DX, 1F7h;status register again
LOOP2:
IN AL, DX;sets AL to status register again

;If the second bit of the status register (DRDY) isn't 1, the device isn't
;ready, so keep looping until it is.

AND AL, 01000000b
JE LOOP2

;----------------------------------------------------------------------------

MOV DX, 1F6h;device/head register
MOV AL, 0;0 selects device 0 (master). 10h would select device 1 (slave).
OUT DX, AL;selects master device

MOV DX, 1F7h;command register
MOV AL, 08h;"DEVICE RESET" command
OUT DX, AL;sends the command!

I'll have to wait for the weekend to actually try this. If it works, we can get rid of the external power source and then we have a complete boot disc

[ldotsfan]

QUOTE(ldotsfan @ Jul 1 2008, 11:25 PM)

I'll have to wait for the weekend to actually try this. If it works, we can get rid of the external power source and then we have a complete boot disc

Error 21 after hotswap and IDE reset XBE. So external power source for new hdd still needed

[Bomb Bloke]

Reckon the X-Box's own PSU could take on both the drives at once with a molex splitter? Bit of a reach maybe...

[ldotsfan]

The PSU has enough juice to power 2 hdds (that's how chimp26 works) but it won't work. We are using an error 5 to 'ready' the new hdd and the only way to 'recover' from that is to power down and hence cutting power to the new hdd - back to square one. The only way I can think of and works is to cheat by using an external power so that the new hdd is woken up and stays that way until we reconnect the IDE cable away at the second hotswap.

[Bomb Bloke]

Argh, I'm a fool. Shoulda realised.