LabVIEW
"Please insert a disk into drive D"
@hammer3 wrote:
See attached screenshot. This just started happening when trying to load a main vi. NO idea why it's looking for D drive. Ifound if I click on Cancel and/or Continue often enough I can get past it. Doesn't pop up on every computer accessing this file though. Only one. What causes this, and how can I make it go away?
I'd think you'd have to insert a disk into D. 😉
Seriously though, look at the other message box. It is trying to load a file that was on disk D. Is there a disk D on this computer?
[edit]
There is obviously a disk D on this computer - it is assigned to a CD-ROM/other removable disc, where on the original PC, disk D was a partition or network drive.
Could it be that you use network disks mapped in My Computer, and that the file tries to acces a file that usually is located in D:\ (Network Shared Drive) and that your computer has that disk mapped with a different letter than D?
@hammer3 wrote:
Inserting a disk into D SHOULDN'T BE NECESSARY because the file resides on our network along with all the other Labview vis, of which this is one of hundreds. OTHER computers can access this vi without this message appearing. I should not have to "insert a disk into D" to read a file that resides on the network. Any other ideas?
Only what EvenDeejay and I have suggested. It really seems that "D:" was a partition (or network drive, in your case) on the PC where it was originally developed, while on your particular computer, "D:" is occupied by a CD-ROM.
@hammer3 wrote:
None of your suggestions is applicable here, but thank you for your inputs.
It is painfully apparent that it is trying to load something from the 😧 drive, but you are saying that your CD-ROM ins't at D:? I have to miagine that somewhere along the line, that file in the jpg got linked to something on somebody's 😧 drive. Somebody who apperently does not have his/her computer set up the same as the one you are using.
Truth be told, this is an operating system error, not a LabVIEW one. Please see this micorsoft bulletin for more info. it's not the exact same thing, because it's not the exact same drive it is complaining about, but as you can see, it's caused by a drive mapping issue.
