RT: Remote desktop says "can't find a suitable device for drive C"

[sls__]

Hello,

there is a french post on exactly the same topic, but I can't apply the solution given there.

My problem is the following: I have a remote desktop prepared to work as RT target. It has been checked for compatibility, the hard drive has been formatted in FAT32 format, it has been found by my host and has been assigned a static ip address. I have installed the software I need ( LabView 9.0 RT) using MAX. Now, when I try to boot it with the option "boot using software installed into the hard drive", all I get is the message

"Can't find a suitable device for drive C"

I have reseted the BIOS, have tried formatting the hard drive in the other format, uninstalled and reinstalled the software, tried to start the target pc without the usb stick, but nothing seems to work.

Do you have any ideas about what is going wrong?

Thank you,

Samuel

[dan_u · Accepted solution]

Did you try to change the BIOS settings for the hard drive controller?

There might be different modes available.

See the Hard Drive section of this document: http://zone.ni.com/devzone/cda/tut/p/id/8239?OpenDocument

[sls__]

Thank you for the link.

The BIOS doesn't let me change anything about the drive controllers... I'm not familiar with hard drives, so I will read further and see if I can get this solved.

[sls__]

Perhaps one question:

In the document you gave me it says that SATA is only supported in AHCI, not in IDE. My drive is in IDE, is there a way of changing it to AHCI?

[dan_u]

So you've got a IDE (and not SATA) hard drive? That should be supported anyway.

That would only confirm my experience... it's hard to find hardware compatible with LV RT. Before buying you cannot know if it's compatible. Once you have it the evaluation tool might tell you it's supported but still it might not work. I tried several motherboards in the last years, most of them did not work.

Your best bet might be to use relatively old hardware.

[sls__]

Oops, that was confusing, sorry. It was indeed a SATA drive, but my BIOS was telling me that it was native IDE (?)

Anyhow, I found the way to change the driver to AHCI, just as you suggested. The option was in a part of the BIOS I wasn't expecting to find.  Now it works! Thank you!

[dan_u]

Great, glad to hear it works!