\Device\Harddisk3\DR3 Error

jumanji said:

TVeblen said:

That is considered bad "netiquette". A forum or newsgroup thread should proceed like a conversation. Editing past posts changes the conversation and makes the following posters look like fools.
It is always important to read the entire thread.
The only exception is when a thread goes off on some tangent. Like this one.

Exactly. I have the same notions. It was only recently that I jumped on an OP or poster who made drastic changes to his earlier post, that made whatever I wrote subsequently completely out of context and wayward that any one who read the thread would consider me an absolute idiot ( and how SevenForums could have given a medal for such an absolute idiot. ). I am not. Incidentally it was the first time I lost my cool and used a . :)

I am a member of another Indian Forum which has strict standards on written English ( no slang, no net language or blabber, no mention of hacking and copying etc., etc.,) and no editing beyond 20 minutes of posting. If the poster has anything to modify beyond 20 minutes, he has to do it only on a new post in that thread.

And I have been seriously considering suggesting this to the Admin. I think it is time for Admin to take note of this.

I disagree with cutting off editing of posts after a given time limit. I have seen many instances where later edits, when done well, were very helpful. There are ways to make edits without making subsequent posts look foolish, e.g. a PS. in the post which simply states that there is a correction in a later post with a time-stamp to show when the edit was made.

Just in case this helps anyone in the future who is searching for a solution to the "There is no Disk in the Drive. Please insert a disk into the drive \Device\Harddisk3\DR3" error message -

I encountered this today after installing and launching a Flashdrive Speed Testing utility, called "SpeedOut".
The installation doesn't require a restart, and gives the option to open the app on the final page of the install.

When launched, it automatically scans USB ports and this dreaded error message came up. It's pretty persistent,
as well, requiring a half dozen attempts to cancel or close the message window before it finally closes, at which point the app finally appears. As aggravating as it is, and as difficult as it is to close, it pretty much makes one not want to leave the app on the computer.

After quite a bit of searching, this forum was the only place I came across that explained the DR3 drive was listed in Drive Manager as Disk02. That disk, however, was the Flash Drive I was desiring to use the utility to determine it's speed on. It also was not in conflict with any other drive, and changing the drive letter did not resolve the problem either.

I have run into applications in the past that did not instruct the user to reboot their machines, despite a reboot actually being necessary to register new DLL's properly, and to update shared DLL's before the application would actually work properly. So, it occurred to me that this may be one of those apps, and I recalled a saying I used to say a lot years ago when I was a Network Administrator "a good reboot never hurt anything", as it just clears out the cache, releases the memory, and refreshes everything and gives a machine a chance to sort itself out, saving changes to the registry on the way down, and starting everything back up in it's proper order on the way back up again.

I"ll be dipped if that didn't fix it right up. The app opened right up and functioned properly with no error message appearing again.

So, if anyone is getting this message after an application is freshly installed when they try to launch it, try rebooting the machine, let it release and refresh everything and sort itself out, and see if it doesn't solve your problem as well, as it did for me today.

Cheers...! ;-)

Always sound advice.