Print

[triggernum5]

Just out of curiousity, at the linux prompt (where you type xboxhd etc) if you type:
ls /dev/hda5*
(thats LS in lowercase)
do you get any results? Its a sure fire way to check if your drive is unlocked and being detected on primary master..  
ls /dev/hd*
is what you type if you get no results..  Basically if the drive is unlocked and detected you should see hd?50 to hd?55 where ? is 'a' for primary master, 'b' for p. slave, 'c' for sec. master, 'd' for sec. slave..
As long as its detected somewhere you can mount/access it manually, but xboxhdm needs it to be on hda for the automated script stuff as you probably already know..  

[Andronicus]

Cool.

 I am re-building my Xboxhdm disk with the files from slayers rather than from UXE.  I will also try that list command.

[triggernum5]

slayers is meant for chips in general unless you just wanna rebuild a stock hdd..  If you're going back to stock it can't hurt to try to include UEEE/SCEEE..  Even if you mess that up, the stock dash still works, and if you do it right then you will have ftp access, and can mod with a gamesave installer without owning a mem card or exploitable game since unleashx lets you browse/launch xbe from the hdd..
As far as gamesave installers go, I can verify that my old "Another Gamesave Installer" will work via the method I described..  Krayzie's may or may not, I'm not sure how his scripts run anymore..

[Andronicus]

I just had some time to play around.  The list command gave me nothing (ls /dev/hda), while dev/hda5 gave me an error.  Maybe because I did not type  dev/hda5*.

So if the drive is locked, why does xboxhd say that it is unlocked?

Man, this is fun and educational and all, but the amount of time I have spent on this....

[triggernum5]

If you understand wildcards in any OS you'd realize that if ls /dev/hda yield nothing that only means that there is no "/dev/hda" this might be a good sign if you did mess up with the * since you hope that /dev/hda50 to hda55 exist (not 'hda')..  I would expect 'ls /dev/hda' to yield a result if the hdd was NOT properly unlocked/installed..  Actually, you should see /dev/hdb - /dev/hdz (or something like that) no matter what, but the ONLY thing you care to see is hda50-hda55.. (Basically no numbers means no partitions)..  
To break down the cmdline, you are interested to know what is in the directory /dev/  (ls is like dir) and you can move from directory to directory with 'cd directory', 'cd /', 'cd ..'

[Andronicus]

I had time to play with my box last night.  here is the results of my list command attempts

ls /dev/hda    -->   /dev/hda
ls /dev/hda5  -->   No Such Device
ls /dev/hda5*-->   No Such Device

I also noted that when starting xboxhd, for a briefe second it displays No Such Device, even when it later says that the hard drive is unlocked.

I would have to assume that this means the hard drive is locked?

So....Now the question is why is it not unlocking?

Here is what I have tried.

My xbox has a Western Digital HD if that matters?

Originaly I had the box connected to a TV, and was dissconnecting the drive from the xbox just before the error screen came up.  I tried connecting it to the PC before powering up the PC, at the first menu screen, and at the command prompt.

Now I am doing it headless.  I have tried dissconnecting the IDE cables as the LED turns Red (about 6 seconds after power up), and a few second on either side.  Again, I tried connecting it to the PC before powering up the PC, at the first menu screen, and at the command prompt.

Forgot to mention, that the DVD is dissconected, so I get the good error (12? or is it 16? can't remember).  And I am indeed connecting the harddrive to the PCs primary with with a cable havin no twist (ie. no cable select).  The harddrive is in "Master" mode, not slave, or cable select.  For the Western Digital, that is the jumper removed.

What am I doing wrong?