After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 627792 - Message on start: "There is no disk in the drive. Please insert a disk into drive"
Message on start: "There is no disk in the drive. Please insert a disk into d...
Status: RESOLVED OBSOLETE
Product: bluefish
Classification: Other
Component: application
2.2.4
Other Windows
: Normal normal
: 2.2.4
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
: 610698 632561 654166 701779 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-08-24 03:26 UTC by Raul Carrillo Garrido aka metsuke
Modified: 2020-04-24 15:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Raul Carrillo Garrido aka metsuke 2010-08-24 03:26:06 UTC
Each time that starts editor a "No hay disco en la unidad. Inserte un disco en la unidad \Device\Harddisk1\DR1" appears. One for each file loaded on editor. I'm working with big proyects so that issue itself makes me desperate.

How can i solve that?
Comment 1 Jim Hayward 2010-08-26 13:02:56 UTC
Are the files you are trying to load on an external hard drive? Does this happen when loading a project or when opening the files one at a time?
Comment 2 Raul Carrillo Garrido aka metsuke 2010-08-26 17:39:25 UTC
Happens when open a single file both on opening directly the file from explorer, and when using open file dialog. I'm not using the "project" feature.

The files are on C: Drive , but the message also appears when using a external drive.

If you need me to make any further testing or revision please let me kwow.

I'm using the program on Windows 7 ... maybe that could be an important detail.

Raul
Comment 3 Fabio Durán Verdugo 2010-11-14 03:10:16 UTC
any news for this report?
Comment 4 Olivier Sessink 2010-11-14 13:40:43 UTC
I've heard this from more users, it happens when the filebrowser in the left pane fills it's popup with possible drive letters. No clue yet how to avoid this.
Comment 5 Daniel Leidert 2010-11-21 19:05:00 UTC
*** Bug 632561 has been marked as a duplicate of this bug. ***
Comment 6 Daniel Leidert 2010-11-21 19:05:18 UTC
*** Bug 610698 has been marked as a duplicate of this bug. ***
Comment 7 Larry Weldon 2011-06-15 18:49:57 UTC
Have the same problem with Windows 7 - does not happen with Vista/XP
Comment 8 fun-stuff 2012-08-11 21:41:14 UTC
Bug still exists with Bluefish 2.23 on Windows 7. When opening a file from Windows Explorer I have to click twice on one of the three buttons ("Cancel"/"Try again"/"Continue") to start Bluefish. Very annoying!
Please fix this. Bluefish is such a good editor!
Comment 9 Olivier Sessink 2012-08-17 13:25:15 UTC
*** Bug 654166 has been marked as a duplicate of this bug. ***
Comment 10 Erich 2013-05-02 18:44:43 UTC
Bug stills exist with Bluefish 2.24 on Windows 8. You don't need to open a file using the Windows Explorer. The error message also is shown when starting bluefish. Bluefish asks for a drive letter that is not in use, but was for a removable hard disk.

There is some type of bluefish memory that even survives uninstalls and new installs.
Comment 11 Daniel Leidert 2013-06-26 16:38:03 UTC
*** Bug 701779 has been marked as a duplicate of this bug. ***
Comment 12 Melvin Stober 2013-08-24 20:24:29 UTC
It's hard to believe this error still exists after 3 fucking years.  When are you guys going to fix it???
Comment 13 Dennis 2013-09-18 18:24:11 UTC
I think I've figured out the culprit...but first, <rant>I find this a bit ridiculous as a Quality Assurance Analyst that this bug has been open for 3 years. I would choose another lesser editor over this application just because of this kind of bug. The user experience is bad right out of the gate. Not to sound insulting, because clearly bluefish has a large user following for a reason, but as an open source project that promotes itself as a "powerful editor targeted towards programmers and webdevelopers", this kind of user experience doesn't reflect that at all. How much productivity would be lost (think about the arthritis caused by this), if every web developer had to click three times every time they opened their primary html editor.</rant>

Cause:
I installed 2.2.4 on my wife's Windows 7 64 bit laptop and saw the error immediately after opening bluefish. I decided to see if the issue happened on my Windows 7 32 bit desktop, it didn't. Then I thought, what could this "\Device\Harddisk1\DR1" be referring to if there is only one hard drive in the laptop. That's when it hit me, the multi-card reader. I tried to disable it in the bios however there was no option, so I disabled it in the Device Manager and bingo, no more error upon launching bluefish. So now that we know how to repeat the issue and we have a cause, someone please save bluefish from this ugly bug and terrible user experience!!! I would do it myself if I knew how to write C code effectively.
Comment 14 Olivier Sessink 2013-09-18 18:59:56 UTC
your rant is completely true. However, we have very little windows developers. This causes windows specific bugs to remain unsolved for a long time. I'm afraid that this will only improve if more developers join that are interested in improving the windows port of Bluefish.

Thanks for finding what causes the issue. I have the feeling that the error is related to the code that loads an icon for each drive (but I don't know for sure since I don't have any windows machine).
Comment 15 George W 2013-11-01 13:10:55 UTC
I found this as a workaround:

http://www.techspot.com/community/topics/usb-drive-or-flash-problems-how-to-cleanup-and-remove-old-usb-storage-drivers.145884/#post-875300

After cleaning up, you must reboot for the changes to take effect.
Comment 16 jvanslyke 2014-01-15 18:08:11 UTC
I have the same problem. Windows XP with a full install. I tried cleaning up the old storage drivers and it didn't change anything.
Comment 17 André Klapper 2020-04-24 15:18:53 UTC
Hi, if this ticket is still valid in a recent version of Bluefish, then please report this under https://sourceforge.net/p/bluefish/tickets/ as GNOME Bugzilla is not used anymore by the Bluefish developers - thanks a lot!