To get by the impasse, I just put a data CD with a valid directory structure into the drive. Wubi was able to read it, and to determine that it contains nothing of interest to Ubuntu. Once Wubi verified that (a) there was a disk in the drive, and (b) it was not the disk it wanted, it started to automatically download the files it needed to go ahead with the installation.
There are options for fixing this issue. I personally don't care whether it ignores my empty drive(s) or interrogates me about my intention to put an install disk into one or more of them. The current implementation, which reports the issue but gives no guidance to the user regarding the next step, is a "sub-optimal" solution.
BTW, you can get rid of pyrun.exe if you get rid of a companion process with an unusual name such as py###.tmp.exe. If you are of a cautious nature, you might want to reboot after having done this.
I had the same issue with Win XP SP 3.
To get by the impasse, I just put a data CD with a valid directory structure into the drive. Wubi was able to read it, and to determine that it contains nothing of interest to Ubuntu. Once Wubi verified that (a) there was a disk in the drive, and (b) it was not the disk it wanted, it started to automatically download the files it needed to go ahead with the installation.
There are options for fixing this issue. I personally don't care whether it ignores my empty drive(s) or interrogates me about my intention to put an install disk into one or more of them. The current implementation, which reports the issue but gives no guidance to the user regarding the next step, is a "sub-optimal" solution.
BTW, you can get rid of pyrun.exe if you get rid of a companion process with an unusual name such as py###.tmp.exe. If you are of a cautious nature, you might want to reboot after having done this.