Print

[naizarak]

So I've been trying to update my 83850cV1 and ms28 drives with this new comp.  The BIOS detects both drives, but my operating systems don't.  I've tried on WinXP 32, using the newest version of JF, and an older version(1.6).  I've also tried both version on Win 7 64, using that x64bit driver in test mode.

Neither one can detect the drive.  The motherboard has an AMD 785G Chipset, and my friend with the same board has been able to flash his drives.  


One thing I've noticed is that booting into Windows with the drives in half-open status significantly slows down the computer.

All help will be appreciated.

This post has been edited by naizarak: Feb 5 2010, 07:29 AM

[Bukmop]

QUOTE

The BIOS detects both drives, but my operating systems don't.  

   Of course, they dont (IMG:style_emoticons/default/smile.gif) You've got Xbox drive but not PC drive.

QUOTE

significantly slows down the computer

   This fact is a chipset depended. With my nforce61 I've got the same problem. Thats why as for me - I perform reading/writing/erasing fw under MS-DOS. I use JF to construst CFW only. I suppose you'd better to do the same way.

[slayer902]

QUOTE(naizarak @ Feb 5 2010, 07:28 AM)

So I've been trying to update my 83850cV1 and ms28 drives with this new comp.  The BIOS detects both drives, but my operating systems don't.  I've tried on WinXP 32, using the newest version of JF, and an older version(1.6).  I've also tried both version on Win 7 64, using that x64bit driver in test mode.

Neither one can detect the drive.  The motherboard has an AMD 785G Chipset, and my friend with the same board has been able to flash his drives.  
One thing I've noticed is that booting into Windows with the drives in half-open status significantly slows down the computer.

All help will be appreciated.

windows shouldn't be able to detect the drive, but jungleflasher should.

[XstefanoX]

I had the same issue...

In my case I figured out that the the xbox drive was using the same interrupt as my lan controller and usb hub. The obvious solution in my case was to disable the nic and one usb hub in the bios. Most bioses have a setting to disable internal devices or at least assign irq's. Change the irq in the bios for the drive when it is attached, or disable some other device you do not use when flashing. I hope this could help you a little.

[royal88]

Assuming you're not missing something incredibly obvious like BIOS/RAID settings or not plugging something in correctly, I recommend removing your base motherboard Catalyst 785G AMD drivers, rebooting into Windows (you'll have all ? marks in Device Manager) then power up your drive.  That worked for me just recently.  After I confirmed everything magically worked I re-installed the latest drivers.

Oh, and the drive won't show as a drive letter in Windows so that's not a good indicator.