C0deBreaker

@Kelsenellenelvian The company I work for researched your app to make sure that it did not violate any copyrights or permissions by using it in a corporate environment and have been using it for approx. a year. Now, you have decided to charge for the application (which is understandable) but offer no support outside of the forums which I spent most of today searching to get an answer to my question. Additionally, you do not explain or justify your sudden licensing strategy or make any effort to answer my post - you took one minute to paste a generic link to your standard message. This does not give me the impression that your support structure would be any better. I have also used this at home and recommended it to several friends. Rest assured, that will no longer continue to be the case. For those of us who have worked with WPI for years and did what we could (within our means) to support this excellent application, the "answer" to my forum post is quite simply a slap in the face. I wish you continued success but it will not be due to any effort on my part.

I'm still looking through the forums but I'm having the exact same issue and I did put START /WAIT at the beginning of all my application .cmd install files. The WPI installer runs all the .cmd files one after the other without pausing between each one and closes while apps are still beating each other up for msiexec rights..... Has anyone else who has run into this problem found a solution? I am trying to standardize the WPI installer for mulitple client sites and using .cmd files so I don't have to keep updating the WPI - I can just change the name of the .exe in the .cmd file. Thanks to everyone in advance for your help!