Bug #625 | There is no disk in the drive. Please insert a disk into drive \device\harddisk | ||
---|---|---|---|
Submitted: | 9 Jun 2003 14:04 | Modified: | 12 Jul 2003 15:46 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
Version: | mysql 4.0.13 | OS: | Windows (Windows 2003) |
Assigned to: | Mark Matthews | CPU Architecture: | Any |
[9 Jun 2003 14:04]
[ name withheld ]
[16 Jun 2003 3:14]
[ name withheld ]
Hello kind Sirs Still no word/news on this bug - my migration efforts are on hold due to this bug - please can you post a progress report.
[16 Jun 2003 6:50]
Mark Matthews
I've tried to reproduce this issue on Win2k3 and have not been able to (i.e, MySQL installs fine in this case). Is drive H: a network drive? Is drive H: failing (hardware-wise)? Do you have full access rights on drive H: in the folder you unzipped the installer to? Can you try using a local drive, preferably C:?
[16 Jun 2003 13:54]
[ name withheld ]
Drive H works - and i have tried moving to different disks - but still no joy. Not sure what to do next - might have to forget about the migration - reinstalling win2k3 would be way too painful.
[16 Jun 2003 14:07]
Mark Matthews
Would you be able to try out an 'installer-less' version of the server (i.e. just a .zip archive that you unzip to c:\)?
[17 Jun 2003 14:11]
[ name withheld ]
Yes I can try that - where do I get that? Would I just install mysql on a win2k machine and then copy the installed files into my win2k3 machine?
[17 Jun 2003 14:14]
Mark Matthews
Our web team is working to get an installer-less version of 4.0.13 posted to the downloads page. In the mean time, you could (as you propose) install it on Win2K and copy the files across to Win2k3...MySQL does not use the registry and does not install files into any system directories (during the install...you can create a 'my.ini' in the Windows directory after the install).
[17 Jun 2003 14:28]
[ name withheld ]
Ok I will try that and let you know tomorrow - how it went. Thank you for following up the bug and providing the install-less version. Long live MySQL - its a wonderful product - a great contribution to towards technology :) Keep up the good work.
[17 Jun 2003 14:47]
Mark Matthews
The 'installer-less' version of 4.0.13 is now posted to http://www.mysql.com/downloads/mysql-4.0.html
[18 Jun 2003 14:40]
[ name withheld ]
Ok people - after hours of sleepless nights in the shed, searching through newsgroups, search engines and the microsoft support sites - I found the problem. I installed the no-install version but got the same error message - outlined below was the cause: The computer was configured to use drive C: for the zip drive, D: for cdrom drive and the 2 hdd drives E: and F: When I ran the mysql setup program - (i now understand the error message - no thanks to microsoft) - for some reason the setup file was basically searching for drive C: (which had no zip disk inside) - I hope you understand things so far. Anyway to solve the problem - I went into disk manager and reassigned the zip drive to Z: and everything works now. Although the problem is solved, once again thank you to the guys at mysql, i am still not sure why this should happened. I hope this helps someone in the future. Gee I love computing - never a dull movement.
[24 Jun 2004 1:40]
Bill Karwin
Microsoft acknowledges this issue, in their knowledgebase article 330137. They recommend exactly the same solution, to use Drive Manager to reassign the drive letter for your Zip drive. Also, a similar error message occurs in various Microsoft operating systems if your PATH environment variable, or a program shortcut (or probably other cases) references a drive letter assigned to a removable media device, and there is no media in that drive. They recommend either (a) put media in that drive, or (b) remove the reference to the drive letter from your PATH or other instance. See Microsoft knowledgebase article 102418.