I am having trouble getting xp to recognize my 59dj in windows while in modeb per 2 wire trick.I am using a via 6421 card that I know works (flashed a ms25).If I have xb in modeb then start computer it won`t recognize,and if I plug it in while windows is loading or after it freezes windows. In device manager there will be a splat. ANd no splat if xb is not hooked up. Any help greatly appreciated ,thank you.

You can use Slax 2.1 with that PCI Sata card. It works just fine.

I`ve tried using slax2.1 with no luck ,that is why I did the 2 wire. It goes into modeb just fine. It`s that windows won`t recognize.Card worked great with ms25. but not hitachi ,it seems like some kind of compatibility issue. I`ve tried many diff boot sequences. I have a t6524 xp media center,amd64. the via 6421L should be in non raid as oem config (and it flashed a ms25 alot ). Any help appreciated .Thank you!

Look in the device manager. See if there is a yellow exclamation next to the sata card. The only way I was able to get my hitachi recognized was to do the modeb during the windows loading screen. So don't power the 360 until the windows loading screen.

Yes it does have the exclamation mark .And I did try your way .I read one of your other posts.And have already done that with no joy. Thanks

If you have your 360 on before your SATA card's BIOS checks on your computer during boot up. It sometimes doesn't work properly. Here is how I do it. Follow these steps.


1) Connect 360 Drive to SATA card.
2) Turn on PC
3) Wait till slax 2.1 starts loading and quickly turn on your 360
4) Once Slax is at the login screen hit Ctrl+Alt+Delete and take the slax disk out when you drive ejects.
5) Boot into windows and it should recognize it.

If you are still getting the exclamation mark. Go to device manager right click the controller and select update driver.

Thanks I tried 520 , 530 and 540. Still no joy. Niether slax2.1 or being recognized in windows with this card after many different boot sequences. Is this card just incompatible ? Shoud I find a different card ? It worked great with the ms25. appreciate the help any more ideas.

I have the same problem with my 59jd, is yours the June 2006 addition?


it freezes my computer some times and other times when i RAW Dump Firmware As the process just freezes or the pc just hangs using toolbox v3.0


anyone any idea?

The drive is in moedB for sure but freezes in windows

I too had troubles with a v59 and a vt6421L. I tried everything, including old, newer and the newest drivers. I tried initiating modeB in several different boot points and in windows. Nothing worked. I ended up buying a cheap silicon image chipset, put the drive in modeB and flashed it with the first boot. I am not too sure what the issue is with this drive, as i've done v40-47 and ms25/28 with that chipset. I spent hours on it and wish i would have bought another card right off the bat.

Caster.

My cipset is Nforce 4 though and it wont work with that either

1. Are You sure Your Card is setted To IDE ;
and not RAID
I flashed my 59JD also 2006 June with a NFORCE4 onboard SATA but it was also on RAID in BIOS, i think with the PCI card you can set it manually to RAID NOT ENABLE.

2.When you putted in ModeB with the Wiretrick , Be sure its in MODEB

If using the Xbox 360 to power the drive and using the
wire/resistor trick, your Xbox 360’s power LED should flash
rapidly
With all methods, it should take two presses of the eject button
to either open or close the DVD tray.
With all methods, when you eject the drive back in using the
eject button, it should auto-eject back open a second later.
Obviously, if the drive shows up in Windows, then it is in
ModeB.

3. WHen its in MODEB DONT reboot your xbox leave it on

To mccartfm: Check your BIOS settings

The card is in mode 0 (non-raid) . The drive is in modeb , however it is 1 click to eject ,2 to close and one to keep closed or it will auto eject. The drive is a june 06 . I`m about to give up and purchase a different card , any suggestions on a new card ?

I used a Sil 3112A chipset to flash the drive.

Caster.

RAID is DISABLED in my bios? This is correct ye?

thanks for reply

I got mine to work with a sil3112 card from ebay $15 shipped . I still couldn`t get slax to work, but after doing the wire trick it recognized and flashed with no problems . Thanks everybody for the help.

I've got a 59DJ drive and an NF4 based mobo. This DFI Venus mobo has a total of eight SATA headers. 4 Nvidia based ones and 4 Silicon 3112a based ones.

I connected the 59DJ to a 3112a, put Slax into the DVD drive on my PC (no, not the 59DJ) booted and had it in ModeB without any problems. When you get back into Windows you should eject the tray, otherwise you'll find your system hangs every now and then. I think I read somewhere that they tray has to be open in order for Windows to recognise it properly. Don't ask me why, it just worked with the tray open and I flashed it with Maximus-Garyopa_XTRM-HITACHI_v2_3_Stealth_Rev2 without any problems.

Windows sometimes freezes on some set ups if you have the hitachi hooked up to your sata. I think the issues that most people have with windows and flashing is the sata-windows compatability. If you eject the hitachi drive during the windows boot up screen that should fix the freezing problem, however. If it's hooked up to sata and it's still not working in windows I recommend buying a sata to usb. Put drive into modeb using slax and sata to your drive, then turn off the computer when it's in mode b. When the computer is off, unplug the sata cable and plug into your hitachi the usb to sata adapter. Turn on the computer(remember to eject slax) and then during the windows boot screen plug in the usb plug and quickly eject the hitachi. That method has worked every time for me. Like I said, the real issue is with sata and windows combined. Avoid that buy not using sata in windows period, buy a $20 sata to usb adapter. And and if you flash and there's a single error during the process but it says 100% at the end, reflash and reflash again until it goes through perfectly. However, redo the entire process when you want to run a restore.