WSINIT.DLL Process Stays When Studio Opens

Keywords: 	 WSINIT.DLL Process Stays When Studio Opens

---

Question:

I've never seen this occur when I worked on NT, but with XP, when I open Winbatch Studop, I get a WBT Dialog Box/Process that remains up for ProgFiles\WinBatch\WSINIT.DLL. Doesn't seem to ever go away.

Work occasionally on Win2K and I _think_ I had the same behavior there.

Usually I kill the process, assuming that its never going to complete.

Is this a known issue, or does this have to stay up while Studio is open and when running scripts? I'm using the latest version of WB+Compiler 2002.

Also parts of Studio and WB in general seem a bit slower on XP. Its not a difference on XP vs. NT on the same box, my new system is about 4x as fast as my previous. The behavior is intermitent, as if WB seems confused... Example, things as simple as text entry or a File Open/Save dialog seem strange. WB is the only app where I find this behavior..

Any known issues or suggestions? Have tried reinstalling for the sake of it, but...

Answer:

When Winbatch Studio first gets installed, there is some initialization code that runs. WSINIT.DLL is simply waiting for you to close Winbatch Studio to complete the required registry initialization.

If you kill it, it never completes and thus tries again the next time you start WinBatch studio.

Open WinBatch Studio. Close WinBatch Studio. Then it ought to go away.

---

Article ID:   W15352