Execute pyInstall build exe file under windows, it show "No Disk, There is no disk in the drive. Please insert a disk into drive \Device\Harddisk3\DR3" [cancel][Try Again][Continue]

[alarmz@…]

[step to reproduce]

1. I have 3 hard disks driver.
   
2. I copy pyInstaller1.5 to Disk2 rather than Disk0
   
3. execute python Makespec.py -D F:\Myprogram\demo.py
   
4. execute python Build.py ..\demo\demo.spec
   
5. pyInstaller will make a exe file for me
   
6. I copy that file to client machine, and client machine have USB card reader,
   

it have Disk2 already mount but no memory card inside.

7. When I execute the demo.exe in the client machine, it will show
   

fallow message "No Disk, There is no disk in the drive.
Please insert a disk into drive \Device\Harddisk3\DR3" [cancel][Try Again][Continue] under windows 2008,
and show "No Disk, Exception Processing Message" [cancel][TryAgain?][Continue] under windows XP sp3

[What happened instead]

Execute binary program created by pyInstaller1.5 or trunk version under windows,
will popup error message
"No Disk, There is no disk in the drive. Please insert a disk into drive \Device\Harddisk3\DR3" [cancel][Try Again][Continue]

[What you expect to happen]
When copy pyInstaller program into Disk0 and rebuild the binary file,
the error message just gone. this problem cost me a lot of time,
hop pyInstaller develop team can take a look.

[rishisharma]

Patch for winmain.c to disable Windows error messages.

[rishisharma]

Hi PyInstaller? team.

I believe I solved this issue for 1.5 by disabling Windows errors. I've attached the patch to be compliant with the GPL here.

Here is the URL that explains the context of shutting these off:

​http://msdn.microsoft.com/en-us/library/ms680621(VS100).aspx

[matysek]

This bug report seems somehow chaotic to me:

• There are steps how to reproduce but no code example.
• I don't know why the message "No Disk, There is no disk in the drive." is showed with the created executable

Could you provide more details?

Could you try development version?

[rishisharma]

FWIW, we could not reproduce this with the 2.0 build. The issue seems to only affect our usage of 1.5.

The way we went about reproducing this is notoriously difficult.

1. User would need to have a USB stick plugged in.
2. User at some point would remove the USB stick
3. User would then start the application

This only occurred with some specific hardware for us. I'm unsure as to why Windows is looking at a now defunct location. However it does. So the patch I submitted really only fixes the bootloader to ignore Windows messages in general.

I'm unsure if it affects HEAD, but I would expect not. If anything I would highly suggest you patch this into 1.5 and release new bootloaders for that version.

The patch itself is fairly benign, so unsure if you wish to include it in HEAD anyhow.

[matysek]

Could you try the HEAS if possible?

I'm not sure if it's the right think to ignore windows messages.