Using just "call" from subprocess starts a new standalone thread in the background running the named program – without any connection to it. That only makes sens in special cases and is not what a normal Windows user wants. The lib subprocess has a lot other goodies, more useful if you want to get any results back :)

As you said before: Some times ago subprocess replaced "popen" (popen returns a pipe to a started program running in a seperate thread in the best case, just like subprocess.call does). subprocess has splitted the complex popen command into several more easy to use parts.

In German, I could tell you much more and give you more precise answers. Nevertheless, I hope that what I have written makes sense.

---