topic Re: 680i help…" error connecting to drive" in Archive

680i help…" error connecting to drive"

idata — Tue, 22 Dec 2009 19:35:33 GMT

Hi,

I've just installed the new toolbox and hit the latest roadblock. Turns out my 680i motherboard identifies all SATA drives as SCSI, which was pretty common for older motherboard BIOS. It never made any difference to operation or performance until now…the Toolbox will not work with a hard drive identified as SCSI. The Toolbox recognizes the different drives and gives me different choices for the SSD vs. the rotary drives, but all functions are grayed-out.

So I can't use TRIM because the 680i is not AHCI compatible, and I can't use Toolbox to maintain the SSD because it hits a SCSI flag and grays-out (even though it does recognize the SSD).

Has anybody found a way to resolve this? I've looked through pages of Google links and tech support forums and found the issue talked about a lot but not a resolution. Typically the answer is that everyone lives with the SCSI-misidentification because it never made any difference whether Windows declared the drive SATA or SCSI. Until now.

Is anyone else's 680i working with the Toolbox?

Thanks

Re: 680i help…" error connecting to drive"

idata — Tue, 22 Dec 2009 21:15:19 GMT

i got the same problem with nforce 780i, i hope someone can help us. I can't use trim and optimizer tools. I can't believe that intel has here no solution!

Re: 680i help…" error connecting to drive"

idata — Wed, 23 Dec 2009 07:41:56 GMT

I ran into the same problem with my Asus nForce 650. There was another response from BorderShot with the solution. Here it is:

Alright, I got this to work by changing the driver from the "NVIDIA nForce Serial ATA Controller" to the generic "Standard Dual Channel PCI IDE Controller". In Vista, Control Panel --> System --> Device Manager, IDE ATA/ATAPI Controllers, select "NVIDIA nForce Serial ATA Controller", right click, Properties, Driver, Update Driver, Browse My Computer, Let me pick from a list, and then select the "Standard Dual Channel PCI IDE Controller". After reboot, I was able to use the SSD Toolbox.

I didnt have the Nvidia nForce serial ata controller driver so i just decided to update the standard duel pci ide controller and rebooted anyways BUT it did NOT help at all. SO I went to nvidia's site to download the lastest nForce driver which did install the nforce serial controller then I followed BorderShot's instruction and it worked like a charm! I am now able to see and TRIM the drive.

Let me know if you have any questions.

Re: 680i help…" error connecting to drive"

idata — Wed, 23 Dec 2009 10:21:26 GMT

Thank you for your feedback. I did the same, but still have the problem. I think the problem is, that my Devices on Win7 are as SCSI Devices declared and SCIS devices are not supported by Intel. Could you look at your Devices? Are they as SCSI delcared?

Re: 680i help…" error connecting to drive"

idata — Wed, 23 Dec 2009 15:58:13 GMT

i installed nforce driver, then i replaced it with Standard Dual Channel PCI IDE Controller, and now it works. Thanks for your help Palo127.

Re: 680i help…" error connecting to drive"

idata — Wed, 23 Dec 2009 17:36:42 GMT

Excellent and thank you Palo127. I will try it when I get back to my computer.

So I replace the Microsoft PCI IDE Controller driver by installing the latest nforce driver which installs the nforce serial driver. Then I replace the new nforce driver with the original Microsoft PCI IDE Controller driver and the SCSI designation will go away? LoL. No wonder I didn't stumble on a solution.

Re: 680i help…" error connecting to drive"

idata — Thu, 24 Dec 2009 07:36:01 GMT

It worked great. Thank you polo127.

Re: 680i help…" error connecting to drive"

idata — Sat, 26 Dec 2009 15:01:56 GMT

You are the man! I had same problem in Windows 7 (64 bit) and my EVGA 680i motherboard and your solutiuon worked like a charm. I would also add that when looking to replace the "NVIDIA nForce Serial ATA Controller", in all likelyhood, you may have more than one installed. Find out which one controls the Intel SSD (look under port 0 or port 1 of each nForce SATA Controllers) and only change the controller that controls your Intel SSD. Then if you have problems with other drives, you may want to switch them all. I only had to change one of the four "NVIDIA nForce Serial ATA Controllers" to the generic "Standard Dual Channel PCI IDE Controller" Tks again Polo127

Re: 680i help…" error connecting to drive"

idata — Sun, 27 Dec 2009 02:07:39 GMT

No problems. Im just glad it works for u guys too. Thx for the extra tip

Re: 680i help…" error connecting to drive"

idata — Thu, 31 Dec 2009 22:08:11 GMT

Just wanted to add my thanks to Polo127, your soloution worked perfectly.

Re: 680i help…" error connecting to drive"

idata — Wed, 06 Jan 2010 22:48:03 GMT

I want to add another "attaboy"! This worked for me, although my SSD is a Gen 1 so the trim tool isn't applicable to me.

Doesn't seem to matter - my drive is fast as all get out, and seems to be staying that way even after several months use as the primary drive in a Win7 desktop.

Best wishes/jim

Re: 680i help…" error connecting to drive"

idata — Thu, 07 Jan 2010 12:50:02 GMT

Hiya !

Same scsi-sata problem. I hope replacing NVDIA drivers may work. I need to know if replace driver can affect the functionality of a second HD with Windows XP installed. Can i boot again from XP or can i have some problem with new drivers ?

Thanks in advance

Regards

Re: 680i help…" error connecting to drive"

idata — Fri, 08 Jan 2010 04:56:07 GMT

I am having the same problem getting an "error connecting to drive" when I run Toolbox. I have an ASUS Striker Extreme with the 680i chipset. When I go to nvidia's website and look for an nforce driver for the 680i, there is no 64-bit, Windows 7 driver available. The 64-bit Vista driver is not allowed to load by Windows 7. How do you get around that?

Re: 680i help…" error connecting to drive"

idata — Fri, 08 Jan 2010 05:25:09 GMT

Hi Avedis,

I'm looking at Nvidia's website right now and it looks like the 680 windows 7 64bit's search would return you back to the search page. Have you tried the 680i LT SLI? Looks like you could download that. It does say Win 7 64 version 15.51.

Re: 680i help…" error connecting to drive"

idata — Fri, 08 Jan 2010 06:34:02 GMT

Polo127, please stick with this thread while I check out your recommendation. I've got to find a way to implement TRIM with a 680i chipset.

Re: 680i help…" error connecting to drive"

idata — Fri, 08 Jan 2010 06:49:52 GMT

POLO!!!!!! YOU ARE A GOD!!!!

I downloaded the nforce driver you recommended, did the IDE Controller swap as prescribed and the Toolbox runs!!!! I did it for only one of the three drives I have and hit the SSD on the first try. I owe you a beer or twelve!!!!

Thanks so much for the help!

Re: 680i help…" error connecting to drive"

idata — Fri, 08 Jan 2010 19:30:36 GMT

Cooool. So the 680i LT SLi worked for you?

Hey I was wondering how long it takes for everyone's trim to complete? Mine only takes like 3 seconds. Is this normal? The instruction on the toolbox says it might take many minutes. I filled up half the space on my 80Gb.

Thanks

Re: 680i help…" error connecting to drive"

idata — Fri, 08 Jan 2010 19:38:20 GMT

Yes, the 680i LT SLi 64-bit driver worked fine.

When I run TRIM on my 80 Gb SSD, it takes a second or two but I only have Windows 7 and a few other applications on it as it is new and I haven't migrated everything over to it that I need to yet.

Thanks again polo, you saved my bacon on this!

Re: 680i help…" error connecting to drive"

idata — Sat, 13 Feb 2010 07:59:33 GMT

Anyone else having stuttering problems once they performed this fix? I got the SSD toolbox to recognize my X-25V 40gb, but switching to the generic driver causes stuttering, which is very noticeable when playing music, but seems to affect just about program/operation i run.

Re: 680i help…" error connecting to drive"

idata — Sat, 13 Feb 2010 17:29:56 GMT

I wish I could help xeren. The fix solved my problem with the SSD Toolbox and I haven't had any stuttering problems with the generic driver. Hopefully polo may have a suggestion for you to try. Good luck!