As annoying as it is, Windows users want to run things like this for convenience sake, so I wound up writing one. What I did was write the module so it created an object and just left it lying around. When the program exited, and all of the conditions were right (Win32, run from Explorer, etc...) it caused a pause to happen during destruction. That way I could have multiple exit points from the program and not need an explicit pause().