>>I think David pointed you in the right direction here. I see DOS and I start thinking cscript.exe (which runs in the console). It's hard to say what you should look for other than a significant drop in any one of the three resources monitored. If I were to hazard a SWAG, I'd be inclined to think System rather than User or GDI, but if any or all of these start dropping without being recovered after termination, you may have found the culprit.
>>
>>BTW, the application, c42pdf.exe, does close its DOS window, doesn't it?
>
>George,
>
>I am sorry to dumb, but which three resources are you talking about. I have been playing with counter logs under Performance Logs and Alerts in the MMC. I will try David's suggestion, but I would like to know why CreateProcss does not work. Is there a reason besides simplicity, why one would use WSH rather than CreateProcess or vice-versa?
>
>Thanks!

Tim,

First, I'm writing about Win98 from this end. It has a System Tool called Resource Meter. My new box with Win2K on it is sitting (un-connected) on the floor behind me. I probably won't be able to get it set up until tomorrow. The Resource Meter shows the percentage of User, System and GDI resources in use. I don't know if such an animal exists under Win2K.

Other than simplicity, I don't think so. There's much, however, to be said for simplicity. Less code to debug and possibly break in the future. Where the WSH can do the job I need done, I use it. When it can't, then I go to the API.