No luck dumping my Hitachi firmware///Samsung works fine. Help?

[topho]

I can't get my Hitachi to detect in windows using the SLAX modeb force method. However, I am using a Nforce 4 mobo, and I don't think this has the Silicon Image controller on it. Is that why it's not working?

Are there other methods to dump my firmware.....could someone help me a little with PLSCSI? The PLSCSI -w command is not working for me, and thus I don't know what to "SET PLSCI = ?" to. Is there an updated version of PLSCSI that would detect my Hitachi and tell me the set number?

POST #1 of this thread. http://www.xboxhacker.net/index.php?option=com_smf&Itemid=33&topic=350.0 explains the process of modifying PLSCSI to correctly show the PLSCSCI -w command. I don't understand what to change in the source code to make it work however.......I don't follow. Could someone compile it or help me compile it? When I use the PLSCSCI -w command.....I just get a weird reply..that doesn't make any sense to me.

Other methods besides PLSCSI. I would rather work with what I've got than try my luck at a PCI SATA controller.

The Hitachi is being detected just fine in my bios.


I need that key, before I can flash my samsung(which is working just dandy with MTKFLASH-NF4.) Please please help me.

[topho]

I ended up using a different computer in my house, because I got anxious. This mobo was based on the Nforce 3. It worked fine with the Slax disc, and it showed up right away in windows. I used memdump to extract the key just fine.

However, for our other Nforce4 friends (many of us), could we try work on PLSCSCI for an alternate method? Or another alternate method and make it fairly easy to follow. I wasn't able to follow the current processes on this forum in relation to the PLSCSCI.

The three methods of firmware extraction on the HITACHI ( that I considered//were easiest/No expense) are MODEB force via Slax, then memdump, ground short into modeb then memdump, and the PLSCSCI. The PLSCSCI method might be a good method for those who don't have the correct SATA Controller and aren't too hot about opening their drive.

Could someone please confirm that the NFORCE4 won't work with Slax>Modeb>Detection in windows. Also, does someone know more about the PLSCSCI method of dumping....(source changes to allow PLSCSCI -w and more about SET PLSCSCI = ?" Thx

[Mjrweed]

My system freezes while booting winxp when in mode_b. (Nforce4 Onboard s-ata) Grounded pin9 to get into mode_b.

[topho]

I've heard of other people with the same exact problem, Weed. Mine doesn't freeze.....it just doesn't work at all, even though it is detected in bios, the Slax CD and modeb doesn't help windows detect it.

[dusan75]

I have Asus P4P800 motherboard with Intel 82801 Sata chipset.  It works fine with Samsung, but when I connected the Hitachi and send to modeb with slax method, windows is freezed when booting... So, the "windows hang up with Hitachi" is not only nforce chipset problem! I am waiting for 15-20 minutes and the windows is booting up, but very very slow. I pushed the windows button and start command prompt, and i can use memdump and succesfully dumped my hitachi. It takes cc. 30 minutes... not too good sollution.