Print

[paradoxmime]

Ok, hours have turned into days and I feel I have tried everything. Using a sata card with non-raid drivers, I have connected the ts-h943 drive and it won't recognize in windows or dos. Just to verify that the sata card is working properly, I connected my other hitachi drive and it sees it both ways.

Now, I have used xtremebootmaker program to create a modified mtkflash to use the sata card. Created a bootable diskette and copied all the necessary files.

I have tried booting to the disc with the xbox powered and it hangs in the boot screen when my sata controller searches for devices. The only way to actually boot to my diskette is to leave the xbox unplugged and turned off till I reach the a: prompt

I have tried running the mtkflash while the drive is disconnected and then after pressing esc key, I power it on to run samread xxxxxxx xxxxx

I get to choose which drive 1,2,3

Neither one recognizes the drive, it just hangs till I press esc

What am I missing? If I use my hitachi drive in mode b, it is seen. However, I don't plan to flash it since it is already flashed. I know from reading that there is no mode b with the ts-h943. Is that correct?

[Exobex]

What's the chip on the SATA card?

[langnao]

What is your SATA chipset and what is your samsung drive model (ms25, ms28)?

[paradoxmime]

I believe the chipset on the sata card is intel. AT least that is what I remember seeing at POST. It's a Silicon Image card if that matters. The drive model is ms25

This post has been edited by paradoxmime: Nov 28 2006, 06:55 AM

[selivus]

Try powering the xbox when the screen for mtkflash says "starting" right before the A: prompt shows up... I don't use samread, though, i use a modified mtk the old fashioned way... hope it helps, works on my board.

[Textbook]

Try both ports on the card as well, and maybe a shorter SATA cable if you can.  Also, make sure both power and video cables are plugged into the 360.

[langnao]

QUOTE(paradoxmime @ Nov 28 2006, 01:18 PM)

I believe the chipset on the sata card is intel. AT least that is what I remember seeing at POST. It's a Silicon Image card if that matters. The drive model is ms25

All the silicon image, SIL 3112, SIL3122, SIL3512, etc does not work with flashing of samsung drive. Quit trying. Try another SATA port for another computer. If you wanna do it on PCI card, get a VIA6421L ...

[Textbook]

Ahh, I didn't see that in his post.  Good eyes langnao.  He's right, that card will never work.

[bigghek]

wow!

[paradoxmime]

Ok, I decided to scrap the controller card and opened up my pc at work using XP64bit windows. Turned on the onboard sata and selected IDE in the BIOS. Then I booted to dos and turned on the XBOX while the status "STARTING..." displayed. Everything worked finally. My only problem was with the xtremebootmaker 3.1 program. The version I downloaded does not work completely. Firstly, it doesn't create a msdos startup disk. I had to do that using windows/format. Secondly, it doesn't automatically create a hacked.bin file. I created it manually using x360sam. After creating, booting back and forth from dos to windows, and manually moving files to the correct dir's, it finally flashed everything and all works well. I have noticed that the samsung drive works so much better "quicker" at reading the discs than my hitachi. Also, I have had no problems burning the disks at 16x and playing them. I have been burning them cautiously at 2.4x

One last note, it seems that using my hitachi drive via hotswap method, produces better results in boot time versus using my Plextor. It rips half the speed is my guess. I haven't yet used the samsung to backup.

Also, this may be needed as a new post but I have issues using the gary-opa 2.3 firmware to extract the ss.bin. It seems the stealth mode keeps me from getting the security sector. I found the 2.1 firmware to work doing this but 2.1 will not boot any discs while in the xbox. It spins then stops then spins again before I get an error of bad disk. Meanwhile I have to reflash to original then to 2.1 to extract, then back to original and then last flash to 2.3 to get up in running. If anyone has any suggestions, I would appreciate it.