Print

[TheSpecialist]

QUOTE(FiJ @ Jun 8 2007, 03:48 AM)

The answer is en emphatic YES!

Took it to work, tried the same setup on a different VIA embedded controller, worked like a charm first time!

Many thanks, TS, you're the man.

Ah, cool, thanks for reporting and glad it works now ! So now we know that some SATA cards just don't work, for example the sil3112 does NOT seem to work. Again, thanks for checking that out

[slapshot591]

I have a 160GB WD BEVS and I put the app on a disk, booted in to dos, dumped the file to the disk, flashed it, and confirmed it, but it tells me that sector 16 is different than the firmware and i hit Y then i hit Y for the undo file, and it tells me it's flashed, but when i confirm it, it doesn't say that it's flashed, but my computer recognizes it as a samsung drive. what am I doing wrong?

[TheSpecialist]

QUOTE(slapshot591 @ Jun 12 2007, 04:50 AM)

I have a 160GB WD BEVS and I put the app on a disk, booted in to dos, dumped the file to the disk, flashed it, and confirmed it, but it tells me that sector 16 is different than the firmware and i hit Y then i hit Y for the undo file, and it tells me it's flashed, but when i confirm it, it doesn't say that it's flashed, but my computer recognizes it as a samsung drive. what am I doing wrong?

You can't use hddss.bin from a Samsung. All the other brands/models are fine. BTW, are there samsung 120 gb's drive now in the wild ??

[Goldberg]

Hi,

I'm hoping the Specialist or someone else can help me out here with my 120gb HD (WD, BEVS LAT Drive).

I have plugged the HD into the Motherboard and booted into DOS. I have had to edit the hddhackr.com file as I have an Nvidia chipset on the motherboard. It recognises the drive fine then ask's me if I want to flash etc......

When I get to the next screen I get an Error Drive is busy message?? If I then try and run hddhackr.com again I get an error stating 'The EC Serial Sting not found'


Any ideas would be greatly appreciated...

Thanks,

Goldberg

PS Keep up the good work!

[TheSpecialist]

QUOTE(Goldberg @ Jun 14 2007, 12:18 PM)

When I get to the next screen I get an Error Drive is busy message?? If I then try and run hddhackr.com again I get an error stating 'The EC Serial Sting not found'

What SATA chipset are you using ?

[Goldberg]

Name   NVIDIA nForce4 Serial ATA Controller
Manufacturer   NVIDIA Corporation
Status   OK
PNP Device ID   PCI\VEN_10DE&DEV_0054&SUBSYS_289510F1&REV_A3\3&13C0B0C5&0&38
I/O Port   0x00001C40-0x00001C47
I/O Port   0x00001C34-0x00001C37
I/O Port   0x00001C38-0x00001C3F
I/O Port   0x00001C30-0x00001C33
I/O Port   0x00001C10-0x00001C1F
Memory Address   0xB0003000-0xB0003FFF
IRQ Channel   IRQ 20
Driver   c:\windows\system32\drivers\nvatabus.sys (5.10.2600.0552 built by: WinDDK, 91.38 KB (93,568 bytes), 18/08/2005 18:52)
Name   NVIDIA nForce4 Serial ATA Controller
Manufacturer   NVIDIA Corporation
Status   OK
PNP Device ID   PCI\VEN_10DE&DEV_0055&SUBSYS_289510F1&REV_A3\3&13C0B0C5&0&40
I/O Port   0x00001C58-0x00001C5F
I/O Port   0x00001C4C-0x00001C4F
I/O Port   0x00001C50-0x00001C57
I/O Port   0x00001C48-0x00001C4B
I/O Port   0x00001C20-0x00001C2F
Memory Address   0xB0004000-0xB0004FFF
IRQ Channel   IRQ 21
Driver   c:\windows\system32\drivers\nvatabus.sys (5.10.2600.0552 built by: WinDDK, 91.38 KB (93,568 bytes), 18/08/2005 18:52)

[HGvR]

Hi,
got a problem with a 120GB WD BEVS RST here.
Hddhackr and all goes well, but the drive does not format in the 360.
I tried to internalize it like in the linked thread in the beginning of this thread.
Question now, is my SATA connection inside the 360 faulty or is my drive damaged?

tia

[HGvR]

Forget it, the drive works very well back in the pc, formats and checks without any problems.
Has to by my beautifully self-made internalization.
 

Sorry for bothering!

[TheSpecialist]

@Goldberg: I really don't have any clue as to what could be wrong. Your SATA chipset should work. Some things you can try:
1. Delete or rename the autoexec.bat and config.sys from your boot floppy (they're not needed and might load some things that mess up the process, so just delete/rename them)
2. Try different SATA cable and/or different SATA connector on your mainboard.

But I don't think this is the problem. So the only thing I can advice you is to try it on another computer. Might be that your HDD is faulty though ... Check if it operates normally under windows.

[Skinleech]

QUOTE(HGvR @ Jun 14 2007, 04:57 PM)

Forget it, the drive works very well back in the pc, formats and checks without any problems.
Has to by my beautifully self-made internalization.
 

Sorry for bothering!

I have the same issue.  Is it a case that the 360 does not see the HDD under the dash, or just that it won't format?

[Goldberg]

QUOTE(TheSpecialist @ Jun 14 2007, 06:29 PM)

@Goldberg: I really don't have any clue as to what could be wrong. Your SATA chipset should work. Some things you can try:
1. Delete or rename the autoexec.bat and config.sys from your boot floppy (they're not needed and might load some things that mess up the process, so just delete/rename them)
2. Try different SATA cable and/or different SATA connector on your mainboard.

But I don't think this is the problem. So the only thing I can advice you is to try it on another computer. Might be that your HDD is faulty though ... Check if it operates normally under windows.

I'm going to try on my Laptop with a USB Floppy drive and the drive plugged into the laptop, all the oves at work are nraid...

Thanks anyway

[HGvR]

@Skinleech: It wouldn't format. It would start to, but after about 30-60 seconds go to "unformatted" again. Now I get E68 after getting E69 since I renewed the sata connection two times and checked and formatted the drive in the pc 2 times. It's only getting worse.
It's a WD1200BEVS-RST.
Don't get me wrong here, I'm connecting stuff for years now, and nothing like that ever happened before.

I don't think there's a bad solder, either, since the errors would be more consistent then. It would never have gotten to the point where I could at least see it in dash and TRY to format it.

It seems to get worse with everything I do with this drive in my PC or at all.
WD test util for DOS doesn't even find the drive.
WD test util for windows found the drive, but gave me a "cable error" on checking. For the same cable I had used to flash it several times, format once and with which I successfully flashed my MS25 several times.
I changed the cable, gone is the error. Drive shows ok, but only 9GB in size. WTF?
Formats fine though, in both WD format util (NTFS) and gparted live cd (ext3).

360 doesn't seem to like pre-formatted drives, plus the drive seems to be very sensible with its connectors: when the sata connector didn't fit 100%, it was error time as well.
Cut the connector sides, helped back then, brought me from E68 to dash with drive shown, but wouldn't format.

Seriously, with all due respect, but I'm not too damn stupid to connect a friggin hard drive. I guess the drive is somehow shot. Either on the inside or the connectors.
Just need to be sure somehow.
Any ideas how to put it to the test, anyone?

@zikronix: You mentioned in the beginning of the thread that your drive was broken, too.
How did you find out? Or rather "prove" it?

[Skinleech]

Thanks for the info - certainly sounds like you've got a case of a faulty drive, the errors seem to random for a solder issue as you say.

I'd started another thread, and it seems that power could be issue in mine - the drive certainly doesn't feel like any power is going through it, there's no indicartion od the heads spinning up at all.

Good luck to you in getting it sorted - mind and restore the drive before you try to return it for a refund/replacement...

[Goldberg]

All sorted now via laptop, cheers TS!

[TheSpecialist]

QUOTE(Goldberg @ Jun 15 2007, 09:28 AM)

All sorted now via laptop, cheers TS!

Good to hear that ! It's amazing how some SATA manufactures obviously don't follow specs when they design their chips. But then, who's using DOS nowadays... only a few hackers

Anyway, if there's a future release of the hddhackr, I'll include a list of SATA cards that might be problematic. Thanks for reporting !