Installing Firefox1.5 RC 3 gives "There is no disk in the drive." error when selecting install drive




13 years ago
11 years ago


(Reporter: Nick_Jenkins, Unassigned)


1.5.0.x Branch
Windows 2000

Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Just installed Firefox 1.5rc3.

When doing a custom install, and selecting the drive and folder into which to install, firefox generates this error (from a ctrl-c on the error dialog box to copy it's exact contents):
setup.exe - No Disk
There is no disk in the drive. Please insert a disk into drive \Device\Harddisk3\DR29. 
Cancel   Try Again   Continue   

Clicking "try again" gives the same error. Clicking "Cancel" goes to the next drive. Clicking continue goes to the next drive (i.e. behaves same as "Cancel").

There are 4 card-readers on this machine (SD/MMC, MD, SMC, and MS), and the error is generated for all 4 disks, and only the device that has the error changes (e.g. to "\Device\Harddisk5\DR31"). Therefore I have to assume this error relates to the card-reader disks (which are becoming increasingly common). The error is generated by scrolling up and scrolling up and down the list of available drives under "My computer". At no point was one of these 4 card-reader drives selected - simply having them appear in the list of disks was enough.

Reproducible: Always

Steps to Reproduce:
1. Install Firefox1.5 Rc 3 on a machine with card-reader disks.
2. Custom install
3. Scroll up and down list of available drives (No need to select any disks).

Actual Results:  
No error unless drive is selected.

Expected Results:  
Error, even though drive is not selected.

Before you try and dupe this (and the dupe would probably be bug 153377), note that bug 153377 has already been marked as FIXED around April 2005, and this is from November 2005, seven months _after_ that bug was fixed. (i.e. if it you think it is a dupe of a bug fixed seven months ago, then why is it still happening?)
Reporter, could you please confirm with a latest 1.8.1 branch nightly? Thanks.
Version: unspecified → 1.5.0.x Branch
-> no feedback/reply for the question if this is reproduce able on a current
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.